Author Topic: Lockup at start of game (Read 357 times)

ZENMS · « **on:** January 29, 2006, 09:20:48 AM »

yesterday I downloaded the game, the two skin files and fired up the game. Everything went well. So I opened the game to setup my joystick and flew a couple of times off line. Closed the game.

This morning, I fired up my pc, clicked on the ah2 icon and the game started. I see the background and clipboard, but the clipboard is darkened and the mouse pointer is stuck at the top left. It just sits there and does nothing. I can hit control/alt/delete and still nothing. I hit the caps lock key to see if the keyboard was still recognized and it is. I have to hit the rest button to get out of it.

I then reinstalled the game, and the two skins files and it does the exact same thing. I ran that dxdiag, the tests and everything checked out ok.

I have a:

3800 X2
6800 GS 256 mb
1 Gb ram
WinXp Pro
DirectX 9c
and 81.98 Nvidia drivers

From what I read, on older Nvidia cards they say to use the old drivers, but I really dont want to try that route as all my other games (Bf2,ET,WB) run great with these drivers.

Any ideas?

The Fugitive · « **Reply #1 on:** January 30, 2006, 06:26:51 AM »

you might have a corrupt skins file. Try loading up without the skins fils added in and see if that works.

Delirium · « **Reply #2 on:** January 30, 2006, 06:56:48 AM »

Check the Hardware forum... there is a problem with dual-core CPUs and Nvidia cards combined with Windows XP.

There is a sticky on top of the forum for ya.

click me for easy access to the sticky

ZENMS · « **Reply #3 on:** January 30, 2006, 04:44:51 PM »

I did an uninstall, deleted directories etc... rebooted and reinstalled just the game. This time I left out the skins. Same result.... spinning clipboard etc... I checked out the thread about it, seems like AH wants to ignore that they need to fix their game. No other game has these problems, especially newer graphically intense games like Q4 or Bf2. I dont understand why someone who runs an X2 system should have to shut down one of their processors to play a game that obviously doesnt support it, or any newer systems.

Oh well maybe it will be fixed in AH3..........

Gooss · « **Reply #4 on:** January 30, 2006, 08:45:40 PM »

ZEN MASTER!

Shut up, fix it, and fly.

Great to see you!

HONK!
Gooss

Schutt · « **Reply #5 on:** January 31, 2006, 01:21:09 AM »

zen, thats exactly the problem described in the other thread that got linked already. here what was written there
found the issue already....
remove /usepmtimer from boot.ini

by overlag:
-------------------------------
A64's X2 driver adds /usepmtimer to the boot.ini, i had removed it before due to some issues, but i had re-tested it last week and everything was fine. However i hadnt tested AH since i had only 256mb ram due to a failure/RMA i was going through.

/usepmtimer is something to do with SMP rigs and cool and quiet i think and obviously AH doesnt like it!

now i gota get my aim back......not that i had aim anyway.....lol

__________________

Skuzzy · « **Reply #6 on:** January 31, 2006, 09:31:38 AM »

There is nothing we can do to fix it. It is beyond the scope of any application to correct a problem in the lower level hardware/drivers or operating system.

We could disable multi-threading, and that would probably take care of the problem. As one of the few true multi-threaded games on the market, there is a good chance we will find issues where other games will not.

But, keep in mind, it has worked for years in the HT enabled Intel CPU and chipsets and works in the dual core Intel as well, even though we do not code to any particular CPU brand.

ZENMS · « **Reply #7 on:** February 03, 2006, 10:46:33 PM »

I set it to run in Win98 mode, but it shuts down one of the processors. I have a logitech G15 keyboard, and it displays but processor loads, as well as ram usage... so it does effect it. I will try the boot ini thingy... then when I get it going I am going to get Goose! Goose, just watch out for Pj's on yer 6!:eek: