Aces High Bulletin Board
Help and Support Forums => Technical Support => Topic started by: Bingo on November 03, 2004, 11:25:32 PM
-
for 2 years been trying to get this game running solidly....upgraded twice,,,,,bought 3 new vid cards.....just replaced my vid card with a new 1 of same make/model.....no relief ,,,,just grief!
Bingo,,,,,out
-
wow...if you have upgraded..then its all you..patience..
what the hell isnt working?
-
I am going to resign in here and to the fact I just can not get this game to work on my machine.
I bought an ATI 9200 128 meg card to begin with before the AH2 swap over. The card worked fine in AH1.
I have been struggling to keep the game playing for quite some time now. I keep getting unexplained restarts. I have upgraded my BIOS, I have upgraded Video card drivers and tried the omega version to no good end. I have takin suggestions that it is my power supply or heat issues and bought a new power supply and installed a new cpu fan and heatsink and still no help. I have purchased spyware, registry cleaners and the like to get rid of anything that may be trying to hide and start that would affect the game and thing just get worse.
As it stands today I can sit in the tower but as soon as I choose a runway the screen freezes up.
I am going to see if Pacific Theatre or IL2 treats me any better.
I am on a fixed income and this game is going to nickle and dime me to death just to try and get it to run.
It has been a fun 2 years when the game was working but a frustrating last 3 or 4 months trying to end the constant restarts.
-
crap..im startn to run liek crap in the new map..im kinda pissed..
moto..dam..The way it sounds you should be running decent..
im getnn alot of freezes..mini ones..fps ar in teens and dip into singles..very very crappy...
-
I had exactly the same problem with the game. I could go into the tower but as soon as I jumped in a plane and tried to takeoff, the game locked up. Sometimes it just sat there, locked, but most of the time it crashed and booted me back to the desktop.
What soundcard do you have?
What version of Windows are you running?
Does your soundcard pass all the DxDiagnostic tests?
In my specific situation, it was caused by corrupt Win98 drivers for my SB Audigy card. The card came with a warning that the default drivers installed would be the generic XP ones. It went on to say that these drivers could cause severe system slowdowns if you use Win98. So I followed their instructions and installed the Win98 drivers from the CD. Everything LOOKED fine in the DxDiagnostic, but I didnt actually run the tests. Finally after installing and reinstalling things a hundred times, I ran the tests on everything just to be sure the basics were covered. Amazingly enough when I ran the tests on the soundcard it locked up and rebooted the computer. Found out that the Win98 drivers included on the CD were corrupt and replaced them with the others. I had other problems too, but that is the one that caused my crashes. Yours could be different. Just one thing to check, and it doesnt cost any money. :) GL!
-
System Information
------------------
Time of this report: 10/22/2004, 17:16:16
Machine name: A
Operating System: Windows XP Home Edition (5.1, Build 2600) Service Pack 1 (2600.xpsp2_gdr.040517-1325)
Language: English (Regional Setting: English)
System Manufacturer: Compaq Presario 061
System Model: DN024A-ABA S5000CL NA310
BIOS: Phoenix - AwardBIOS v6.00PG
Processor: AMD Athlon(tm) XP 2600+, ~2.1GHz
Memory: 1024MB RAM
Page File: 218MB used, 1431MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
DxDiag Version: 5.03.0001.0904 32bit Unicode
DxDiag Notes
------------
DirectX Files Tab: No problems found.
Display Tab 1: No problems found.
Sound Tab 1: No problems found.
Sound Tab 2: No problems found.
Music Tab: No problems found.
Input Tab: No problems found.
Network Tab: No problems found.
Description: Logitech USB Headset
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: USB\Vid_046d&Pid_0a01&Rev_0113&MI_00
Manufacturer ID: 65535
Product ID: 65535
Type: WDM
Driver Name: usbaudio.sys
Driver Version: 5.01.2600.1106 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 8/29/2002 01:32:32, 56832 bytes
Other Files:
Driver Provider: Microsoft
HW Accel Level: Full
Cap Flags: 0xF5F
Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 0, 0
Static/Strm HW 3D Bufs: 0, 0
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No
Registry: OK
Sound Test Result: Not run
Description: Realtek AC97 Audio
Default Sound Playback: No
Default Voice Playback: No
Hardware ID: PCI\VEN_1106&DEV_3059&SUBSYS_39021462&REV_50
Manufacturer ID: 65535
Product ID: 65535
Type: WDM
Driver Name: ALCXWDM.SYS
Driver Version: 5.10.0000.5410 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 2/17/2004 06:49:14, 538236 bytes
Other Files:
Driver Provider: Realtek Semiconductor Corp.
HW Accel Level: Full
Cap Flags: 0xF5F
Min/Max Sample Rate: 100, 192000
Static/Strm HW Mix Bufs: 33, 32
Static/Strm HW 3D Bufs: 33, 32
HW Memory: 0
Voice Management: Yes
EAX(tm) 2.0 Listen/Src: Yes, Yes
I3DL2(tm) Listen/Src: Yes, Yes
Sensaura(tm) ZoomFX(tm): No
Registry: OK
Sound Test Result: Not run
---------------------
Sound Capture Devices
---------------------
Description: Logitech USB Headset
Default Sound Capture: Yes
Default Voice Capture: Yes
Driver Name: usbaudio.sys
Driver Version: 5.01.2600.1106 (English)
Driver Attributes: Final Retail
Date and Size: 8/29/2002 01:32:32, 56832 bytes
Cap Flags: 0x41
Format Flags: 0xCCC
Description: Realtek AC97 Audio
Default Sound Capture: No
Default Voice Capture: No
Driver Name: ALCXWDM.SYS
Driver Version: 5.10.0000.5410 (English)
Driver Attributes: Final Retail
Date and Size: 2/17/2004 06:49:14, 538236 bytes
Cap Flags: 0x41
Format Flags: 0xFFF
-
Only things I can see that MIGHT be a problem (I'm not sayin they ARE problems, just potential) are these..............
It shows your USB headset and your soundcard as separate sound devices. There may be a conflict there. Do you use the onboard sound? I mean, do you have desktop speakers in addition to the headset? Or is the headset all you use? Try disabling the onboard sound card if you dont use it. See if that helps.
While the drivers for your onboard sound card are recent, the drivers for your headset are over 2 years old. See if Logitech has newer drivers available. I doubt that is your problem, but it doesnt hurt to check and its free.
You have hardware acceleration turned to high on both the onboard sound card and the headset. Try turning them down to 3/4, especially for the onboard sound card as issues have often been posted with these. If 3/4 has no effect, turn it down to 1/2, and then disable hardware acceleration entirely. If none of these settings work, disable the sound card and see if the game starts with absolutely no sound card on your system. Eliminate the possibility.
Use the DX Diagnostic tool and actually run the tests on each tab. Especially the sound tab. Make sure the listed devices pass all the tests. They are simple tests, and yes its boring, but you may be surprised. According to the DxDiagnostic report you didnt run the tests yet. I've found problems that way more than once.
Last but not least (of my suggestions anyway), check your hardware IRQ settings. Make sure nothing is in conflict, and make sure nothing is sharing an IRQ setting. I had this problem also, no conflicts but I had several major devices that were sharing IRQs. Game wouldnt run.
Hopefully something here will help.
-
Windows does not like two sound cards in a system. Remove either the USB one (too much CPU overhead) or remove the onboard one.
-
I have gone back to the other headset I have that y's off the speakers.
I will give this a try. This may be a part of the problem but the headset is only about 3 weeks old and this problem is about 4-5 months old.
Thanks for the suggestion. I am open to anything that might get me up and running again.
-
That did nothing to help the problem.:confused: :(
I can sit in the tower but as soon as I choose a runway I get a Total Freeze up.
Before it was restarts. I don't know which is worse.:(
I am coming to DFW Next Friday a.m. to go see Fedj57, Muggs65, Mugz, Fryman, and Flak8me I should drop it off with you skuzzy and let you look at it as a test bed the 4 days I'm gone. hehehe
-
Just curious MOTO,do you have animated water enabled ?
and second since you never posted in our group what you have and havent tried,have you tried a memory test? in some not all,
they tend to creep out and can have the same effects that you descibe,ive encountered 3 in my time,it just came to me (old age,sorry) :)
Joe/nsty1
-
HW Accel Level: Full
Turn your soundcard acceleration down to 3/4. You can make the change in DX Diag.
-
There are a couple of things that can cause a freeze up when exiting the tower to go fly.
1) Currently, there is a bug in the Spit 9/14 if you have selected bombs to carry. Just go the hangar and deselect them. This will fix the problem until we issue the next patch.
2) If you have bitmaps in your squad folder which are not formatted correctly, you will hang or crash to desktop when you exit the tower to fly. Clear your squad art files out of the "squads" folder.
-
Thx skuzzy the freeze ups were in the Spit IX with ord. but that did nothing for the restart. I was able to play for about 1/2 an hour then Poof it restarts the machine :(
-
I had a touchy CPU that would cause a restart at relatively low temps.
Might want monitor the CPU temp and see if the restarts are all occcuring at about the same temperature.
-
Last suggestion I know to make isnt a pretty one. Have your CPU and MOBO tested. Usually a shop will charge you about 40-50 bucks for it, if you know someone they might take it on for free and do it in their spare time. Compaq's dont have the greatest record. I dont know if the MOBO is original or not, or if you have made any changes to components. If I remember correctly, Compaq's require you to use ECC RAM instead of the standard stuff. That could be a culprit. I know you said you replaced the heat sink and fan on the processor, but from experience I've seen the XP 2600 can run pretty warm, esp. if the airflow through the case isnt good, even with a decent heat sink and fan. Your BIOS should have a reading that shows CPU temps. It might not even be a problem with overheating, it might be the cutout circuit that controls the "reset-on-overheat" function is bad, so the MOBO just THINKS the CPU is overheating. Testing would turn that up. I honestly dont know what else to suggest.
-
I do have a cpu temp .monitor running and as far as I can tell when the game sis playing the CPU runs about 50-55 degrees C'
I did purchase a cheap sound card and a fan that I have as an intake on the front of the case. It is in the intake position because I grabbed the wrong sizt to fit in the back. I will get an exhaust fan next time I am near a computer store.
Currently room temp is 79.F CPU is at 50'C and MOB is 32'C.
I had a suggestion about the soundcard so I will try it.
My problem may not be common but I don't think it is unique either. I have seen a few other comments about similar problems.
How would a shop test my MOB?
I have some diagnostics tools that say CPU benchmark is ok. It is not the best and not the worst. Can they put it under a heavy load and log the problems?
-
55C degrees is pretty warm. Thats about .......... 130F degrees I think? The hottest mine gets is about 120F. And even that is running hot IMO. If it goes hotter when I start overclocking I may have to go with water cooling. I dont know what the reset limit is set at on your MOBO, but I'm betting you are at least close if not there. Try taking the sides off the case and blow a fan into the insides and run it, see if that makes a diff. This may still not help, but if it does there's your problem. I'd try the soundcard first though. Just take it out and try to run the game. Its an easier and cheaper solution if thats the problem lol.
-
i had to keep the side off of my computer with a desk fan blowing into it inorder to keep my computer from crapping out on me. It was restarting when i was in the middle of a fight. My computer has a fan and my video card has a fan also.. i figured that my video card is overheating and windows is shutting it down to save it from frying. just my luck, my desk fan just died the other night.. geeze:(
-
Depends on the card, but if you have monitoring software for it you should get a warning before it reaches critical temps. My FX5900 is set to warn me if it hits 48C degrees. Usually if your computer just resets like that its the CPU overheating. Of course if one is too hot, the other likely isnt all that cool.
-
Moto, CPU overheating will also show up in other areas. Your system will just start acting very wierd. Do you leave it on? Do so and if it starts acting strange then maybe heating is the issue. I am leaning more toward RAM. I know this is not an answer you want to hear but that's what my feeling is here. I'm in IT and have had servers do really stupid stuff that was related to flakey RAM.
If your ram is not all on one stick pull out some of the RAM (half)and see if you can run AH. If not switch it and see if that works.
Your system sounds fairly new and RAM ussually has long warranties so you may be able to get it replaced.