Intel 810 Chipset Graphics Drvr. PV 2.1 Problem

[SMasica]

Hi all. I'm a new member to this Forum, but I've had it bookmarked for some time. I'd like to tap some of the community's knowledge and experience. I'm trying to help out a friend.

Friend's system:

HP Pavilion 6635 PC, Intel Celeron 533MHz CPU, 64MB RAM, 10GB HDD, HP Pavilion M70/D5259A Monitor, 56X CDR, Win98SE.

Problem:

His young kids didn't shut down the PC properly after playing games, etc. Left the game CD in the drive and just powered off. Upon start-up, get the BSOD and "A Fatal Exception 0D Has Occurred At 2047:00000316 - Yadda-Yadda..." Could only get into Safe Mode. No Hardware Conflicts or anything obviously wrong physically.

I did some digging in the MS KB articles and Fatal Exception 0D's are usually video driver related. I went into MSCONFIG and used Selective Startup to narrow it down. Seems the System.ini file was the culprit.

In Safe Mode, I deleted the Display Driver, Restarted, Windows detected the device, and installed the correct driver for the Intel 810 Graphics Driver PV 2.1. Everything looked OK.

I then went back to MSCONFIG and set everything to Normal Startup and Restarted. Got the same BSOD, went into Safe Mode again, deleted and re-installed the display driver. Again, everything seems OK as long as I leave it as Selective Startup with the System.ini File bypassed.

Question: Is this OK to do? Or should the System.ini File be modified to fully correct this problem? If so, how?

Side Question: Do the System.ini, Win.ini Files have to be loaded every time Win98 boots along with Autoexec.bat and Config.sys?

Thanks.

 

[SMasica]

BTTT

I didn't think my question was that much of a stumper. Anyone?

 

[AndyHui]

win.ini and system.ini are only there for legacy applications. They are not needed in the 32-bit versions of Windows. You can bypass system.ini safely, although you may want to grab a regular, uncorrupted system.ini and replace the corrupted one.

 

[SMasica]

Thanks. I finally did diagnose and solve the problem. Using MSCONFIG, I went through SYSTEM.INI line-by-line. There was a line that was: SYSTEM.DRV = ATMSYS.DRV. It should have been SYSTEM.DRV = SYSTEM.DRV. I changed it, re-tested, and now everything is back to normal. The MS KB articles were very helpful in narrowiing this down.