You finally provided something to go on. Check that the correct drive type
is found in cmos setup or try an auto-configure for the drive controller's
channel setup.
--
Regards,
Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
"mike" wrote:
| Thanks for the input.
|
| The drive is an 80GB parallel IDE drive.
| I have a CDRW drive on secondary slave.
| If I install the drive as secondary master where it boots but boot from
| the win98 floppy:
| Ranish partition manager shows 3 fat32 partitions with the first one
active.
| Fdisk shows two fat32 partitions plus a third with the label ms-ramdrive
| like it
| was put there by the boot floppy, but it's 8gigabytes which happens
| to be the size of the third hard drive partition.??? The order is
| C,E,D with E having the ms-ramdrive label.
| First partition is still active.
| "dir c:" produces a listing of the C drive, as expected.
|
|
| If I install the drive as primary master where it won't boot and boot
| from the win98 floppy:
| Ranish partition manager shows the identical 3 fat32 partitions as before.
| Fdisk shows the same 3 partitions as before, but the first one is marked
| as unknown system type.
| "dir c:" gives an error "Invalid media type reading drive C"
| fdisk /mbr didn't help
|
| It appears that the partition is being interpreted differently depending
| whether the drive is primary master or secondary master.
|
| I HAVE done an extensive web search on this problem. I found several
| complaints about similar-sounding problems. Problem was blamed
| on win2k renaming it's boot drive letter to something that's no longer
| there, but no answers about fixing it.
|
| Remember that I had none of these problems until I temporarily installed
| a second hard drive as secondary master. I can ghost the image of the
| C drive back and the system will work normally again.
|
| I have tried "fixboot" in the past, but don't remember how I got did it,
| 'cause the repair console is on the drive that won't boot.
|
| Ideas?
| thanks, mike