After an improper shutdown, ScanDisk appears and runs through Drive C twice - right to the end of the blue squares - then starts a
third time and freezes after the third square. It has been doing exactly this several times recently. When I Cancel ScanDisk, the
O/S boots up as normal and ScanDisk then runs quite quickly and without a hitch, so is there something adrift in ME, and if so is
there a cure?
Adaware and Grisoft's AVG show no spyware or v*ruses in the system, all my programs run OK and I don't use any Norton software.

Signature
Jim, in sunny Brisbane, Oz.
Scandisk works fine for me, scandskw is a whole different story for me
and several friends. With the exception of the efforts of the MVP
voluneers here, ME is no longer supported my microsoft (excepting
critical security updates thru June 2006 I think it is) so whichever
scandskw odditty(s) have surfaced, you will need to tolerate or find a
third party program to use as a substitute.
Most of the users I know agree that using "scandefrag" makes a huge
difference if encountering the continual restarting problem.
In my case, some two years ago my scandskw began overwriting the
existing log every 2-3 sessions while set to append, its also set to
display summary on if error found and recently I see where it no
longer complies with that setting although it continues to log the
error(s) in the most recently generated log file.
You could try replacing the scandskw.exe file, I did but it made no
difference in my situation.
Good Luck
>After an improper shutdown, ScanDisk appears and runs through Drive C twice - right to the end of the blue squares - then starts a
>third time and freezes after the third square. It has been doing exactly this several times recently. When I Cancel ScanDisk, the
>O/S boots up as normal and ScanDisk then runs quite quickly and without a hitch, so is there something adrift in ME, and if so is
>there a cure?
-- Keyboard not detected
Press F1 to continue
Rick T - 22 Jul 2005 20:07 GMT
> In my case, some two years ago my scandskw began overwriting the
> existing log every 2-3 sessions while set to append,
tried naming the scandiskw log <whatever>.OLD ? maybe there's a size
restraint on it.
Rick
TheRealFastlane - 01 Aug 2005 13:58 GMT
Rick, no such filename, is there supposed to be ?
AFAIK, the dos and windows version write to scandisk.log
in the root of C:. My settings for scandskw when run from windows
(excluding scandefrag) have been show summary only if errors, append,
make copies, convert to files, invalid filenames + dates/times.
Recently I notice that it is not bringing up the summary is found but
does still log the errors. Today I notice in the log
Drive Local Disk (E:) contained the following errors:
The drive contained an error in its FSInfoSector.
Resolution: Repair the error
Results: Error was corrected as specified above.
Which I "been told" should only be reported for the win/boot drive
which in my case is C: (which also had an fsinfosector error due to
getting the VMCPD blue screen which requires a cold boot after any
keypress).
>> In my case, some two years ago my scandskw began overwriting the
>> existing log every 2-3 sessions while set to append,
[quoted text clipped - 3 lines]
>
>Rick
-- Keyboard not detected
Press F1 to continue
Rick T - 01 Aug 2005 18:43 GMT
Just meant since apparently scandiskw is occasionally creating a new
file instead of appending that you should rename it <whatever the log
name is>.OLD so it would still be around; no idea why that's happening;
would be weird if the error was connected to the log.
But generally ScanDefrag is the best solution for most people's problems.
Rick
> Rick, no such filename, is there supposed to be ?
> AFAIK, the dos and windows version write to scandisk.log
[quoted text clipped - 24 lines]
> -- Keyboard not detected
> Press F1 to continue
Jim Cladingboel - 02 Aug 2005 06:13 GMT
Rick, I think you missed the point. RealFastlane was saying he has no such file as ScandskW.log but should he have one?
I made the same comment a week or three ago when I had a similar problem with ScanDisk not working correctly after an improper
shutdown.
There is no ScandskW file on my PC, but there is a Scandisk.log!

Signature
Jim, in sunny Brisbane, Oz.
> Just meant since apparently scandiskw is occasionally creating a new
> file instead of appending that you should rename it <whatever the log
[quoted text clipped - 33 lines]
> > -- Keyboard not detected
> > Press F1 to continue
Jim Cladingboel - 23 Jul 2005 07:13 GMT
Thanks, but my Scandisk.log is just 1 KB, so that doesn't seem to be the problem. I don't have scandiskw.exe but have found
Scandisk.exe, 240 KB, appearing twice on Drive C. Once in Windows\Command and again in Windows\Options\Install, both listed as
Applications.
Guess I'll have to live with the problem and keep 'Improper Shutdowns' to a minimum....?
Jim.
> Scandisk works fine for me, scandskw is a whole different story for me
> and several friends. With the exception of the efforts of the MVP
[quoted text clipped - 17 lines]
> >O/S boots up as normal and ScanDisk then runs quite quickly and without a hitch, so is there something adrift in ME, and if so is
> >there a cure?
Rick T wrote
From: "Rick T" <plinnane3REMOVE@NOSPAMyahoo.com>
Subject: Re: ScanDisk & Improper Shutdown
Date: Saturday, 23 July 2005 5:07 AM
> In my case, some two years ago my scandskw began overwriting the
> existing log every 2-3 sessions while set to append,
tried naming the scandiskw log <whatever>.OLD ? maybe there's a size
restraint on it.
Rick