scandisk errors

So you has a current backup
So was you able to run Scandisk with no errors
are did you just give up?


"Jim" wrote in message
...
Thanks for the many varied responses. I luckily have a current backup and
used it to restore to [original location] and it seems to have worked like
a
breeze. Most of these files are system junk collections I will never read
again and perhaps I could have just deleted them without much ado about
it.
The KB articles are self explanatory in themselves, so thanks again.
"Jim" wrote in message
...
I did find answers to many of my questions in:
http://support.microsoft.com/kb/186365
I did not find out how to restore the file to its original folder
location
after [ move to repair] option. If I just place the file in the root path
folder it appears to have come from will this work? The KB article above
suggests that user of this option write down the root path to folder file
before moving the file. Unfortunately, I did not think to do this prior
to
the move/repair selection and there was no warning to user. My first
attempt
to
restore was to use {scanreg / restore} in dos-mode and no luck...
"Jim" wrote in message
.. .
If you uncheck the automatic fix scandisk errors, a prompt pops up and
three
options are allowed. The choices are ignore, move and repair and delete
the
file. If I chose the [move and repair] option, the program moves the
file
to
the top of the host local drive C: . My question(s) are what is
repaired
and
how do I restore the file to its proper folder location? Do I have to
repair
this file myself? When and why would I want to delete the file?

The only errors that scandisk reports are MS-Dos name length errors
that
exceed 66 characters in length. Why does win98 name some MS-Dos files
like
this? Is this the only error that scandisk reports? It seems easier to
just
leave the program to autofix everything it finds, but then I would
never
learn what all it fixes.

So you has a current backup
So was you able to run Scandisk with no errors
are did you just give up?


"Jim" wrote in message
...
Thanks for the many varied responses. I luckily have a current backup and
used it to restore to [original location] and it seems to have worked like
a
breeze. Most of these files are system junk collections I will never read
again and perhaps I could have just deleted them without much ado about
it.
The KB articles are self explanatory in themselves, so thanks again.
"Jim" wrote in message
...
I did find answers to many of my questions in:
http://support.microsoft.com/kb/186365
I did not find out how to restore the file to its original folder
location
after [ move to repair] option. If I just place the file in the root path
folder it appears to have come from will this work? The KB article above
suggests that user of this option write down the root path to folder file
before moving the file. Unfortunately, I did not think to do this prior
to
the move/repair selection and there was no warning to user. My first
attempt
to
restore was to use {scanreg / restore} in dos-mode and no luck...
"Jim" wrote in message
.. .
If you uncheck the automatic fix scandisk errors, a prompt pops up and
three
options are allowed. The choices are ignore, move and repair and delete
the
file. If I chose the [move and repair] option, the program moves the
file
to
the top of the host local drive C: . My question(s) are what is
repaired
and
how do I restore the file to its proper folder location? Do I have to
repair
this file myself? When and why would I want to delete the file?

The only errors that scandisk reports are MS-Dos name length errors
that
exceed 66 characters in length. Why does win98 name some MS-Dos files
like
this? Is this the only error that scandisk reports? It seems easier to
just
leave the program to autofix everything it finds, but then I would
never
learn what all it fixes.

I am ok.
I ran scandisk without errors, and also did a though scan...which took a
long time. I believe there is some info in those articles about doing a
command-line scan in dos at the prompt, but one needs to load the [Himn.sys]
first to do this procedure to check for errors and implies HDD damages.
I do a regular (old school) backup monthly at the very least, and weekly if
this were a critical workstation.

"Hot-text" wrote in message
...
So you has a current backup
So was you able to run Scandisk with no errors
are did you just give up?


"Jim" wrote in message
...
Thanks for the many varied responses. I luckily have a current backup
and
used it to restore to [original location] and it seems to have worked
like
a
breeze. Most of these files are system junk collections I will never
read
again and perhaps I could have just deleted them without much ado about
it.
The KB articles are self explanatory in themselves, so thanks again.
"Jim" wrote in message
...
I did find answers to many of my questions in:
http://support.microsoft.com/kb/186365
I did not find out how to restore the file to its original folder
location
after [ move to repair] option. If I just place the file in the root
path
folder it appears to have come from will this work? The KB article
above
suggests that user of this option write down the root path to folder
file
before moving the file. Unfortunately, I did not think to do this prior
to
the move/repair selection and there was no warning to user. My first
attempt
to
restore was to use {scanreg / restore} in dos-mode and no luck...
"Jim" wrote in message
.. .
If you uncheck the automatic fix scandisk errors, a prompt pops up
and
three
options are allowed. The choices are ignore, move and repair and
delete
the
file. If I chose the [move and repair] option, the program moves the
file
to
the top of the host local drive C: . My question(s) are what is
repaired
and
how do I restore the file to its proper folder location? Do I have to
repair
this file myself? When and why would I want to delete the file?

The only errors that scandisk reports are MS-Dos name length errors
that
exceed 66 characters in length. Why does win98 name some MS-Dos files
like
this? Is this the only error that scandisk reports? It seems easier
to
just
leave the program to autofix everything it finds, but then I would
never
learn what all it fixes.

I am ok.
I ran scandisk without errors, and also did a though scan...which took a
long time. I believe there is some info in those articles about doing a
command-line scan in dos at the prompt, but one needs to load the [Himn.sys]
first to do this procedure to check for errors and implies HDD damages.
I do a regular (old school) backup monthly at the very least, and weekly if
this were a critical workstation.

"Hot-text" wrote in message
...
So you has a current backup
So was you able to run Scandisk with no errors
are did you just give up?


"Jim" wrote in message
...
Thanks for the many varied responses. I luckily have a current backup
and
used it to restore to [original location] and it seems to have worked
like
a
breeze. Most of these files are system junk collections I will never
read
again and perhaps I could have just deleted them without much ado about
it.
The KB articles are self explanatory in themselves, so thanks again.
"Jim" wrote in message
...
I did find answers to many of my questions in:
http://support.microsoft.com/kb/186365
I did not find out how to restore the file to its original folder
location
after [ move to repair] option. If I just place the file in the root
path
folder it appears to have come from will this work? The KB article
above
suggests that user of this option write down the root path to folder
file
before moving the file. Unfortunately, I did not think to do this prior
to
the move/repair selection and there was no warning to user. My first
attempt
to
restore was to use {scanreg / restore} in dos-mode and no luck...
"Jim" wrote in message
.. .
If you uncheck the automatic fix scandisk errors, a prompt pops up
and
three
options are allowed. The choices are ignore, move and repair and
delete
the
file. If I chose the [move and repair] option, the program moves the
file
to
the top of the host local drive C: . My question(s) are what is
repaired
and
how do I restore the file to its proper folder location? Do I have to
repair
this file myself? When and why would I want to delete the file?

The only errors that scandisk reports are MS-Dos name length errors
that
exceed 66 characters in length. Why does win98 name some MS-Dos files
like
this? Is this the only error that scandisk reports? It seems easier
to
just
leave the program to autofix everything it finds, but then I would
never
learn what all it fixes.

get a new HDD and copy the Old HDD to, Then put new HDD in the Box and the
day you need it you can be back up and running in 5 min.

For MEB will have same more good INFO for you. so keep a eye out for his
POST




"Jim" wrote in message
...
I am ok.
I ran scandisk without errors, and also did a though scan...which took a
long time. I believe there is some info in those articles about doing a
command-line scan in dos at the prompt, but one needs to load the
[Himn.sys]
first to do this procedure to check for errors and implies HDD damages.
I do a regular (old school) backup monthly at the very least, and weekly
if
this were a critical workstation.

"Hot-text" wrote in message
...
So you has a current backup
So was you able to run Scandisk with no errors
are did you just give up?


"Jim" wrote in message
...
Thanks for the many varied responses. I luckily have a current backup
and
used it to restore to [original location] and it seems to have worked
like
a
breeze. Most of these files are system junk collections I will never
read
again and perhaps I could have just deleted them without much ado about
it.
The KB articles are self explanatory in themselves, so thanks again.
"Jim" wrote in message
...
I did find answers to many of my questions in:
http://support.microsoft.com/kb/186365
I did not find out how to restore the file to its original folder
location
after [ move to repair] option. If I just place the file in the root
path
folder it appears to have come from will this work? The KB article
above
suggests that user of this option write down the root path to folder
file
before moving the file. Unfortunately, I did not think to do this
prior
to
the move/repair selection and there was no warning to user. My first
attempt
to
restore was to use {scanreg / restore} in dos-mode and no luck...
"Jim" wrote in message
.. .
If you uncheck the automatic fix scandisk errors, a prompt pops up
and
three
options are allowed. The choices are ignore, move and repair and
delete
the
file. If I chose the [move and repair] option, the program moves the
file
to
the top of the host local drive C: . My question(s) are what is
repaired
and
how do I restore the file to its proper folder location? Do I have
to
repair
this file myself? When and why would I want to delete the file?

The only errors that scandisk reports are MS-Dos name length errors
that
exceed 66 characters in length. Why does win98 name some MS-Dos
files
like
this? Is this the only error that scandisk reports? It seems easier
to
just
leave the program to autofix everything it finds, but then I would
never
learn what all it fixes.

get a new HDD and copy the Old HDD to, Then put new HDD in the Box and the
day you need it you can be back up and running in 5 min.

For MEB will have same more good INFO for you. so keep a eye out for his
POST




"Jim" wrote in message
...
I am ok.
I ran scandisk without errors, and also did a though scan...which took a
long time. I believe there is some info in those articles about doing a
command-line scan in dos at the prompt, but one needs to load the
[Himn.sys]
first to do this procedure to check for errors and implies HDD damages.
I do a regular (old school) backup monthly at the very least, and weekly
if
this were a critical workstation.

"Hot-text" wrote in message
...
So you has a current backup
So was you able to run Scandisk with no errors
are did you just give up?


"Jim" wrote in message
...
Thanks for the many varied responses. I luckily have a current backup
and
used it to restore to [original location] and it seems to have worked
like
a
breeze. Most of these files are system junk collections I will never
read
again and perhaps I could have just deleted them without much ado about
it.
The KB articles are self explanatory in themselves, so thanks again.
"Jim" wrote in message
...
I did find answers to many of my questions in:
http://support.microsoft.com/kb/186365
I did not find out how to restore the file to its original folder
location
after [ move to repair] option. If I just place the file in the root
path
folder it appears to have come from will this work? The KB article
above
suggests that user of this option write down the root path to folder
file
before moving the file. Unfortunately, I did not think to do this
prior
to
the move/repair selection and there was no warning to user. My first
attempt
to
restore was to use {scanreg / restore} in dos-mode and no luck...
"Jim" wrote in message
.. .
If you uncheck the automatic fix scandisk errors, a prompt pops up
and
three
options are allowed. The choices are ignore, move and repair and
delete
the
file. If I chose the [move and repair] option, the program moves the
file
to
the top of the host local drive C: . My question(s) are what is
repaired
and
how do I restore the file to its proper folder location? Do I have
to
repair
this file myself? When and why would I want to delete the file?

The only errors that scandisk reports are MS-Dos name length errors
that
exceed 66 characters in length. Why does win98 name some MS-Dos
files
like
this? Is this the only error that scandisk reports? It seems easier
to
just
leave the program to autofix everything it finds, but then I would
never
learn what all it fixes.