If this problem is less than five days old, restore a copy of the registry
that predates the onset of the problem and see if that helps. The five-day
limit assumes that the computer is booted every day. If it is not booted
every day, you may have an old enough registry backup that you can use even
though more than five days have elapsed. Note that any registry changes
made after the date of the restored registry will be lost.

Ways of restoring the W98 registry include:

On the Start Menu, select Shut Down and Restart in MSDOS Mode. At the
Windows prompt, type: scanreg /restore and hit enter.

Boot to the boot menu by holding down either the ctrl or F8 key after the
ram count occurs on the boot screen. Select Command Prompt Only and at the
C: prompt, type: scanreg /restore and hit enter.

Boot with the W98 start up floppy disk--CDRom support doesn't matter. At
the A: prompt, type: C: and hit enter. At the C: prompt, type: CD
Windows\Command and hit enter. At the Command prompt, type: scanreg
/restore and hit enter.

Once the registry restore screen appears, select the date of the registry
that you wish to restore by highlighting it and then click enter. If you
see a registry named: Rbbad.cab, that is a copy of the registry that has
already been replaced.

--
Regards


Ron Badour, MS MVP for W98
Tips: http://home.satx.rr.com/badour
Knowledge Base Info:
http://support.microsoft.com/default.aspx?pr=kbinfo



"chowbaby" wrote in message
...
My computer's display properties, task bar and system tray all show in a
very
light yellow color. This happened all of a sudden after my computer froze
and I had to reboot. Ever since when I go into the display properties to
try
and change to anything (Windows standard) that might be better visually,
the
system hangs. Task Manager shows "not responding" next to Display
Properties. I have run my anti-virus, Adaware and Ewido. I would just
reinstall Windows but the software did not come with my computer. Nothing
appears to help. Could this be just a video driver problem? I tried this
also but received back that the system was already running the most
current
driver.

Anyone run across this before and know how to fix it? Thanks
--
SXL