1782- Disk Controller Failure

January 3, 2008

Re: 1782- Disk Controller Failure

"Ben Myers" <benjmyers@mindR-e-m-o-v-Espring.com> wrote in

news:#mtrKChTIHA.3400@TK2MSFTNGP03.phx.gbl:

>> > "ms" <ms@invalid.com> wrote in message

>> > news:5tlqaaF1e3mk8U1@mid.individual.net...

>> >> I'm using a P166 that was in an earlier thread as a test machine.

>> >> I have connected a series of used small hard drives to check their

>> >> status.

>> >> When sucessful, first get Setup screen, auto detect the hard

>> >> drive,

>

>> > then

>> >> reboot with a W98 boot disk, fdisk, then format.

>> >> Having success with 4 different drives, the motherboard, power

> cable,

>> >> data cable all are OK.

>> >> But 2 drives gave initially 1782 Disk Controller Failure.

>> >> I searched, find that if above items are ok, maybe the

>> >> master/slave

>

>> >> setting may cause this error.

>> >> One drive had a diagram, so it gave the error when set for Master.

>> >> The other, Western Digital 31000, saved a data page but not sure

>> >> of

>

>> > the

>> >> diagram for the plug.

>> >> Is it likely that both drives are defective from the above data?

>> "Ben Myers" <benjmyers@mindR-e-m-o-v-Espring.com> wrote in

>> > Try the drives on a known good computer

>> > If this is the Compaq 8702, the diagnostic utility may be helpful.

>> > ftp://ftp.hp.com/pub/softpaq/sp02001-02500/sp2141.exe

>

>> Thanks, Ben,

>> That Compaq utility is the one you recommended before, when I see the

> A

>> drive, it does allow configuring the BIOS for the drive, I used it on

>> several drives that were FAT-32 in this machine.

>> But it seems the 3 problem drives can only be tried on a NT type

> machine,

>

> NTFS, FAT32 and FAT are file systems, not computer types.

> The "NTDLR is missing" message you are receiving is being generated by

> a NT style boot loader on the disks themselves.

>

>> I have one but it's not handy for this, and my intent is for these

> drives

>> to be used in a W98 machine. So if they check out as NT drives, it

> does

>> not get me FAT-32.

>

> The "NTDLR is missing" message does not necessarily mean there are

> NTFS partitions on the drive. Use the Windows 98 version of fdisk to

> examine them.

>

>> When these drives hook to either a DOS or W98 machine, I can't see

>> the

> A

>> drive due to the NTLDR error message.

>

> Try creating a fresh Windows 98 boot floppy and make sure the boot

> sequence is correct. Don't forget to save any changes to the BIOS

> setup.

>

> http://www.bootdisk.com/bootdisk.htm

>

>> IMO, I just need to see the A drive so I can wipe the drives, then

>> proceed.

>

> If there are NTFS partitions and the Windows 98 version of fdisk won't

> delete them, see

> http://support.microsoft.com/kb/103049

>

> Ben

>

Thanks, Ben. Will post back.

ms

January 3, 2008

Re: 1782- Disk Controller Failure

"Ben Myers" <benjmyers@mindR-e-m-o-v-Espring.com> wrote in

news:#mtrKChTIHA.3400@TK2MSFTNGP03.phx.gbl:

>> > then

>> >> reboot with a W98 boot disk, fdisk, then format.

>> >> Having success with 4 different drives, the motherboard, power

> cable,

>> >> data cable all are OK.

>> >> But 2 drives gave initially 1782 Disk Controller Failure.

>> >> I searched, find that if above items are ok, maybe the

>> >> master/slave

>

>> >> setting may cause this error.

>> >> One drive had a diagram, so it gave the error when set for Master.

>> >> The other, Western Digital 31000, saved a data page but not sure

>> >> of

>

>> > the

>> >> diagram for the plug.

>> >> Is it likely that both drives are defective from the above data?

>> "Ben Myers" <benjmyers@mindR-e-m-o-v-Espring.com> wrote in

>> > Try the drives on a known good computer

>> > If this is the Compaq 8702, the diagnostic utility may be helpful.

>> > ftp://ftp.hp.com/pub/softpaq/sp02001-02500/sp2141.exe

>

>> Thanks, Ben,

>> That Compaq utility is the one you recommended before, when I see the

> A

>> drive, it does allow configuring the BIOS for the drive, I used it on

>> several drives that were FAT-32 in this machine.

>> But it seems the 3 problem drives can only be tried on a NT type

> machine,

>

> NTFS, FAT32 and FAT are file systems, not computer types.

> The "NTDLR is missing" message you are receiving is being generated by

> a NT style boot loader on the disks themselves.

>

>> I have one but it's not handy for this, and my intent is for these

> drives

>> to be used in a W98 machine. So if they check out as NT drives, it

> does

>> not get me FAT-32.

>

> The "NTDLR is missing" message does not necessarily mean there are

> NTFS partitions on the drive. Use the Windows 98 version of fdisk to

> examine them.

>

>> When these drives hook to either a DOS or W98 machine, I can't see

>> the

> A

>> drive due to the NTLDR error message.

>

> Try creating a fresh Windows 98 boot floppy and make sure the boot

> sequence is correct. Don't forget to save any changes to the BIOS

> setup.

>

> http://www.bootdisk.com/bootdisk.htm

>

>> IMO, I just need to see the A drive so I can wipe the drives, then

>> proceed.

>

> If there are NTFS partitions and the Windows 98 version of fdisk won't

> delete them, see

> http://support.microsoft.com/kb/103049

>

> Ben

Earlier in thread, I used a W98 boot disk from IIRC, your earlier advice.

I got another W98SE w/o ram drive boot disk again, this time much better

results. A puzzle there, they should have been the same boot disk.

2 of the 3 problem drives showed A, I was able to fisk and format, one

will replace a smaller hard drive for use with a old DOS game.

The third drive was 15 GB, would be useful, but this one shows:

1790- Disk 0 error. Believe that is a bad drive. Is there anything I can

do to check that drive out? Would have to get past that screen.

Thanks for the help, salvaged 2 small drives.

ms

January 4, 2008

Re: 1782- Disk Controller Failure

"ms" <ms@invalid.com> wrote in message news:5u500hF1fesm0U1@mid.individual.net...

> Earlier in thread, I used a W98 boot disk from IIRC, your earlier advice.

> I got another W98SE w/o ram drive boot disk again, this time much better

> results. A puzzle there, they should have been the same boot disk.

Sounds like the boot sector was overwritten. Try a virus scan on it.

> 2 of the 3 problem drives showed A, I was able to fisk and format, one

> will replace a smaller hard drive for use with a old DOS game.

> The third drive was 15 GB, would be useful, but this one shows:

> 1790- Disk 0 error. Believe that is a bad drive. Is there anything I can

> do to check that drive out? Would have to get past that screen.

The 8702 originally shipped with a 2.5 gigabyte drive, so its BIOS may

not be able to handle a 15 gigabyte. The support site doesn't show a

BIOS update to help with this, so the only way to use the drive at its

full capacity in this computer would probably be a drive overlay program

from the drive's manufacturer. Also, try hitting F1 to get past the error

message.

Maxtor and Seagate http://www.seagate.com/www/en-us/support/

Western Digital http://support.wdc.com/download/dlg/dlg11_dos.exe

Ben

January 4, 2008

Re: 1782- Disk Controller Failure

"Ben Myers" <benjmyers@mindR-e-m-o-v-Espring.com> wrote in

news:uUNwVrrTIHA.4196@TK2MSFTNGP04.phx.gbl:

> "ms" <ms@invalid.com> wrote in message

> news:5u500hF1fesm0U1@mid.individual.net...

>> Earlier in thread, I used a W98 boot disk from IIRC, your earlier

> advice.

>> I got another W98SE w/o ram drive boot disk again, this time much

> better

>> results. A puzzle there, they should have been the same boot disk.

>

> Sounds like the boot sector was overwritten. Try a virus scan on it.

>

>> 2 of the 3 problem drives showed A, I was able to fisk and format,

>> one

>

>> will replace a smaller hard drive for use with a old DOS game.

>> The third drive was 15 GB, would be useful, but this one shows:

>> 1790- Disk 0 error. Believe that is a bad drive. Is there anything I

> can

>> do to check that drive out? Would have to get past that screen.

>

> The 8702 originally shipped with a 2.5 gigabyte drive, so its BIOS may

> not be able to handle a 15 gigabyte. The support site doesn't show a

> BIOS update to help with this, so the only way to use the drive at its

> full capacity in this computer would probably be a drive overlay

> program from the drive's manufacturer. Also, try hitting F1 to get

> past the error message.

>

> Maxtor and Seagate http://www.seagate.com/www/en-us/support/

> Western Digital http://support.wdc.com/download/dlg/dlg11_dos.exe

>

> Ben

This drive would be for another computer, just want to test it in the

P166, but your comment applies.

Your link to a WD boot disk led to a different boot disk than before,

this one is ver. 11.0, and repeating F1 got it past the error screen.

The message: starting Caldera DR-DOS, then just a blinking cursor. The

floppy drive continues to read, but nothing beyond that.

Comment?

ms

January 4, 2008

Re: 1782- Disk Controller Failure

"ms" <ms@invalid.com> wrote in message news:5u77lgF1gjvmvU1@mid.individual.net...

> This drive would be for another computer, just want to test it in the

> P166, but your comment applies.

> Your link to a WD boot disk led to a different boot disk than before,

> this one is ver. 11.0, and repeating F1 got it past the error screen.

> The message: starting Caldera DR-DOS, then just a blinking cursor. The

> floppy drive continues to read, but nothing beyond that.

Try running the program again using a different floppy. If this doesn't help, try

downloading the file again.

http://support.wdc.com/download/dlg/dlg11_dos.exe

Also, please note that you will probably have to repeat this procedure with the

other computer when you transfer the drive.

Ben

January 4, 2008

Re: 1782- Disk Controller Failure

"Ben Myers" <benjmyers@mindR-e-m-o-v-Espring.com> wrote in

news:e3F1DyvTIHA.4768@TK2MSFTNGP02.phx.gbl:

> "ms" <ms@invalid.com> wrote in message

> news:5u77lgF1gjvmvU1@mid.individual.net...

>> This drive would be for another computer, just want to test it in the

>> P166, but your comment applies.

>> Your link to a WD boot disk led to a different boot disk than before,

>> this one is ver. 11.0, and repeating F1 got it past the error screen.

>> The message: starting Caldera DR-DOS, then just a blinking cursor.

>> The

>

>> floppy drive continues to read, but nothing beyond that.

>

> Try running the program again using a different floppy. If this

> doesn't help, try downloading the file again.

>

> http://support.wdc.com/download/dlg/dlg11_dos.exe

>

> Also, please note that you will probably have to repeat this procedure

> with the other computer when you transfer the drive.

>

> Ben

A new download and rewriting a new floppy, result is the same.

I then tried the Compaq diagnostic boot disk, with repeated F1, I get

past the 1790 message. but then just a blinking cursor and a F1- boot

screen (normal for the Compaq disk), and the floppy drive continues to

read.

I then put in a W98 boot disk, hit F1, it rebooted, F1 again to get past

the error message, get the "NTLDR is missing" message, F1, just a

blinking cursor and floppy drive reads.

The different floppy disks read normally in another computer.

I have not yet with this drive been able to read the Compaq disk and

detect this drive (or attempt to) in the BIOS, as I did with the others.

The hard drive is still the 15 GB one you suggested the BIOS may not

handle. As discussed earlier, the "NTLDR is missing" suggests it is

starting to read the hard drive?

ms

January 5, 2008

Re: 1782- Disk Controller Failure

"ms" <ms@invalid.com> wrote in message news:5u7qhcF1gkhphU1@mid.individual.net...

> A new download and rewriting a new floppy, result is the same.

> I then tried the Compaq diagnostic boot disk, with repeated F1, I get

> past the 1790 message. but then just a blinking cursor and a F1- boot

> screen (normal for the Compaq disk), and the floppy drive continues to

> read.

> I then put in a W98 boot disk, hit F1, it rebooted, F1 again to get past

> the error message, get the "NTLDR is missing" message, F1, just a

> blinking cursor and floppy drive reads.

> The different floppy disks read normally in another computer.

> I have not yet with this drive been able to read the Compaq disk and

> detect this drive (or attempt to) in the BIOS, as I did with the others.

> The hard drive is still the 15 GB one you suggested the BIOS may not

> handle. As discussed earlier, the "NTLDR is missing" suggests it is

> starting to read the hard drive?

You might consider installing the drive in the other computer, since it

might work just fine. If you want to keep going with this one, check

the drive or its documentation to see if there is some way to use the

disk at a reduced capacity, such as 8 gigabytes. You also might try

disconnecting the drive, then going into the BIOS setup and setting

the drive parameters manually. If the BIOS won't accept the drive's

parameters, try using the largest parameters allowable. Then

reconnect the drive. Please note that even if you get the drive working,

you may have to go through all of this again on the other computer.

Also, the "NTLDR is missing" message is probably coming from a

floppy disk with a corrupt boot sector.

Ben

January 6, 2008

Re: 1782- Disk Controller Failure

"Ben Myers" <benjmyers@mindR-e-m-o-v-Espring.com> wrote in

news:em1jhu3TIHA.4880@TK2MSFTNGP03.phx.gbl:

> "ms" <ms@invalid.com> wrote in message

> news:5u7qhcF1gkhphU1@mid.individual.net...

>> A new download and rewriting a new floppy, result is the same.

>> I then tried the Compaq diagnostic boot disk, with repeated F1, I get

>> past the 1790 message. but then just a blinking cursor and a F1- boot

>> screen (normal for the Compaq disk), and the floppy drive continues

>> to

>

>> read.

>> I then put in a W98 boot disk, hit F1, it rebooted, F1 again to get

> past

>> the error message, get the "NTLDR is missing" message, F1, just a

>> blinking cursor and floppy drive reads.

>> The different floppy disks read normally in another computer.

>> I have not yet with this drive been able to read the Compaq disk and

>> detect this drive (or attempt to) in the BIOS, as I did with the

> others.

>> The hard drive is still the 15 GB one you suggested the BIOS may not

>> handle. As discussed earlier, the "NTLDR is missing" suggests it is

>> starting to read the hard drive?

>

> You might consider installing the drive in the other computer, since

> it might work just fine. If you want to keep going with this one,

> check the drive or its documentation to see if there is some way to

> use the disk at a reduced capacity, such as 8 gigabytes. You also

> might try disconnecting the drive, then going into the BIOS setup and

> setting the drive parameters manually. If the BIOS won't accept the

> drive's parameters, try using the largest parameters allowable. Then

> reconnect the drive. Please note that even if you get the drive

> working, you may have to go through all of this again on the other

> computer. Also, the "NTLDR is missing" message is probably coming from

> a floppy disk with a corrupt boot sector.

>

> Ben

I used the floppy to boot up a W98 computer, it worked fine, suggest the

boot sector is OK.

I will try as you suggest above, if success, will post back, if not, will

close this long thread, and later try the drive in another machine.

Thanks very much for the help.

ms

January 7, 2008