imported_Ohmz
11-04-2003, 09:20 AM
First, let me apologize for the length of this post. I want to include enough detail to describe the problem accurately.
The problem is that the server refuses to run as a service for Windows 2000. I use FireDaemon to run it as a service the same way I do any other Q3 engine game - the others work fine. However, with CoD, it starts the process (I can see it from the task manager process list), but creates a file named __codmp and never fully starts up the server. I can tell it's not fully started because the process only takes up 3mb of RAM and the UDP port does not show up in a netstat -an, meaning it never bound the server to the port. The game will start up correctly if I run it manually using the same batch file that FireDaemon calls to run the gameserver. So it's something specific to CoD running as a background process.
Interestingly, this same setup works fine for me under Windows XP, using FireDaemon. Both the XP system and the Win2k Server have DirectX 9.0b. The only thing I can think of that is different between the two systems is that on the XP system I installed the game straight from the CDs, whereas on the Win2k Server the game was never installed - just copied via FTP. If I must install the game locally to make it work, I will pay to have it done (the server is 1500 miles away from me), but my gut feeling is that doing that will make no difference.
This problem is definitely CoD specific, because I can run any other game in this manner and it works fine - Q3, MoH, Halo, etc.
Anyone have any ideas? I will try contacting Activision as well, but I'm not too hopeful there. I'm wondering if they may have a special cvar or command line parameter that will fix this issue. Otherwise I may be stuck waiting for them to release a Windows dedicated server (if they even plan to). They must be doing something strange during the server initialization. I wouldn't doubt it since I've already noticed another peculiar problem where the server fails to run all of your config commands if you name your config file server.cfg. Any other filename appears to work fine.
-Ohmz
The problem is that the server refuses to run as a service for Windows 2000. I use FireDaemon to run it as a service the same way I do any other Q3 engine game - the others work fine. However, with CoD, it starts the process (I can see it from the task manager process list), but creates a file named __codmp and never fully starts up the server. I can tell it's not fully started because the process only takes up 3mb of RAM and the UDP port does not show up in a netstat -an, meaning it never bound the server to the port. The game will start up correctly if I run it manually using the same batch file that FireDaemon calls to run the gameserver. So it's something specific to CoD running as a background process.
Interestingly, this same setup works fine for me under Windows XP, using FireDaemon. Both the XP system and the Win2k Server have DirectX 9.0b. The only thing I can think of that is different between the two systems is that on the XP system I installed the game straight from the CDs, whereas on the Win2k Server the game was never installed - just copied via FTP. If I must install the game locally to make it work, I will pay to have it done (the server is 1500 miles away from me), but my gut feeling is that doing that will make no difference.
This problem is definitely CoD specific, because I can run any other game in this manner and it works fine - Q3, MoH, Halo, etc.
Anyone have any ideas? I will try contacting Activision as well, but I'm not too hopeful there. I'm wondering if they may have a special cvar or command line parameter that will fix this issue. Otherwise I may be stuck waiting for them to release a Windows dedicated server (if they even plan to). They must be doing something strange during the server initialization. I wouldn't doubt it since I've already noticed another peculiar problem where the server fails to run all of your config commands if you name your config file server.cfg. Any other filename appears to work fine.
-Ohmz