Overclocked CPU problems don't always show up as crashes; EAR Sound says sometimes they show up as stuttering video and/or looping audio.
Even people who don't think they're overclocked sometimes are, thanks to unscrupulous chip resellers, who sometimes label 300MHz parts as 350MHz etc.
You can even have problems if there's a price tag on your CPU between the chip and the heat sink... don't laugh, it happens.
One user had crashes every other game until he fixed his DRAM timing in BIOS (it had been set to 10ns, but he had 8ns RAM, he says). He then crashed only once every few games until he set the motherboard jumper labelled "RAM Speed" to "CPU" instead of "AGP". (The only other program this caused problems for was Truespace, he says.)
If you crash in multiplayer when there are lots of players and/or
explosions, and you see one of these CRC's,
024C-C3F9, 113D-9BED, 2AC0-8969, 4320-D1C9, 4DDF-8951, 592E-50A6, 8378-38B0, 8E4C-5933, B125-8D8C, B5C6-3951, BD38-7FC7, C398-F55E, EA47-1ED3, F049-9FBC, or FC54-6DF7
Try installing the latest Ear Sound drivers. See http://www.earsound.com/ and look under "Supported Hardware", or download and run http://www.earsound.com/download/dlls/iaspkg0.exe.
Each active TCP/IP entry in your Networking Control Panel counts as one Internet address. (Also, if your ISP is using a NAT that changes your Internet address, that counts as an extra Internet address.) To fix this, delete unused TCP/IP entries in the Networking Control Panel, delete unused dialup or LAN adaptors in the Networking Control Panel, or disable unused LAN adapters in Control Panel / System / Device Manager while you play.
To tell how many local IP addresses you have, run winipcfg.exe. The pulldown list shows all your interfaces. Those that have IP addresses different from 0.0.0.0 count as an active IP address.
To tell whether you are behind a NAT (which gives you another address), compare the IP address displayed by ICQ with the addresses displayed by winipcfg.exe. If none of the addresses displayed by winipcfg.exe match the one displayed by ICQ, you are probably behind a NAT which is giving you yet another Internet address.
The following ISPs have been reported to use NAT:
One way to set your OS for English was mentioned on alt.games.heavy-gear by "Wing" (Note: I haven't verified this. Don't try this if you're not comfortable with regedit):
Re: HG2 - Setup won't even run....helpBe sure to write down the old value so you can restore it later.
I think that you have to edit the registry to get it working, just as we Chinese Windows users do. Use regedit, open HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Nls\Locale and set the first item [ ab(default)] to 00000409. This works for Chinese Windows, and I guess that it should work fine on French Windows, too.
Likewise, if you have a foreign version of the game, it will refuse to install if you don't have the right version of the OS. The same workaround -- setting the registry to match the locale the game expects -- can be used; for instance, the German game wants HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Nls\Locale to be 00000407.
You can download a zipfile containing 'bindings.def' files
for French, German, Spanish, Italian, Portugese and Swedish
(For some languages, Win95 and Win98 have different key names. Both
are included.) Grab the 'bindings.def' from the folder in the zipfile
named after the appropriate language and OS, and drop it into your HG2
directory. Note that the Portugese bindings file was user-contributed and
may contain errors; I don't have the official one for that language.
If you're patient, you can use the game's reconfiguration screen to reconfigure each key.
If you're brave, you can also try editing the file 'bindings.def' (see how-to for French, how-to for German).
Astute users have noticed that the earlier HG2 demo (released in late 1998) creates a file "controls.usr" the first time it runs. This contains the names you'll need when you edit bindings.def.
This won't work properly for key names that use funny chars, so Chinese users will have to wait for the localized version of the game, or somehow play with an English DirectX.
Christer Carlsson (email@example.com) contributed the Swedish bindings.
Here are his notes:
Mentioned in a previous post that I was locking up on the load screen every time I started a mission after the first one. ... Some one on the list E-mailed me asking if it was always after the first mission or after I changed my control configuration, well after testing thing it turned out that it was related to my changing controls. If I just loaded one of the pre done configurations everything worked fine, but if I remapped any of the keys it would lock up as soon as I tried to go into a mission. ... I read an earlier post in which the person mentioned that the had the same problem & could play again by restoring the bindings.def file, I tried this & it worked.
After this I changed my keys around again and checked the new bindings.def to the backed up one, other than the keys I changed the only diferance was in the top of the file where there is a line that describes my joystick, somthing like 0=sidewinder presision pro, well in the original file it only has one line for the presicion pro, on the new bindings.def it has three lines one for each of my controllers ( a Sidwewinder Precision Pro, a Sidewinder Freestyle pro & a Sidewinder Forcefeedback pro.) All are attached at the same time (the Presicion & Freestyle are USB). For the hell of it I deleted all but the first joystick line & guess what my new config works & I don't lock up.
Another approach might be to assign forward and backward to different input channels; see the post by Dan Roberts.
Finally, you might consider using the Palex control set instead. It's the HG2 way.
According to the folks at EAR Sound, if you're occasionally having trouble with HG2 detecting the CD, and you have auto-insert notification software running, disable it! Here's their list of various software packages which can cause this problem, plus notes on how to disable auto insert notification, if known:
Third-party programs that emulate the CD-ROM are also known to cause problems. Virtual Drive 2000, for instance, caused one user's DVD to no longer detect audio tracks properly, even after he uninstalled it.
Finally, a very few users have CD-ROM drives that simply don't like the way HG2 looks for the CD. A fix is in the works.
One cause seems to be a problem with DirectX 6.1, Windows 95, and Internet Explorer 3. According to EAR Sound, the Windows core has been changed by the DX6.1 install, and now Windows 95/IE3 crashes when you unload DirectX. Microsoft no longer supports IE3, and they suggest people in this situation install IE4.
One user reports this kind of problem (with a particular mission) being cured when he updated his SBLive drivers. Another reports that killing csinject (part of Norton Cleansweep) solved his problems.
The famous PIII + W98 + DX6.1 Problem. D3D Games crashing/not loading. ... appears to be a problem that Intel/Microsoft/Software Vendors have all chosen to ignore.You can find the reference version of VMCPD.VXD by opening \Win98\Win98_48.cab on your Win98 cd-rom using Winzip 7.0 or later.
The problem arises from the Floating Point Operations of the PIII and Windows Virtual Memory Management (VMM32.VXD).
So why does it happen. Well there's a cute little 23K file named VMCPD.VXD within the C:\Windows\System\VMM32\ directory which gets overwritten. DX6.1, MultiMedia Drivers, etc all appear never to check the version before overwriting it. I will bet if your D3D games are crashing out as they load data then you VMCPD.VXD is version 4.10.1413. To check the version locate the file, right click on it, select Properties and go to the Version tab.
The Fix - You need to extract the VMCPD.VXD from the Windows '98 Cabs (Win98_48.cab). The correct version number is 4.10.1998. Copy this file in to the C:\Windows\System\VMM32\ directory overwriting the existing VMCPD.VXD. Reboot the PC and everything should now be okay.
I had the problem with my TNT (stb velocity 4400) - was totally unplayable framerates - till I found a small card in the box saying that I have to turn off all the video memory cashing and shading in the bios. After that everything was perfect.
If you have an ATX motherboard whose onboard 3.3 volt regulator can't supply enough power, you may be able to bypass the onboard regulator and use the 3.3 volt supply of your ATX power supply instead; see the workarounds below. Contact your motherboard manufacturer to verify that you need to do this beforehand, since this is a drastic step.
According to Abit, the AGP card needs more power than some of their motherboards can supply. For a workaround and more info, see http://hem.fyristorg.com/redtop/
According to Asus, their P2L97 motherboards before revision 2.04
could only supply 2.5 amps, and do not support the Riva TNT card
without modification. Their newer cards can supply 6.0 amps, which
is enough to power a single Riva TNT.
For more info, see http://www.asus.com/products/techref/misc/rivatnt.html. For a workaround, see http://www.asus.com/products/techref/misc/rivatnt-rework.html.
I just happened across a work-around for some of the graphics corruptions in HG2. The corruption can result in invisible text in "Esc" and Tactical Map menus, as well as inability to display exterior views (other than blocky shadows, I haven't noticed the other problems listed in the troubleshooting guide).
Here's the fix: having the yellow text brought up by pressing "O" (for orders) fixes this in some maps (but not in the tutorial which requires using the tac map... sigh).