Slave HD Failure Results in Dual Boot Failure? (W2K and Linux)

W

W. Watson

Well, things are not going according to Hoyle. I found the defective HD was
a 300G WDL that I purchased not too many months ago, and was using it as a
slave. I took it out, and tried firing up the system with the master, 80G
WDL WD800BB-75CAA0. I installed it at the end of the cable as a single
master, and removed the jumpers. My sys has an Athlon XP 2200+ CPU. When I
boot up I get:

Primary IDE no 80-pin cable installed.
CPU is unworkable or has changed.
CMOS checksum error--defaults loaded.

If I continue, I get a screen full of data about devices (DMI pool), and
then an L.

I changed out the cable to an 80-pin cable, blue, grey, and black. Got the
same results without the checksum error. It appears the L is from Linux.
Originally, my machine only had w2k and Linux as a dual boot. I added the
300G drive much later. I doubt that Linux ever used it. So why won't this
boot up and give me the standard DOS Linux choices? I believe Linux is using
the LILO loader.
 
P

Pegasus \(MVP\)

W. Watson said:
Well, things are not going according to Hoyle. I found the defective HD was
a 300G WDL that I purchased not too many months ago, and was using it as a
slave. I took it out, and tried firing up the system with the master, 80G
WDL WD800BB-75CAA0. I installed it at the end of the cable as a single
master, and removed the jumpers. My sys has an Athlon XP 2200+ CPU. When I
boot up I get:

Primary IDE no 80-pin cable installed.
CPU is unworkable or has changed.
CMOS checksum error--defaults loaded.

If I continue, I get a screen full of data about devices (DMI pool), and
then an L.

I changed out the cable to an 80-pin cable, blue, grey, and black. Got the
same results without the checksum error. It appears the L is from Linux.
Originally, my machine only had w2k and Linux as a dual boot. I added the
300G drive much later. I doubt that Linux ever used it. So why won't this
boot up and give me the standard DOS Linux choices? I believe Linux is using
the LILO loader.

Your first task is to find out if you have a CPU/Motherboard
problem or a disk/disk controller problem. Booting the machine
with a boot CD or a boot floppy (www.bootdisk.com) will tell
you straight away.
 
W

W. Watson

It booted up in an old copy of DR DOS, but couldn't see the C-drive. I then
"booted" up the a 4 disk (floppy) from 7/2005 of W2K. I'm now sitting at a
window that gives me three choices. Install, Repair or Quit. I guess I have
no choice but to repair, but is that wise?
 
P

Pegasus \(MVP\)

No, Repair is not your best option at this stage. Here is what
you should do:
- Format a floppy disk on some other Win2000/XP PC.
Don't do it on a Win9x PC - it won't work.
- Copy these files from the \i386 folder of your Win2000 CD to A:\
ntldr
ntdetect.com
- Create a file a:\boot.ini with these lines
[Boot Loader]
Timeout=3
Default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[Operating Systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="1 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINNT="2 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(0)partition(3)\WINNT="3 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(1)\WINNT="4 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(2)\WINNT="5 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(3)\WINNT="6 Microsoft Windows 2000
Professional" /fastdetect
- Boot the machine with this floppy

Try each of the boot options to see if one of them works.
 
W

W. Watson

I tried this but it stalled right after verifying the DMI pool successfully.
It may be that I took ntldr to be part of the folder name, as in
a:\ntldr. What is the structure on A:

ntldr (a file??)
ntdetect.com
boot.ini

or
ntldr (a folder)
nttdetect.com
boot.ini

BTW, I'm on w2k pro. Here's my ini file: (and I think I see a mistake. see
below)
[boot loader]
timeout=3
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="1 Microsoft Windows " /fastdetect
/NoExecute=OptIn
multi(0)disk(0)rdisk(0)partition(2)\WINNT="2 Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(0)partition(3)\WINNT="3 Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(1)partition(1)\WINNT="4 Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(1)partition(2)\WINNT="5 Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(1)partition(3)\WINNT="6 Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn

The WINNT line does not have 2000 Professional.

I'll be back later after I make the change.
Pegasus said:
No, Repair is not your best option at this stage. Here is what
you should do:
- Format a floppy disk on some other Win2000/XP PC.
Don't do it on a Win9x PC - it won't work.
- Copy these files from the \i386 folder of your Win2000 CD to A:\
ntldr
ntdetect.com
- Create a file a:\boot.ini with these lines
[Boot Loader]
Timeout=3
Default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[Operating Systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="1 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINNT="2 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(0)partition(3)\WINNT="3 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(1)\WINNT="4 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(2)\WINNT="5 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(3)\WINNT="6 Microsoft Windows 2000
Professional" /fastdetect
- Boot the machine with this floppy

Try each of the boot options to see if one of them works.
 
P

Pegasus \(MVP\)

I wrote
===============
Copy these files from the \i386 folder of your Win2000 CD to A:\

ntldr
ntdetect.com
===============

This means: go to the i386 folder on the CD, then take the two
files and copy them to the root of A:.

The words in boot.ini between double quotes are comments.
You can put "Cat and dog" in there - it would not matter.

You must, of course, instruct your BIOS to boot from the
floppy disk.


W. Watson said:
I tried this but it stalled right after verifying the DMI pool successfully.
It may be that I took ntldr to be part of the folder name, as in
a:\ntldr. What is the structure on A:

ntldr (a file??)
ntdetect.com
boot.ini

or
ntldr (a folder)
nttdetect.com
boot.ini

BTW, I'm on w2k pro. Here's my ini file: (and I think I see a mistake. see
below)
[boot loader]
timeout=3
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="1 Microsoft Windows " /fastdetect
/NoExecute=OptIn
multi(0)disk(0)rdisk(0)partition(2)\WINNT="2 Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(0)partition(3)\WINNT="3 Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(1)partition(1)\WINNT="4 Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(1)partition(2)\WINNT="5 Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(1)partition(3)\WINNT="6 Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn

The WINNT line does not have 2000 Professional.

I'll be back later after I make the change.
Pegasus said:
No, Repair is not your best option at this stage. Here is what
you should do:
- Format a floppy disk on some other Win2000/XP PC.
Don't do it on a Win9x PC - it won't work.
- Copy these files from the \i386 folder of your Win2000 CD to A:\
ntldr
ntdetect.com
- Create a file a:\boot.ini with these lines
[Boot Loader]
Timeout=3
Default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[Operating Systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="1 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINNT="2 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(0)partition(3)\WINNT="3 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(1)\WINNT="4 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(2)\WINNT="5 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(3)\WINNT="6 Microsoft Windows 2000
Professional" /fastdetect
- Boot the machine with this floppy

Try each of the boot options to see if one of them works.

W. Watson said:
It booted up in an old copy of DR DOS, but couldn't see the C-drive. I then
"booted" up the a 4 disk (floppy) from 7/2005 of W2K. I'm now sitting at a
window that gives me three choices. Install, Repair or Quit. I guess I have
no choice but to repair, but is that wise?

W. Watson wrote:
Good idea. Thanks.

Pegasus (MVP) wrote:
Well, things are not going according to Hoyle. I found the defective HD
was
a 300G WDL that I purchased not too many months ago, and was using it
as a
slave. I took it out, and tried firing up the system with the master,
80G
WDL WD800BB-75CAA0. I installed it at the end of the cable as a
single
master, and removed the jumpers. My sys has an Athlon XP 2200+ CPU.
When I
boot up I get:

Primary IDE no 80-pin cable installed.
CPU is unworkable or has changed.
CMOS checksum error--defaults loaded.

If I continue, I get a screen full of data about devices (DMI pool), and
then an L.

I changed out the cable to an 80-pin cable, blue, grey, and black.
Got the
same results without the checksum error. It appears the L is from Linux.
Originally, my machine only had w2k and Linux as a dual boot. I added
the
300G drive much later. I doubt that Linux ever used it. So why won't
this
boot up and give me the standard DOS Linux choices? I believe Linux is
using
the LILO loader.


--
Wayne Watson (Nevada City, CA)

Web Page: <speckledwithStars.net>
Your first task is to find out if you have a CPU/Motherboard
problem or a disk/disk controller problem. Booting the machine
with a boot CD or a boot floppy (www.bootdisk.com) will tell
you straight away.
 
W

W. Watson

Good. That worked fine. The first entry got me into W2K. What file do I
modify with the boot.ini file entries that I produced per our exchange? I
would guess it only requires the replacement of the first multi() entry from
the boot.ini file I created.

multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn

I really do not need or use Linux. I would think there is some Linux entry
similar to the multi() entries that I could just remove.
I wrote
===============
Copy these files from the \i386 folder of your Win2000 CD to A:\

ntldr
ntdetect.com
===============

This means: go to the i386 folder on the CD, then take the two
files and copy them to the root of A:.

The words in boot.ini between double quotes are comments.
You can put "Cat and dog" in there - it would not matter.

You must, of course, instruct your BIOS to boot from the
floppy disk.


W. Watson said:
I tried this but it stalled right after verifying the DMI pool successfully.
It may be that I took ntldr to be part of the folder name, as in
a:\ntldr. What is the structure on A:

ntldr (a file??)
ntdetect.com
boot.ini

or
ntldr (a folder)
nttdetect.com
boot.ini

BTW, I'm on w2k pro. Here's my ini file: (and I think I see a mistake. see
below)
[boot loader]
timeout=3
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="1 Microsoft Windows " /fastdetect
/NoExecute=OptIn
multi(0)disk(0)rdisk(0)partition(2)\WINNT="2 Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(0)partition(3)\WINNT="3 Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(1)partition(1)\WINNT="4 Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(1)partition(2)\WINNT="5 Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(1)partition(3)\WINNT="6 Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn

The WINNT line does not have 2000 Professional.

I'll be back later after I make the change.
Pegasus said:
No, Repair is not your best option at this stage. Here is what
you should do:
- Format a floppy disk on some other Win2000/XP PC.
Don't do it on a Win9x PC - it won't work.
- Copy these files from the \i386 folder of your Win2000 CD to A:\
ntldr
ntdetect.com
- Create a file a:\boot.ini with these lines
[Boot Loader]
Timeout=3
Default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[Operating Systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="1 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINNT="2 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(0)partition(3)\WINNT="3 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(1)\WINNT="4 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(2)\WINNT="5 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(3)\WINNT="6 Microsoft Windows 2000
Professional" /fastdetect
- Boot the machine with this floppy

Try each of the boot options to see if one of them works.

It booted up in an old copy of DR DOS, but couldn't see the C-drive. I
then
"booted" up the a 4 disk (floppy) from 7/2005 of W2K. I'm now sitting at a
window that gives me three choices. Install, Repair or Quit. I guess I
have
no choice but to repair, but is that wise?

W. Watson wrote:
Good idea. Thanks.

Pegasus (MVP) wrote:
Well, things are not going according to Hoyle. I found the defective
HD
was
a 300G WDL that I purchased not too many months ago, and was using it
as a
slave. I took it out, and tried firing up the system with the master,
80G
WDL WD800BB-75CAA0. I installed it at the end of the cable as a single
master, and removed the jumpers. My sys has an Athlon XP 2200+ CPU.
When I
boot up I get:

Primary IDE no 80-pin cable installed.
CPU is unworkable or has changed.
CMOS checksum error--defaults loaded.

If I continue, I get a screen full of data about devices (DMI pool),
and
then an L.

I changed out the cable to an 80-pin cable, blue, grey, and black.
Got the
same results without the checksum error. It appears the L is from
Linux.
Originally, my machine only had w2k and Linux as a dual boot. I added
the
300G drive much later. I doubt that Linux ever used it. So why won't
this
boot up and give me the standard DOS Linux choices? I believe Linux is
using
the LILO loader.


--
Wayne Watson (Nevada City, CA)

Web Page: <speckledwithStars.net>
Your first task is to find out if you have a CPU/Motherboard
problem or a disk/disk controller problem. Booting the machine
with a boot CD or a boot floppy (www.bootdisk.com) will tell
you straight away.
 
P

Pegasus \(MVP\)

You make the hidden file c:\boot.ini the same as a:\boot.ini
but you omit the irrelevant lines (most of those I labelled
"1 Microsoft" etc).

You may still face a problem when booting from the hard disk.
If you do then you must boot the machine into the Recovery
Console, using your Win2000 CD, and run these commands:
fixmbr
fixboot


W. Watson said:
Good. That worked fine. The first entry got me into W2K. What file do I
modify with the boot.ini file entries that I produced per our exchange? I
would guess it only requires the replacement of the first multi() entry from
the boot.ini file I created.

multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn

I really do not need or use Linux. I would think there is some Linux entry
similar to the multi() entries that I could just remove.
I wrote
===============
Copy these files from the \i386 folder of your Win2000 CD to A:\

ntldr
ntdetect.com
===============

This means: go to the i386 folder on the CD, then take the two
files and copy them to the root of A:.

The words in boot.ini between double quotes are comments.
You can put "Cat and dog" in there - it would not matter.

You must, of course, instruct your BIOS to boot from the
floppy disk.


W. Watson said:
I tried this but it stalled right after verifying the DMI pool successfully.
It may be that I took ntldr to be part of the folder name, as in
a:\ntldr. What is the structure on A:

ntldr (a file??)
ntdetect.com
boot.ini

or
ntldr (a folder)
nttdetect.com
boot.ini

BTW, I'm on w2k pro. Here's my ini file: (and I think I see a mistake. see
below)
[boot loader]
timeout=3
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="1 Microsoft Windows " /fastdetect
/NoExecute=OptIn
multi(0)disk(0)rdisk(0)partition(2)\WINNT="2 Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(0)partition(3)\WINNT="3 Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(1)partition(1)\WINNT="4 Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(1)partition(2)\WINNT="5 Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(1)partition(3)\WINNT="6 Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn

The WINNT line does not have 2000 Professional.

I'll be back later after I make the change.
Pegasus (MVP) wrote:
No, Repair is not your best option at this stage. Here is what
you should do:
- Format a floppy disk on some other Win2000/XP PC.
Don't do it on a Win9x PC - it won't work.
- Copy these files from the \i386 folder of your Win2000 CD to A:\
ntldr
ntdetect.com
- Create a file a:\boot.ini with these lines
[Boot Loader]
Timeout=3
Default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[Operating Systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="1 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINNT="2 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(0)partition(3)\WINNT="3 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(1)\WINNT="4 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(2)\WINNT="5 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(3)\WINNT="6 Microsoft Windows 2000
Professional" /fastdetect
- Boot the machine with this floppy

Try each of the boot options to see if one of them works.

It booted up in an old copy of DR DOS, but couldn't see the C-drive. I
then
"booted" up the a 4 disk (floppy) from 7/2005 of W2K. I'm now sitting at a
window that gives me three choices. Install, Repair or Quit. I guess I
have
no choice but to repair, but is that wise?

W. Watson wrote:
Good idea. Thanks.

Pegasus (MVP) wrote:
Well, things are not going according to Hoyle. I found the defective
HD
was
a 300G WDL that I purchased not too many months ago, and was using it
as a
slave. I took it out, and tried firing up the system with the master,
80G
WDL WD800BB-75CAA0. I installed it at the end of the cable as a single
master, and removed the jumpers. My sys has an Athlon XP 2200+ CPU.
When I
boot up I get:

Primary IDE no 80-pin cable installed.
CPU is unworkable or has changed.
CMOS checksum error--defaults loaded.

If I continue, I get a screen full of data about devices (DMI pool),
and
then an L.

I changed out the cable to an 80-pin cable, blue, grey, and black.
Got the
same results without the checksum error. It appears the L is from
Linux.
Originally, my machine only had w2k and Linux as a dual boot. I added
the
300G drive much later. I doubt that Linux ever used it. So why won't
this
boot up and give me the standard DOS Linux choices? I believe
Linux
is
using
the LILO loader.


--
Wayne Watson (Nevada City, CA)

Web Page: <speckledwithStars.net>
Your first task is to find out if you have a CPU/Motherboard
problem or a disk/disk controller problem. Booting the machine
with a boot CD or a boot floppy (www.bootdisk.com) will tell
you straight away.
 
W

W. Watson

Things are not looking good. I no longer seem to have a cpu. Maybe it got
overheated, so I'll try later. However, I can't even get to a BIOS screen of
any sort. Of course my monitor could have died, but it's unlikely. There
just too many anomalies now. I can't power off with the switch in the front,
and have to pull the plug instead. Once I plug it in and push the start
button, it's trying to do something but nothing appears on the monitor.

I've tried booting from the floppy and a CD (upgrade CD for w2k), and am
getting nowhere. I'll look at the power switches on the front and see if
they have been damaged, but it seems unlikely they have anything to do with
the disappearance of BIOS. Interestingly, the upgrade CD makes an odd noise
when I put it in the CD player, but an NT 4 CD does not. This is getting weird.
You make the hidden file c:\boot.ini the same as a:\boot.ini
but you omit the irrelevant lines (most of those I labelled
"1 Microsoft" etc).

You may still face a problem when booting from the hard disk.
If you do then you must boot the machine into the Recovery
Console, using your Win2000 CD, and run these commands:
fixmbr
fixboot


W. Watson said:
Good. That worked fine. The first entry got me into W2K. What file do I
modify with the boot.ini file entries that I produced per our exchange? I
would guess it only requires the replacement of the first multi() entry from
the boot.ini file I created.

multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn

I really do not need or use Linux. I would think there is some Linux entry
similar to the multi() entries that I could just remove.
I wrote
===============
Copy these files from the \i386 folder of your Win2000 CD to A:\

ntldr
ntdetect.com
===============

This means: go to the i386 folder on the CD, then take the two
files and copy them to the root of A:.

The words in boot.ini between double quotes are comments.
You can put "Cat and dog" in there - it would not matter.

You must, of course, instruct your BIOS to boot from the
floppy disk.


I tried this but it stalled right after verifying the DMI pool
successfully.
It may be that I took ntldr to be part of the folder name, as in
a:\ntldr. What is the structure on A:

ntldr (a file??)
ntdetect.com
boot.ini

or
ntldr (a folder)
nttdetect.com
boot.ini

BTW, I'm on w2k pro. Here's my ini file: (and I think I see a mistake. see
below)
[boot loader]
timeout=3
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="1 Microsoft Windows "
/fastdetect
/NoExecute=OptIn
multi(0)disk(0)rdisk(0)partition(2)\WINNT="2 Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(0)partition(3)\WINNT="3 Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(1)partition(1)\WINNT="4 Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(1)partition(2)\WINNT="5 Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(1)partition(3)\WINNT="6 Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn

The WINNT line does not have 2000 Professional.

I'll be back later after I make the change.
Pegasus (MVP) wrote:
No, Repair is not your best option at this stage. Here is what
you should do:
- Format a floppy disk on some other Win2000/XP PC.
Don't do it on a Win9x PC - it won't work.
- Copy these files from the \i386 folder of your Win2000 CD to A:\
ntldr
ntdetect.com
- Create a file a:\boot.ini with these lines
[Boot Loader]
Timeout=3
Default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[Operating Systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="1 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINNT="2 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(0)partition(3)\WINNT="3 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(1)\WINNT="4 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(2)\WINNT="5 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(3)\WINNT="6 Microsoft Windows 2000
Professional" /fastdetect
- Boot the machine with this floppy

Try each of the boot options to see if one of them works.

It booted up in an old copy of DR DOS, but couldn't see the C-drive. I
then
"booted" up the a 4 disk (floppy) from 7/2005 of W2K. I'm now sitting
at a
window that gives me three choices. Install, Repair or Quit. I guess I
have
no choice but to repair, but is that wise?

W. Watson wrote:
Good idea. Thanks.

Pegasus (MVP) wrote:
Well, things are not going according to Hoyle. I found the defective
HD
was
a 300G WDL that I purchased not too many months ago, and was using
it
as a
slave. I took it out, and tried firing up the system with the
master,
80G
WDL WD800BB-75CAA0. I installed it at the end of the cable as a
single
master, and removed the jumpers. My sys has an Athlon XP 2200+ CPU.
When I
boot up I get:

Primary IDE no 80-pin cable installed.
CPU is unworkable or has changed.
CMOS checksum error--defaults loaded.

If I continue, I get a screen full of data about devices (DMI pool),
and
then an L.

I changed out the cable to an 80-pin cable, blue, grey, and black.
Got the
same results without the checksum error. It appears the L is from
Linux.
Originally, my machine only had w2k and Linux as a dual boot. I
added
the
300G drive much later. I doubt that Linux ever used it. So why won't
this
boot up and give me the standard DOS Linux choices? I believe Linux
is
using
the LILO loader.


--
Wayne Watson (Nevada City, CA)

Web Page: <speckledwithStars.net>
Your first task is to find out if you have a CPU/Motherboard
problem or a disk/disk controller problem. Booting the machine
with a boot CD or a boot floppy (www.bootdisk.com) will tell
you straight away.
 
P

Pegasus \(MVP\)

A CPU/motherboard failure was my first suspicion. Without a CPU
you won't get into the BIOS. Time for a hardware upgrade?

W. Watson said:
Things are not looking good. I no longer seem to have a cpu. Maybe it got
overheated, so I'll try later. However, I can't even get to a BIOS screen of
any sort. Of course my monitor could have died, but it's unlikely. There
just too many anomalies now. I can't power off with the switch in the front,
and have to pull the plug instead. Once I plug it in and push the start
button, it's trying to do something but nothing appears on the monitor.

I've tried booting from the floppy and a CD (upgrade CD for w2k), and am
getting nowhere. I'll look at the power switches on the front and see if
they have been damaged, but it seems unlikely they have anything to do with
the disappearance of BIOS. Interestingly, the upgrade CD makes an odd noise
when I put it in the CD player, but an NT 4 CD does not. This is getting weird.
You make the hidden file c:\boot.ini the same as a:\boot.ini
but you omit the irrelevant lines (most of those I labelled
"1 Microsoft" etc).

You may still face a problem when booting from the hard disk.
If you do then you must boot the machine into the Recovery
Console, using your Win2000 CD, and run these commands:
fixmbr
fixboot


W. Watson said:
Good. That worked fine. The first entry got me into W2K. What file do I
modify with the boot.ini file entries that I produced per our exchange? I
would guess it only requires the replacement of the first multi() entry from
the boot.ini file I created.

multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn

I really do not need or use Linux. I would think there is some Linux entry
similar to the multi() entries that I could just remove.

Pegasus (MVP) wrote:
I wrote
===============
Copy these files from the \i386 folder of your Win2000 CD to A:\

ntldr
ntdetect.com
===============

This means: go to the i386 folder on the CD, then take the two
files and copy them to the root of A:.

The words in boot.ini between double quotes are comments.
You can put "Cat and dog" in there - it would not matter.

You must, of course, instruct your BIOS to boot from the
floppy disk.


I tried this but it stalled right after verifying the DMI pool
successfully.
It may be that I took ntldr to be part of the folder name, as in
a:\ntldr. What is the structure on A:

ntldr (a file??)
ntdetect.com
boot.ini

or
ntldr (a folder)
nttdetect.com
boot.ini

BTW, I'm on w2k pro. Here's my ini file: (and I think I see a
mistake.
see
below)
[boot loader]
timeout=3
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="1 Microsoft Windows "
/fastdetect
/NoExecute=OptIn
multi(0)disk(0)rdisk(0)partition(2)\WINNT="2 Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(0)partition(3)\WINNT="3 Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(1)partition(1)\WINNT="4 Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(1)partition(2)\WINNT="5 Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(1)partition(3)\WINNT="6 Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn

The WINNT line does not have 2000 Professional.

I'll be back later after I make the change.
Pegasus (MVP) wrote:
No, Repair is not your best option at this stage. Here is what
you should do:
- Format a floppy disk on some other Win2000/XP PC.
Don't do it on a Win9x PC - it won't work.
- Copy these files from the \i386 folder of your Win2000 CD to A:\
ntldr
ntdetect.com
- Create a file a:\boot.ini with these lines
[Boot Loader]
Timeout=3
Default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[Operating Systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="1 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINNT="2 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(0)partition(3)\WINNT="3 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(1)\WINNT="4 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(2)\WINNT="5 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(3)\WINNT="6 Microsoft Windows 2000
Professional" /fastdetect
- Boot the machine with this floppy

Try each of the boot options to see if one of them works.

It booted up in an old copy of DR DOS, but couldn't see the
C-drive.
I
then
"booted" up the a 4 disk (floppy) from 7/2005 of W2K. I'm now sitting
at a
window that gives me three choices. Install, Repair or Quit. I
guess
I
have
no choice but to repair, but is that wise?

W. Watson wrote:
Good idea. Thanks.

Pegasus (MVP) wrote:
Well, things are not going according to Hoyle. I found the defective
HD
was
a 300G WDL that I purchased not too many months ago, and was using
it
as a
slave. I took it out, and tried firing up the system with the
master,
80G
WDL WD800BB-75CAA0. I installed it at the end of the cable as a
single
master, and removed the jumpers. My sys has an Athlon XP 2200+ CPU.
When I
boot up I get:

Primary IDE no 80-pin cable installed.
CPU is unworkable or has changed.
CMOS checksum error--defaults loaded.

If I continue, I get a screen full of data about devices (DMI pool),
and
then an L.

I changed out the cable to an 80-pin cable, blue, grey, and black.
Got the
same results without the checksum error. It appears the L is from
Linux.
Originally, my machine only had w2k and Linux as a dual boot. I
added
the
300G drive much later. I doubt that Linux ever used it. So why won't
this
boot up and give me the standard DOS Linux choices? I believe Linux
is
using
the LILO loader.


--
Wayne Watson (Nevada City, CA)

Web Page: <speckledwithStars.net>
Your first task is to find out if you have a CPU/Motherboard
problem or a disk/disk controller problem. Booting the machine
with a boot CD or a boot floppy (www.bootdisk.com) will tell
you straight away.
 
W

W. Watson

Seems likely. I hope the troublesome MB wasn't responsible for trashing the
hard drive. Fortunately, there wasn't much of value out there, and it was a
lot older drive than I thought.
A CPU/motherboard failure was my first suspicion. Without a CPU
you won't get into the BIOS. Time for a hardware upgrade?

W. Watson said:
Things are not looking good. I no longer seem to have a cpu. Maybe it got
overheated, so I'll try later. However, I can't even get to a BIOS screen of
any sort. Of course my monitor could have died, but it's unlikely. There
just too many anomalies now. I can't power off with the switch in the front,
and have to pull the plug instead. Once I plug it in and push the start
button, it's trying to do something but nothing appears on the monitor.

I've tried booting from the floppy and a CD (upgrade CD for w2k), and am
getting nowhere. I'll look at the power switches on the front and see if
they have been damaged, but it seems unlikely they have anything to do with
the disappearance of BIOS. Interestingly, the upgrade CD makes an odd noise
when I put it in the CD player, but an NT 4 CD does not. This is getting weird.
Pegasus said:
You make the hidden file c:\boot.ini the same as a:\boot.ini
but you omit the irrelevant lines (most of those I labelled
"1 Microsoft" etc).

You may still face a problem when booting from the hard disk.
If you do then you must boot the machine into the Recovery
Console, using your Win2000 CD, and run these commands:
fixmbr
fixboot


Good. That worked fine. The first entry got me into W2K. What file do I
modify with the boot.ini file entries that I produced per our exchange? I
would guess it only requires the replacement of the first multi() entry
from
the boot.ini file I created.

multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn

I really do not need or use Linux. I would think there is some Linux entry
similar to the multi() entries that I could just remove.

Pegasus (MVP) wrote:
I wrote
===============
Copy these files from the \i386 folder of your Win2000 CD to A:\

ntldr
ntdetect.com
===============

This means: go to the i386 folder on the CD, then take the two
files and copy them to the root of A:.

The words in boot.ini between double quotes are comments.
You can put "Cat and dog" in there - it would not matter.

You must, of course, instruct your BIOS to boot from the
floppy disk.


I tried this but it stalled right after verifying the DMI pool
successfully.
It may be that I took ntldr to be part of the folder name, as in
a:\ntldr. What is the structure on A:

ntldr (a file??)
ntdetect.com
boot.ini

or
ntldr (a folder)
nttdetect.com
boot.ini

BTW, I'm on w2k pro. Here's my ini file: (and I think I see a mistake.
see
below)
[boot loader]
timeout=3
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="1 Microsoft Windows "
/fastdetect
/NoExecute=OptIn
multi(0)disk(0)rdisk(0)partition(2)\WINNT="2 Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(0)partition(3)\WINNT="3 Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(1)partition(1)\WINNT="4 Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(1)partition(2)\WINNT="5 Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(1)partition(3)\WINNT="6 Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn

The WINNT line does not have 2000 Professional.

I'll be back later after I make the change.
Pegasus (MVP) wrote:
No, Repair is not your best option at this stage. Here is what
you should do:
- Format a floppy disk on some other Win2000/XP PC.
Don't do it on a Win9x PC - it won't work.
- Copy these files from the \i386 folder of your Win2000 CD to A:\
ntldr
ntdetect.com
- Create a file a:\boot.ini with these lines
[Boot Loader]
Timeout=3
Default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[Operating Systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="1 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINNT="2 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(0)partition(3)\WINNT="3 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(1)\WINNT="4 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(2)\WINNT="5 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(3)\WINNT="6 Microsoft Windows 2000
Professional" /fastdetect
- Boot the machine with this floppy

Try each of the boot options to see if one of them works.

It booted up in an old copy of DR DOS, but couldn't see the C-drive.
I
then
"booted" up the a 4 disk (floppy) from 7/2005 of W2K. I'm now sitting
at a
window that gives me three choices. Install, Repair or Quit. I guess
I
have
no choice but to repair, but is that wise?

W. Watson wrote:
Good idea. Thanks.

Pegasus (MVP) wrote:
Well, things are not going according to Hoyle. I found the
defective
HD
was
a 300G WDL that I purchased not too many months ago, and was using
it
as a
slave. I took it out, and tried firing up the system with the
master,
80G
WDL WD800BB-75CAA0. I installed it at the end of the cable as a
single
master, and removed the jumpers. My sys has an Athlon XP 2200+
CPU.
When I
boot up I get:

Primary IDE no 80-pin cable installed.
CPU is unworkable or has changed.
CMOS checksum error--defaults loaded.

If I continue, I get a screen full of data about devices (DMI
pool),
and
then an L.

I changed out the cable to an 80-pin cable, blue, grey, and black.
Got the
same results without the checksum error. It appears the L is from
Linux.
Originally, my machine only had w2k and Linux as a dual boot. I
added
the
300G drive much later. I doubt that Linux ever used it. So why
won't
this
boot up and give me the standard DOS Linux choices? I believe
Linux
is
using
the LILO loader.


--
Wayne Watson (Nevada City, CA)

Web Page: <speckledwithStars.net>
Your first task is to find out if you have a CPU/Motherboard
problem or a disk/disk controller problem. Booting the machine
with a boot CD or a boot floppy (www.bootdisk.com) will tell
you straight away.
 
W

W. Watson

Traumatized but not dead. I was talking to a friend about not being
available later today, because I was going to buy a new computer. Short
story on what I told him about the symptoms is that he suggested removing
the 3v battery. I did and that got me to cmos. "It's allliiivvve!", so
sayeth Dr. Frankenstein. :) An old trick I had completely forgotten about.

Anyway, I'm going to replace the battery and proceed to see what is really
working.

W. Watson said:
Seems likely. I hope the troublesome MB wasn't responsible for trashing
the hard drive. Fortunately, there wasn't much of value out there, and
it was a lot older drive than I thought.
A CPU/motherboard failure was my first suspicion. Without a CPU
you won't get into the BIOS. Time for a hardware upgrade?

W. Watson said:
Things are not looking good. I no longer seem to have a cpu. Maybe it
got
overheated, so I'll try later. However, I can't even get to a BIOS
screen of
any sort. Of course my monitor could have died, but it's unlikely. There
just too many anomalies now. I can't power off with the switch in the front,
and have to pull the plug instead. Once I plug it in and push the start
button, it's trying to do something but nothing appears on the monitor.

I've tried booting from the floppy and a CD (upgrade CD for w2k), and am
getting nowhere. I'll look at the power switches on the front and see if
they have been damaged, but it seems unlikely they have anything to do with
the disappearance of BIOS. Interestingly, the upgrade CD makes an odd noise
when I put it in the CD player, but an NT 4 CD does not. This is getting weird.
Pegasus (MVP) wrote:
You make the hidden file c:\boot.ini the same as a:\boot.ini
but you omit the irrelevant lines (most of those I labelled
"1 Microsoft" etc).

You may still face a problem when booting from the hard disk.
If you do then you must boot the machine into the Recovery
Console, using your Win2000 CD, and run these commands:
fixmbr
fixboot


Good. That worked fine. The first entry got me into W2K. What file do I
modify with the boot.ini file entries that I produced per our
exchange? I
would guess it only requires the replacement of the first multi()
entry
from
the boot.ini file I created.

multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn

I really do not need or use Linux. I would think there is some Linux entry
similar to the multi() entries that I could just remove.

Pegasus (MVP) wrote:
I wrote
===============
Copy these files from the \i386 folder of your Win2000 CD to A:\

ntldr
ntdetect.com
===============

This means: go to the i386 folder on the CD, then take the two
files and copy them to the root of A:.

The words in boot.ini between double quotes are comments.
You can put "Cat and dog" in there - it would not matter.

You must, of course, instruct your BIOS to boot from the
floppy disk.


I tried this but it stalled right after verifying the DMI pool
successfully.
It may be that I took ntldr to be part of the folder name, as in
a:\ntldr. What is the structure on A:

ntldr (a file??)
ntdetect.com
boot.ini

or
ntldr (a folder)
nttdetect.com
boot.ini

BTW, I'm on w2k pro. Here's my ini file: (and I think I see a mistake.
see
below)
[boot loader]
timeout=3
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="1 Microsoft Windows "
/fastdetect
/NoExecute=OptIn
multi(0)disk(0)rdisk(0)partition(2)\WINNT="2 Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(0)partition(3)\WINNT="3 Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(1)partition(1)\WINNT="4 Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(1)partition(2)\WINNT="5 Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(1)partition(3)\WINNT="6 Microsoft Windows 2000
Professional" /fastdetect /NoExecute=OptIn

The WINNT line does not have 2000 Professional.

I'll be back later after I make the change.
Pegasus (MVP) wrote:
No, Repair is not your best option at this stage. Here is what
you should do:
- Format a floppy disk on some other Win2000/XP PC.
Don't do it on a Win9x PC - it won't work.
- Copy these files from the \i386 folder of your Win2000 CD to A:\
ntldr
ntdetect.com
- Create a file a:\boot.ini with these lines
[Boot Loader]
Timeout=3
Default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[Operating Systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="1 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINNT="2 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(0)partition(3)\WINNT="3 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(1)\WINNT="4 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(2)\WINNT="5 Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(3)\WINNT="6 Microsoft Windows 2000
Professional" /fastdetect
- Boot the machine with this floppy

Try each of the boot options to see if one of them works.

It booted up in an old copy of DR DOS, but couldn't see the C-drive.
I
then
"booted" up the a 4 disk (floppy) from 7/2005 of W2K. I'm now sitting
at a
window that gives me three choices. Install, Repair or Quit. I guess
I
have
no choice but to repair, but is that wise?

W. Watson wrote:
Good idea. Thanks.

Pegasus (MVP) wrote:
Well, things are not going according to Hoyle. I found the
defective
HD
was
a 300G WDL that I purchased not too many months ago, and was using
it
as a
slave. I took it out, and tried firing up the system with the
master,
80G
WDL WD800BB-75CAA0. I installed it at the end of the cable as a
single
master, and removed the jumpers. My sys has an Athlon XP 2200+
CPU.
When I
boot up I get:

Primary IDE no 80-pin cable installed.
CPU is unworkable or has changed.
CMOS checksum error--defaults loaded.

If I continue, I get a screen full of data about devices (DMI
pool),
and
then an L.

I changed out the cable to an 80-pin cable, blue, grey, and black.
Got the
same results without the checksum error. It appears the L is from
Linux.
Originally, my machine only had w2k and Linux as a dual boot. I
added
the
300G drive much later. I doubt that Linux ever used it. So why
won't
this
boot up and give me the standard DOS Linux choices? I believe
Linux
is
using
the LILO loader.


--
Wayne Watson (Nevada City, CA)

Web Page: <speckledwithStars.net>
Your first task is to find out if you have a CPU/Motherboard
problem or a disk/disk controller problem. Booting the machine
with a boot CD or a boot floppy (www.bootdisk.com) will tell
you straight away.


--
Wayne Watson (Nevada City, CA)

Web Page: <speckledwithStars.net>
 
W

W. Watson

W. Watson said:
Traumatized but not dead. I was talking to a friend about not being
available later today, because I was going to buy a new computer. Short
story on what I told him about the symptoms is that he suggested
removing the 3v battery. I did and that got me to cmos. "It's
allliiivvve!", so sayeth Dr. Frankenstein. :) An old trick I had
completely forgotten about.

(A slight digression in the first two paragraphs, but then into the meat. I
started them as I thought we were done for the night.)
Keeping the battery out of the computer allows me too see BIOS. I can boot
W2K up from a floppy. If the new battery goes in, then I can't see BIOS.
This is nutty. I have to keep the cmos battery out to do anything.

I cannot boot up from the MS 2000 CD to get at the Repair Console, since
this requires being able to modify BIOS to put the CD ahead of the HD. Stop.
It's now solved, so I no longer need to continue with this paragraph.

Well, I wrote the above about 2 hours ago in the midst of a marathon session
with a buddy who stopped over to help with some X-10 work. I mentioned
something about my difficulty, and he immediately got interested in solving
this tough nut. We never got to X-10, but after 5 hours did solve it.

A side issue that consumed a lot of time was the Win 2K install (for getting
at the Remote Console) CD that emitted unusual sounds, and wouldn't boot
under any circumstances. It would boot in other PCs. By the time I decided
to make a copy of it and use the copy for the problem PC, we had solved
almost all the problems without it. So now to the heart of this.

The real culprit were both the old and new batteries for different reasons.
The old battery simply failed as mentioned in my previous post. It couldn't
hold BIOS settings. When the new battery was put it in, it just wouldn't
work, so we had to resort to not using any batteries to get anywhere. When
we finally got W2K (the 4 w2k boot floppies I made at the MVP's suggestion
helped here.) back up, we decided to try the new battery again. It didn't
balk, but still had trouble holding BIOS. We'd have to reset BIOS as we
experimented with the W2K boot. Eventually, we theorize, we had the machine
up long enough that the battery started fully charging the capacitors of the
cmos chip. Finally, we could boot with the date/time, cpu speed, and other
settings changing. The cmos msg stopped appearing.

In summary, this boils down to a dead battery, and then getting enough time
on the new battery to hold the charge for cmos.

All seems well. We did have a slight digression at the end. My buddy decided
we should set the CPU speed to its max, 2200. I usually hold back at 2000.
All seemed OK until he happened into the Control Panel. It was really weird.
Folders that shouldn't be there, and they were empty. For awhile, we figured
we screwed up something by pushing the install CD into areas that didn't
quite get us to the Remote Console, as we struggled to figure out some way
to do so. Then it dawned on him that the speed was too high. Back to 2000,
where I normally run it. The CP is happy and it looks like this mystery that
started with my secondary 30G HD failing is at a happy ending. It looked for
quite awhile the CPU, MB or PSU might be the culprits.

The inventory of problems is:
bad battery
dead HD (it was 5 years old and contained little of interest)
new battery that took time to charge cmos
dual boot system that had to be resurrected to just W2k (which was OK by me)
flaky original W2k install CD.
possibly a flaky CD reader

The end of course, is that it wasn't the cpu, psu, or the motherboard, and I
don't have to buy new equipment. Yea!!
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top