defrag and scandisk vs APPLOG ....

Doing my usual monthly defrag last night, I decided to reverse the order and do
F: E: D: and finish with C:. F: E: and D: all went without incident, but C: was
another story.

Progress stayed at 0% while the disk activity light displayed what looked like a
samba beat. Definitely looping around. So after about 5 minutes I aborted that
and tried scandisk. This time it looked more like a tango, but still stayed on
0%. Downloaded latest virus definitions and ran a complete scan of C: without
incident.

Went into the MSKB and found the "complete list of KB articles re SCANDISK" and
ditto for DEFRAG. Eventually found one that seemed similar, which recommended
deleting the C:\Windows\APPLOG folder and then retrying scandisk and defrag.

So to my question - and the point of this post - what does APPLOG hold that is
relevant to Scandisk and Defrag, and why should its contents cause this
behaviour?

It is not what it holds but whether or not there is a corrupt file in the
folder. Here is part of my standard blurb, check out #5:

TROUBLESHOOTING PROBLEMS WITH DISK DEFRAGMENTER

1. Apply one recommendation at a time and then try Defrag again to see if
it helped.

2. Disable the screensaver, anti virus program and the cable/DSL modem, if
any.

3. Delete the files in the Recycle Bin, the browser cache (Temporary
Internet Files folder if using MSIE) and the Temp, History and Recent
folders. Corrupt files can cause Defrag problems.

4. You may receive a notice indicating the drive was written to and caused
Defrag to restart. This means some process is causing hard drive activity
which interferes with Defrag. Either reboot to safe mode and run Defrag
from there or use EndItAll2, a free program which shuts down nearly all
running programs except Explorer and Systray. Download the program from
here: http://www.docsdownloads.com/Tier1/enditall.htm To boot to safe mode
in W98, see: http://support.microsoft.com/support/kb/articles/q180/9/02.asp

5. It's possible corrupt files in the Cookies and Applog folders will cause
Defrag problems. Since those files contain useful information, you can
either move them to a partition other than the one being Defragged or to
floppy disks. Once Defrag is complete, you can replace the files. If it
appears either folder contains corrupt files, you will either have to try to
determine which files are corrupt, delete all the files and let them rebuild
as part of your normal operations or move the folders during the next Defrag
session. If you run into problems deleting a file because it is corrupt, try
deleting it from a DOS prompt.

6. The first Defrag after installing or upgrading to Win98 may take a
significant amount of time to complete. Also, Defrag may appear to stall
out at the 10% mark; however, this is a common occurrence. As long as there
is disk activity, let Defrag run. The appearance of stalling with W95 may
also occur but it will generally be before 10%.


--
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



"budgie" <me DeleteThis @privacy.net> wrote in message
news:lo9dk251ggokhmdmjtrqh4b2anjnp6sgd5@4ax.com...
> Doing my usual monthly defrag last night, I decided to reverse the order
> and do
> F: E: D: and finish with C:. F: E: and D: all went without incident, but
> C: was
> another story.
>
> Progress stayed at 0% while the disk activity light displayed what looked
> like a
> samba beat. Definitely looping around. So after about 5 minutes I
> aborted that
> and tried scandisk. This time it looked more like a tango, but still
> stayed on
> 0%. Downloaded latest virus definitions and ran a complete scan of C:
> without
> incident.
>
> Went into the MSKB and found the "complete list of KB articles re
> SCANDISK" and
> ditto for DEFRAG. Eventually found one that seemed similar, which
> recommended
> deleting the C:\Windows\APPLOG folder and then retrying scandisk and
> defrag.
>
> So to my question - and the point of this post - what does APPLOG hold
> that is
> relevant to Scandisk and Defrag, and why should its contents cause this
> behaviour?