When I try to run scanregw.exe, I receive a message stating that the file appears to be corrupt. Is there any way to repair or reinstall this program without reinstalling Windows? I'm running Win98SE on a Pentium III 550.

Go to START > RUN and type, sfc.exe and press enter. This will run the system file checker program ( W98 only ) and it will attempt to repair or replace any corrupt or missing system files. Also , try Scandisk . Toggle F8 or press Ctrl key during bootup ( depends on your computor ) , choose Command prompt only ( NOT Safe mode Command prompt ), then at the C: prompt , type Scandisk /all & press Enter . When finished , type win & press Enter .

You can use sfc to "extract" scanregw.exe without actually the checker itself. This is a safer option because sfc sometimes reports corrupted files when they are not. Here are some notes about sfc which I disected & collated:- SFC can be useful for extracting files but be careful with versions because it puts back "original" files (most folk will have updated IE for example). DON'T USE SFC TO EXTRACT:- Any file which has a later date than those on the W98 CD (see note) unless this is your intention, msisys.vxd and vmm32.vxd are specific examples of this. gdi.exe - SFC gets it wrong. ** krnl386.exe - SFC gets it wrong. ** msisys.vxd - This file is modified every time MSINFO32 is run. user.exe - SFC gets it wrong. ** setupx.dll - SFC can extract wrong version (W98 first edition only). vmm32.vxd - (constructed during windows installation, the one on the CD is only a shell). ** The one on the W98 CD in mini.cab should NOT be used. Location depends on OS version. Look in win98_41.cab and above for these files. Note: It is worth recording the date/time of the "majority" of files in c:\windows\command because these are original Win98 CD versions. This gives you a quick way to decide whether SFC should be used or not.

oops...typo Response 2, lines 2/3 should read: without actually running the checker itself

I had tried scandisk already, and it did not detect the corruption. I also tried the latest Norton Utilities, and it missed it, too. Following John's recommendation, I just tried the sfc scan, but it did not report the corruption either. However, using sfc to extract the file worked like a charm. Thanks guys.