An extremely annoying and weird problem

Hi, I have the weirdest and most annoying problem ever (on my laptop), this is just so weird, i played age of empires (it ran fine) then I closed it, my brother ran IconArt,(about 5-10mins later) I then restarted aoe, it loaded the menus fine but as it went to play, it reverts to the desktop(it also changes the resolution and palette for about .5 seconds) with no message at all, this also occurs with Simisle with a message saying something like simisle.exe has caused a H1 error in Simisle.exe.

I have reinstalled AOE again, I have the latest drivers (i think), I'm using directx 8

Sorry if i have placed this in the wrong forum.

 

Hi Ray,

Run dxdiag (enter dxdiag at the Start > Run command line). Run through the graphics tests.
Suggest you go to DirectX 8.1 if you have DirectX 8.0 (check your version in dxdiag). It works well with Win 98. DirectX 9.0 will not run with some older graphics adapters.

Check for updated graphics adapter drivers. They should be available at the laptop manufacturer's website for your model.

Something during the installation of AOE may have caused a problem. Uninstall it while you get the other programs going again.

Matt

 

i have directx 8.1 i used to have 9 but the graphics on certain things stopped working, anyway the program is fine now(i haven't done anything to fix it!)

 

Thanks for letting us know.

I read somewhere in the distant past that Windows is capable of adapting itself. It may take a few reboots as Steve said. I find that it may take a few reboots before a problem finally disappears (Windows works out where to look and what to load).
It may have been that the wrong version of a file was selected. Windows found and installed the correct one.

Matt

 

Hi, so windows evoles then...

 

I have one 98SE machine that I USED to have to reboot between a certain two games. Otherwise I would have the same problem. If we ran in the A-B sequence it required a restart of Windows in between. If we ran B-A sequence there would be no problem.

Or if we waited at least 10 minutes between A & B there would be no problems. On further investigation I found that A was not shutting down properly.

Anyway. In a case such as the one at hand I suggest NOT blaming or messing with Windows itself until you can be real sure it is Windows causing the problem.

BillyBob