KCK wrote:1. ...you telling us that you had InCDUDFReader installed all the time? 2. not all the drivers mentioned in the other thread are listed now. 3. Why don't you simply list the current Iosubsys directory
1. No 2&3. Not all drivers are mentioned because I removed (renamed) them early on in the troubleshooting game, and here is my current InfoTool 2.0 report
YES, the report's correct - I did re-install the IAAs to see if my shutdown problem is really related to the std 98 IDE Controller Drivers. Well, I couldn't believe my eyes, but the shutdown problem is still
I obviously changed someting or other during my troubleshooting process that has nothing to do with Microsoft vs. Intel IDE Controller...
I did my best to retrace my steps, but was unable to determine any change that might affect shutdown.
I went a step further & analyzed various backed-up drivers & DLLs via Version Conflict Manager (VCM)
. I was shocked to find that there were a few VIP files where the backed-up version was of a newer version than the ones actually in use! This blew me away until I took note of the backup date, and realized it coincided with a HDD crash I experienced at the beginning of the year. I had no option but to "re-install" 98SE from the CD, and the Windows update feature appearantly did not "reset" 100%.
Some of the more interesting files include pci.vxd, vpowered.vxd, ifsmgr.vxd, msconfig.exe, vserver.vxd, msnet32.dll, and User.exe.
After an extensive analysis, I determined that all the shutdown "delay" MS updates had been overwritten with the original 98SE CD files. I used the VCM utility to restore all but User.exe (I tried that one, boy, what a painful mistake that was, lol), but in the end, I still have my shutdown failure IFF InCD 3.5.x is installed. Sniff. Last but not least, I did a few bootlog tests, one with InCD installed & one w/o. Unfortunately this proved futile, as both logs were identical (except for the loading of the InCD-related drivers), and ended with the stmt EndTerminate = User
and no Terminate/EndTerminate pair for Kernel.exe
I know what you're thinking - this calls for a clean re-install of 98SE + updates, and re-install of all apps & drivers. I agree! However... I have so many apps installed on this rig, including custom profiles for just about each one, that even after six month's worth of dilligent re-installing, I would never be able to recover everything.
Therefore, I propose that we bring this thread to a close, as it is now becoming more of a "How to fix my screwed-up OS"
than an InCD problem. It just so happens that I was made aware of my system's state only upon installation of the recent InCD 3.5.x & EasyWrite versions.
The last "working" configuration I had then, was InCD 188.8.131.52 & InCDUDFReader 2.04: since I have no interest to roll that far
back, I will concentrate on InCD4.x which actually runs on my "personalized" 98 SE rig
InCD4 has it's problems, but like everyone else, I'll just wait it out.
Thanks to all, and to you in particular, KCK & sorry for wasting our time!