• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Win98SE Startup Problem

Iluvatar

Member
When I turn on my computer I get the message:
"While initializing device VCACHE. Windows protection error. You need to restart your computer."

It worked fine a few hours earlier, and all I did was check my email (didn't install any hardware/software). I used DocMemory, and it says all my RAM is fine. I don't think its a hardware problem at all, in fact I'm using the same computer right now, in Windows 98 using a different hard drive and it works fine. I suppose the hard drive could be failing, but I thought I'd ask in here before I start a 15+ hour surface scan.

Here's the bootlog I get when I try to startup:

[000FEC30] Loading Device = C:\WINDOWS\HIMEM.SYS
(Logo disabled)
[000FEC30] LoadSuccess = C:\WINDOWS\HIMEM.SYS
[000FEC30] Loading Device = C:\WINDOWS\DBLBUFF.SYS
[000FEC30] LoadSuccess = C:\WINDOWS\DBLBUFF.SYS
[000FEC30] Loading Device = C:\WINDOWS\IFSHLP.SYS
[000FEC30] LoadSuccess = C:\WINDOWS\IFSHLP.SYS

In the previous bootlog, the next thing that would be loaded is the VMM. Does anyone have any ideas?

Thanks

-Iluvatar
 
here is a link to a vcache tweak guide and utility. Perhaps all that's needed is to adjust the Vcache settings in the original hard drive's system ini. Good luck and I hope this helps.
 
I already had tweaked the Vcache setting to get Windows to work with 512MB of RAM, but thanks for that guide anyways. Apparently the values I used weren't optimal. The problem is still there, but with a new twist. Sometimes it boots up with an identical message, except it says VFAT instead of VCACHE. Is there a driver that might be corrupt? I ran the system file checker in Windows 98, but it says that they are all fine.
 
When I have my FSB overclocked too much, I run into those kinds of errors quite frequently. Are you overclocked?
 
WarCon's observation,as usual, is excellent, however if you haven't overclocked the FSB it is also possible that your O.S. has corrupted stacks, ect... in which case an overlay reinstall of win98SE would repair the damage. I would also suggest if that doesn't resolve your issue to enable S.MA.R.T. monitoring for your HDD and run the diagnostic utility offered by your HDD's manufacture. Let us know how your getting on 🙂
 
Back
Top