CAll of Duty Expansion Pak for Server 2003

This is a discussion about CAll of Duty Expansion Pak for Server 2003 in the Windows Games category; I need help in installing the call of duty expansion pack for windows server 2003. any ideas? the original COD installed with no probs, but the ex pack claims it needs winxp. someone help me. what the hell do i do????? thanks.

Windows Games 5469 This topic was started by ,


data/avatar/default/avatar10.webp

2 Posts
Location -
Joined 2004-09-24
I need help in installing the call of duty expansion pack for windows server 2003. any ideas? the original COD installed with no probs, but the ex pack claims it needs winxp. someone help me. what the hell do i do????? thanks.

Participate in our website and join the conversation

You already have an account on our website? To log in, use the link provided below.
Login
Create a new user account. Registration is free and takes only a few seconds.
Register
This subject has been archived. New comments and votes cannot be submitted.
Sep 24
Created
Sep 24
Last Response
0
Likes
1 minute
Read Time
User User User User
Users

Responses to this topic


data/avatar/default/avatar26.webp

690 Posts
Location -
Joined 2004-05-06
Windows 2003 comes with Compatibility Mode, Right click Setup.exe (or whatever the EXE is), click Properties, Compatibility, enable it and select Windows XP from drop down list.
 

data/avatar/default/avatar10.webp

2 Posts
Location -
Joined 2004-09-24
OP
i tried that, still same message appears."need winxp to install". so i copied the files on to my hardrive and changed the properties there...still no effect. would i need a hex editor or something to modify the msi file?

data/avatar/default/avatar35.webp

2172 Posts
Location -
Joined 2002-08-26
You'll have to use ORCA to modify the .msi, and remove any OS checks/dependancies.

data/avatar/default/avatar01.webp

738 Posts
Location -
Joined 2002-12-11
As a comparason
 
DOOM 3 wont install on Win2k3 without using a "/a" with the setup.exe
 
Perhaps it might be worth a try using setup.exe /a
 
Adam had the correct idea about OS dependencies within the MSI db.