Call of duty 4 (COD4) on windows seven

[killerprince]

if u run pbsvc and pbsetup at the same time it might work both run as administrator. i mean that works for me and i'm on rtm

 

[peksii]

Got punkbuster work on windows 7 ultimate build 7232

 

[Civ]

Can anyone try my method on 7600.16385??
-Install clean copy od win7 without formatting
-Browse in C:/windows.old/Program Files/Activision and move "Call of Duty 4" folder in c:/ProgramFiles/
-DO NOT reinstall call of duty 4 or pb services (pbsvc.exe) -dunno about pbsetup.exe-
-Launch the game, enter your mp cd key in multiplayer options, open console and type /seta con_gameMsgWindow0FadeInTime "0"
-Try the game and feedback here!!

Did you try this yourself yet? Anybody else?

if u run pbsvc and pbsetup at the same time it might work both run as administrator. i mean that works for me and i'm on rtm

All of these methods seem to work with the 32-bit version of the 7600 RTM build but not with the 64-bit/x64 installation, which I have. :huh:

 

[rjc8620003]

yep works fine here on RTM

 

[skunksmash]

PB updated itself last week & now the ''Windows API function'' error is gone , so i CAN CONFIRM COD4 is fully functional on build 7100..... finally

 

[burp154]

it works for build 7264 32bit as well . No wonder I haven't been getting kicked out :<

 

[nino206]

if u run pbsvc and pbsetup at the same time it might work both run as administrator. i mean that works for me and i'm on rtm

Should i first run pbsvc or pbsetup?

 

[killerprince]

either way doesn't matter only need to do that setup once

 

[nino206]

Jep, It works... no more api kick, but now disallowed program/driver kick, wtf....
I'll go crazy....

 

[Appel]

Hey people,

This has worked for me, but remember to start off with a clean install in case you have made other attempts to *fix* this.

1. Install CoD4 with PB that comes with it.

2. Install all the patches to bring it up to the current version (1.7)

3. Do a PB manual update.

4. Run Cod4 to make sure all services start.

5. Set the following files to Vista compatibility mode:

• C:\Windows\SysWOW64\PnkBstrA.exe
• C:\Windows\SysWOW64\PnkBstrB.exe

6. Play the game.

This has been verified on 64b only, builds: 7100 & 7600 (3 Machines, 2x 7100 and 1 7600) I have been able to play it on build 7100 32b but the executable's are in a different location and I haven't documented them.

I have logged about 3.5 days of constant play with this working, and I've been playing on PB enabled servers.

Please let me know if this works for you

 

[Mark]

Hey people,

This has worked for me, but remember to start off with a clean install in case you have made other attempts to *fix* this.

1. Install CoD4 with PB that comes with it.

2. Install all the patches to bring it up to the current version (1.7)

3. Do a PB manual update.

4. Run Cod4 to make sure all services start.

5. Set the following files to Vista compatibility mode:

• C:\Windows\SysWOW64\PnkBstrA.exe
• C:\Windows\SysWOW64\PnkBstrB.exe

6. Play the game.

This has been verified on 64b only, builds: 7100 & 7600 (3 Machines, 2x 7100 and 1 7600) I have been able to play it on build 7100 32b but the executable's are in a different location and I haven't documented them.

I have logged about 3.5 days of constant play with this working, and I've been playing on PB enabled servers.

Please let me know if this works for you

That's exactly the way I have mine working on build 7600 x64 but I also changed the game exe to Vista Compatibility as well but probably wasn't needed.

 

[Appel]

I think this is the best way to get it going under Windows 7, I helped to get to this through another forum when this worked we posted it and more and more people started reporting that it started to work.

Although I only included my personal successes.

 

[Appel]

That's exactly the way I have mine working on build 7600 x64 but I also changed the game exe to Vista Compatibility as well but probably wasn't needed.

No, that wasn't necessary, because the problem lies with Punkbuster. Not Call of Duty.

 

[Mark]

No, that wasn't necessary, because the problem lies with Punkbuster. Not Call of Duty.

I didn't think it was but as it was working I didn't want to change anything as you could understand.

I had actually applied this fix a while ago after someone suggested it but at the time it didn't work and it was just recently that I tried again and found I wasn't getting kicked.

 

[NuT]

I'm running the RTM and no pb kicks in cod4, quake 3, or COD world at war!

 

[pandelis]

i just updated to RTM but still cant use Single Player. I dont install pb, i can enter multiplayer screen. but i cant make Single Player work from start.



any workaround?

 

[pandelis]

multiplayer works but single player wont!!! installed 1.7 patch. no way! helpp

 

[Appel]

multiplayer works but single player wont!!! installed 1.7 patch. no way! helpp

The executable name doesn't match the executable name I use for CoD.
I suggest you uninstall Cod, delete the entire directory from your program files and then do a complete reinstall. (Don't forget to back up your multilayer profile)

Also you should check if all drivers are installed, and install the manufacturers drivers instead of the windows default drivers, I've come across a similar error with someone who didn't have his sound card installed.

 

[TheSk8rJesus]

If you downloaded the official RC from Microsoft then it should be 7100, if not then you can check by clicking on the start orb and type winver and hit enter and should be on the first line.

Also if you want to play online then you will need build 7100 or 7127

Okay i am using Windows 7 Pro from volume license site, is cod 4 working with punkbuster now no problems or is it a work around?

 

[Mark]

I'm using the RTM version now and COD4 and World at War both work fine with no kicks.