Boot error

[tshad]

I had started my W2K Pro machine yesterday and it got an NTLDR error. I
moved the drive to another machine to look at it and found all my boot files
changed. They all had ".error" appended to them (boot.ini.error,
ntdetect.com.error, io.sys.error, msdos.sys.error,config.sys.error). When
it first happened I figured I had a hardware error, but that wouldn't cause
the files to change.

I thought I might have a virus, but neither Norton nor TrendMicro could find
anything.

Anyone know what might have caused this?

Thanks,

Tom.

 

[Dave Patrick]

Windows 2000 does not use or create io.sys, msdos.sys, config.sys

Some other process created them.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
|I had started my W2K Pro machine yesterday and it got an NTLDR error. I
| moved the drive to another machine to look at it and found all my boot
files
| changed. They all had ".error" appended to them (boot.ini.error,
| ntdetect.com.error, io.sys.error, msdos.sys.error,config.sys.error). When
| it first happened I figured I had a hardware error, but that wouldn't
cause
| the files to change.
|
| I thought I might have a virus, but neither Norton nor TrendMicro could
find
| anything.
|
| Anyone know what might have caused this?
|
| Thanks,
|
| Tom.
|
|

 

[Jud]

Windows 2000 does not use or create io.sys, msdos.sys, config.sys

Some other process created them.

--

Really,??
I have copies of them on my C drive perhaps you could explain that then.

Its just a machine running 2k nothing else

Jud

 

[Dave Patrick]

OK, I should have said;
Windows 2000 does not use io.sys, msdos.sys, config.sys
They should be zero byte files.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| Really,??
| I have copies of them on my C drive perhaps you could explain that then.
|
| Its just a machine running 2k nothing else
|
| Jud
|
|

 

[Jud]

OK, I should have said;
Windows 2000 does not use io.sys, msdos.sys, config.sys
They should be zero byte files.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
People skills = Zero
http://www.microsoft.com/protect

"Jud" wrote:

So the previous OP could have them on his machine showing what he stated,
and because you didn't think to phrase your post correctly he may well be
thinking that he's a dummy or that the posters in here are a bunch of
cynical hardfaced gits who mock those of a lesser knowledge, but ignore me
i'm rambling.

Jud

 

[John John]

...snip...

How many drinks have you had today? Or are you always obnoxious like that?

John

 

[Jud]

How many drinks have you had today? Or are you always obnoxious like that?

John

Who rattled your cage ?? or are you one of these who go through the posts
looking for a chance to throw in his five pence worth as he can't answer
any of the questions.

My opinion was directed at the previous poster for his lack of thought, i'm
not looking for an apology, just making a point.

Jud

 

[Scott]

Jud,
Do you really expect anybody to help you now, after you
just made an @$$ out of yourself. Maybe you should
understand that these are people who are helping you and
that the only reward that they are receiving is a simple
thank you. Goodluck.

 

[Jud]

Jud,
Do you really expect anybody to help you now, after you
just made an @$$ out of yourself. Maybe you should
understand that these are people who are helping you and
that the only reward that they are receiving is a simple
thank you. Goodluck.

asked for help Scott, that was the original poster, I just mentioned a
point.

If your gonna but in get the facts or you end up looking like an @$$.

Jud

PS I dont ask for help, if i cant fix it, it aint fixable.

 

[Geoffw]

obnoxious like
that?
Who rattled your cage ?? or are you one of these who go through the posts
looking for a chance to throw in his five pence worth as he can't answer
any of the questions.

isn't this exactly what you have done, I see no correction
from you, just a critical reply

Geoff

 

[scott]

I apologize, to the other person who basically called you
an @$$. They were right. Get over yourself, because you
ARE AN @$$. Sorry for tyhe misunderstanding.

 

[tshad]

OK, I should have said;
Windows 2000 does not use io.sys, msdos.sys, config.sys
They should be zero byte files.

That is exactly what mine are.

As a matter a fact, I have msdos.sys.error and msdos.sys as well as io.sys
and io.sys.error (all 0 bytes).

Tom

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| Really,??
| I have copies of them on my C drive perhaps you could explain that then.
|
| Its just a machine running 2k nothing else
|
| Jud
|
|

 

[Dave Patrick]

You can start the recovery console and from a command prompt issue the
command;
fixboot
to repair the bootsector.

To start the Recovery Console, start the computer from the Windows 2000
Setup CD or the Windows 2000 Setup floppy disks. If you do not have Setup
floppy disks and your computer cannot start from the Windows 2000 Setup CD,
use another Windows 2000-based computer to create the Setup floppy disks.
Press ENTER at the "Setup Notification" screen. Press R to repair a Windows
2000 installation, and then press C to use the Recovery Console. The
Recovery Console then prompts you for the administrator password. If you do
not have the correct password, Recovery Console does not allow access to the
computer. If an incorrect password is entered three times, the Recovery
Console quits and restarts the computer. Note If the registry is corrupted
or missing or no valid installations are found, the Recovery Console starts
in the root of the startup volume without requiring a password. You cannot
access any folders, but you can carry out commands such as chkdsk, fixboot,
and fixmbr for limited disk repairs. Once the password has been validated,
you have full access to the Recovery Console, but limited access to the hard
disk. You can only access the following folders on your computer: drive
root, %systemroot% or %windir%

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| That is exactly what mine are.
|
| As a matter a fact, I have msdos.sys.error and msdos.sys as well as io.sys
| and io.sys.error (all 0 bytes).
|
| Tom

 

[tshad]

You can start the recovery console and from a command prompt issue the
command;
fixboot
to repair the bootsector.

To start the Recovery Console, start the computer from the Windows 2000
Setup CD or the Windows 2000 Setup floppy disks. If you do not have Setup
floppy disks and your computer cannot start from the Windows 2000 Setup
CD,
use another Windows 2000-based computer to create the Setup floppy disks.
Press ENTER at the "Setup Notification" screen. Press R to repair a
Windows
2000 installation, and then press C to use the Recovery Console. The
Recovery Console then prompts you for the administrator password. If you
do
not have the correct password, Recovery Console does not allow access to
the
computer. If an incorrect password is entered three times, the Recovery
Console quits and restarts the computer. Note If the registry is corrupted
or missing or no valid installations are found, the Recovery Console
starts
in the root of the startup volume without requiring a password. You cannot
access any folders, but you can carry out commands such as chkdsk,
fixboot,
and fixmbr for limited disk repairs. Once the password has been validated,
you have full access to the Recovery Console, but limited access to the
hard
disk. You can only access the following folders on your computer: drive
root, %systemroot% or %windir%

I am going to look at that.

But when I just renamed all the files by taking the ".error" from the end of
the files, everything is working fine.

I am just confused as to how the ".error" got added to all the files.
Obviously the boot sector is OK as it boots up fine now. Nobody has been
able to tell me what caused it and I can't seem to find anywhere on the net
where it is mentioned.

Thanks,

Tom.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| That is exactly what mine are.
|
| As a matter a fact, I have msdos.sys.error and msdos.sys as well as
io.sys
| and io.sys.error (all 0 bytes).
|
| Tom

 

[Dave Patrick]

No I've never seen or heard of this. So you had to delete the native files
then rename the *.error back to native file names?

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| I am going to look at that.
|
| But when I just renamed all the files by taking the ".error" from the end
of
| the files, everything is working fine.
|
| I am just confused as to how the ".error" got added to all the files.
| Obviously the boot sector is OK as it boots up fine now. Nobody has been
| able to tell me what caused it and I can't seem to find anywhere on the
net
| where it is mentioned.
|
| Thanks,
|
| Tom.
| > --
| > Regards,
| >
| > Dave Patrick ....Please no email replies - reply in newsgroup.
| > Microsoft Certified Professional
| > Microsoft MVP [Windows]
| > http://www.microsoft.com/protect
| >
| > "tshad" wrote:
| > | That is exactly what mine are.
| > |
| > | As a matter a fact, I have msdos.sys.error and msdos.sys as well as
| > io.sys
| > | and io.sys.error (all 0 bytes).
| > |
| > | Tom
| >
| >
|
|

 

[tshad]

No I've never seen or heard of this. So you had to delete the native files
then rename the *.error back to native file names?

For the config.sys.error, io.sys.error and msdos.sys.error, I just deleted
the files as the normal files were there also (0 length - I assume when
accessed, they were just created).

For the boot.ini.error and ntdetect.com.error, I just renamed the files and
then everything has been fine since.

It was all confusing because this machine seemed to be causing me a problem
for about 6 months. I had another disk that wasn't able to boot and for
some reason lost most of its data (except the disk space in use seems to
still be about the same). All my folders whose names began with A-D seem to
still be there and what is in the root is now the contents of another
folder.

I have no idea what caused that. Could be some sort of hardware problem
that scrambled the directory structure. I then rebuilt the drive with a new
disk and everything seemed to be working fine until this happened. Now the
hardware doesn't seem to be the issue, as that wouldn't have renamed the
files.

Very confusing.

I am putting this machine away, as I can't figure out what is cause this.

Fun stuff.

Thanks,

Tom.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| I am going to look at that.
|
| But when I just renamed all the files by taking the ".error" from the
end
of
| the files, everything is working fine.
|
| I am just confused as to how the ".error" got added to all the files.
| Obviously the boot sector is OK as it boots up fine now. Nobody has
been
| able to tell me what caused it and I can't seem to find anywhere on the
net
| where it is mentioned.
|
| Thanks,
|
| Tom.
| > --
| > Regards,
| >
| > Dave Patrick ....Please no email replies - reply in newsgroup.
| > Microsoft Certified Professional
| > Microsoft MVP [Windows]
| > http://www.microsoft.com/protect
| >
| > "tshad" wrote:
| > | That is exactly what mine are.
| > |
| > | As a matter a fact, I have msdos.sys.error and msdos.sys as well as
| > io.sys
| > | and io.sys.error (all 0 bytes).
| > |
| > | Tom
| >
| >
|
|

 

[Dave Patrick]

It could be drive and or controller failure. You should be able to download
a disk diagnostic utility from the drive manufacturer's web site.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| For the config.sys.error, io.sys.error and msdos.sys.error, I just deleted
| the files as the normal files were there also (0 length - I assume when
| accessed, they were just created).
|
| For the boot.ini.error and ntdetect.com.error, I just renamed the files
and
| then everything has been fine since.
|
| It was all confusing because this machine seemed to be causing me a
problem
| for about 6 months. I had another disk that wasn't able to boot and for
| some reason lost most of its data (except the disk space in use seems to
| still be about the same). All my folders whose names began with A-D seem
to
| still be there and what is in the root is now the contents of another
| folder.
|
| I have no idea what caused that. Could be some sort of hardware problem
| that scrambled the directory structure. I then rebuilt the drive with a
new
| disk and everything seemed to be working fine until this happened. Now
the
| hardware doesn't seem to be the issue, as that wouldn't have renamed the
| files.
|
| Very confusing.
|
| I am putting this machine away, as I can't figure out what is cause this.
|
| Fun stuff.
|
| Thanks,
|
| Tom.

 

[tshad]

It could be drive and or controller failure. You should be able to
download
a disk diagnostic utility from the drive manufacturer's web site.

I agree, but that wouldn't change the names of the boot files, would it?

Tom

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| For the config.sys.error, io.sys.error and msdos.sys.error, I just
deleted
| the files as the normal files were there also (0 length - I assume when
| accessed, they were just created).
|
| For the boot.ini.error and ntdetect.com.error, I just renamed the files
and
| then everything has been fine since.
|
| It was all confusing because this machine seemed to be causing me a
problem
| for about 6 months. I had another disk that wasn't able to boot and for
| some reason lost most of its data (except the disk space in use seems to
| still be about the same). All my folders whose names began with A-D
seem
to
| still be there and what is in the root is now the contents of another
| folder.
|
| I have no idea what caused that. Could be some sort of hardware problem
| that scrambled the directory structure. I then rebuilt the drive with a
new
| disk and everything seemed to be working fine until this happened. Now
the
| hardware doesn't seem to be the issue, as that wouldn't have renamed the
| files.
|
| Very confusing.
|
| I am putting this machine away, as I can't figure out what is cause
this.
|
| Fun stuff.
|
| Thanks,
|
| Tom.

 

[Dave Patrick]

Probably not in of itself. But it might have triggered the event.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| I agree, but that wouldn't change the names of the boot files, would it?
|
| Tom