No boot with single HD

  • Thread starter Thread starter Z
  • Start date Start date
Z

Z

I have a 40GB & 1.2GB WD hard drives. I had the 1.2Gb as the main drive,
then purchased the 40Gb.

I installed W2K & latest updates on the 40GB drive "C". Erased all of the
1.2GB to use it as a backup for downloads on "D".

The drive cable became flakey & the system would not boot. I removed
the1.2GB drive & tried the new cable. No boot.

I used the WD diag floppy & it said there was no HD available. I put the
1.2GB drive back in the puter with the 40GB as master & 1.2 as slave.

It will boot with both drives, but not just the "C" drive with W2K
installed. It will not boot from just the 1.2GB alone.

When I do a detail dir of the 1.2GB drive it only shows my download folder &
no files outside of it.

Both the 40GB "C" drive & the 1.2GB "D" drive are default shared.

I did not want to reformat or re-install W2K untill all options are tried.

Anyone with a solution as to what I need from the 1.2GB copied over to the
40GB?

Zeke
 
"No boot" tells us nothing of the problem.

--
Regards,

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


:
| I have a 40GB & 1.2GB WD hard drives. I had the 1.2Gb as the main drive,
| then purchased the 40Gb.
|
| I installed W2K & latest updates on the 40GB drive "C". Erased all of the
| 1.2GB to use it as a backup for downloads on "D".
|
| The drive cable became flakey & the system would not boot. I removed
| the1.2GB drive & tried the new cable. No boot.
|
| I used the WD diag floppy & it said there was no HD available. I put the
| 1.2GB drive back in the puter with the 40GB as master & 1.2 as slave.
|
| It will boot with both drives, but not just the "C" drive with W2K
| installed. It will not boot from just the 1.2GB alone.
|
| When I do a detail dir of the 1.2GB drive it only shows my download folder
&
| no files outside of it.
|
| Both the 40GB "C" drive & the 1.2GB "D" drive are default shared.
|
| I did not want to reformat or re-install W2K untill all options are tried.
|
| Anyone with a solution as to what I need from the 1.2GB copied over to the
| 40GB?
|
| Zeke
|
|
 
:
| I have a 40GB & 1.2GB WD hard drives. I had the 1.2Gb as the main drive,
| then purchased the 40Gb.
|
| I installed W2K & latest updates on the 40GB drive "C". Erased all of the
| 1.2GB to use it as a backup for downloads on "D".
Click to expand...

What _exactly_ was the sequence of steps you took to install W2K onto C:? At
what point did you "erase" D:? Etc.
 
It gets as far as searching for IDE drives & that is it . No Boot.

The Epox MoBo 8RDA+ with AMD 2200 stalls at "75h" which is detect & install
IDE drives for several minutes when the 40GB NTFS drive is attempting to
boot-up alone. Then it goes to a "DTR" or "DTE", (something like that,)
message to put in a system drive & reboot. MoBo & CPU & 40GB NTFS & 1.2Gb
FAT hard drives have worked together for months.

When both drives are in it does not pause in the boot process. MoBo then
gives "FFh" as complete. W2K then works.

It seems to either need something off the 1.2Gb drive or the cable
connection to boot with. Warm boot or cold boot does the same. I use one
new cable for both drives Master & Slave.

Boot with DOS & use SpinRite & SpinRite5 does not see the 40GB drive . It
will see the 1.2GB as the "2nd physical drive" & calls it "C". SpinRite
only sees the 1.2gb drive just the same as the Wester Digital diag program.

I wanted to replace the 1.2GB FAT drive with an 80GB drive for TV recording.

Z
 
Wolf Kirchmeir said:
What _exactly_ was the sequence of steps you took to install W2K onto C:?
Click to expand...

I just used the W2K install CD. The 40GB was the only drive at the time.
At what point did you "erase" D:? Etc.

I later put the 1.2GB drive back in & erased it. Used it for months as a
backup drive for downloads.

Z
 
I just used the W2K install CD. The 40GB was the only drive at the time.
Click to expand...

Well, then, the system should be booting from this drive.
I later put the 1.2GB drive back in & erased it. Used it for months as a
backup drive for downloads.

Z
Click to expand...

Do you mean you deleted all files that were on it, or that you reformatted
it? IMO, you should have reformatted it NTFS, but that might not have made a
difference anyway.

On reflection, I think what you are doing is "moving to new hardware",
because when you take the 1.2GB drive out, the hardware configuration
changes. W2K expects to find the drive, but can't. Try uninstalling the 1.2GB
drive from Device Manager, then power down and remove it.

Other than that, I have no suggestions. Sorry.
 
Z said:
I have a 40GB & 1.2GB WD hard drives. I had the 1.2Gb as the main drive,
then purchased the 40Gb.

I installed W2K & latest updates on the 40GB drive "C". Erased all of the
1.2GB to use it as a backup for downloads on "D".

The drive cable became flakey & the system would not boot. I removed
the1.2GB drive & tried the new cable. No boot.

I used the WD diag floppy & it said there was no HD available. I put the
1.2GB drive back in the puter with the 40GB as master & 1.2 as slave.

It will boot with both drives, but not just the "C" drive with W2K
installed. It will not boot from just the 1.2GB alone.

When I do a detail dir of the 1.2GB drive it only shows my download folder &
no files outside of it.

Both the 40GB "C" drive & the 1.2GB "D" drive are default shared.

I did not want to reformat or re-install W2K untill all options are tried.

Anyone with a solution as to what I need from the 1.2GB copied over to the
40GB?
Click to expand...

Sounds like several possibilities here.

With the system booting while both drives are installed but not with a
single drive, it sounds like you are leaving the Master/Slave jumpers in
place on the installed drive. All the IDE drives I've played with want to be
either Cable Select or unjumpered if installed as a standalone. (My
preference is unjumpered as it indicates this is truly a standalone drive.)
When connecting 2 drives on the same IDE channel, I suggest using
Master/Slave rather than Cable Select.

With the WD diagnostics utility not finding your drive, I'd re-examine the
Master/Slave jumpers. I'd also suspect the cable, the BIOS settings (Auto
works just fine for IDE drives in most all circumstances), and even the
possibility of a bum drive. Try using an ATA100 cable instead of an ATA66
cable - the signal quality on the ATA100 cables is better. Most of the time,
cable defects are not visible - do not rely upon visual inspection of the
cable. If it is a bum drive, it isn't necessarily the 40GB, but it becomes
the prime suspect. The age of the 1.2GB drive, however, also makes it a
suspect. There is a chance you spiked one of the controller boards along the
way.

Since I am not really sure about what the setup looked like when you did the
install to the 40GB drive, I won't even speculate on what Win2K did.
Concentrate first on the hardware and BIOS level. Get the DOS-based WD
diagnostics utility happy. If you can't settle that problem, there's no
sense in working on the OS problems.

As a personal suggestion, avoid SpinRite. I've encountered several problem
postings where people have used SpinRite and it made some rather undesirable
changes to the drive. (I do not recall whether those changes went all the
way to the controller board or if they were limited to the disk format.)
 
MyndPhlyp said:
folder

Sounds like several possibilities here.

With the system booting while both drives are installed but not with a
single drive, it sounds like you are leaving the Master/Slave jumpers in
place on the installed drive. All the IDE drives I've played with want to be
either Cable Select or unjumpered if installed as a standalone. (My
preference is unjumpered as it indicates this is truly a standalone drive.)
When connecting 2 drives on the same IDE channel, I suggest using
Master/Slave rather than Cable Select.

With the WD diagnostics utility not finding your drive, I'd re-examine the
Master/Slave jumpers. I'd also suspect the cable, the BIOS settings (Auto
works just fine for IDE drives in most all circumstances), and even the
possibility of a bum drive. Try using an ATA100 cable instead of an ATA66
cable - the signal quality on the ATA100 cables is better. Most of the time,
cable defects are not visible - do not rely upon visual inspection of the
cable. If it is a bum drive, it isn't necessarily the 40GB, but it becomes
the prime suspect. The age of the 1.2GB drive, however, also makes it a
suspect. There is a chance you spiked one of the controller boards along the
way.

Since I am not really sure about what the setup looked like when you did the
install to the 40GB drive, I won't even speculate on what Win2K did.
Concentrate first on the hardware and BIOS level. Get the DOS-based WD
diagnostics utility happy. If you can't settle that problem, there's no
sense in working on the OS problems.

As a personal suggestion, avoid SpinRite. I've encountered several problem
postings where people have used SpinRite and it made some rather undesirable
changes to the drive. (I do not recall whether those changes went all the
way to the controller board or if they were limited to the disk format.)
Click to expand...
***************************
BUT..... re-rig the drives so it will boot, go into add/remove programs,
check "show hidden devices" and remove all hard drives....you cant just add
something new to w2k, you have to remove the old one first.just a thought
 
EdK said:
BUT..... re-rig the drives so it will boot, go into add/remove programs,
check "show hidden devices" and remove all hard drives....you cant just add
something new to w2k, you have to remove the old one first.just a thought
Click to expand...

Good thought.

I seem to recall the OP mentioned somewhere in this thread the 1.2GB drive
was removed prior to installing Win2K on the 40GB drive. (I noticed it after
posting.) Which one of the two OSs gets booted would depend on which is the
Master and which is the Slave, wouldn't it?

Then the fun really begins. If the OP successfully installed to the 40GB
drive, has it configured as the Master with the 1.2GB as the Slave, and
boots into the OS on the 40GB drive does the OS have the 1.2GB drive
"installed" or is it just a peripheral hanging off the side? I seem to
recall you had to actually add the drive to the OS before it became
accessible, which would lead to the next step in the process - deleting the
contents of the 1.2GB drive.

Was the deletion of the contents of the 1.2GB drive a format or a delete?
Makes a bit of a difference. Personally, I would go the route you
mentioned - remove the drive from the OS first - and go one extra step - use
a DEBUG script to blow off the boot sector so that it appears like a virgin
drive.

Oh, this gets to be SO much fun.
 
Your 1.2gb drive contained the boot sector, the 40gb drive just contained
Win2K and was not thus active or bootable. The sys would only boot with both
drives in place.
Do not use cable select onless specifically recommended, use master and
slave jumpers only
David
 
Back
Top