Defragmentation.

[Rod]

I am aware I can defragment in safe mode,
just curious as to why suddenly, after 5 years,
my defrag is doing what others have experienced,
and aborting half way through and starting again?

I always use "end it all" with av shut down.

any ideas?
Thank you very much.

 

[AlmostBob]

after 5 years 'something' has found a way to bypass enditall ?
such 'something's are often something nasty
run enditall
and then check to see if there are processes that shouldn't be there
scan for malware
do all the things that others were instructed to do when
"defrag is doing what others have experienced, and aborting half way through
and starting again"

--
-- -- -- -- --
Adaware http://www.lavasoft.de
spybot http://www.safer-networking.org
AVG free antivirus http://free.grisoft.com/
Etrust/Vet/CA.online Antivirus scan
http://www3.ca.com/securityadvisor/virusinfo/scan.aspx
Super Antispyware http://www.superantispyware.com/
Panda online AntiVirus scan http://www.activescan.com
Panda online AntiSpyware Scan
http://www.pandasoftware.com/virus_info/spyware/test/
Catalog of removal tools (1)
http://www.pandasoftware.com/download/utilities/
Catalog of removal tools (2)
http://www3.ca.com/securityadvisor/newsinfo/collateral.aspx?CID=40387
Trouble Shooting guide to Windows http://mvps.org/winhelp2002/
Blocking Unwanted Parasites with a Hosts file
http://mvps.org/winhelp2002/hosts.htm
links provided as a courtesy, read all instructions on the pages before
use
Grateful thanks to the authors/webmasters
_
"Rod" <pookiethai@iprimus.com.au> wrote in message
news:uXsPXTUIIHA.3940@TK2MSFTNGP05.phx.gbl...
> I am aware I can defragment in safe mode,
> just curious as to why suddenly, after 5 years,
> my defrag is doing what others have experienced,
> and aborting half way through and starting again?
>
> I always use "end it all" with av shut down.
>
> any ideas?
> Thank you very much.
>
>
>

 

[Don Phillipson]

"Rod" <pookiethai@iprimus.com.au> wrote in message
news:uXsPXTUIIHA.3940@TK2MSFTNGP05.phx.gbl...

> I am aware I can defragment in safe mode,
> just curious as to why suddenly, after 5 years,
> my defrag is doing what others have experienced,
> and aborting half way through and starting again?

Might this not be a hint that it would be prudent to
run the manufacturer's diagnostics on this 5-year-old drive?

--
Don Phillipson
Carlsbad Springs
(Ottawa, Canada)

 

[Peter Keller]

Rod wrote:
> I am aware I can defragment in safe mode,
> just curious as to why suddenly, after 5 years,
> my defrag is doing what others have experienced,
> and aborting half way through and starting again?
>
> I always use "end it all" with av shut down.
>
> any ideas?
> Thank you very much.
>
>
>
Here is an old Vic Ferri trick that I saved. I use it all the time.

>Power Defrag is very popular but all it does is reboot into defrag,
instead of
explorer.exe, and then after defragging is done, it reboots again and
restores
explorer.exe.

You can do this manually and with out having to reboot(a little trick I
came up
with) to start defrag as the only process running. Here's how:

1. Open system.ini or just use msconfig.exe to change the shell=explorer.exe
line to shell=defrag.exe The line is under the [boot] section.

2.Press Ctrl+Alt+Del, highlight Explorer and click End Task

3. Click NO when the Shut down screen comes up.

4. Now click End Task again

And that will do it as a subsitute to rebooting - defrag.exe will now
come up -
the same way Power Defrag brings it on after a reboot(no more explorer)
Then defrag your disk and reboot into DOS
and use the instructions I gave at the top to restore the shell= line
back to
shell=explorer.exe.

 

[Rod]

"Rod" <pookiethai@iprimus.com.au> wrote in message
news:uXsPXTUIIHA.3940@TK2MSFTNGP05.phx.gbl...

Thank you very much gentlemen,
advice appreciated.

Re:
>Might this not be a hint that it would be prudent to
>run the manufacturer's diagnostics on this 5-year-old drive?

Indeed:
I have never done that before, do I have to rip the cover
off the box for the drive details, or can it be done otherwise?
I am a bit hesitant there is dust and muck in there
that would suit archaeology.

I always scan disk prior to defrag, and there are always faults
that are fixed, (this has been recurring for years)

I am due to cross over to XP soon, but want to keep
this system as a duplication.

Sincere thanks for the other advice.
R.

 

[AlmostBob]

even removing the arheological detritus may help

--
-- -- -- -- --
Adaware http://www.lavasoft.de
spybot http://www.safer-networking.org
AVG free antivirus http://free.grisoft.com/
Etrust/Vet/CA.online Antivirus scan
http://www3.ca.com/securityadvisor/virusinfo/scan.aspx
Super Antispyware http://www.superantispyware.com/
Panda online AntiVirus scan http://www.activescan.com
Panda online AntiSpyware Scan
http://www.pandasoftware.com/virus_info/spyware/test/
Catalog of removal tools (1)
http://www.pandasoftware.com/download/utilities/
Catalog of removal tools (2)
http://www3.ca.com/securityadvisor/newsinfo/collateral.aspx?CID=40387
Trouble Shooting guide to Windows http://mvps.org/winhelp2002/
Blocking Unwanted Parasites with a Hosts file
http://mvps.org/winhelp2002/hosts.htm
links provided as a courtesy, read all instructions on the pages before
use
Grateful thanks to the authors/webmasters
_
"Rod" <pookiethai@iprimus.com.au> wrote in message
news:eWtOJWZIIHA.5360@TK2MSFTNGP03.phx.gbl...
>
> "Rod" <pookiethai@iprimus.com.au> wrote in message
> news:uXsPXTUIIHA.3940@TK2MSFTNGP05.phx.gbl...
>
> Thank you very much gentlemen,
> advice appreciated.
>
> Re:
> >Might this not be a hint that it would be prudent to
> >run the manufacturer's diagnostics on this 5-year-old drive?
>
> Indeed:
> I have never done that before, do I have to rip the cover
> off the box for the drive details, or can it be done otherwise?
> I am a bit hesitant there is dust and muck in there
> that would suit archaeology.
>
> I always scan disk prior to defrag, and there are always faults
> that are fixed, (this has been recurring for years)
>
> I am due to cross over to XP soon, but want to keep
> this system as a duplication.
>
> Sincere thanks for the other advice.
> R.
>
>
>
>
>
>
>

 

[Rod]

"AlmostBob" <anonymous1@discussions.microsoft.com> wrote in message
news:uNAnZOfIIHA.484@TK2MSFTNGP06.phx.gbl...
> even removing the arheological detritus may help

Agreed, but I am of the school
if it aint broke, don't fix it, which has served me well.
It sort of <is> broke, but not enough to consider tinkering, Almost.

 

[PCR]

Rod wrote:
| I am aware I can defragment in safe mode,
| just curious as to why suddenly, after 5 years,
| my defrag is doing what others have experienced,
| and aborting half way through and starting again?

Here are the items I have collected that have been said to caus that...

1. Turn off screen saver (R-Clk Desktop, Properties, Screen Saver--
None)
2. Turn off power management (Control Panel, Power Management--
Always On,Never,Never,Never)
3. Suspend Task Scheduler
4. Disable any permanent internet cable connection, perhaps.
5. Turn off interfering programs.

| I always use "end it all" with av shut down.

That probably got items 3 & 5 only. But did you "START, Run, MSInfo32" &
look in the "Software Environment, Running Tasks" to ensure most stuff
indeed did shut down? Maybe use the Edit menu to copy & post what
remains running.

| any ideas?

It wouldn't hurt to do as Phillipson said-- especially if it also
constantly restarts in Safe Mode or running it as Keller said. But I
hope you know how to edit System.ini in DOS, if you do the later!

Also-- did you run Scandisk first? Sometimes it is necessary to do that.
But don't let IT constantly restart, either!

| Thank you very much.

--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR
pcrrcp@netzero.net

 

[Rod]

"PCR" <pcrrcp@netzero.net> wrote in message
news:u3RF5plIIHA.6108@TK2MSFTNGP03.phx.gbl...

> Also-- did you run Scandisk first? Sometimes it is necessary to do that.
> But don't let IT constantly restart, either!

cheers PCR,
yep, I always run scandisk first (from advice here)
there are always problems, but scan disk
fixes them. (<it> never restarts)
I'm working through the advice.
Thanks PCR.

 

[PCR]

Rod wrote:
| "PCR" <pcrrcp@netzero.net> wrote in message
| news:u3RF5plIIHA.6108@TK2MSFTNGP03.phx.gbl...
|
|> Also-- did you run Scandisk first? Sometimes it is necessary to do
|> that. But don't let IT constantly restart, either!
|
| cheers PCR,

Cheers.

| yep, I always run scandisk first (from advice here)
| there are always problems, but scan disk
| fixes them.

Very good! Maybe post the errors from C:\SCANDISK.LOG.

| (<it> never restarts)

It has less a chance to restart, if you run the Standard instead of the
Thorough.

| I'm working through the advice.

Keep us informed. Here are some programs that may be helpful...

http://www.pcmag.com/ 's CrackUp, by Gregory A. Wolking & Bob Flanders,
says when a Defrag may be necessary.

"DiskAction" reports the last 12 processes that access any partition. It
discovered the Microsoft Windows Critical Update Notification tool was
accessing my HDD every five minutes. It can be uninstalled in "Control
Panel, Add/Remove Programs". Then, occasionally, "START, Windows Update"
on your own.

"BHOCop" found a Browser Helper Object called Wavehelper Class, created
by "Wavetop", that was building a monstrosity of an error log called
"Logit.txt" in here. "START, Find, F/F, Logit.txt"-- see one?

Now, my hard drive is quieter than my mouse. (Of course, I now also have
384 MB RAM, up from an initial 64, eliminating Swap File activity.)

| Thanks PCR.

You are welcome.

--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR
pcrrcp@netzero.net

 

[thanatoid]

"Rod" <pookiethai@iprimus.com.au> wrote in
news:eOjf6o1IIHA.4196@TK2MSFTNGP04.phx.gbl:

>
> "PCR" <pcrrcp@netzero.net> wrote in message
>
>> Very good! Maybe post the errors from C:\SCANDISK.LOG.
>
> ------------------------------------------------------------
> ---------------- ------
> If i scan disk tommorow
> I'll probably get the same error
> ---------------------------------------------------------
>
> Log file generated at 14:05 on 10/11/2007.
>
> ScanDisk used the following options:
> Standard test
>
> Drive RODNEY 6GB (C contained the following errors:
>
> ScanDisk found 4096 bytes of data in 1 lost file
> fragment(s).
> Resolution: Ignore this error and continue
> ScanDisk restarted. Unrepaired errors may be reported
> again.
>
> ScanDisk found 4096 bytes of data in 1 lost file
> fragment(s).
> Resolution: Ignore this error and continue
>
> The drive contained an error in its FSInfoSector.
> Resolution: Repair the error
> Results: Error was corrected as specified above.
>
> ScanDisk found errors on this drive but did not fix all of
> them.

The scandisk.ini file found in the windows\command directory
contains a LOT of extremely useful options which you can set,
with rem'd instructions throughout. One of the few things MS has
done really well.

Mess around with that file and set things right.

I've been using Windows since 1992 and I have NEVER had scandisk
report anything as "not fixed".

I also HIGHLY recommend doing scandisk in DOS. It works MUCH
better - and it DOES use the above mentioned ini file.

I do all my partitions once every 6 weeks or so just in case.

Windows being Windows, there are always minor "problems" on at
least on or two partitions, but they are ALWAYS fixed.

 

[Rod]

"PCR" <pcrrcp@netzero.net> wrote in message


> Very good! Maybe post the errors from C:\SCANDISK.LOG.

----------------------------------------------------------------------------
------
If i scan disk tommorow
I'll probably get the same error
---------------------------------------------------------


Log file generated at 14:05 on 10/11/2007.

ScanDisk used the following options:
Standard test

Drive RODNEY 6GB (C contained the following errors:

ScanDisk found 4096 bytes of data in 1 lost file fragment(s).
Resolution: Ignore this error and continue
ScanDisk restarted. Unrepaired errors may be reported again.


ScanDisk found 4096 bytes of data in 1 lost file fragment(s).
Resolution: Ignore this error and continue

The drive contained an error in its FSInfoSector.
Resolution: Repair the error
Results: Error was corrected as specified above.

ScanDisk found errors on this drive but did not fix all of them.

 

[Rod]

"Rod" <pookiethai@iprimus.com.au> wrote in message
news:eOjf6o1IIHA.4196@TK2MSFTNGP04.phx.gbl...
> "PCR" <pcrrcp@netzero.net> wrote in message
> > Very good! Maybe post the errors from C:\SCANDISK.LOG.
---------------------------------------------------------------------------
-
> ------
> If i scan disk tommorow
> I'll probably get the same error
> ---------------------------------------------------------

I have never looked at "Scandisk.log" before
there was no file association with it.

I had the exact same error notice on my <VERY FIRST>
scan disk in 2001

Guess I have to live with it

 

[PCR]

Rod wrote:
| "PCR" <pcrrcp@netzero.net> wrote in message
|
|
|> Very good! Maybe post the errors from C:\SCANDISK.LOG.
|
| ----------------------------------------------------------------------
------
| ------
| If i scan disk tommorow
| I'll probably get the same error
| ---------------------------------------------------------
|
|
| Log file generated at 14:05 on 10/11/2007.
|
| ScanDisk used the following options:
| Standard test
|
| Drive RODNEY 6GB (C contained the following errors:
|
| ScanDisk found 4096 bytes of data in 1 lost file fragment(s).
| Resolution: Ignore this error and continue
| ScanDisk restarted. Unrepaired errors may be reported again.
|
|
| ScanDisk found 4096 bytes of data in 1 lost file fragment(s).
| Resolution: Ignore this error and continue

I'm not sure which setting governs that error in Scandisk.ini. Open your
file in Notepad, & post it, for me to take a guess. (I can't readily
tell looking just at mine or even at cquirke's page.) It is...
C:\WINDOWS\COMMAND\Scandisk.ini.

Also, BEST look at cquirke's page (it is ultra-tough & scary reading,
though)...
http://cquirke.mvps.org/9x/scandisk.htm

| The drive contained an error in its FSInfoSector.
| Resolution: Repair the error
| Results: Error was corrected as specified above.

That is clearly this one...
http://cquirke.mvps.org/9x/scandisk.htm#BadFreeSpace
.......Quote cquirke..............
FSInfo_Sector: Incorrect free space count

This problem is trivial for ScanDisk to fix safely.
.......EOQ.............................

| ScanDisk found errors on this drive but did not fix all of them.

As thanatoid said, it is a setting in C:\WINDOWS\COMMAND\Scandisk.ini
that governs whether the DOS Scandisk will fix errors automatically or
not. But they shouldn't ALL be set to willy-nilly fix them!


--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR
pcrrcp@netzero.net

 

[Rod]

"PCR" <pcrrcp@netzero.net> wrote in message

> I'm not sure which setting governs that error in Scandisk.ini. Open your
> file in Notepad, & post it, for me to take a guess. (I can't readily
> tell looking just at mine or even at cquirke's page.) It is...
> C:\WINDOWS\COMMAND\Scandisk.ini.

I am working through your post.
( I hope I am not taking up too much of your valuable time PCR,
I am near transferring to winXP and 160 Gb disk,
Please feel free to abort advice whenever
I think my disk will hold out till then.
I find your advice interesting however.


here is scandisk.ini.

SCANDISK.INI

This file contains settings you can use to customize the ScanDisk program.
The settings in this file do not apply when running ScanDisk in Windows
95,
unless you are checking an unmounted compressed volume file. These
settings
will apply if you run ScanDisk from an MS-DOS prompt in single-application
mode.



-------------------------------------------------------------------
The [ENVIRONMENT] section contains the following settings, which
determine general aspects of ScanDisk's behavior:

Display Configures ScanDisk to run with a particular type of
display. The default display type is Auto (ScanDisk
adjusts to the current display).

Mouse Enables or disables mouse support. The default value is On.

ScanTimeOut Determines whether ScanDisk should detect disk timeouts
while performing a surface scan. The default value is Off.

NumPasses Determines how many times ScanDisk should check each
cluster during a surface scan. The default value is 1.

LabelCheck Determines whether ScanDisk should check volume labels
for invalid characters. The default is Off.

LfnCheck Activates Scandisk to validate Long File Names, if they
exist.
The default is ON, to check Long File Names for problems.

SpaceCheck Determines whether ScanDisk should check for invalid spaces
in filenames. The default is Off.

Mount Determines whether ScanDisk will mount unmounted DoubleSpace
drives once it has determined they are error-free.


[ENVIRONMENT]
Display = Auto Auto, Mono, Color, Off
Mouse = On On, Off
ScanTimeOut = On On, Off
NumPasses = 1 1 through 65,535 (anything over 10 is slow)
LabelCheck = Off On, Off
LfnCheck = On On, Off
SpaceCheck = Off On, Off
Mount = Prompt Prompt, Always, Never

-------------------------------------------------------------------
The [CUSTOM] section determines ScanDisk's behavior when ScanDisk is
started with the /CUSTOM switch. You can adjust these settings to
create a customized "version" of ScanDisk. This can be especially
useful for running ScanDisk from a batch file. The [CUSTOM] settings are:

DriveSummary Determines whether ScanDisk displays full-screen
summary information after checking each drive.
The default is Auto (ScanDisk displays the summary
only if it encounters errors on that drive).

AllSummary Determines whether ScanDisk displays full-screen
summary information after checking all drives.
The default is Auto (ScanDisk displays the summary
only if it encounters errors on any drive).

Surface Determines whether ScanDisk will perform a surface scan:
Never (Default) Does not perform a surface scan.
Always Performs a surface scan without prompting first.
Prompt Prompts before performing a surface scan.
The /SURFACE command-line switch overrides this setting.

CheckHost Determines whether ScanDisk will first check a host drive
before checking any compressed drives located on that drive.
Never (Default) Does not check the host drive.
Always Checks the host drive without prompting first.
Prompt Prompts before checking the host drive.

SaveLog Determines what ScanDisk does with the repair log file:
Off (Default) Does not save the repair log.
Append Appends the log to the previous log, if any.
Overwrite Replaces the previous log with the new log.

Undo Determines whether ScanDisk creates an Undo floppy disk.
The default is Never (ScanDisk does not create an Undo
disk).
The Prompt value causes ScanDisk to prompt you for a disk.

[CUSTOM]
DriveSummary = Off Auto, On, Off
AllSummary = Off Auto, On, Off
Surface = Never Never, Always, Prompt
CheckHost = Always Never, Always, Prompt
SaveLog = Append Off, Append, Overwrite
Undo = Never Prompt, Never

The following settings determine the corrective action ScanDisk will
take if it was started with the /CUSTOM switch and finds a disk error.

The next five settings accept any of the following values:
Prompt Causes ScanDisk to prompt you before fixing this problem.
Fix Causes ScanDisk to fix the problem without prompting you.
Quit Causes ScanDisk to terminate if it encounters this problem.

DS_Header = Fix Damaged DoubleSpace volume file header
FAT_Media = Fix Missing or invalid FAT media byte
Okay_Entries = Fix Damaged, but repairable, directories/files
Bad_Chain = Fix Files or directories which should be
truncated
Crosslinks = Fix FAT-level crosslinks


The next seven settings accept any of the following values:
Prompt Causes ScanDisk to prompt you before fixing this problem.
Fix Causes ScanDisk to fix the problem without prompting you.
Quit Causes ScanDisk to terminate if it encounters this problem.
Skip Causes ScanDisk to skip fixing this problem, but continue
checking the disk.

Boot_Sector = Fix Damaged boot sector on DoubleSpace drive
FSInfo_Sector = Fix Incorrect free space count
Invalid_MDFAT = Fix Invalid MDFAT entries
DS_Crosslinks = Fix Internal (MDFAT-level) crosslinks
DS_LostClust = Fix Internal lost clusters
DS_Signatures = Fix Missing DoubleSpace volume signatures
Mismatch_FAT = Fix Mismatched FATs on non-DoubleSpace drives
Bad_Clusters = Prompt Physical damage or decompression errors


The next setting accepts any of the following values:

Prompt Causes ScanDisk to prompt you before fixing this problem.
Delete Causes ScanDisk to delete the damaged directory entries
without prompting you first.
Quit Causes ScanDisk to terminate if it encounters this problem.

Bad_Entries = Delete Damaged and irrepairable directories or
files


The next setting accepts any of the following values:

Prompt Causes ScanDisk to prompt you before fixing this problem.
Save Causes ScanDisk to save the lost clusters as files in the
root directory without prompting you first.
Delete Causes ScanDisk to delete the contents of the lost clusters
without prompting you first.
Quit Causes ScanDisk to terminate if it encounters this problem.
Skip Causes ScanDisk to skip fixing this problem, but continue
checking the disk.

LostClust = Delete Lost clusters

 

[PCR]

Rod wrote:
| "PCR" <pcrrcp@netzero.net> wrote in message
|
|> I'm not sure which setting governs that error in Scandisk.ini. Open
|> your file in Notepad, & post it, for me to take a guess. (I can't
|> readily tell looking just at mine or even at cquirke's page.) It
|> is... C:\WINDOWS\COMMAND\Scandisk.ini.
|
| I am working through your post.
| ( I hope I am not taking up too much of your valuable time PCR,

I just hope something comes of it. If not, someone else may well jump in
with more to try.

| I am near transferring to winXP and 160 Gb disk,
| Please feel free to abort advice whenever

Very likely I will continue to advise, even after you are gone & burnt
to a crisp in XP-irradiation!

| I think my disk will hold out till then.
| I find your advice interesting however.

Usually, all my best stuff is up front. More below.

| here is scandisk.ini.
|
| SCANDISK.INI
|
| This file contains settings you can use to customize the ScanDisk
| program. The settings in this file do not apply when running
| ScanDisk in Windows 95,
| unless you are checking an unmounted compressed volume file. These
| settings
| will apply if you run ScanDisk from an MS-DOS prompt in
| single-application mode.
|
|
|
| -------------------------------------------------------------------
| The [ENVIRONMENT] section contains the following settings, which
| determine general aspects of ScanDisk's behavior:
|
| Display Configures ScanDisk to run with a particular type of
| display. The default display type is Auto (ScanDisk
| adjusts to the current display).
|
| Mouse Enables or disables mouse support. The default value
| is On.
| ScanTimeOut Determines whether ScanDisk should detect disk timeouts
| while performing a surface scan. The default value is
| Off.
| NumPasses Determines how many times ScanDisk should check each
| cluster during a surface scan. The default value is 1.
|
| LabelCheck Determines whether ScanDisk should check volume labels
| for invalid characters. The default is Off.
|
| LfnCheck Activates Scandisk to validate Long File Names, if they
| exist.
| The default is ON, to check Long File Names for
| problems.
| SpaceCheck Determines whether ScanDisk should check for invalid
| spaces in filenames. The default is Off.
|
| Mount Determines whether ScanDisk will mount unmounted
| DoubleSpace drives once it has determined they are
| error-free.
|
| [ENVIRONMENT]
| Display = Auto Auto, Mono, Color, Off
| Mouse = On On, Off
| ScanTimeOut = On On, Off
| NumPasses = 1 1 through 65,535 (anything over 10 is slow)

Maybe change that figure to 5 -- (NumPasses = 5) --, which I have done
on advice from "Windows 98 Secrets" (Livingston/Straub). It is the
number of tries ScanDisk will do, before deciding there is an error.

| LabelCheck = Off On, Off
| LfnCheck = On On, Off
| SpaceCheck = Off On, Off
| Mount = Prompt Prompt, Always, Never
|
| -------------------------------------------------------------------
| The [CUSTOM] section determines ScanDisk's behavior when ScanDisk is
| started with the /CUSTOM switch. You can adjust these settings to
| create a customized "version" of ScanDisk. This can be especially
| useful for running ScanDisk from a batch file. The [CUSTOM]
| settings are:
| DriveSummary Determines whether ScanDisk displays full-screen
| summary information after checking each drive.
| The default is Auto (ScanDisk displays the summary
| only if it encounters errors on that drive).
|
| AllSummary Determines whether ScanDisk displays full-screen
| summary information after checking all drives.
| The default is Auto (ScanDisk displays the summary
| only if it encounters errors on any drive).
|
| Surface Determines whether ScanDisk will perform a surface
| scan: Never (Default) Does not perform a
| surface scan. Always Performs a surface scan
| without prompting first. Prompt Prompts before
| performing a surface scan. The /SURFACE command-line
| switch overrides this setting.
| CheckHost Determines whether ScanDisk will first check a host
| drive before checking any compressed drives located
| on that drive. Never (Default) Does not check
| the host drive. Always Checks the host drive
| without prompting first. Prompt Prompts before
| checking the host drive.
| SaveLog Determines what ScanDisk does with the repair log
| file: Off (Default) Does not save the
| repair log. Append Appends the log to the
| previous log, if any. Overwrite Replaces the
| previous log with the new log.
| Undo Determines whether ScanDisk creates an Undo floppy
| disk. The default is Never (ScanDisk does not create
| an Undo disk).
| The Prompt value causes ScanDisk to prompt you for a
| disk.
|
| [CUSTOM]
| DriveSummary = Off Auto, On, Off
| AllSummary = Off Auto, On, Off
| Surface = Never Never, Always, Prompt
| CheckHost = Always Never, Always, Prompt
| SaveLog = Append Off, Append, Overwrite
| Undo = Never Prompt, Never

Well, mine is set: Undo = Prompt

This will cause ScanDisk to ask whether to write a file to a floppy that
will enable it to undo whatever fix it does. Although I never actually
do that, some day I might-- if ever the error sounds grievous enough!
(Then again, I'd probably rather run to my full system backup than fix a
really bad partition.)

You'd want to undo the fix, if ScanDisk got it wrong as cquirke has said
it could possibly do. Then, you'd have to get disk editing software &
fix it yourself!

| The following settings determine the corrective action ScanDisk will
| take if it was started with the /CUSTOM switch and finds a disk
| error.
|
| The next five settings accept any of the following values:
| Prompt Causes ScanDisk to prompt you before fixing this
| problem. Fix Causes ScanDisk to fix the problem without
| prompting you. Quit Causes ScanDisk to terminate if it
| encounters this problem.
|
| DS_Header = Fix Damaged DoubleSpace volume file header
| FAT_Media = Fix Missing or invalid FAT media byte
| Okay_Entries = Fix Damaged, but repairable, directories/files
| Bad_Chain = Fix Files or directories which should be
truncated
| Crosslinks = Fix FAT-level crosslinks

ALL of those say to Fix! I HOPE for your sake cquirke doesn't see this!
Best go read his site, &/or make a full system backup immediately! Mine
are all set to Prompt! However, none of those can be the cause of
your...

ScanDisk found 4096 bytes of data in 1 lost file fragment(s).
Resolution: Ignore this error and continue

...., because ScanDisk would have fixed it, instead. Therefore, either
none of those govern that particular error-- or, it was not a DOS
ScanDisk that produced the report you copied out of ScanDisk.log. Can it
be you ran ScanDisk in Windows, instead?

| The next seven settings accept any of the following values:
| Prompt Causes ScanDisk to prompt you before fixing this
| problem. Fix Causes ScanDisk to fix the problem without
| prompting you. Quit Causes ScanDisk to terminate if it
| encounters this problem. Skip Causes ScanDisk to skip
| fixing this problem, but continue checking the disk.
|
| Boot_Sector = Fix Damaged boot sector on DoubleSpace
| drive FSInfo_Sector = Fix Incorrect free space count
| Invalid_MDFAT = Fix Invalid MDFAT entries
| DS_Crosslinks = Fix Internal (MDFAT-level) crosslinks
| DS_LostClust = Fix Internal lost clusters
| DS_Signatures = Fix Missing DoubleSpace volume signatures
| Mismatch_FAT = Fix Mismatched FATs on non-DoubleSpace drives
| Bad_Clusters = Prompt Physical damage or decompression errors

Same as above-- these are ALL set to Fix, except for Bad_Clusters! Going
by this page...
http://cquirke.mvps.org/9x/scandisk.htm#BadCluster

...., it just doesn't quite sound like that one is doing it. Do you
remember getting a prompt to fix it & declining?

I think, instead, you ran ScanDisk in Windows to get this result. That
one doesn't use ScanDisk.ini to decide what to do...

"START button, Run, ScanDisk, Advanced button"

In the "Lost file fragments" box, what is selected? I am bolted for
"Convert to files". Also, I am unchecked to "Automatically fix errors"
on its main requestor.

| The next setting accepts any of the following values:
|
| Prompt Causes ScanDisk to prompt you before fixing this
| problem. Delete Causes ScanDisk to delete the damaged
| directory entries without prompting you first.
| Quit Causes ScanDisk to terminate if it encounters this
| problem.
|
| Bad_Entries = Delete Damaged and irrepairable directories or
files

Best change this one to Prompt, per...
http://cquirke.mvps.org/9x/scandisk.htm#BadEntry

Then, if you see it ever happen, say a long prayer that ScanDisk got it
right &/or go running for your full system backup!

| The next setting accepts any of the following values:
|
| Prompt Causes ScanDisk to prompt you before fixing this
| problem. Save Causes ScanDisk to save the lost clusters as
| files in the root directory without prompting you
| first. Delete Causes ScanDisk to delete the contents of the
| lost clusters without prompting you first.
| Quit Causes ScanDisk to terminate if it encounters this
| problem. Skip Causes ScanDisk to skip fixing this problem,
| but continue checking the disk.
|
| LostClust = Delete Lost clusters

http://cquirke.mvps.org/9x/scandisk.htm#LostCluster

Usually, it is OK to delete those, but go read that site!

--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR
pcrrcp@netzero.net

 

[Rod]

"PCR" <pcrrcp@netzero.net> wrote in message

> ..., because ScanDisk would have fixed it, instead. Therefore, either
> none of those govern that particular error-- or, it was not a DOS
> ScanDisk that produced the report you copied out of ScanDisk.log. Can it
> be you ran ScanDisk in Windows, instead?

Of course, what elese is there
I run endit all then scan disk.

I am reading Mr. Quirke.

 

[Rod]

"PCR" <pcrrcp@netzero.net> wrote in message


> http://cquirke.mvps.org/9x/scandisk.htm

Aha! herein lies my fault source

FSInfo_Sector: Incorrect free space count
This problem is trivial for ScanDisk to fix safely. Because
the FAT32 File Allocation Tables can be large and thus
slow to scan, Windows keeps a record of the free space
capacity cached within the FAT32 volume boot record for
quick reference. Because this value is updated on a
now-and-then basis, it often differs from the true free space
as deduced from the state of the FAT itself, if the system
suffers a bad exit from Windows. That is why this problem
is often seen after the system crashes, restarts, or is
switched off while running Windows.

My system regularly crashes, something to do with memory
I think, a small 6Gb Hdd and the number of images I regularly
deal with, magazine scanning etc.
I trust this ,<trivial error> will end with my new XP system.

 

[PCR]

Rod wrote:
| "PCR" <pcrrcp@netzero.net> wrote in message
|
|
|> http://cquirke.mvps.org/9x/scandisk.htm
|
| Aha! herein lies my fault source
|
| FSInfo_Sector: Incorrect free space count
| This problem is trivial for ScanDisk to fix safely. Because
| the FAT32 File Allocation Tables can be large and thus
| slow to scan, Windows keeps a record of the free space
| capacity cached within the FAT32 volume boot record for
| quick reference. Because this value is updated on a
| now-and-then basis, it often differs from the true free space
| as deduced from the state of the FAT itself, if the system
| suffers a bad exit from Windows. That is why this problem
| is often seen after the system crashes, restarts, or is
| switched off while running Windows.
|
| My system regularly crashes, something to do with memory
| I think, a small 6Gb Hdd and the number of images I regularly
| deal with, magazine scanning etc.
| I trust this ,<trivial error> will end with my new XP system.

That explains one of them, but not...

ScanDisk found 4096 bytes of data in 1 lost file fragment(s).
Resolution: Ignore this error and continue

Rod wrote:
| "PCR" <pcrrcp@netzero.net> wrote in message
|
|> ..., because ScanDisk would have fixed it, instead. Therefore, either
|> none of those govern that particular error-- or, it was not a DOS
|> ScanDisk that produced the report you copied out of ScanDisk.log.
|> Can it be you ran ScanDisk in Windows, instead?
|
| Of course, what elese is there

The other one is DOS ScanDisk, which may run automatically at boot after
a bad shutdown. However, clearly it wasn't that.

| I run endit all then scan disk.

Very good. That explains it. So...

"START button, Run, ScanDisk, Advanced button"

In the "Lost file fragments" box, bolt "Convert to files". Also, uncheck
"Automatically fix errors" on its main requestor.

| I am reading Mr. Quirke.

Very good! Adjust your ScanDisk.ini accordingly! Post your new
ScanDisk.ini after you are through for examination.