PDA

View Full Version : CoD2MP_s.exe Slow Start



kung foo man
27th November 2012, 04:58
Hey all,

does anybody know why CoD2 is starting so slowly?

The screen is just black for around 37 seconds. :S

I had that problem one time before because of a wrong DNS-Server, but the current one should work just fine.

Regards,
kung

Peterlankton
28th November 2012, 15:54
If your CoD starts that slowly the only cause I'm aware of is that your game doesn't have access to the internet.
Probably some ports are blocked by your firewall or whatever. That's all I know by experience.

kung foo man
5th February 2013, 17:00
It seems to be a general Windows 8 Problem. Does anybody got Windows 8 without a slow CoD2-Startup?

thOuMta
6th February 2013, 11:00
If your CoD2MP_s.exe slow start its because you must add your '' DNS '' from your box to your pc.

Sorry for my english

kung foo man
6th February 2013, 11:09
Hm, you mean this?

136

Thats unfortunately not working :S

thOuMta
6th February 2013, 11:10
Yes you must search what is your DNS from you box and copy past here :)

kung foo man
6th February 2013, 11:15
Before i had 192.168.0.1 (my router as dns) in there, but that didnt work also. :)

thOuMta
6th February 2013, 11:16
Who is your internet developper ?

kung foo man
6th February 2013, 11:19
My Internet Provider is EWE Tel

thOuMta
6th February 2013, 11:23
So you need search what is the EWE Tel DNS (maybe from 192.168.1.1) and put to your pc :)
Or you search from Google what is the DNS from EWE Tel

kung foo man
6th February 2013, 11:29
Hey, found the DNS of my Provider (212.6.64.232), but unfortunately it doesnt work also. :D

I really think its a Windows 8 Issue, because i had the same network configuration in Windows XP but never had problems with that. :o

thOuMta
6th February 2013, 11:31
So its Windows 8 had problems :/

Tally
6th February 2013, 12:12
Does it start quicker if you disconnect from the internet and run offline? Finding a network for online purposes will slow the compile time, so checking to see if it is indeed a network issue (router?) will help to diagnose the problem.

If you start quicker offline, then you know it's a networking problem; if not, then you know it's a genuine compile issue, which may be driver related.

kung foo man
6th February 2013, 14:29
Finally pulled the network cable out, to be sure the net is gone. It took again a huge amount of seconds to start CoD2.

Tally
6th February 2013, 16:00
Finally pulled the network cable out, to be sure the net is gone. It took again a huge amount of seconds to start CoD2.

What chipset are you using? AMD or Nvidia?

kung foo man
6th February 2013, 16:39
Hey Tally, made a SiSoftware Sandra Hardware List for clearing the hardware up:




System
Modell : GigaByte PH67-UD3-B3
Gehäuse : GigaByte Desktop
Mainboard : GigaByte PH67-UD3-B3
System BIOS : Award (OEM) F2 02/22/2011
Gesamtspeicher : 16GB DIMM DDR3

Prozessor(en)
Prozessor : Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz (4C 3.5GHz/3.7GHz, 3.5GHz IMC, 2x 256kB L2, 6MB L3)
Sockel/Slot : FC LGA1155

Chipsatz
Speichercontroller : Intel Core (Sandy Bridge) DRAM Controller 100MHz, 2x 8GB DIMM DDR3 1.33GHz 128-bit

Speichermodul(e)
Speichermodul : G.Skill F3-12800CL9-4GBXL 4GB DIMM DDR3 PC3-12800U DDR3-1600 (9-9-9-25 4-34-10-5)
Speichermodul : G.Skill F3-12800CL9-4GBXL 4GB DIMM DDR3 PC3-12800U DDR3-1600 (9-9-9-25 4-34-10-5)
Speichermodul : G.Skill F3-12800CL9-4GBXL 4GB DIMM DDR3 PC3-12800U DDR3-1600 (9-9-9-25 4-34-10-5)
Speichermodul : G.Skill F3-12800CL9-4GBXL 4GB DIMM DDR3 PC3-12800U DDR3-1600 (9-9-9-25 4-34-10-5)

Grafiksystem
Monitor : Samsung SyncMaster
(1440x900, 26.2")
Monitor : Samsung SyncMaster
(1440x900, 26.2")
Grafikkarte : NVIDIA GeForce 210 (2CU 16SP SM4.1 1.4GHz, 512MB DDR2 800MHz 128-bit, PCIe 2.00 x16)
Grafikkarte : AMD Radeon HD 6670 (6CU 400SP SM5.0 800MHz, 1GB DDR3 128-bit, PCIe 2.00 x16)

Grafikprozessor
OpenCL GP-Prozessor : AMD Radeon HD 6670 (480SP 6C 800MHz, 1GB DDR3 128-bit)
OpenCL GP-Prozessor : NVIDIA GeForce 210 (16SP 2C 1.4GHz, 512MB DDR2 800MHz 128-bit)
Compute Shader Prozessor : AMD Radeon HD 6670 (400SP 800MHz, 1GB DDR3 128-bit)
Compute Shader Prozessor : NVIDIA GeForce 210 (16SP 1.4GHz, 512MB DDR2 800MHz 128-bit)
CUDA GP-Prozessor : NVIDIA GeForce 210 (16SP 2C 1.4GHz, 512MB DDR2 800MHz 64-bit)

Physische Speichergeräte
WDC WD10EAVS-00D7B1 (1TB, SATA300, 3.5", 5400rpm, 8MB Cache) : 932GB (C:) (D:)
SAMSUNG HD160JJ (160GB, SATA300, 3.5", 7200rpm, 8MB Cache) : 149GB (E:) (H:) (I:) (J:)
Seagate ST3500820AS (500.1GB, USB2/SATA300, 3.5", 7200rpm, 8MB Cache) : 466GB (G:)
SAMSUNG HD154UI (1.5TB, USB2/SATA300, 3.5", 7200rpm, 32MB Cache) : 1TB (F:)

Peripherie
LPC Hub Controller 1 : Gigabyte H67 LPC Controller
LPC Legacy Controller 1 : T2 87-28
Audio Gerät : Gigabyte Cougar Point High Definition Audio Controller
Audio Gerät : ASUS High Definition Audio Controller
Serielle Port(s) : 1
Laufwerkscontroller : Gigabyte Cougar Point 4 port SATA IDE Controller
Laufwerkscontroller : Gigabyte Cougar Point 2 port SATA IDE Controller
USB Controller 1 : Gigabyte Cougar Point USB Enhanced Host Controller #2
USB Controller 2 : Gigabyte Cougar Point USB Enhanced Host Controller #1
System SMBus Controller 1 : Intel ICH SMBus


Sensoren
Ort : Microsoft Visual Studio Location Simulator Sensor (Ort, Unbekannt)

Peripherie

Netzwerkdienste
Netzwerkadapter : Controller der Familie Realtek PCIe GBE (Ethernet, 100Mbps)

Betriebssystem
Windowssystem : Microsoft Windows 8 Professional 6.02.9200
Kompatibel mit Plattform : x64

Windows Leistungsindex
Aktuelles System : 4.1

Tally
6th February 2013, 18:41
That is showing 2 graphics cards. Can I take it that the Nvidia onboard card is disabled and that you are using the HD 6670? Have you updated to the very latest AMD driver? There was one for the 6670 released on the 27th of January 2013.

I said all that, but actually it is probably a legacy DirectX driver problem in Windows 8. Games like COD2 use DX7 and DX9, and it takes time for the legacy drivers to emulate the older versions of DirectX. I think that is probably what is happening here, and will probably never be fixed until such time as MS do something about it.

kung foo man
10th August 2013, 19:32
Well, final solution was -> .exe -> Properties -> Run XP Compatibility mode, as IzNoGod figured out, but r_gamma isn't working then

(Just saw some guest in here searching obviously for solution)

megazor
11th August 2013, 03:52
Years ago I had similar problem with my CoD1 usually starting for about one minute. I noticed that it started much faster when either a) LAN cable was plugged off or b) headphones were plugged on xD
When I bought a new PC, the problem was gone.

IzNoGoD
12th August 2013, 19:09
Setting this compatibility mode lowers my fps dramatically.

I now get 125 stable, although i have to watch through 2 minutes of black screen.

Mitch
24th February 2014, 19:08
i just set com_hunkMegs to 512 and it increases the load time of cod2 a lot. So keep com_hunkMegs on the default 160.

deivis33
25th December 2014, 20:23
Well, final solution was -> .exe -> Properties -> Run XP Compatibility mode, as IzNoGod figured out, but r_gamma isn't working then

(Just saw some guest in here searching obviously for solution)

Same problem here with Windows 8.1. (DirectX7 and ATI HD4850)
Call of Duty 2 in running compatibility mode caused noticeable lags in mouse movements, and the r_gamma isn't working too
Solution for me: Come back to Win7 x64

IzNoGoD
25th December 2014, 21:36
Heres a fix for cod2 on win8+

Use cod2fix.reg and one of the items in the winfixes folder (choose your appropriate scaling percentage)

Fix based on:
http://donewmouseaccel.blogspot.nl/2010/03/markc-windows-7-mouse-acceleration-fix.html
and
http://support.microsoft.com/kb/2908279

Good luck :)

Edit: after applying the registry fix, execute the following command:


Rundll32 apphelp.dll,ShimFlushCache
Then, reboot your pc

Mitch
26th January 2015, 11:37
The problem lies somewhere in the DirectDraw emulation in Windows 8(.1).

http://answers.microsoft.com/en-us/windows/forum/windows_8-gaming/directdraw-emulation-is-broken-in-windows-881/4edfc685-72b2-4688-95ed-c745ddd38825?page=1

Prawy
18th January 2021, 17:56
For me fix was simple. I just connect my headphones through jack or USB and then i just enabled mix stereo.

agribilos
19th January 2021, 18:15
I had the same issue with windows 10. It got solved when i set the compatibility settings as shown below. No problem with fps draw either.
1643

Mitch
24th July 2023, 13:48
There is a patched version of 1.3 that solves the black screen issue: https://cdn.discordapp.com/attachments/825622671172829184/877008965496623164/Call.of.Duty.2.Custom.Patch-LuKeStorm.rar
I haven't had any issues with this patch and i'm able to run it without compatibility settings on Windows 11.

https://steamcommunity.com/app/2630/discussions/0/3196988242389390014/

kung foo man
25th July 2023, 08:22
There is a patched version of 1.3 that solves the black screen issue: https://cdn.discordapp.com/attachments/825622671172829184/877008965496623164/Call.of.Duty.2.Custom.Patch-LuKeStorm.rar
I haven't had any issues with this patch and i'm able to run it without compatibility settings on Windows 11.

https://steamcommunity.com/app/2630/discussions/0/3196988242389390014/


Nice, seems legit, byte compare for 1.3:


arr[0x33ee0] = 0xc3; // was 0x51
arr[0x33fc2] = 0x90; // was 0xe8
arr[0x33fc3] = 0x90; // was 0x09
arr[0x33fc4] = 0x90; // was 0xcb
arr[0x33fc5] = 0x90; // was 0xfe
arr[0x33fc6] = 0x90; // was 0xff
arr[0x65190] = 0xc3; // was 0x6a
arr[0x65191] = 0x90; // was 0x00
arr[0x65209] = 0x90; // was 0x74
arr[0x6520a] = 0x90; // was 0x66
arr[0x664cd] = 0xeb; // was 0x75
arr[0x664ce] = 0x2d; // was 0x06
arr[0xb3b7c] = 0x90; // was 0x75
arr[0xb3b7d] = 0x90; // was 0x09
arr[0xb8dd0] = 0xc3; // was 0x55
arr[0xb9569] = 0x74; // was 0x90
arr[0xb956a] = 0x0b; // was 0x90

vanfreddy
4th August 2023, 22:17
to fix the problem all you have to do is to enable stereomix in the record setting in windows sound settings