Regarding the error message, check
this page.
I start my server from the command line, e.g.:
C:\Program Files (x86)\Steam>steam.exe -silent -login MySteamLogin MySteamPassword -applaunch 63950 -server
I'll probably use FireDaemon to manage this automatically, once I've worked out how to automate the first steps (f settings.cmd and loading the first mission).
Regarding mission cycling, you could use multiple cmd files, for example:
Start with f mission1.cmd, which will stop any existing battle and load MyFirstMission.mis
Code:
battle stop
missLoad missions/Multi/Dogfight/MyFirstMission.mis
timeout 180.00 chat Welcome to My Server ALL
timeout 340.00 chat Maps rotate Every 4 hours ALL
timeout 14200.000 chat Map will change in 3 minutes ALL
timeout 14260.000 chat Map will change in 2 minutes ALL
timeout 14320.000 chat Map will change in 1 minutes ALL
timeout 14400.000 f mission2.cmd
battle start
After 4 hours the above mission will end and call mission2.cmd, for example:
Code:
battle stop
missLoad missions/Multi/Dogfight/MySecondMission.mis
timeout 180.00 chat Welcome to My Server ALL
timeout 340.00 chat Maps rotate Every 4 hours ALL
timeout 14200.000 chat Map will change in 3 minutes ALL
timeout 14260.000 chat Map will change in 2 minutes ALL
timeout 14320.000 chat Map will change in 1 minutes ALL
timeout 14400.000 f mission1.cmd
battle start
After 4 hours MySecondMission will end and the first file will be called again. Rinse and repeat, or add more .cmd files as required.
Hope that helps.
Regards
epoch