Chkdsk Reports Nonexistent Errors

> This is leading me to suspect that CHKDSK may be erroneously reporting
> errors that do not really exist.

Running chkdsk in read-only mode will do that.

Don't even bother running CHKDSK in read-only mode. It is a waste of time
and prone to not accurately reporting information. CHKDSK might report
spurious errors because it cannot lock the drive.

"Chkdsk might not accurately report information in read-only mode."
From...
Chkdsk
http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit...-us/Def

<quote>
If you run chkdsk without the /f command-line option on an active
partition, it might report spurious errors because it cannot lock the
drive.
<quote>

<quote>
Using chkdsk with open files
If you specify the /f command-line option, chkdsk sends an error message if
there are open files on the disk. If you do not specify the /f command-line
option and open files exist, chkdsk might report lost allocation units on
the disk. This could happen if open files have not yet been recorded in the
file allocation table. If chkdsk reports the loss of a large number of
allocation units, consider repairing the disk.
<quote>
From...
Chkdsk
http://www.microsoft.com/resources/documentation/windows/xp/all/proddo...en-us/c

<quote>
In read-only mode, CHKDSK quits before it completes all three phases if it
encounters errors in earlier phases, and CHKDSK is prone to falsely
reporting errors. For example, CHKDSK may report disk corruption if NTFS
happens to modify areas of a disk while CHKDSK is examining the disk. For
correct verification, a volume must be static, and the only way to guarantee
a static state is to lock the volume. CHKDSK locks the volume only if you
specify the /F switch (or the /R switch, which implies /F). You may need to
run CHKDSK more than once to get CHKDSK to complete all its passes
in read-only mode.
<quote>
From...
An Explanation of the New C and I Switches That Are Available to Use with
Chkdsk.exe
http://support.microsoft.com/kb/314835
------------------

For a look at the chkdsk log.

Open the Event Viewer...
Start | Run | Type: eventvwr | Click OK |
Look in Application | Listed as Information |
Event ID: 1001
Source: Winlogon
[[Description: This includes file system type; drive letter or GUID, and
volume name or serial number to help determine what volume Chkdsk ran
against. Also included is whether Chkdsk ran because a user scheduled it or
because the dirty bit was set.]]

[[When Autochk runs against a volume at boot time it records its output to a
file called Bootex.log in the root of the volume being checked. The Winlogon
service then moves the contents of each Bootex.log file to the Application
Event log.]]

[[This file states whether Chkdsk encountered any errors and, if so,
whether they were fixed.]]
------------

Reading a chkdsk log

chkdsk log will be similar to this...

Checking file system on C:
The type of the file system is NTFS.
Volume label is Local Disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 10 unused index entries from index $SII of file 0x9.
Cleaning up 10 unused index entries from index $SDH of file 0x9.
Cleaning up 10 unused security descriptors.

4096543 KB total disk space.
2906360 KB in 19901 files.
6344 KB in 1301 indexes.
0 KB in bad sectors.
49379 KB in use by the system.
22544 KB occupied by the log file.
1134460 KB available on disk.

4096 bytes in each allocation unit.
1024135 total allocation units on disk.
283615 allocation units available on disk.

It is housecleaning and housecleaning is going to happen if you run
chkdsk.exe. Think Merry Maids with brooms.

> Cleaning up minor inconsistencies on the drive.

[[In the above error message, "minor inconsistencies" refers to a state
where redundant information stored in different places is "out of synch."
This is a natural and expected condition whenever there are open files on
the volume that have undergone modification. The redundant information is
not brought into synchronization until the files are closed. Typically, this
error message occurs when CHKDSK is run against the volume containing
Windows NT system files (including active user profiles and the pagefile).

WORKAROUND
You can usually safely ignore this error message even if the message appears
without there being open files, because it is only the redundant information
that is out of synchronization. The only side effect you may see as a result
of this message is an incorrect reading of free disk space or something
similar. ]]
from...
"CHKDSK detected minor inconsistencies" error message in Windows 2000 and in
Windows NT
http://support.microsoft.com/kb/109524

> Cleaning up 10 unused index entries from index $SII of file 0x9.
> Cleaning up 10 unused index entries from index $SDH of file 0x9.

[[Chkdsk.exe reports only unused index and security descriptor entries that
were removed. ]]
[[Chkdsk.exe just reclaims the unused security descriptors as a housekeeping
activity, and it does not actually fix any kind of problem. ]]
from...
Windows 2000 Chkdsk Reports Cleaning Unused Security Descriptors
http://support.microsoft.com/kb/255008

> Cleaning up 10 unused security descriptors.

[[When you delete a file or folder with permissions that you've set by hand
rather than allowed to be automatically inherited from its parent, the ACL
(Access Control List, the security descriptor) isn't deleted, but cached.
Running CHKDSK against these "dead" items cleans up the ACLs that are no
longer in use and frees up space. ]]
from...
Tip: Don't Panic At CHKDSK "Security Descriptor" Cleanup
http://www.winmag.com/columns/powerw2k/2000/46.htm#tip

[[This problem occurs because if Chkdsk is run against an NTFS volume,
Chkdsk.exe may report that security descriptors are in the database that are
no longer referenced by any file or folder and that it is removing them.
However, Chkdsk.exe just reclaims the unused security descriptors as a
housekeeping activity, and it does not actually fix any kind of problem. ]]
from...
Windows 2000 Chkdsk Reports Cleaning Unused Security Descriptors
http://support.microsoft.com/kb/255008

[[4096543 KB total disk space.
(This value is the total formatted disk capacity.)

2906360 KB in 19901 files.
(This value is the space used by user file data.)

6344 KB in 1301 indexes.
(This value is the space used by NTFS indexes.)

0 KB in bad sectors.
(This value is the space lost to bad sectors.)

49379 KB in use by the system.
(This value is includes MFT and other NTFS metafiles.)

22544 KB occupied by the log file.
(This value is the NTFS Log file; you use the chkdsk /l:size to adjust this
value.)

1134460 KB available on disk.
(This value is the available FREE disk space.)

4096 bytes in each allocation unit.
(This value is the cluster size [4K])

1024135 total allocation units on disk.
(This value is the total clusters on disk.)

283615 allocation units available on disk.
(This value is the available free clusters.) ]]
from...
How to locate and correct disk space problems on NTFS volumes in Windows XP
http://support.microsoft.com/kb/315688

See also...
Understanding what CHKDSK does
here...

An explanation of the new /C and /I Switches that are available to use with
Chkdsk.exe
http://support.microsoft.com/kb/314835

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In news:Rq6dnXdjbKFtT4TbnZ2dnUVZ_vmqnZ2d@comcast.com,
M and D <m.and.d DeleteThis @news.invalid> hunted and pecked:
> A follow-up to my original post:
>
> According to the MSKB article I cited in my original post: "This problem
> occurs because the Chkdsk utility may not find references to all the
> security IDs if the master file table is larger than 4 gigabytes (GB) or
> if there are more than 4,194,303 files on the volume."
>
> I just finished running Windows Defragmenter on my C:\ drive, because I
> remembered that the report it provides at the conclusion of a defrag
> includes the size of the master file table and total number of files on
> the volume. The results are as follows:
>
> Total MFT size: 65MB -- nowhere near 4GB! [76% of the MFT is in use]
> Total number of files: 47,120 -- nowhere near 4 million!
>
> This is leading me to suspect that CHKDSK may be erroneously reporting
> errors that do not really exist.
>
> In any case, as I said at the outset, " I am way out of my league on this
> one" so I really hope someone can help me out here. And thanks for
> reading thus far.
>
> M and D
>
> "M and D" <m.and.d DeleteThis @news.invalid> wrote in message
> news:x9SdnVq-1sSf0ITbnZ2dnUVZ_uGjnZ2d@comcast.com...
> Folks, I am way out of my league on this one so I really hope someone can
> help.
>
> My C:\ drive has the problem described in "The CHKDSK utility incorrectly
> identifies and deletes in-use security descriptors" [MSKB 831374]:
> http://support.microsoft.com/kb/831374
>
> I believe this to be true since my symptoms are identical to the symptoms
> described in the article.
>
> A bit of background:
> I ran CHKDSK on my C:\ drive at reboot. The second stage ("CHKDSK is
> verifying indexes") took several minutes to complete, so I figured
> something was wrong. When Windows re-started I ran CHKDSK in read-only to
> see if my C:\ drive was now free of errors. No, said CHKDSK, your drive
> still has errors, run CHKDSK again at reboot. So I ran CHKDSK again at
> reboot, and again the second stage took several minutes to complete, and
> when Windows re-started I again ran CHKDSK in read only, and again CHKDSK
> said 'you still have errors, run CHKDSK at restart'....
>
> This went on and on. After the fifth time of running CHKDSK at bootup I
> decided to look at Event Viewer, and that's where I saw exactly the
> symptoms reported in the above MSKB article.
>
> According to the article: "This problem occurs because the Chkdsk utility
> may not find references to all the security IDs if the master file table
> is larger than 4 gigabytes (GB) or if there are more than 4,194,303 files
> on the volume. Therefore, the undiscovered security descriptors are
> reset."
>
> I don't understand most of that, but I'm very sure that I have /way/ less
> than 4 million files on my C:\ drive. I don't know how to check if my
> master file table is really larger than 4 gigabytes.
>
> The recommended resolution is to "obtain the latest service pack for
> Windows XP", but I am completely up to date at Microsoft Update.
>
> I'm really at a loss. What do I do about this?
>
> M and D

Try running CHKDSK from the XP recovery console, instead of from within XP
itself. This should avoid problems with locked files, since the recovery
console is outside of windows.

You can run the recovery console from (1) XP CDROM, (2) downloadable floppy
set, called setup disks, free from Microsoft, (3) by installing it on the
hard drive. See the following links for more infomation about the recovery
console:

http://www.kellys-korner-xp.com/win_xp_rec.htm



http://www.wown.com/j_helmig/wxprcons.htm



http://www.xxcopy.com/xxcopy33.htm (near bottom)



http://www.webtree.ca/windowsxp/repair_xp.htm (about number 26 in list)



Note that inside the recovery console the options for CHKDSK are slightly
different than within windows. Specifically, use /P to force a check,
without any fixing. Use /R (not /F) to check and fix. /R also checks the
free space on the disk, so be patient.



"M and D" <m.and.d.RemoveThis@news.invalid> wrote in message
news:x9SdnVq-1sSf0ITbnZ2dnUVZ_uGjnZ2d@comcast.com...
Folks, I am way out of my league on this one so I really hope someone can
help.

My C:\ drive has the problem described in "The CHKDSK utility incorrectly
identifies and deletes in-use security descriptors" [MSKB 831374]:
http://support.microsoft.com/kb/831374

I believe this to be true since my symptoms are identical to the symptoms
described in the article.

A bit of background:
I ran CHKDSK on my C:\ drive at reboot. The second stage ("CHKDSK is
verifying indexes") took several minutes to complete, so I figured something
was wrong. When Windows re-started I ran CHKDSK in read-only to see if my
C:\ drive was now free of errors. No, said CHKDSK, your drive still has
errors, run CHKDSK again at reboot. So I ran CHKDSK again at reboot, and
again the second stage took several minutes to complete, and when Windows
re-started I again ran CHKDSK in read only, and again CHKDSK said 'you still
have errors, run CHKDSK at restart'....

This went on and on. After the fifth time of running CHKDSK at bootup I
decided to look at Event Viewer, and that's where I saw exactly the symptoms
reported in the above MSKB article.

According to the article: "This problem occurs because the Chkdsk utility
may not find references to all the security IDs if the master file table is
larger than 4 gigabytes (GB) or if there are more than 4,194,303 files on
the volume. Therefore, the undiscovered security descriptors are reset."

I don't understand most of that, but I'm very sure that I have /way/ less
than 4 million files on my C:\ drive. I don't know how to check if my master
file table is really larger than 4 gigabytes.

The recommended resolution is to "obtain the latest service pack for Windows
XP", but I am completely up to date at Microsoft Update.

I'm really at a loss. What do I do about this?

M and D

Hi Bob. Thanks very much for your suggestion. The thing is that my XP CD is the original gold release and I'm now at SP 2. When I run CHKDSK at bootup I believe it's running before Windows loads.

Nonetheless this is a good reminder to me to fashion a slipstreamed Windows CD in case I should need one in future.

M and D


"Bob Harris" <rharris270[SPAM]@hotmail.com> wrote in message news:eiZvbtweHHA.1388@TK2MSFTNGP05.phx.gbl...
> Try running CHKDSK from the XP recovery console, instead of from within XP
> itself. This should avoid problems with locked files, since the recovery
> console is outside of windows.
>
> You can run the recovery console from (1) XP CDROM, (2) downloadable floppy
> set, called setup disks, free from Microsoft, (3) by installing it on the
> hard drive. See the following links for more infomation about the recovery
> console:
>
> http://www.kellys-korner-xp.com/win_xp_rec.htm
>
>
>
> http://www.wown.com/j_helmig/wxprcons.htm
>
>
>
> http://www.xxcopy.com/xxcopy33.htm (near bottom)
>
>
>
> http://www.webtree.ca/windowsxp/repair_xp.htm (about number 26 in list)
>
>
>
> Note that inside the recovery console the options for CHKDSK are slightly
> different than within windows. Specifically, use /P to force a check,
> without any fixing. Use /R (not /F) to check and fix. /R also checks the
> free space on the disk, so be patient.
>
>
>
> "M and D" <m.and.d.TakeThisOut@news.invalid> wrote in message
> news:x9SdnVq-1sSf0ITbnZ2dnUVZ_uGjnZ2d@comcast.com...
> Folks, I am way out of my league on this one so I really hope someone can
> help.
>
> My C:\ drive has the problem described in "The CHKDSK utility incorrectly
> identifies and deletes in-use security descriptors" [MSKB 831374]:
> http://support.microsoft.com/kb/831374
>
> I believe this to be true since my symptoms are identical to the symptoms
> described in the article.
>
> A bit of background:
> I ran CHKDSK on my C:\ drive at reboot. The second stage ("CHKDSK is
> verifying indexes") took several minutes to complete, so I figured something
> was wrong. When Windows re-started I ran CHKDSK in read-only to see if my
> C:\ drive was now free of errors. No, said CHKDSK, your drive still has
> errors, run CHKDSK again at reboot. So I ran CHKDSK again at reboot, and
> again the second stage took several minutes to complete, and when Windows
> re-started I again ran CHKDSK in read only, and again CHKDSK said 'you still
> have errors, run CHKDSK at restart'....
>
> This went on and on. After the fifth time of running CHKDSK at bootup I
> decided to look at Event Viewer, and that's where I saw exactly the symptoms
> reported in the above MSKB article.
>
> According to the article: "This problem occurs because the Chkdsk utility
> may not find references to all the security IDs if the master file table is
> larger than 4 gigabytes (GB) or if there are more than 4,194,303 files on
> the volume. Therefore, the undiscovered security descriptors are reset."
>
> I don't understand most of that, but I'm very sure that I have /way/ less
> than 4 million files on my C:\ drive. I don't know how to check if my master
> file table is really larger than 4 gigabytes.
>
> The recommended resolution is to "obtain the latest service pack for Windows
> XP", but I am completely up to date at Microsoft Update.
>
> I'm really at a loss. What do I do about this?
>
> M and D
>
>
>
>
>

On Mon, 9 Apr 2007 12:43:03 -0600, "Wesley Vogel"

>Don't even bother running CHKDSK in read-only mode. It is a waste of time
>and prone to not accurately reporting information. CHKDSK might report
>spurious errors because it cannot lock the drive.

I just love the logic here.

Because ChkDsk makes mistakes when run with the safety catch on, you
should run it with the safety catch off.

What would be more useful (as long as one is forced to live with tool
designs that pre-date MS-DOS 6) is to force ChkDsk to run on boot, as
if it was run with /F, so that it could report more accurately without
irreversibly blowing things up if it gets things wrong.

But it can't, because what runs at boot is not ChkDsk, but the even
more brain-dead AutoChk that can't run without "fixing".



>-------------------- ----- ---- --- -- - - - -
Hmmm... what was the *other* idea?
>-------------------- ----- ---- --- -- - - - -

> Because ChkDsk makes mistakes when run with the safety catch on, you
> should run it with the safety catch off.

Or do not run it at all.

Hey Chris,

You ever heard of The Creaking Door?

I download a lot of old radio programs and burn them to CD. I do not watch
TV. Nobody seems to know much about The Creaking Door. I listened to a
couple of episodes last night and thought that they were pretty good. The
Creaking Door was sponsored by State Express 555 (pronounced State Express
Three Fives) cigarettes, which Google tells me still exists.

''The Creaking Door was an old-time radio series of horror and suspense
shows originating in South Africa.

There are at present anywhere from 34-37 extant episodes in MP3 circulation,
yet no currently available program logs for the series indicate the year of
the series' broadcast (though it was likely sometime in the 1950s, given the
generally high audio quality of the available shows), or the total number of
episodes, and only a handful of them are known by their broadcast order.
The stories are thrillers in the Inner Sanctum vein, and generally thought
of favorably by most fans of Old Time Radio."

"In 1964, South Africa began The Creaking Door, using original scripts which
included stories with a heavy emphasis on the supernatural. The topics
ranged from haunted houses to a woman who turns into a giant cat, and of
course, the typical paranoid murderer so often presented on the original
Inner Sanctum. The host for this series was Peter Bloomfield.''

Free Old time Radio Shows - The Creaking Door
Click on the Links below to listen for free online:
http://www.radiolovers.com/pages/creakingdoor.htm

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In news:r8cl13901g3fdv0h7oimg7282en8bt90l7@4ax.com,
cquirke (MVP Windows shell/user) <cquirkenews RemoveThis @nospam.mvps.org> hunted and
pecked:
> On Mon, 9 Apr 2007 12:43:03 -0600, "Wesley Vogel"
>
>> Don't even bother running CHKDSK in read-only mode. It is a waste of
>> time and prone to not accurately reporting information. CHKDSK might
>> report spurious errors because it cannot lock the drive.
>
> I just love the logic here.
>
> Because ChkDsk makes mistakes when run with the safety catch on, you
> should run it with the safety catch off.
>
> What would be more useful (as long as one is forced to live with tool
> designs that pre-date MS-DOS 6) is to force ChkDsk to run on boot, as
> if it was run with /F, so that it could report more accurately without
> irreversibly blowing things up if it gets things wrong.
>
> But it can't, because what runs at boot is not ChkDsk, but the even
> more brain-dead AutoChk that can't run without "fixing".
>
>
>
>> -------------------- ----- ---- --- -- - - - -
> Hmmm... what was the *other* idea?
>> -------------------- ----- ---- --- -- - - - -

Thank you sincerely for responding to my posts.

Evidentally we've been reading the same articles in our research.

I understand and accept that CHKDSK in read-only mode can produce erroneous conclusions. I also understand some - okay, a little bit - of the housekeeping that Windows performs on the NTFS file system. I'm almost ready to drop my concerns and go merrily on my way, except for one thing:

When I've run CHKDSK /f in the past, the second stage ("CHKDSK is verifying indexes") took only seconds to complete. Now the progress indicator is stuck at 0% for almost a minute while my disk is grinding away, and then it progresses swiftly to 100% and CHKDSK goes on normally. And this now happens everytime I run CHKDSK. /Something/ is going on during that minute of grinding, and that's what concerns me.

From what I've read on the web, the messages I see in Event Viewer...here's a typical example:

Cleaning up 2 unused index entries from index $SII of file 0x9.
Cleaning up 2 unused index entries from index $SDH of file 0x9.
Cleaning up 2 unused security descriptors.

....are either completely normal /or/ they're a sign that my NTFS file system is corrupted and my disk is nearing death. That uncertainty and the minute of disk grinding leave me unsure of what to do.

I'd really appreciate your advice.

M and D

"Wesley Vogel" <123WVogel955.DeleteThis@comcast.net> wrote in message news:urqaDLweHHA.5044@TK2MSFTNGP05.phx.gbl...
>> Because ChkDsk makes mistakes when run with the safety catch on, you
>> should run it with the safety catch off.
>
> Or do not run it at all.
>
> Hey Chris,
>
> You ever heard of The Creaking Door?
>
> I download a lot of old radio programs and burn them to CD. I do not watch
> TV. Nobody seems to know much about The Creaking Door. I listened to a
> couple of episodes last night and thought that they were pretty good. The
> Creaking Door was sponsored by State Express 555 (pronounced State Express
> Three Fives) cigarettes, which Google tells me still exists.
>
> ''The Creaking Door was an old-time radio series of horror and suspense
> shows originating in South Africa.
>
> There are at present anywhere from 34-37 extant episodes in MP3 circulation,
> yet no currently available program logs for the series indicate the year of
> the series' broadcast (though it was likely sometime in the 1950s, given the
> generally high audio quality of the available shows), or the total number of
> episodes, and only a handful of them are known by their broadcast order.
> The stories are thrillers in the Inner Sanctum vein, and generally thought
> of favorably by most fans of Old Time Radio."
>
> "In 1964, South Africa began The Creaking Door, using original scripts which
> included stories with a heavy emphasis on the supernatural. The topics
> ranged from haunted houses to a woman who turns into a giant cat, and of
> course, the typical paranoid murderer so often presented on the original
> Inner Sanctum. The host for this series was Peter Bloomfield.''
>
> Free Old time Radio Shows - The Creaking Door
> Click on the Links below to listen for free online:
> http://www.radiolovers.com/pages/creakingdoor.htm
>
> --
> Hope this helps. Let us know.
>
> Wes
> MS-MVP Windows Shell/User
>
> In news:r8cl13901g3fdv0h7oimg7282en8bt90l7@4ax.com,
> cquirke (MVP Windows shell/user) <cquirkenews.DeleteThis@nospam.mvps.org> hunted and
> pecked:
>> On Mon, 9 Apr 2007 12:43:03 -0600, "Wesley Vogel"
>>
>>> Don't even bother running CHKDSK in read-only mode. It is a waste of
>>> time and prone to not accurately reporting information. CHKDSK might
>>> report spurious errors because it cannot lock the drive.
>>
>> I just love the logic here.
>>
>> Because ChkDsk makes mistakes when run with the safety catch on, you
>> should run it with the safety catch off.
>>
>> What would be more useful (as long as one is forced to live with tool
>> designs that pre-date MS-DOS 6) is to force ChkDsk to run on boot, as
>> if it was run with /F, so that it could report more accurately without
>> irreversibly blowing things up if it gets things wrong.
>>
>> But it can't, because what runs at boot is not ChkDsk, but the even
>> more brain-dead AutoChk that can't run without "fixing".
>>
>>
>>
>>> -------------------- ----- ---- --- -- - - - -
>> Hmmm... what was the *other* idea?
>>> -------------------- ----- ---- --- -- - - - -
>
>

M and D,

> Cleaning up 2 unused index entries from index $SII of file 0x9.
> Cleaning up 2 unused index entries from index $SDH of file 0x9.

[[Chkdsk.exe just reclaims the unused security descriptors as a housekeeping
activity, and it does not actually fix any kind of problem. ]]

> Cleaning up 2 unused security descriptors.

[[Chkdsk.exe just reclaims the unused security descriptors as a
housekeeping activity, and it does not actually fix any kind of problem. ]]

Is normal. I think there is much ado about nothing. Meaning I do not think
you have any problem whatsoever.

Here are some chkdsk log samples that I have saved. Notice the 0 KB in bad
sectors. parts

Date: 12/4/2004
Checking file system on C:
The type of the file system is NTFS.
Volume label is Local Disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 10 unused index entries from index $SII of file 0x9.
Cleaning up 10 unused index entries from index $SDH of file 0x9.
Cleaning up 10 unused security descriptors.

9952235 KB total disk space.
6020596 KB in 40720 files.
15248 KB in 2053 indexes.
0 KB in bad sectors.
102811 KB in use by the system.
51824 KB occupied by the log file.
3813580 KB available on disk.

4096 bytes in each allocation unit.
2488058 total allocation units on disk.
953395 allocation units available on disk.

Date: 10/31/2005
Checking file system on C:
The type of the file system is NTFS.
Volume label is Local Disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 10 unused index entries from index $SII of file 0x9.
Cleaning up 10 unused index entries from index $SDH of file 0x9.
Cleaning up 10 unused security descriptors.
CHKDSK is verifying file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.

9952235 KB total disk space.
8294548 KB in 45987 files.
18368 KB in 2270 indexes.
0 KB in bad sectors.
106159 KB in use by the system.
51824 KB occupied by the log file.
1533160 KB available on disk.

4096 bytes in each allocation unit.
2488058 total allocation units on disk.
383290 allocation units available on disk.

Date: 02/05/2006
Checking file system on C:
The type of the file system is NTFS.
Volume label is Local Disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 8 unused index entries from index $SII of file 0x9.
Cleaning up 8 unused index entries from index $SDH of file 0x9.
Cleaning up 8 unused security descriptors.
CHKDSK is verifying file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.

9952235 KB total disk space.
7967676 KB in 45429 files.
18224 KB in 2251 indexes.
0 KB in bad sectors.
106179 KB in use by the system.
51824 KB occupied by the log file.
1860156 KB available on disk.

4096 bytes in each allocation unit.
2488058 total allocation units on disk.
465039 allocation units available on disk.

I bought a new machine with a hard drive @ 232 GB not 9.49 GB and this is
from the new machine.

Date: 31/Mar/07
Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 79 unused index entries from index $SII of file 0x9.
Cleaning up 79 unused index entries from index $SDH of file 0x9.
Cleaning up 79 unused security descriptors.
CHKDSK is verifying file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.

244187968 KB total disk space.
11322912 KB in 53772 files.
20504 KB in 3070 indexes.
0 KB in bad sectors.
134204 KB in use by the system.
65536 KB occupied by the log file.
232710348 KB available on disk.

4096 bytes in each allocation unit.
61046992 total allocation units on disk.
58177587 allocation units available on disk.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In news:4rqdnXy-mZ4QeYfbnZ2dnUVZ_silnZ2d@comcast.com,
M and D <m.and.d RemoveThis @news.invalid> hunted and pecked:
> Thank you sincerely for responding to my posts.
>
> Evidentally we've been reading the same articles in our research.
>
> I understand and accept that CHKDSK in read-only mode can produce
> erroneous conclusions. I also understand some - okay, a little bit - of
> the housekeeping that Windows performs on the NTFS file system. I'm
> almost ready to drop my concerns and go merrily on my way, except for one
> thing:
>
> When I've run CHKDSK /f in the past, the second stage ("CHKDSK is
> verifying indexes") took only seconds to complete. Now the progress
> indicator is stuck at 0% for almost a minute while my disk is grinding
> away, and then it progresses swiftly to 100% and CHKDSK goes on normally.
> And this now happens everytime I run CHKDSK. /Something/ is going on
> during that minute of grinding, and that's what concerns me.
>
> From what I've read on the web, the messages I see in Event
> Viewer...here's a typical example:
>
> Cleaning up 2 unused index entries from index $SII of file 0x9.
> Cleaning up 2 unused index entries from index $SDH of file 0x9.
> Cleaning up 2 unused security descriptors.
>
> ...are either completely normal /or/ they're a sign that my NTFS file
> system is corrupted and my disk is nearing death. That uncertainty and
> the minute of disk grinding leave me unsure of what to do.
>
> I'd really appreciate your advice.
>
> M and D
>
> "Wesley Vogel" <123WVogel955 RemoveThis @comcast.net> wrote in message
> news:urqaDLweHHA.5044@TK2MSFTNGP05.phx.gbl...
>>> Because ChkDsk makes mistakes when run with the safety catch on, you
>>> should run it with the safety catch off.
>>
>> Or do not run it at all.
>>
>> Hey Chris,
>>
>> You ever heard of The Creaking Door?
>>
>> I download a lot of old radio programs and burn them to CD. I do not
>> watch TV. Nobody seems to know much about The Creaking Door. I
>> listened to a couple of episodes last night and thought that they were
>> pretty good. The Creaking Door was sponsored by State Express 555
>> (pronounced State Express Three Fives) cigarettes, which Google tells me
>> still exists.
>>
>> ''The Creaking Door was an old-time radio series of horror and suspense
>> shows originating in South Africa.
>>
>> There are at present anywhere from 34-37 extant episodes in MP3
>> circulation, yet no currently available program logs for the series
>> indicate the year of the series' broadcast (though it was likely
>> sometime in the 1950s, given the generally high audio quality of the
>> available shows), or the total number of episodes, and only a handful of
>> them are known by their broadcast order. The stories are thrillers in
>> the Inner Sanctum vein, and generally thought of favorably by most fans
>> of Old Time Radio."
>>
>> "In 1964, South Africa began The Creaking Door, using original scripts
>> which included stories with a heavy emphasis on the supernatural. The
>> topics ranged from haunted houses to a woman who turns into a giant cat,
>> and of course, the typical paranoid murderer so often presented on the
>> original Inner Sanctum. The host for this series was Peter Bloomfield.''
>>
>> Free Old time Radio Shows - The Creaking Door
>> Click on the Links below to listen for free online:
>> http://www.radiolovers.com/pages/creakingdoor.htm
>>
>> --
>> Hope this helps. Let us know.
>>
>> Wes
>> MS-MVP Windows Shell/User
>>
>> In news:r8cl13901g3fdv0h7oimg7282en8bt90l7@4ax.com,
>> cquirke (MVP Windows shell/user) <cquirkenews RemoveThis @nospam.mvps.org> hunted and
>> pecked:
>>> On Mon, 9 Apr 2007 12:43:03 -0600, "Wesley Vogel"
>>>
>>>> Don't even bother running CHKDSK in read-only mode. It is a waste of
>>>> time and prone to not accurately reporting information. CHKDSK might
>>>> report spurious errors because it cannot lock the drive.
>>>
>>> I just love the logic here.
>>>
>>> Because ChkDsk makes mistakes when run with the safety catch on, you
>>> should run it with the safety catch off.
>>>
>>> What would be more useful (as long as one is forced to live with tool
>>> designs that pre-date MS-DOS 6) is to force ChkDsk to run on boot, as
>>> if it was run with /F, so that it could report more accurately without
>>> irreversibly blowing things up if it gets things wrong.
>>>
>>> But it can't, because what runs at boot is not ChkDsk, but the even
>>> more brain-dead AutoChk that can't run without "fixing".
>>>
>>>
>>>
>>>> -------------------- ----- ---- --- -- - - - -
>>> Hmmm... what was the *other* idea?
>>>> -------------------- ----- ---- --- -- - - - -

Hi again Wesley,

I believe that "0 KB in bad sectors" refers to the surface of the disk, whereas the reports I am seeing in Event Viewer refer to logical errors.

Nonetheless, I've concluded that I really am seeing nothing more than Windows XP internal housekeeping, so I'm not going to worry any more.

As for my concern that CHKDSK didn't in the past make my hard disk grind away for a minute or so during "CHKDSK is verifying indexes"...I haven't run CHKDSK in a long, long time during which I've installed lots of updates from Microsoft Update, so perhaps that behavior is typical for Windows XP nowadays.

Thanks very much for investing so much of your time to help me out. I do appreciate it. Enjoy your new computer.

M and D
(That's 'Mom and Dad' - I'm Dad.)


"Wesley Vogel" <123WVogel955.RemoveThis@comcast.net> wrote in message news:e%23h22GxeHHA.284@TK2MSFTNGP05.phx.gbl...
>M and D,
>
>> Cleaning up 2 unused index entries from index $SII of file 0x9.
>> Cleaning up 2 unused index entries from index $SDH of file 0x9.
>
> [[Chkdsk.exe just reclaims the unused security descriptors as a housekeeping
> activity, and it does not actually fix any kind of problem. ]]
>
>> Cleaning up 2 unused security descriptors.
>
> [[Chkdsk.exe just reclaims the unused security descriptors as a
> housekeeping activity, and it does not actually fix any kind of problem. ]]
>
> Is normal. I think there is much ado about nothing. Meaning I do not think
> you have any problem whatsoever.
>
> Here are some chkdsk log samples that I have saved. Notice the 0 KB in bad
> sectors. parts
>
> Date: 12/4/2004
> Checking file system on C:
> The type of the file system is NTFS.
> Volume label is Local Disk.
> Cleaning up minor inconsistencies on the drive.
> Cleaning up 10 unused index entries from index $SII of file 0x9.
> Cleaning up 10 unused index entries from index $SDH of file 0x9.
> Cleaning up 10 unused security descriptors.
>
> 9952235 KB total disk space.
> 6020596 KB in 40720 files.
> 15248 KB in 2053 indexes.
> 0 KB in bad sectors.
> 102811 KB in use by the system.
> 51824 KB occupied by the log file.
> 3813580 KB available on disk.
>
> 4096 bytes in each allocation unit.
> 2488058 total allocation units on disk.
> 953395 allocation units available on disk.
>
> Date: 10/31/2005
> Checking file system on C:
> The type of the file system is NTFS.
> Volume label is Local Disk.
> Cleaning up minor inconsistencies on the drive.
> Cleaning up 10 unused index entries from index $SII of file 0x9.
> Cleaning up 10 unused index entries from index $SDH of file 0x9.
> Cleaning up 10 unused security descriptors.
> CHKDSK is verifying file data (stage 4 of 5)...
> File data verification completed.
> CHKDSK is verifying free space (stage 5 of 5)...
> Free space verification is complete.
>
> 9952235 KB total disk space.
> 8294548 KB in 45987 files.
> 18368 KB in 2270 indexes.
> 0 KB in bad sectors.
> 106159 KB in use by the system.
> 51824 KB occupied by the log file.
> 1533160 KB available on disk.
>
> 4096 bytes in each allocation unit.
> 2488058 total allocation units on disk.
> 383290 allocation units available on disk.
>
> Date: 02/05/2006
> Checking file system on C:
> The type of the file system is NTFS.
> Volume label is Local Disk.
> Cleaning up minor inconsistencies on the drive.
> Cleaning up 8 unused index entries from index $SII of file 0x9.
> Cleaning up 8 unused index entries from index $SDH of file 0x9.
> Cleaning up 8 unused security descriptors.
> CHKDSK is verifying file data (stage 4 of 5)...
> File data verification completed.
> CHKDSK is verifying free space (stage 5 of 5)...
> Free space verification is complete.
>
> 9952235 KB total disk space.
> 7967676 KB in 45429 files.
> 18224 KB in 2251 indexes.
> 0 KB in bad sectors.
> 106179 KB in use by the system.
> 51824 KB occupied by the log file.
> 1860156 KB available on disk.
>
> 4096 bytes in each allocation unit.
> 2488058 total allocation units on disk.
> 465039 allocation units available on disk.
>
> I bought a new machine with a hard drive @ 232 GB not 9.49 GB and this is
> from the new machine.
>
> Date: 31/Mar/07
> Checking file system on C:
> The type of the file system is NTFS.
>
> A disk check has been scheduled.
> Windows will now check the disk.
> Cleaning up minor inconsistencies on the drive.
> Cleaning up 79 unused index entries from index $SII of file 0x9.
> Cleaning up 79 unused index entries from index $SDH of file 0x9.
> Cleaning up 79 unused security descriptors.
> CHKDSK is verifying file data (stage 4 of 5)...
> File data verification completed.
> CHKDSK is verifying free space (stage 5 of 5)...
> Free space verification is complete.
>
> 244187968 KB total disk space.
> 11322912 KB in 53772 files.
> 20504 KB in 3070 indexes.
> 0 KB in bad sectors.
> 134204 KB in use by the system.
> 65536 KB occupied by the log file.
> 232710348 KB available on disk.
>
> 4096 bytes in each allocation unit.
> 61046992 total allocation units on disk.
> 58177587 allocation units available on disk.
>
> --
> Hope this helps. Let us know.
>
> Wes
> MS-MVP Windows Shell/User
>
> In news:4rqdnXy-mZ4QeYfbnZ2dnUVZ_silnZ2d@comcast.com,
> M and D <m.and.d.RemoveThis@news.invalid> hunted and pecked:
>> Thank you sincerely for responding to my posts.
>>
>> Evidentally we've been reading the same articles in our research.
>>
>> I understand and accept that CHKDSK in read-only mode can produce
>> erroneous conclusions. I also understand some - okay, a little bit - of
>> the housekeeping that Windows performs on the NTFS file system. I'm
>> almost ready to drop my concerns and go merrily on my way, except for one
>> thing:
>>
>> When I've run CHKDSK /f in the past, the second stage ("CHKDSK is
>> verifying indexes") took only seconds to complete. Now the progress
>> indicator is stuck at 0% for almost a minute while my disk is grinding
>> away, and then it progresses swiftly to 100% and CHKDSK goes on normally.
>> And this now happens everytime I run CHKDSK. /Something/ is going on
>> during that minute of grinding, and that's what concerns me.
>>
>> From what I've read on the web, the messages I see in Event
>> Viewer...here's a typical example:
>>
>> Cleaning up 2 unused index entries from index $SII of file 0x9.
>> Cleaning up 2 unused index entries from index $SDH of file 0x9.
>> Cleaning up 2 unused security descriptors.
>>
>> ...are either completely normal /or/ they're a sign that my NTFS file
>> system is corrupted and my disk is nearing death. That uncertainty and
>> the minute of disk grinding leave me unsure of what to do.
>>
>> I'd really appreciate your advice.
>>
>> M and D
>>
>> "Wesley Vogel" <123WVogel955.RemoveThis@comcast.net> wrote in message
>> news:urqaDLweHHA.5044@TK2MSFTNGP05.phx.gbl...
>>>> Because ChkDsk makes mistakes when run with the safety catch on, you
>>>> should run it with the safety catch off.
>>>
>>> Or do not run it at all.
>>>
>>> Hey Chris,
>>>
>>> You ever heard of The Creaking Door?
>>>
>>> I download a lot of old radio programs and burn them to CD. I do not
>>> watch TV. Nobody seems to know much about The Creaking Door. I
>>> listened to a couple of episodes last night and thought that they were
>>> pretty good. The Creaking Door was sponsored by State Express 555
>>> (pronounced State Express Three Fives) cigarettes, which Google tells me
>>> still exists.
>>>
>>> ''The Creaking Door was an old-time radio series of horror and suspense
>>> shows originating in South Africa.
>>>
>>> There are at present anywhere from 34-37 extant episodes in MP3
>>> circulation, yet no currently available program logs for the series
>>> indicate the year of the series' broadcast (though it was likely
>>> sometime in the 1950s, given the generally high audio quality of the
>>> available shows), or the total number of episodes, and only a handful of
>>> them are known by their broadcast order. The stories are thrillers in
>>> the Inner Sanctum vein, and generally thought of favorably by most fans
>>> of Old Time Radio."
>>>
>>> "In 1964, South Africa began The Creaking Door, using original scripts
>>> which included stories with a heavy emphasis on the supernatural. The
>>> topics ranged from haunted houses to a woman who turns into a giant cat,
>>> and of course, the typical paranoid murderer so often presented on the
>>> original Inner Sanctum. The host for this series was Peter Bloomfield.''
>>>
>>> Free Old time Radio Shows - The Creaking Door
>>> Click on the Links below to listen for free online:
>>> http://www.radiolovers.com/pages/creakingdoor.htm
>>>
>>> --
>>> Hope this helps. Let us know.
>>>
>>> Wes
>>> MS-MVP Windows Shell/User
>>>
>>> In news:r8cl13901g3fdv0h7oimg7282en8bt90l7@4ax.com,
>>> cquirke (MVP Windows shell/user) <cquirkenews.RemoveThis@nospam.mvps.org> hunted and
>>> pecked:
>>>> On Mon, 9 Apr 2007 12:43:03 -0600, "Wesley Vogel"
>>>>
>>>>> Don't even bother running CHKDSK in read-only mode. It is a waste of
>>>>> time and prone to not accurately reporting information. CHKDSK might
>>>>> report spurious errors because it cannot lock the drive.
>>>>
>>>> I just love the logic here.
>>>>
>>>> Because ChkDsk makes mistakes when run with the safety catch on, you
>>>> should run it with the safety catch off.
>>>>
>>>> What would be more useful (as long as one is forced to live with tool
>>>> designs that pre-date MS-DOS 6) is to force ChkDsk to run on boot, as
>>>> if it was run with /F, so that it could report more accurately without
>>>> irreversibly blowing things up if it gets things wrong.
>>>>
>>>> But it can't, because what runs at boot is not ChkDsk, but the even
>>>> more brain-dead AutoChk that can't run without "fixing".
>>>>
>>>>
>>>>
>>>>> -------------------- ----- ---- --- -- - - - -
>>>> Hmmm... what was the *other* idea?
>>>>> -------------------- ----- ---- --- -- - - - -
>

Keep having fun, Dad!

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In news:Ar6dneqbJLqBn4bbnZ2dnUVZ_tGvnZ2d@comcast.com,
M and D <m.and.d.TakeThisOut@news.invalid> hunted and pecked:
> Hi again Wesley,
>
> I believe that "0 KB in bad sectors" refers to the surface of the disk,
> whereas the reports I am seeing in Event Viewer refer to logical errors.
>
> Nonetheless, I've concluded that I really am seeing nothing more than
> Windows XP internal housekeeping, so I'm not going to worry any more.
>
> As for my concern that CHKDSK didn't in the past make my hard disk grind
> away for a minute or so during "CHKDSK is verifying indexes"...I haven't
> run CHKDSK in a long, long time during which I've installed lots of
> updates from Microsoft Update, so perhaps that behavior is typical for
> Windows XP nowadays.
>
> Thanks very much for investing so much of your time to help me out. I do
> appreciate it. Enjoy your new computer.
>
> M and D
> (That's 'Mom and Dad' - I'm Dad.)
>
>
> "Wesley Vogel" <123WVogel955.TakeThisOut@comcast.net> wrote in message
> news:e%23h22GxeHHA.284@TK2MSFTNGP05.phx.gbl...
>> M and D,
>>
>>> Cleaning up 2 unused index entries from index $SII of file 0x9.
>>> Cleaning up 2 unused index entries from index $SDH of file 0x9.
>>
>> [[Chkdsk.exe just reclaims the unused security descriptors as a
>> housekeeping activity, and it does not actually fix any kind of problem.
>> ]]
>>
>>> Cleaning up 2 unused security descriptors.
>>
>> [[Chkdsk.exe just reclaims the unused security descriptors as a
>> housekeeping activity, and it does not actually fix any kind of problem.
>> ]]
>>
>> Is normal. I think there is much ado about nothing. Meaning I do not
>> think you have any problem whatsoever.
>>
>> Here are some chkdsk log samples that I have saved. Notice the 0 KB in
>> bad sectors. parts
>>
>> Date: 12/4/2004
>> Checking file system on C:
>> The type of the file system is NTFS.
>> Volume label is Local Disk.
>> Cleaning up minor inconsistencies on the drive.
>> Cleaning up 10 unused index entries from index $SII of file 0x9.
>> Cleaning up 10 unused index entries from index $SDH of file 0x9.
>> Cleaning up 10 unused security descriptors.
>>
>> 9952235 KB total disk space.
>> 6020596 KB in 40720 files.
>> 15248 KB in 2053 indexes.
>> 0 KB in bad sectors.
>> 102811 KB in use by the system.
>> 51824 KB occupied by the log file.
>> 3813580 KB available on disk.
>>
>> 4096 bytes in each allocation unit.
>> 2488058 total allocation units on disk.
>> 953395 allocation units available on disk.
>>
>> Date: 10/31/2005
>> Checking file system on C:
>> The type of the file system is NTFS.
>> Volume label is Local Disk.
>> Cleaning up minor inconsistencies on the drive.
>> Cleaning up 10 unused index entries from index $SII of file 0x9.
>> Cleaning up 10 unused index entries from index $SDH of file 0x9.
>> Cleaning up 10 unused security descriptors.
>> CHKDSK is verifying file data (stage 4 of 5)...
>> File data verification completed.
>> CHKDSK is verifying free space (stage 5 of 5)...
>> Free space verification is complete.
>>
>> 9952235 KB total disk space.
>> 8294548 KB in 45987 files.
>> 18368 KB in 2270 indexes.
>> 0 KB in bad sectors.
>> 106159 KB in use by the system.
>> 51824 KB occupied by the log file.
>> 1533160 KB available on disk.
>>
>> 4096 bytes in each allocation unit.
>> 2488058 total allocation units on disk.
>> 383290 allocation units available on disk.
>>
>> Date: 02/05/2006
>> Checking file system on C:
>> The type of the file system is NTFS.
>> Volume label is Local Disk.
>> Cleaning up minor inconsistencies on the drive.
>> Cleaning up 8 unused index entries from index $SII of file 0x9.
>> Cleaning up 8 unused index entries from index $SDH of file 0x9.
>> Cleaning up 8 unused security descriptors.
>> CHKDSK is verifying file data (stage 4 of 5)...
>> File data verification completed.
>> CHKDSK is verifying free space (stage 5 of 5)...
>> Free space verification is complete.
>>
>> 9952235 KB total disk space.
>> 7967676 KB in 45429 files.
>> 18224 KB in 2251 indexes.
>> 0 KB in bad sectors.
>> 106179 KB in use by the system.
>> 51824 KB occupied by the log file.
>> 1860156 KB available on disk.
>>
>> 4096 bytes in each allocation unit.
>> 2488058 total allocation units on disk.
>> 465039 allocation units available on disk.
>>
>> I bought a new machine with a hard drive @ 232 GB not 9.49 GB and this is
>> from the new machine.
>>
>> Date: 31/Mar/07
>> Checking file system on C:
>> The type of the file system is NTFS.
>>
>> A disk check has been scheduled.
>> Windows will now check the disk.
>> Cleaning up minor inconsistencies on the drive.
>> Cleaning up 79 unused index entries from index $SII of file 0x9.
>> Cleaning up 79 unused index entries from index $SDH of file 0x9.
>> Cleaning up 79 unused security descriptors.
>> CHKDSK is verifying file data (stage 4 of 5)...
>> File data verification completed.
>> CHKDSK is verifying free space (stage 5 of 5)...
>> Free space verification is complete.
>>
>> 244187968 KB total disk space.
>> 11322912 KB in 53772 files.
>> 20504 KB in 3070 indexes.
>> 0 KB in bad sectors.
>> 134204 KB in use by the system.
>> 65536 KB occupied by the log file.
>> 232710348 KB available on disk.
>>
>> 4096 bytes in each allocation unit.
>> 61046992 total allocation units on disk.
>> 58177587 allocation units available on disk.
>>
>> --
>> Hope this helps. Let us know.
>>
>> Wes
>> MS-MVP Windows Shell/User
>>
>> In news:4rqdnXy-mZ4QeYfbnZ2dnUVZ_silnZ2d@comcast.com,
>> M and D <m.and.d.TakeThisOut@news.invalid> hunted and pecked:
>>> Thank you sincerely for responding to my posts.
>>>
>>> Evidentally we've been reading the same articles in our research.
>>>
>>> I understand and accept that CHKDSK in read-only mode can produce
>>> erroneous conclusions. I also understand some - okay, a little bit - of
>>> the housekeeping that Windows performs on the NTFS file system. I'm
>>> almost ready to drop my concerns and go merrily on my way, except for
>>> one thing:
>>>
>>> When I've run CHKDSK /f in the past, the second stage ("CHKDSK is
>>> verifying indexes") took only seconds to complete. Now the progress
>>> indicator is stuck at 0% for almost a minute while my disk is grinding
>>> away, and then it progresses swiftly to 100% and CHKDSK goes on
>>> normally. And this now happens everytime I run CHKDSK. /Something/ is
>>> going on during that minute of grinding, and that's what concerns me.
>>>
>>> From what I've read on the web, the messages I see in Event
>>> Viewer...here's a typical example:
>>>
>>> Cleaning up 2 unused index entries from index $SII of file 0x9.
>>> Cleaning up 2 unused index entries from index $SDH of file 0x9.
>>> Cleaning up 2 unused security descriptors.
>>>
>>> ...are either completely normal /or/ they're a sign that my NTFS file
>>> system is corrupted and my disk is nearing death. That uncertainty and
>>> the minute of disk grinding leave me unsure of what to do.
>>>
>>> I'd really appreciate your advice.
>>>
>>> M and D
>>>
>>> "Wesley Vogel" <123WVogel955.TakeThisOut@comcast.net> wrote in message
>>> news:urqaDLweHHA.5044@TK2MSFTNGP05.phx.gbl...
>>>>> Because ChkDsk makes mistakes when run with the safety catch on, you
>>>>> should run it with the safety catch off.
>>>>
>>>> Or do not run it at all.
>>>>
>>>> Hey Chris,
>>>>
>>>> You ever heard of The Creaking Door?
>>>>
>>>> I download a lot of old radio programs and burn them to CD. I do not
>>>> watch TV. Nobody seems to know much about The Creaking Door. I
>>>> listened to a couple of episodes last night and thought that they were
>>>> pretty good. The Creaking Door was sponsored by State Express 555
>>>> (pronounced State Express Three Fives) cigarettes, which Google tells
>>>> me still exists.
>>>>
>>>> ''The Creaking Door was an old-time radio series of horror and suspense
>>>> shows originating in South Africa.
>>>>
>>>> There are at present anywhere from 34-37 extant episodes in MP3
>>>> circulation, yet no currently available program logs for the series
>>>> indicate the year of the series' broadcast (though it was likely
>>>> sometime in the 1950s, given the generally high audio quality of the
>>>> available shows), or the total number of episodes, and only a handful
>>>> of them are known by their broadcast order. The stories are thrillers
>>>> in the Inner Sanctum vein, and generally thought of favorably by most
>>>> fans of Old Time Radio."
>>>>
>>>> "In 1964, South Africa began The Creaking Door, using original scripts
>>>> which included stories with a heavy emphasis on the supernatural. The
>>>> topics ranged from haunted houses to a woman who turns into a giant
>>>> cat, and of course, the typical paranoid murderer so often presented
>>>> on the original Inner Sanctum. The host for this series was Peter
>>>> Bloomfield.''
>>>>
>>>> Free Old time Radio Shows - The Creaking Door
>>>> Click on the Links below to listen for free online:
>>>> http://www.radiolovers.com/pages/creakingdoor.htm
>>>>
>>>> --
>>>> Hope this helps. Let us know.
>>>>
>>>> Wes
>>>> MS-MVP Windows Shell/User
>>>>
>>>> In news:r8cl13901g3fdv0h7oimg7282en8bt90l7@4ax.com,
>>>> cquirke (MVP Windows shell/user) <cquirkenews.TakeThisOut@nospam.mvps.org> hunted
>>>> and pecked:
>>>>> On Mon, 9 Apr 2007 12:43:03 -0600, "Wesley Vogel"
>>>>>
>>>>>> Don't even bother running CHKDSK in read-only mode. It is a waste of
>>>>>> time and prone to not accurately reporting information. CHKDSK might
>>>>>> report spurious errors because it cannot lock the drive.
>>>>>
>>>>> I just love the logic here.
>>>>>
>>>>> Because ChkDsk makes mistakes when run with the safety catch on, you
>>>>> should run it with the safety catch off.
>>>>>
>>>>> What would be more useful (as long as one is forced to live with tool
>>>>> designs that pre-date MS-DOS 6) is to force ChkDsk to run on boot, as
>>>>> if it was run with /F, so that it could report more accurately without
>>>>> irreversibly blowing things up if it gets things wrong.
>>>>>
>>>>> But it can't, because what runs at boot is not ChkDsk, but the even
>>>>> more brain-dead AutoChk that can't run without "fixing".
>>>>>
>>>>>
>>>>>
>>>>>> -------------------- ----- ---- --- -- - - - -
>>>>> Hmmm... what was the *other* idea?
>>>>>> -------------------- ----- ---- --- -- - - - -

On Mon, 9 Apr 2007 17:56:57 -0600, "Wesley Vogel"

>> Because ChkDsk makes mistakes when run with the safety catch on, you
>> should run it with the safety catch off.

>Or do not run it at all.

That works for me if FATxx and < 137G, as I can boot into Win98 DOS
Mode and use Scandisk from there - but that's not safe > 137G, and
it's not a solution for NTFS. There ARE no other solutions for NTFS.

>You ever heard of The Creaking Door?

It rings a vague bell...

>I download a lot of old radio programs and burn them to CD. I do not watch
>TV. Nobody seems to know much about The Creaking Door. I listened to a
>couple of episodes last night and thought that they were pretty good. The
>Creaking Door was sponsored by State Express 555 (pronounced State Express
>Three Fives) cigarettes, which Google tells me still exists.

Was it on the radio in the '60s or early '70s? I remember an SF
series, too, that did a Raol Dahl, a Vonnegut and a Ballard.

>''The Creaking Door was an old-time radio series of horror and suspense
>shows originating in South Africa.

Yep - sounds like the one...

>There are at present anywhere from 34-37 extant episodes in MP3 circulation,
>yet no currently available program logs for the series indicate the year of
>the series' broadcast

If I heard it, it would be between 1965 and 1974, I guess...

>"In 1964, South Africa began The Creaking Door, using original scripts
>... The host for this series was Peter Bloomfield.''

>Free Old time Radio Shows - The Creaking Door

>http://www.radiolovers.com/pages/creakingdoor.htm

Cool, thanks! Ahhh... yes, and I do remember 555 cigs... heh, they've
got "The Men From The Ministry" under "Sci-Fi and Super Heroes"







>--------------- ----- ---- --- -- - - -
IRC is just multiplayer notepad.
>--------------- ----- ---- --- -- - - -

> Was it on the radio in the '60s or early '70s? I remember an SF
> series, too, that did a Raol Dahl, a Vonnegut and a Ballard.

I was hoping that you might know when it originally aired. You could
have heard rebroadcasts in the 70s. I'm sure that if it aired that late
there would be more documentation on it available on the web.

Roald Dahl had a TV show here in the US.

Oops, I see that it was British, Tales of the Unexpected.
http://en.wikipedia.org/wiki/Tales_of_the_Unexpected_%28TV_series%29

I seem to remember some TV show here that Roald Dahl hosted, but cannot
remember the name. Maybe they broadcasted Tales of the Unexpected here,
I've seen plenty of other British TV shows here. I just about grew up
watching old Monty Python rebroadcasts on Public TV.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In news:c6n223htnq6hm1cc4j6b58omutaq6o2ae6@4ax.com,
cquirke (MVP Windows shell/user) <cquirkenews.DeleteThis@nospam.mvps.org> hunted and
pecked:
> On Mon, 9 Apr 2007 17:56:57 -0600, "Wesley Vogel"
>
>>> Because ChkDsk makes mistakes when run with the safety catch on, you
>>> should run it with the safety catch off.
>
>> Or do not run it at all.
>
> That works for me if FATxx and < 137G, as I can boot into Win98 DOS
> Mode and use Scandisk from there - but that's not safe > 137G, and
> it's not a solution for NTFS. There ARE no other solutions for NTFS.
>
>> You ever heard of The Creaking Door?
>
> It rings a vague bell...
>
>> I download a lot of old radio programs and burn them to CD. I do not
>> watch TV. Nobody seems to know much about The Creaking Door. I
>> listened to a couple of episodes last night and thought that they were
>> pretty good. The Creaking Door was sponsored by State Express 555
>> (pronounced State Express Three Fives) cigarettes, which Google tells me
>> still exists.
>
> Was it on the radio in the '60s or early '70s? I remember an SF
> series, too, that did a Raol Dahl, a Vonnegut and a Ballard.
>
>> ''The Creaking Door was an old-time radio series of horror and suspense
>> shows originating in South Africa.
>
> Yep - sounds like the one...
>
>> There are at present anywhere from 34-37 extant episodes in MP3
>> circulation, yet no currently available program logs for the series
>> indicate the year of the series' broadcast
>
> If I heard it, it would be between 1965 and 1974, I guess...
>
>> "In 1964, South Africa began The Creaking Door, using original scripts
>> ... The host for this series was Peter Bloomfield.''
>
>> Free Old time Radio Shows - The Creaking Door
>
>> http://www.radiolovers.com/pages/creakingdoor.htm
>
> Cool, thanks! Ahhh... yes, and I do remember 555 cigs... heh, they've
> got "The Men From The Ministry" under "Sci-Fi and Super Heroes"
>
>
>
>
>
>
>
>> --------------- ----- ---- --- -- - - -
> IRC is just multiplayer notepad.
>> --------------- ----- ---- --- -- - - -

On Sat, 14 Apr 2007 19:14:08 -0600, "Wesley Vogel"
> cquirke said

>> Was it on the radio in the '60s or early '70s?

>I was hoping that you might know when it originally aired. You could
>have heard rebroadcasts in the 70s. I'm sure that if it aired that late
>there would be more documentation on it available on the web.

I'm surprised it's there at all... the early '70s were a long time
ago, compared to the "everything's available" Internet era.

>I seem to remember some TV show here that Roald Dahl hosted

No, SF69 was not hosted by him; rather, one episode was based on a
story by him (the one where an oxygen-starved aviator hallucinates
that German pilots are singing to him as they are shooting him down)

I *loved* SF69



>------------------------- ---- --- -- - - - -
Let's make a humming sound
>------------------------- ---- --- -- - - - -