Originally posted by rabbidrabbit
is the file name "boot.ini" I have the same problem but could not find the file in either win2003 or xp64.
Originally posted by rabbidrabbit
looks like its just Nvidia and any AMD x2 processor from what I have heard.
Originally posted by Skuzzy
Overlag, thatnk you very much for finding this bugger. I greately appreciate it. It is fast becoming the number one problem in Aces High.
I am going to sticky this one.
Originally posted by rabbidrabbit
My boot.ini in xp64 looks like this:
[boot loader]
timeout=1
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows XP Professional x64 Edition" /noexecute=optin /fastdetect
My boot.ini in win2003 looks like this:
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise" /fastdetect /NoExecute=OptOut
Not seeing the switch you are talking about but have the same spinning clipboard problem.
Originally posted by rabbidrabbit
I'm seeing pretty much the same thing you are. The screen turns a shade darker and the clipboard spins. Often I can ctrl-alt-del out of it but sometimes the machines locks up entirely and I have to hardboot.
[boot loader]
timeout=5
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows XP Professional x64 Edition" /noexecute=optin /fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows XP Professional x64 Edition ONECPU" /onecpu /noexecute=optin /fastdetect
Originally posted by vaikku
Finally found a solution, even annoying one, to this AMD64 X2 lockup problem I was having.
You have to run WinXP64 in sinle processor mode.
To do so you have to add /onecpu parameter in boot.ini:
run notepad c:\boot.ini
copy & paste the last line and add /onecpu parameter to the new line.
For example here is my boot.ini after modification.
Now I have to restart windows in onecpu mode to play AH, but at least I can play it now...
Originally posted by numb
those 77.77 drivers are crap when i had them and i tried 2 play i would get a blue screen update 2 the newest ones
Originally posted by Kev367th
Came across this while researching a game I was looking at buying.
Seems to be an almost exclusively Win XP/XP64 problem. (so whatever they changed in the 'task/thread manager' from 2000 to XP is the problem)
Two more workarounds -
1) Use XP's ability to 'emulate' an earlier OS. Set the game to run as a Win98 game (still maintains dual cores operating).
2) Start the game, ALT - TAB out
press CTRL+ALT+DEL to get the task manager
select the 'Processes' tab
find the game process and right click it
select "Set Affinity"
uncheck one of the cores (this forces the game to run single core only),seems best is to uncheck the 1st one, i.e. CPU 0.
Originally posted by numb
those 77.77 drivers are crap when i had them and i tried 2 play i would get a blue screen update 2 the newest ones
Originally posted by Kev367th
Looks like an XP64 problem, although I ran earlier versions of AH2 on XP64 Betas without a prob.
So may be something that has been changed in AH2.
Works great on Win 2000.