PDA

View Full Version : Patching a windows dedicated server ?


Loop
01-30-2004, 04:06 PM
Hello,
my server is running Win2K/SP4, the patch exe says "no valid installAtion", i am not in the mood to upload my patched installation..
Help urgently needed..

Thx,

Loop

imported_ian
01-30-2004, 05:50 PM
Do you have a real install of CoD on another computer somewhere? If so, export the registry setting, and import them on your server. I just tried it and I can now install the patch!

Loop
01-30-2004, 06:25 PM
a patch is a patch is a patch


so it should work via exe or uploading the corresponding files.otherwise its crap

dunno if my cd key is in the reg...so i will not upload my regstuff.I noticed another thin with our public server which is run by multiplay.uk,
quote:
"Dear Multiplay Clanserver Customer,

We're issuing this urgent email regarding todays release of the v1.2
patch for Call of Duty. Before you read any further DO NOT upgrade to
v1.2 or you will not be able to play on your clanserver you have with
us. This is due to a major issue with the linux dedicated process which
means we are unable to upgrade our Call of Duty servers until there is a
fix. Given the uproar around the CoD server admin community at present,
we're hoping this will be very soon.

Now the technical details of the problem. Virtually all linux game
servers run using a component of linux called glib-2.2. You have
various flavours of linux, from slackware to debian to RedHat but
glib-2.2 is common across them. With the v1.2 release of the linux
dedicated server for Call of Duty, Infinity Ward have decided to compile
it only for use with glib-2.3. This is not standard across all linux
systems and in fact only a few linux game servers are capable of running
on it! To gve you an analogy, this is like creating a dedicated server
that only runs on Windows Server 2003, but on no other versions of
windows (2000, XP, ME, 98, etc.).

Both Battlefield 1942 and Elite Force 2 tried to move to use glib-2.3
previously but encountered similar outcries from the community and were
forced to roll back. In the case of BF1942, this fix was within hours
of the developers realising the problem. We can but hope for Infinity
Ward to respond similarly quickly.

Just in case Infinity Ward do not release a fix for this, we have put in
place a backup plan. We have ordered 6 new dual xeon 2.8 machines.
These when combined with the new servers we put in last night, and with
a bit of reshuffling, will enable us to move all of our Call of Duty
servers to boxes where only Call of Duty is run (and the few games that
can run under glib-2.3). This will enable us to run v1.2 on those
machines, but will involve quite a bit of downtime, and a change of IP
and port for all CoD servers.

A further problem with this backup plan is the lead time on getting this
new hardware, which won't reach us until Monday 9th February. This
means realistically we're looking at Wednesday 11th February before we
could have the servers in place and the update and reshuffle completed.

Suffice to say the IW server admins list is alive with people screaming
at Infinity Ward to fix this. We can only hope they make a swift fix to
this problem.

Please accept our apologies for the inconvenience caused by this. All
we can suggest for now if you have already updated to v1.2, is to
downgrade/reinstall back to v1.1. We'll keep you updated with any news
and developments on this problem. "

end quote
--------------------------------------------------------------------------------
Well, seems we have to wait for some fixing.

Best regards,

Loop

imported_drbopp
01-30-2004, 07:02 PM
Does anyone have a tried and true answer for this? I am not just gonna try something just on a chance that it may work.........

DR.

imported_ian
01-30-2004, 11:35 PM
If you do what I said, it works. I just did this for my server, and a friends server. Both are up and running like a charm.

Loop, I dont know what you mean by "a patch is a patch.." This patch is just like any other patch from any other game, it will not work if it cant find a previous version in the registry.

(I'm assuming) You have nothing in your registry because you just uploaded the files to your server, instead of installing straight from the CD.

Grab the CoD registry setting from another computer and import it on your servers. It takes all of 30 seconds to do.

bigyin
01-31-2004, 02:05 AM
just upload these files to your windows server and it will work

thats is the only files the patch changed

worked ok for me server is up and running now :!:


C:\Program Files\Call of Duty\CoDMP.exe 1.49 MB
C:\Program Files\Call of Duty\version.inf 135 bytes
C:\Program Files\Call of Duty\main\cgame_mp_x86.dll 524 KB
C:\Program Files\Call of Duty\main\game_mp_x86.dll 472 KB
C:\Program Files\Call of Duty\main\localized_english_pak2.pk3 17.1 KB
C:\Program Files\Call of Duty\main\pak0.pk3 156 MB
C:\Program Files\Call of Duty\main\pak8.pk3 1.04 MB
C:\Program Files\Call of Duty\main\ui_mp_x86.dll 268 KB

rudedog
01-31-2004, 08:32 AM
Bigyin, that's what I did also.

My only problem is I can't seem to see my server in the browser list.

anyone else having this problem?

Rammer_DD
01-31-2004, 08:53 AM
had the only windows server out of the 4 running is the only one that shows up ????????