1782- Disk Controller Failure

  • Thread starter Thread starter ms
  • Start date Start date
M

ms

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?

ms
 
"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?
>

Possibly, possibly not. The error could be the cause of non-bootable disks,
incorrect jumper setting, non-detection by the BIOS, HD configuration incorrect in
BIOS, cables not connected securely/properly and/or "improper" boot sequence.

--

Brian A. Sesko { MS MVP_Shell/User }
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375
 
"Brian A." <gonefish'n@afarawaylake> wrote in
news:eOK8W3cSIHA.4752@TK2MSFTNGP05.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?
>>
>
> Possibly, possibly not. The error could be the cause of
> non-bootable disks,
> incorrect jumper setting, non-detection by the BIOS, HD configuration
> incorrect in BIOS, cables not connected securely/properly and/or
> "improper" boot sequence.
>

Thanks, Brian.

Then Autodetect in this Setup does not always detect a particular drive?
One reason could be the BIOS is old in a P166?

ms
 
"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?
>
> ms
>
>
>
>

Last I looked, Western Digital has jumper settings for all its hard drives
at their websites, if that's what you're asking for.

westerndigital.com

wdc.com


With the power connector on the right, the jumper pins in the middle, and
the 40 pin data connector on the left, the jumper block is a six pin model
per the spec page. Jumper pin 1 is on the upper right, pin 6 is on the
lower left.

Single (master without slave) no jumper pin, OR, 3 and 5, OR 4 and 6.

Dual master (master w/slave present on same data cable) 4 and 5.

Slave, 3 and 4.

Cable select, (if another ide device is present on same data cable, must
also be set cable select) 1 and 2.


Formatted capacity, 1,083MB.
512 bytes per sector.
3 platters, 6 heads.
Recording method, 1,7 RLL.
Head park is automatic.
Rotational speed is 4495 rpm.
Buffer size is 128K.

The model number is AC31000.

Bios is not a factor in problem solving interface problems with this drive.
Very simple hard drive, even for P166 days. I would recommend a triple RAM
check during bios routine. The spindle start time is 10s from power on to
drive ready as noted in the spec page.
Dave
 
"Lil' Dave" <spamyourself@virus.net> wrote in
news:OYs73EjSIHA.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?
>>
>> ms
>>
>>
>>
>>
>
> Last I looked, Western Digital has jumper settings for all its hard
> drives at their websites, if that's what you're asking for.
>
> westerndigital.com
>
> wdc.com
>
>
> With the power connector on the right, the jumper pins in the middle,
> and the 40 pin data connector on the left, the jumper block is a six
> pin model per the spec page. Jumper pin 1 is on the upper right, pin
> 6 is on the lower left.
>
> Single (master without slave) no jumper pin, OR, 3 and 5, OR 4 and 6.
>
> Dual master (master w/slave present on same data cable) 4 and 5.
>
> Slave, 3 and 4.
>
> Cable select, (if another ide device is present on same data cable,
> must also be set cable select) 1 and 2.
>
Thanks for the detail, Dave.

If I picture the above, the jumper pins are:
5 3 1
6 4 2

The existing jumper is between 5 and 6, not listed above.

If this is to be a single drive, from above, "no jumper pin" looks like
the thing to do.

Comment?

ms


>
> Formatted capacity, 1,083MB.
> 512 bytes per sector.
> 3 platters, 6 heads.
> Recording method, 1,7 RLL.
> Head park is automatic.
> Rotational speed is 4495 rpm.
> Buffer size is 128K.
>
> The model number is AC31000.
>
> Bios is not a factor in problem solving interface problems with this
> drive. Very simple hard drive, even for P166 days. I would recommend
> a triple RAM check during bios routine. The spindle start time is 10s
> from power on to drive ready as noted in the spec page.
> Dave
>
>
>
 
ms <ms@invalid.com> wrote in news:5to1chF1e9uauU1@mid.individual.net:

> "Lil' Dave" <spamyourself@virus.net> wrote in
> news:OYs73EjSIHA.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.
>>
> Thanks for the detail, Dave.
>
> If I picture the above, the jumper pins are:
> 5 3 1
> 6 4 2
>
> The existing jumper is between 5 and 6, not listed above.
>
> If this is to be a single drive, from above, "no jumper pin" looks like
> the thing to do.
>
> Comment?

Some test data.

On the subject drive, I removed the jumper, first step in testing a drive
in this old Compaq P166 is boot with the Compaq setup disk. On bootup,
got the error message "NTDLR is missing". Looked up in saved data, this
file is part of NT type boot sequence. The computer had W95, IIRC, NT
requires a lot more machine than this, doubt it ever had anything but
W95. The hard drive is 1 GB, not sure it's history.

I tried 2 other drives, one unknown, one known good, both now give the
same error message on bootup. The computer did not give this message
before today, using other hard drives.

Advice?

ms
 
"ms" <ms@invalid.com> wrote in message news:5to8pmF105qrvU1@mid.individual.net...
> ms <ms@invalid.com> wrote in news:5to1chF1e9uauU1@mid.individual.net:
>
>> "Lil' Dave" <spamyourself@virus.net> wrote in
>> news:OYs73EjSIHA.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.
>>>
>> Thanks for the detail, Dave.
>>
>> If I picture the above, the jumper pins are:
>> 5 3 1
>> 6 4 2

That's the proper way depending on how the drive is held while you look at it, ICR
if they actually had a 7th pin back when.
There should be markings, S - M - CS, on the top or bottom side of the drive where
the pins are, which may require a magnifying glass to see them well enough.

>>
>> The existing jumper is between 5 and 6, not listed above.

Prolly a typo since L.D. typed 4-5 and we all know jumpers aren't set on diagnals.

>>
>> If this is to be a single drive, from above, "no jumper pin" looks like
>> the thing to do.

If it's the WD drive, that's how it was done back when, no jumper for a Single
drive. However, they did come with the jumper set on 2 odd or even pins which was
also considered Single.

>>
>> Comment?
>
> Some test data.
>
> On the subject drive, I removed the jumper, first step in testing a drive
> in this old Compaq P166 is boot with the Compaq setup disk. On bootup,
> got the error message "NTDLR is missing". Looked up in saved data, this
> file is part of NT type boot sequence. The computer had W95, IIRC, NT
> requires a lot more machine than this, doubt it ever had anything but
> W95. The hard drive is 1 GB, not sure it's history.

NTLDR = NT Loader and is used for NT/2000/XP.
It doesn't matter what the PC originally had installed for an OS, you're testing
using a totally different drive than what was with it and it may have had an NT
flavor OS on it.

Can't you boot with a 98 boot disk to check what, if anything, may be on it.


>
> I tried 2 other drives, one unknown, one known good, both now give the
> same error message on bootup. The computer did not give this message
> before today, using other hard drives.
>

Again, could be a non-bootable disk, the drive isn't configured and/or properly
detected by the BIOS, the boot sequence isn't set properly in the BIOS ( you are
swapping out disks and using a compuke boot disk ), corrupt boot sector / MBR,
faulty ribbon data cable, etc.


--

Brian A. Sesko { MS MVP_Shell/User }
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375
 
"Brian A." <gonefish'n@afarawaylake> wrote in message
news:uLhtHFpSIHA.1164@TK2MSFTNGP02.phx.gbl...
> "ms" <ms@invalid.com> wrote in message
> news:5to8pmF105qrvU1@mid.individual.net...
>> ms <ms@invalid.com> wrote in news:5to1chF1e9uauU1@mid.individual.net:
>>
>>> "Lil' Dave" <spamyourself@virus.net> wrote in
>>> news:OYs73EjSIHA.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.
>>>>
>>> Thanks for the detail, Dave.
>>>
>>> If I picture the above, the jumper pins are:
>>> 5 3 1
>>> 6 4 2
>
> That's the proper way depending on how the drive is held while you look
> at it, ICR if they actually had a 7th pin back when.
> There should be markings, S - M - CS, on the top or bottom side of the
> drive where the pins are, which may require a magnifying glass to see them
> well enough.
>
>>>
>>> The existing jumper is between 5 and 6, not listed above.
>
> Prolly a typo since L.D. typed 4-5 and we all know jumpers aren't set on
> diagnals.
>
>>>
>>> If this is to be a single drive, from above, "no jumper pin" looks like
>>> the thing to do.
>
> If it's the WD drive, that's how it was done back when, no jumper for a
> Single drive. However, they did come with the jumper set on 2 odd or even
> pins which was also considered Single.
>
>>>
>>> Comment?
>>
>> Some test data.
>>
>> On the subject drive, I removed the jumper, first step in testing a drive
>> in this old Compaq P166 is boot with the Compaq setup disk. On bootup,
>> got the error message "NTDLR is missing". Looked up in saved data, this
>> file is part of NT type boot sequence. The computer had W95, IIRC, NT
>> requires a lot more machine than this, doubt it ever had anything but
>> W95. The hard drive is 1 GB, not sure it's history.
>
> NTLDR = NT Loader and is used for NT/2000/XP.
> It doesn't matter what the PC originally had installed for an OS, you're
> testing using a totally different drive than what was with it and it may
> have had an NT flavor OS on it.
>
> Can't you boot with a 98 boot disk to check what, if anything, may be on
> it.
>
>
>>
>> I tried 2 other drives, one unknown, one known good, both now give the
>> same error message on bootup. The computer did not give this message
>> before today, using other hard drives.
>>
>
> Again, could be a non-bootable disk, the drive isn't configured and/or
> properly detected by the BIOS, the boot sequence isn't set properly in the
> BIOS ( you are swapping out disks and using a compuke boot disk ),
> corrupt boot sector / MBR, faulty ribbon data cable, etc.
>
>
> --
>
> Brian A. Sesko { MS MVP_Shell/User }
> Conflicts start where information lacks.
> http://basconotw.mvps.org/
>
> Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
> How to ask a question: http://support.microsoft.com/kb/555375
>
>
>
>

Right. Shoulda been 5 and 6, not 4 and 5.

With few exceptions, WD ide drives can use 3 and 5, OR, 4 and 6, as a jumper
storage location when intending to use master alone configuration for the
hard drive.

Believe you're thinking about the 9 pin configuration with the odd extra
pin. AC31000 model drive don't have that per the spec sheet. But, the spec
sheet may be wrong. I do recall having a 9 pin WD drive similar to this
model number many years ago. There is no storage location for jumper
storage, and, one must use a jumper for master alone for this type if I
recall correctly.
Dave
 
"Lil' Dave" <spamyourself@virus.net> wrote in message
news:u6ef57pSIHA.2376@TK2MSFTNGP02.phx.gbl...
>
> Right. Shoulda been 5 and 6, not 4 and 5.

Figured that much, however, it might be interesting results.

>
> With few exceptions, WD ide drives can use 3 and 5, OR, 4 and 6, as a jumper
> storage location when intending to use master alone configuration for the hard
> drive.

I've always used WD drives w/the exception of 1 Seagate Barracuda, and IIRC which I
may not, they all had that back when I can(t) recall. ~[|8o}

>
> Believe you're thinking about the 9 pin configuration with the odd extra pin.
> AC31000 model drive don't have that per the spec sheet. But, the spec sheet may be
> wrong. I do recall having a 9 pin WD drive similar to this model number many years
> ago. There is no storage location for jumper storage, and, one must use a jumper
> for master alone for this type if I recall correctly.

Could very well be, it's been quite some time since I've had a drive that only used
a single jumper.



--

Brian A. Sesko { MS MVP_Shell/User }
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375
 
"Brian A." <gonefish'n@afarawaylake> wrote in
news:uLhtHFpSIHA.1164@TK2MSFTNGP02.phx.gbl:

> "ms" <ms@invalid.com> wrote in message
> news:5to8pmF105qrvU1@mid.individual.net...
>> ms <ms@invalid.com> wrote in news:5to1chF1e9uauU1@mid.individual.net:
>>
>>> "Lil' Dave" <spamyourself@virus.net> wrote in
>>> news:OYs73EjSIHA.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.
>>>>
>>> Thanks for the detail, Dave.
>>>
>>> If I picture the above, the jumper pins are:
>>> 5 3 1
>>> 6 4 2
>
> That's the proper way depending on how the drive is held while you
> look at it, ICR
> if they actually had a 7th pin back when.
> There should be markings, S - M - CS, on the top or bottom side of the
> drive where the pins are, which may require a magnifying glass to see
> them well enough.
>
This one does not have those markings.
>>>
>>> The existing jumper is between 5 and 6, not listed above.
>
> Prolly a typo since L.D. typed 4-5 and we all know jumpers aren't
> set on diagnals.
>
>>>
>>> If this is to be a single drive, from above, "no jumper pin" looks
>>> like the thing to do.
>
> If it's the WD drive, that's how it was done back when, no jumper
> for a Single
> drive. However, they did come with the jumper set on 2 odd or even
> pins which was also considered Single.
>

So my results are with no jumper. See below.
>>>
>>> Comment?
>>
>> Some test data.
>>
>> On the subject drive, I removed the jumper, first step in testing a
>> drive in this old Compaq P166 is boot with the Compaq setup disk. On
>> bootup, got the error message "NTDLR is missing". Looked up in saved
>> data, this file is part of NT type boot sequence. The computer had
>> W95, IIRC, NT requires a lot more machine than this, doubt it ever
>> had anything but W95. The hard drive is 1 GB, not sure it's history.
>
> NTLDR = NT Loader and is used for NT/2000/XP.
> It doesn't matter what the PC originally had installed for an OS,
> you're testing using a totally different drive than what was with it
> and it may have had an NT flavor OS on it.
>
> Can't you boot with a 98 boot disk to check what, if anything, may
> be on it.
>
Tried that, first get the usual Compaq "F1 to save defaults", then get
"NTDLR is missing"

I now have 3 unknown drives that might be OK if that message and jumpers
are sorted out.

Can I search for that file and put it on my W98 boot floppy to copy to C:
Being DOS on the drive, no windows folder to put it in. Is that a
possible way to solve this issue?
>
>>
>> I tried 2 other drives, one unknown, one known good, both now give
>> the same error message on bootup. The computer did not give this
>> message before today, using other hard drives.
>>
>
> Again, could be a non-bootable disk, the drive isn't configured
> and/or properly
> detected by the BIOS, the boot sequence isn't set properly in the BIOS
> ( you are swapping out disks and using a compuke boot disk ), corrupt
> boot sector / MBR, faulty ribbon data cable, etc.
>

Until I get past that message, BIOS can't look at the drives.

Advice?

ms
 
ms wrote:
> "Brian A." <gonefish'n@afarawaylake> wrote in
> news:uLhtHFpSIHA.1164@TK2MSFTNGP02.phx.gbl:
>
>> "ms" <ms@invalid.com> wrote in message
>> news:5to8pmF105qrvU1@mid.individual.net...
>>> ms <ms@invalid.com> wrote in
>>> news:5to1chF1e9uauU1@mid.individual.net:
>>>
>>>> "Lil' Dave" <spamyourself@virus.net> wrote in
>>>> news:OYs73EjSIHA.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.
>>>>>
>>>> Thanks for the detail, Dave.
>>>>
>>>> If I picture the above, the jumper pins are:
>>>> 5 3 1
>>>> 6 4 2
>>
>> That's the proper way depending on how the drive is held while
>> you look at it, ICR
>> if they actually had a 7th pin back when.
>> There should be markings, S - M - CS, on the top or bottom side of
>> the drive where the pins are, which may require a magnifying glass
>> to see them well enough.
>>
> This one does not have those markings.
>>>>
>>>> The existing jumper is between 5 and 6, not listed above.
>>
>> Prolly a typo since L.D. typed 4-5 and we all know jumpers aren't
>> set on diagnals.
>>
>>>>
>>>> If this is to be a single drive, from above, "no jumper pin"
>>>> looks like the thing to do.
>>
>> If it's the WD drive, that's how it was done back when, no jumper
>> for a Single
>> drive. However, they did come with the jumper set on 2 odd or even
>> pins which was also considered Single.
>>
>
> So my results are with no jumper. See below.
>>>>
>>>> Comment?
>>>
>>> Some test data.
>>>
>>> On the subject drive, I removed the jumper, first step in testing
>>> a drive in this old Compaq P166 is boot with the Compaq setup
>>> disk. On bootup, got the error message "NTDLR is missing". Looked
>>> up in saved data, this file is part of NT type boot sequence. The
>>> computer had W95, IIRC, NT requires a lot more machine than this,
>>> doubt it ever had anything but W95. The hard drive is 1 GB, not
>>> sure it's history.
>>
>> NTLDR = NT Loader and is used for NT/2000/XP.
>> It doesn't matter what the PC originally had installed for an OS,
>> you're testing using a totally different drive than what was with
>> it and it may have had an NT flavor OS on it.
>>
>> Can't you boot with a 98 boot disk to check what, if anything,
>> may be on it.
>>
> Tried that, first get the usual Compaq "F1 to save defaults", then
> get "NTDLR is missing"
>
> I now have 3 unknown drives that might be OK if that message and
> jumpers are sorted out.
>
> Can I search for that file and put it on my W98 boot floppy to copy
> to C: Being DOS on the drive, no windows folder to put it in. Is
> that a possible way to solve this issue?

No idea but putting the jumper back the way it was (or correctly if
not so originally) might be since you didn't get the error message
before you changed it. And no, I have no idea what/if the jumper has
to do with generating that particular message. Heck, I don't even
care.



--

dadiOH
____________________________

dadiOH's dandies v3.06...
....a help file of info about MP3s, recording from
LP/cassette and tips & tricks on this and that.
Get it at http://mysite.verizon.net/xico
 
"ms" <ms@invalid.com> wrote in message
news:5tq0ghF1ds7chU1@mid.individual.net...
> "Brian A." <gonefish'n@afarawaylake> wrote in
> news:uLhtHFpSIHA.1164@TK2MSFTNGP02.phx.gbl:
>
>> "ms" <ms@invalid.com> wrote in message
>> news:5to8pmF105qrvU1@mid.individual.net...
>>> ms <ms@invalid.com> wrote in news:5to1chF1e9uauU1@mid.individual.net:
>>>
>>>> "Lil' Dave" <spamyourself@virus.net> wrote in
>>>> news:OYs73EjSIHA.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.
>>>>>
>>>> Thanks for the detail, Dave.
>>>>
>>>> If I picture the above, the jumper pins are:
>>>> 5 3 1
>>>> 6 4 2
>>
>> That's the proper way depending on how the drive is held while you
>> look at it, ICR
>> if they actually had a 7th pin back when.
>> There should be markings, S - M - CS, on the top or bottom side of the
>> drive where the pins are, which may require a magnifying glass to see
>> them well enough.
>>
> This one does not have those markings.
>>>>
>>>> The existing jumper is between 5 and 6, not listed above.
>>
>> Prolly a typo since L.D. typed 4-5 and we all know jumpers aren't
>> set on diagnals.
>>
>>>>
>>>> If this is to be a single drive, from above, "no jumper pin" looks
>>>> like the thing to do.
>>
>> If it's the WD drive, that's how it was done back when, no jumper
>> for a Single
>> drive. However, they did come with the jumper set on 2 odd or even
>> pins which was also considered Single.
>>
>
> So my results are with no jumper. See below.
>>>>
>>>> Comment?
>>>
>>> Some test data.
>>>
>>> On the subject drive, I removed the jumper, first step in testing a
>>> drive in this old Compaq P166 is boot with the Compaq setup disk. On
>>> bootup, got the error message "NTDLR is missing". Looked up in saved
>>> data, this file is part of NT type boot sequence. The computer had
>>> W95, IIRC, NT requires a lot more machine than this, doubt it ever
>>> had anything but W95. The hard drive is 1 GB, not sure it's history.
>>
>> NTLDR = NT Loader and is used for NT/2000/XP.
>> It doesn't matter what the PC originally had installed for an OS,
>> you're testing using a totally different drive than what was with it
>> and it may have had an NT flavor OS on it.
>>
>> Can't you boot with a 98 boot disk to check what, if anything, may
>> be on it.
>>
> Tried that, first get the usual Compaq "F1 to save defaults", then get
> "NTDLR is missing"
>
> I now have 3 unknown drives that might be OK if that message and jumpers
> are sorted out.
>
> Can I search for that file and put it on my W98 boot floppy to copy to C:
> Being DOS on the drive, no windows folder to put it in. Is that a
> possible way to solve this issue?
>>
>>>
>>> I tried 2 other drives, one unknown, one known good, both now give
>>> the same error message on bootup. The computer did not give this
>>> message before today, using other hard drives.
>>>
>>
>> Again, could be a non-bootable disk, the drive isn't configured
>> and/or properly
>> detected by the BIOS, the boot sequence isn't set properly in the BIOS
>> ( you are swapping out disks and using a compuke boot disk ), corrupt
>> boot sector / MBR, faulty ribbon data cable, etc.
>>
>
> Until I get past that message, BIOS can't look at the drives.
>
> Advice?
>
> ms

Well, my assessment is you probably have a fair idea of it. And, you are
probably aware from input this thread that the message is coming from a hard
drive attempting to boot. Therefore, the hard drive or hard drives have
been assessed by the bios.

Am not a real smart guy, but, I would remove all hard drives but the
AC31000. Then, go from there.
Dave
 
"Lil' Dave" <spamyourself@virus.net> wrote in
news:uCmnu#2SIHA.4104@TK2MSFTNGP05.phx.gbl:

> "ms" <ms@invalid.com> wrote in message
> news:5tq0ghF1ds7chU1@mid.individual.net...
>> "Brian A." <gonefish'n@afarawaylake> wrote in
>> news:uLhtHFpSIHA.1164@TK2MSFTNGP02.phx.gbl:
>>
>>> "ms" <ms@invalid.com> wrote in message
>>> news:5to8pmF105qrvU1@mid.individual.net...
>>>> ms <ms@invalid.com> wrote in
>>>> news:5to1chF1e9uauU1@mid.individual.net:
>>>>
>>>>> "Lil' Dave" <spamyourself@virus.net> wrote in
>>>>> news:OYs73EjSIHA.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.
>>>>>>
>>>>> Thanks for the detail, Dave.
>>>>>
>>>>> If I picture the above, the jumper pins are:
>>>>> 5 3 1
>>>>> 6 4 2
>>>
>>> That's the proper way depending on how the drive is held while you
>>> look at it, ICR
>>> if they actually had a 7th pin back when.
>>> There should be markings, S - M - CS, on the top or bottom side of
>>> the drive where the pins are, which may require a magnifying glass
>>> to see them well enough.
>>>
>> This one does not have those markings.
>>>>>
>>>>> The existing jumper is between 5 and 6, not listed above.
>>>
>>> Prolly a typo since L.D. typed 4-5 and we all know jumpers aren't
>>> set on diagnals.
>>>
>>>>>
>>>>> If this is to be a single drive, from above, "no jumper pin" looks
>>>>> like the thing to do.
>>>
>>> If it's the WD drive, that's how it was done back when, no jumper
>>> for a Single
>>> drive. However, they did come with the jumper set on 2 odd or even
>>> pins which was also considered Single.
>>>
>>
>> So my results are with no jumper. See below.
>>>>>
>>>>> Comment?
>>>>
>>>> Some test data.
>>>>
>>>> On the subject drive, I removed the jumper, first step in testing a
>>>> drive in this old Compaq P166 is boot with the Compaq setup disk.
>>>> On bootup, got the error message "NTDLR is missing". Looked up in
>>>> saved data, this file is part of NT type boot sequence. The
>>>> computer had W95, IIRC, NT requires a lot more machine than this,
>>>> doubt it ever had anything but W95. The hard drive is 1 GB, not
>>>> sure it's history.
>>>
>>> NTLDR = NT Loader and is used for NT/2000/XP.
>>> It doesn't matter what the PC originally had installed for an OS,
>>> you're testing using a totally different drive than what was with it
>>> and it may have had an NT flavor OS on it.
>>>
>>> Can't you boot with a 98 boot disk to check what, if anything, may
>>> be on it.
>>>
>> Tried that, first get the usual Compaq "F1 to save defaults", then
>> get "NTDLR is missing"
>>
>> I now have 3 unknown drives that might be OK if that message and
>> jumpers are sorted out.
>>
>> Can I search for that file and put it on my W98 boot floppy to copy
>> to C: Being DOS on the drive, no windows folder to put it in. Is that
>> a possible way to solve this issue?
>>>
>>>>
>>>> I tried 2 other drives, one unknown, one known good, both now give
>>>> the same error message on bootup. The computer did not give this
>>>> message before today, using other hard drives.
>>>>
>>>
>>> Again, could be a non-bootable disk, the drive isn't configured
>>> and/or properly
>>> detected by the BIOS, the boot sequence isn't set properly in the
>>> BIOS ( you are swapping out disks and using a compuke boot disk ),
>>> corrupt boot sector / MBR, faulty ribbon data cable, etc.
>>>
>>
>> Until I get past that message, BIOS can't look at the drives.
>>
>> Advice?
>>
>> ms
>
> Well, my assessment is you probably have a fair idea of it. And, you
> are probably aware from input this thread that the message is coming
> from a hard drive attempting to boot. Therefore, the hard drive or
> hard drives have been assessed by the bios.
>
> Am not a real smart guy, but, I would remove all hard drives but the
> AC31000. Then, go from there.
> Dave
>
>

I am using the AC31000 drive.

I searched on my W2K machine, found an "image" sort of icon labeled
"ntdlr", and ntdetect.com (this may cause error message, see below)
Nothing else in W2K.

My wife has a XP Pro machine, searched there, there are no files in i386
for ntdlr. Several search engines found nothing else. The OS behaves
fine, so that's a puzzle.

I put the 2 above files on a W98 boot disk, booted up, get message "W2000
can't start because *** is corupted or missing." Maybe caused by
ntdetect.com. Of course, neither of these was ntdlr.exe.

Searched Google, no luck for ntdlr.exe. Many posts about "missing"
message, a few say search in i386 folder for ntdlr.exe, not in my
machines.

My intent is to wind up with FAT-32 formatted drives, when finished, not
NT type drives.

Advice?

ms
 
> "Lil' Dave" <spamyourself@virus.net> wrote in
> news:uCmnu#2SIHA.4104@TK2MSFTNGP05.phx.gbl:
>>
>> Am not a real smart guy, but, I would remove all hard drives but the
>> AC31000. Then, go from there.
>> Dave
>>
>>
>
> I am using the AC31000 drive.
>
> I searched on my W2K machine, found an "image" sort of icon labeled
> "ntdlr", and ntdetect.com (this may cause error message, see below)
> Nothing else in W2K.
>
> My wife has a XP Pro machine, searched there, there are no files in i386
> for ntdlr. Several search engines found nothing else. The OS behaves
> fine, so that's a puzzle.

Try the correct file name: NTLDR

>
> I put the 2 above files on a W98 boot disk, booted up, get message "W2000
> can't start because *** is corupted or missing." Maybe caused by
> ntdetect.com. Of course, neither of these was ntdlr.exe.
>
> Searched Google, no luck for ntdlr.exe. Many posts about "missing"
> message, a few say search in i386 folder for ntdlr.exe, not in my
> machines.
>
> My intent is to wind up with FAT-32 formatted drives, when finished, not
> NT type drives.

Did you even try to boot with a 98 boot disk to see what, if anything, is on the
disk and try to fdisk/format it?


--

Brian A. Sesko { MS MVP_Shell/User }
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375



>
> Advice?
>
> ms
 
"ms" <ms@invalid.com> wrote in message
news:5tsurlF1f41njU1@mid.individual.net...
> "Lil' Dave" <spamyourself@virus.net> wrote in
> news:uCmnu#2SIHA.4104@TK2MSFTNGP05.phx.gbl:
>
>> "ms" <ms@invalid.com> wrote in message
>> news:5tq0ghF1ds7chU1@mid.individual.net...
>>> "Brian A." <gonefish'n@afarawaylake> wrote in
>>> news:uLhtHFpSIHA.1164@TK2MSFTNGP02.phx.gbl:
>>>
>>>> "ms" <ms@invalid.com> wrote in message
>>>> news:5to8pmF105qrvU1@mid.individual.net...
>>>>> ms <ms@invalid.com> wrote in
>>>>> news:5to1chF1e9uauU1@mid.individual.net:
>>>>>
>>>>>> "Lil' Dave" <spamyourself@virus.net> wrote in
>>>>>> news:OYs73EjSIHA.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.
>>>>>>>
>>>>>> Thanks for the detail, Dave.
>>>>>>
>>>>>> If I picture the above, the jumper pins are:
>>>>>> 5 3 1
>>>>>> 6 4 2
>>>>
>>>> That's the proper way depending on how the drive is held while you
>>>> look at it, ICR
>>>> if they actually had a 7th pin back when.
>>>> There should be markings, S - M - CS, on the top or bottom side of
>>>> the drive where the pins are, which may require a magnifying glass
>>>> to see them well enough.
>>>>
>>> This one does not have those markings.
>>>>>>
>>>>>> The existing jumper is between 5 and 6, not listed above.
>>>>
>>>> Prolly a typo since L.D. typed 4-5 and we all know jumpers aren't
>>>> set on diagnals.
>>>>
>>>>>>
>>>>>> If this is to be a single drive, from above, "no jumper pin" looks
>>>>>> like the thing to do.
>>>>
>>>> If it's the WD drive, that's how it was done back when, no jumper
>>>> for a Single
>>>> drive. However, they did come with the jumper set on 2 odd or even
>>>> pins which was also considered Single.
>>>>
>>>
>>> So my results are with no jumper. See below.
>>>>>>
>>>>>> Comment?
>>>>>
>>>>> Some test data.
>>>>>
>>>>> On the subject drive, I removed the jumper, first step in testing a
>>>>> drive in this old Compaq P166 is boot with the Compaq setup disk.
>>>>> On bootup, got the error message "NTDLR is missing". Looked up in
>>>>> saved data, this file is part of NT type boot sequence. The
>>>>> computer had W95, IIRC, NT requires a lot more machine than this,
>>>>> doubt it ever had anything but W95. The hard drive is 1 GB, not
>>>>> sure it's history.
>>>>
>>>> NTLDR = NT Loader and is used for NT/2000/XP.
>>>> It doesn't matter what the PC originally had installed for an OS,
>>>> you're testing using a totally different drive than what was with it
>>>> and it may have had an NT flavor OS on it.
>>>>
>>>> Can't you boot with a 98 boot disk to check what, if anything, may
>>>> be on it.
>>>>
>>> Tried that, first get the usual Compaq "F1 to save defaults", then
>>> get "NTDLR is missing"
>>>
>>> I now have 3 unknown drives that might be OK if that message and
>>> jumpers are sorted out.
>>>
>>> Can I search for that file and put it on my W98 boot floppy to copy
>>> to C: Being DOS on the drive, no windows folder to put it in. Is that
>>> a possible way to solve this issue?
>>>>
>>>>>
>>>>> I tried 2 other drives, one unknown, one known good, both now give
>>>>> the same error message on bootup. The computer did not give this
>>>>> message before today, using other hard drives.
>>>>>
>>>>
>>>> Again, could be a non-bootable disk, the drive isn't configured
>>>> and/or properly
>>>> detected by the BIOS, the boot sequence isn't set properly in the
>>>> BIOS ( you are swapping out disks and using a compuke boot disk ),
>>>> corrupt boot sector / MBR, faulty ribbon data cable, etc.
>>>>
>>>
>>> Until I get past that message, BIOS can't look at the drives.
>>>
>>> Advice?
>>>
>>> ms
>>
>> Well, my assessment is you probably have a fair idea of it. And, you
>> are probably aware from input this thread that the message is coming
>> from a hard drive attempting to boot. Therefore, the hard drive or
>> hard drives have been assessed by the bios.
>>
>> Am not a real smart guy, but, I would remove all hard drives but the
>> AC31000. Then, go from there.
>> Dave
>>
>>
>
> I am using the AC31000 drive.
>
> I searched on my W2K machine, found an "image" sort of icon labeled
> "ntdlr", and ntdetect.com (this may cause error message, see below)
> Nothing else in W2K.
>
> My wife has a XP Pro machine, searched there, there are no files in i386
> for ntdlr. Several search engines found nothing else. The OS behaves
> fine, so that's a puzzle.
>
> I put the 2 above files on a W98 boot disk, booted up, get message "W2000
> can't start because *** is corupted or missing." Maybe caused by
> ntdetect.com. Of course, neither of these was ntdlr.exe.
>
> Searched Google, no luck for ntdlr.exe. Many posts about "missing"
> message, a few say search in i386 folder for ntdlr.exe, not in my
> machines.
>
> My intent is to wind up with FAT-32 formatted drives, when finished, not
> NT type drives.
>
> Advice?
>
> ms

Then why all the skirt around, and skirt the issue stuff. Wipe the AC31000
with the WD software writing zeroes to it. Be done with it. Then, start
from scratch.

I know for a fact that you know how to get a known properly working boot 98
startup diskette.

Dave
 
"Brian A." <gonefish'n@afarawaylake> wrote in message
news:esvbCd%23SIHA.5264@TK2MSFTNGP02.phx.gbl...
>> "Lil' Dave" <spamyourself@virus.net> wrote in
>> news:uCmnu#2SIHA.4104@TK2MSFTNGP05.phx.gbl:
>>>
>>> Am not a real smart guy, but, I would remove all hard drives but the
>>> AC31000. Then, go from there.
>>> Dave
>>>
>>>
>>
>> I am using the AC31000 drive.
>>
>> I searched on my W2K machine, found an "image" sort of icon labeled
>> "ntdlr", and ntdetect.com (this may cause error message, see below)
>> Nothing else in W2K.
>>
>> My wife has a XP Pro machine, searched there, there are no files in i386
>> for ntdlr. Several search engines found nothing else. The OS behaves
>> fine, so that's a puzzle.
>
> Try the correct file name: NTLDR
>
>>
>> I put the 2 above files on a W98 boot disk, booted up, get message "W2000
>> can't start because *** is corupted or missing." Maybe caused by
>> ntdetect.com. Of course, neither of these was ntdlr.exe.
>>
>> Searched Google, no luck for ntdlr.exe. Many posts about "missing"
>> message, a few say search in i386 folder for ntdlr.exe, not in my
>> machines.
>>
>> My intent is to wind up with FAT-32 formatted drives, when finished, not
>> NT type drives.
>
> Did you even try to boot with a 98 boot disk to see what, if anything, is
> on the disk and try to fdisk/format it?
>
>
> --
>
> Brian A. Sesko { MS MVP_Shell/User }
> Conflicts start where information lacks.
> http://basconotw.mvps.org/
>
> Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
> How to ask a question: http://support.microsoft.com/kb/555375
>


Brian,

Believe he's messing with a diskette with ntldr on it. We both know that
ntldr is not an executable. We both know that ntdlr is a hidden system
file. I didn't want to go down the road he's taking us. Thus, the
subsequent post I just made.

Dave
 
"Brian A." <gonefish'n@afarawaylake> wrote in
news:esvbCd#SIHA.5264@TK2MSFTNGP02.phx.gbl:

>> "Lil' Dave" <spamyourself@virus.net> wrote in
>> news:uCmnu#2SIHA.4104@TK2MSFTNGP05.phx.gbl:
>>>
>>> Am not a real smart guy, but, I would remove all hard drives but the
>>> AC31000. Then, go from there.
>>> Dave
>>>
>>>
>>
>> I am using the AC31000 drive.
>>
>> I searched on my W2K machine, found an "image" sort of icon labeled
>> "ntdlr", and ntdetect.com (this may cause error message, see below)
>> Nothing else in W2K.
>>
>> My wife has a XP Pro machine, searched there, there are no files in
>> i386 for ntdlr. Several search engines found nothing else. The OS
>> behaves fine, so that's a puzzle.
>
> Try the correct file name: NTLDR
>
Bad sleep. But it looks like a better solution in Dave's post.
>>
>> I put the 2 above files on a W98 boot disk, booted up, get message
>> "W2000 can't start because *** is corupted or missing." Maybe caused
>> by ntdetect.com. Of course, neither of these was ntdlr.exe.
>>
>> Searched Google, no luck for ntdlr.exe. Many posts about "missing"
>> message, a few say search in i386 folder for ntdlr.exe, not in my
>> machines.
>>
>> My intent is to wind up with FAT-32 formatted drives, when finished,
>> not NT type drives.
>
> Did you even try to boot with a 98 boot disk to see what, if
> anything, is on the
> disk and try to fdisk/format it?
>
>

Yes, look earlier in the thread where I answered, did that. It wound up
with the missing file message, stopped there.

ms
 
"Lil' Dave" <spamyourself@virus.net> wrote in
news:eSMfIm$SIHA.1188@TK2MSFTNGP04.phx.gbl:

> "ms" <ms@invalid.com> wrote in message
> news:5tsurlF1f41njU1@mid.individual.net...
>> "Lil' Dave" <spamyourself@virus.net> wrote in
>> news:uCmnu#2SIHA.4104@TK2MSFTNGP05.phx.gbl:
>>
>>> "ms" <ms@invalid.com> wrote in message
>>> news:5tq0ghF1ds7chU1@mid.individual.net...
>>>> "Brian A." <gonefish'n@afarawaylake> wrote in
>>>> news:uLhtHFpSIHA.1164@TK2MSFTNGP02.phx.gbl:
>>>>
>>>>> "ms" <ms@invalid.com> wrote in message
>>>>> news:5to8pmF105qrvU1@mid.individual.net...
>>>>>> ms <ms@invalid.com> wrote in
>>>>>> news:5to1chF1e9uauU1@mid.individual.net:
>>>>>>
>>>>>>> "Lil' Dave" <spamyourself@virus.net> wrote in
>>>>>>> news:OYs73EjSIHA.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.
>>>>>>>>
>>>>>>> Thanks for the detail, Dave.
>>>>>>>
>>>>>>> If I picture the above, the jumper pins are:
>>>>>>> 5 3 1
>>>>>>> 6 4 2
>>>>>
>>>>> That's the proper way depending on how the drive is held while
>>>>> you look at it, ICR
>>>>> if they actually had a 7th pin back when.
>>>>> There should be markings, S - M - CS, on the top or bottom side of
>>>>> the drive where the pins are, which may require a magnifying glass
>>>>> to see them well enough.
>>>>>
>>>> This one does not have those markings.
>>>>>>>
>>>>>>> The existing jumper is between 5 and 6, not listed above.
>>>>>
>>>>> Prolly a typo since L.D. typed 4-5 and we all know jumpers
>>>>> aren't set on diagnals.
>>>>>
>>>>>>>
>>>>>>> If this is to be a single drive, from above, "no jumper pin"
>>>>>>> looks like the thing to do.
>>>>>
>>>>> If it's the WD drive, that's how it was done back when, no
>>>>> jumper for a Single
>>>>> drive. However, they did come with the jumper set on 2 odd or
>>>>> even pins which was also considered Single.
>>>>>
>>>>
>>>> So my results are with no jumper. See below.
>>>>>>>
>>>>>>> Comment?
>>>>>>
>>>>>> Some test data.
>>>>>>
>>>>>> On the subject drive, I removed the jumper, first step in testing
>>>>>> a drive in this old Compaq P166 is boot with the Compaq setup
>>>>>> disk. On bootup, got the error message "NTDLR is missing". Looked
>>>>>> up in saved data, this file is part of NT type boot sequence. The
>>>>>> computer had W95, IIRC, NT requires a lot more machine than this,
>>>>>> doubt it ever had anything but W95. The hard drive is 1 GB, not
>>>>>> sure it's history.
>>>>>
>>>>> NTLDR = NT Loader and is used for NT/2000/XP.
>>>>> It doesn't matter what the PC originally had installed for an OS,
>>>>> you're testing using a totally different drive than what was with
>>>>> it and it may have had an NT flavor OS on it.
>>>>>
>>>>> Can't you boot with a 98 boot disk to check what, if anything,
>>>>> may be on it.
>>>>>
>>>> Tried that, first get the usual Compaq "F1 to save defaults", then
>>>> get "NTDLR is missing"
>>>>
>>>> I now have 3 unknown drives that might be OK if that message and
>>>> jumpers are sorted out.
>>>>
>>>> Can I search for that file and put it on my W98 boot floppy to copy
>>>> to C: Being DOS on the drive, no windows folder to put it in. Is
>>>> that a possible way to solve this issue?
>>>>>
>>>>>>
>>>>>> I tried 2 other drives, one unknown, one known good, both now
>>>>>> give the same error message on bootup. The computer did not give
>>>>>> this message before today, using other hard drives.
>>>>>>
>>>>>
>>>>> Again, could be a non-bootable disk, the drive isn't configured
>>>>> and/or properly
>>>>> detected by the BIOS, the boot sequence isn't set properly in the
>>>>> BIOS ( you are swapping out disks and using a compuke boot disk ),
>>>>> corrupt boot sector / MBR, faulty ribbon data cable, etc.
>>>>>
>>>>
>>>> Until I get past that message, BIOS can't look at the drives.
>>>>
>>>> Advice?
>>>>
>>>> ms
>>>
>>> Well, my assessment is you probably have a fair idea of it. And,
>>> you are probably aware from input this thread that the message is
>>> coming from a hard drive attempting to boot. Therefore, the hard
>>> drive or hard drives have been assessed by the bios.
>>>
>>> Am not a real smart guy, but, I would remove all hard drives but the
>>> AC31000. Then, go from there.
>>> Dave
>>>
>>>
>>
>> I am using the AC31000 drive.
>>
>> I searched on my W2K machine, found an "image" sort of icon labeled
>> "ntdlr", and ntdetect.com (this may cause error message, see below)
>> Nothing else in W2K.
>>
>> My wife has a XP Pro machine, searched there, there are no files in
>> i386 for ntdlr. Several search engines found nothing else. The OS
>> behaves fine, so that's a puzzle.
>>
>> I put the 2 above files on a W98 boot disk, booted up, get message
>> "W2000 can't start because *** is corupted or missing." Maybe caused
>> by ntdetect.com. Of course, neither of these was ntdlr.exe.
>>
>> Searched Google, no luck for ntdlr.exe. Many posts about "missing"
>> message, a few say search in i386 folder for ntdlr.exe, not in my
>> machines.
>>
>> My intent is to wind up with FAT-32 formatted drives, when finished,
>> not NT type drives.
>>
>> Advice?
>>
>> ms
>
> Then why all the skirt around, and skirt the issue stuff. Wipe the
> AC31000 with the WD software writing zeroes to it. Be done with it.
> Then, start from scratch.
>
> I know for a fact that you know how to get a known properly working
> boot 98 startup diskette.
>
> Dave
>
Thanks, Dave, that's better than a general "wipe" utility. I have a
couple of WD floppies, will look there first.

ms
 
ms wrote:

>> Did you even try to boot with a 98 boot disk to see what, if
>> anything, is on the
>> disk and try to fdisk/format it?
>>
>>
>
> Yes, look earlier in the thread where I answered, did that. It
> wound up with the missing file message, stopped there.

Gee, that's a shame, ms. What could it mean? Could it mean that the
floppy was never accessed?

Could be...and that means that you are SOL (unless the floppy or
floppy cable is bad) since you'd have to <GASP> change the BIOS boot
order.

BTW, a 20-30 second Google session yields a weath of info. Like this.
http://tinyempire.com/notes/ntldrismissing.htm

dadiOH...who had hopes - now dashed - that 2008 would be a better
year.
 
"Lil' Dave" <spamyourself@virus.net> wrote in
news:eSMfIm$SIHA.1188@TK2MSFTNGP04.phx.gbl:

> "ms" <ms@invalid.com> wrote in message
> news:5tsurlF1f41njU1@mid.individual.net...
>> "Lil' Dave" <spamyourself@virus.net> wrote in
>> news:uCmnu#2SIHA.4104@TK2MSFTNGP05.phx.gbl:
>>
>>> "ms" <ms@invalid.com> wrote in message
>>> news:5tq0ghF1ds7chU1@mid.individual.net...
>>>> "Brian A." <gonefish'n@afarawaylake> wrote in
>>>> news:uLhtHFpSIHA.1164@TK2MSFTNGP02.phx.gbl:
>>>>
>>>>> "ms" <ms@invalid.com> wrote in message
>>>>> news:5to8pmF105qrvU1@mid.individual.net...
>>>>>> ms <ms@invalid.com> wrote in
>>>>>> news:5to1chF1e9uauU1@mid.individual.net:
>>>>>>
>>>>>>> "Lil' Dave" <spamyourself@virus.net> wrote in
>>>>>>> news:OYs73EjSIHA.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.
>>>>>>>>
>>>>>>> Thanks for the detail, Dave.
>>>>>>>
>>>>>>> If I picture the above, the jumper pins are:
>>>>>>> 5 3 1
>>>>>>> 6 4 2
>>>>>
>>>>> That's the proper way depending on how the drive is held while
>>>>> you look at it, ICR
>>>>> if they actually had a 7th pin back when.
>>>>> There should be markings, S - M - CS, on the top or bottom side of
>>>>> the drive where the pins are, which may require a magnifying glass
>>>>> to see them well enough.
>>>>>
>>>> This one does not have those markings.
>>>>>>>
>>>>>>> The existing jumper is between 5 and 6, not listed above.
>>>>>
>>>>> Prolly a typo since L.D. typed 4-5 and we all know jumpers
>>>>> aren't set on diagnals.
>>>>>
>>>>>>>
>>>>>>> If this is to be a single drive, from above, "no jumper pin"
>>>>>>> looks like the thing to do.
>>>>>
>>>>> If it's the WD drive, that's how it was done back when, no
>>>>> jumper for a Single
>>>>> drive. However, they did come with the jumper set on 2 odd or
>>>>> even pins which was also considered Single.
>>>>>
>>>>
>>>> So my results are with no jumper. See below.
>>>>>>>
>>>>>>> Comment?
>>>>>>
>>>>>> Some test data.
>>>>>>
>>>>>> On the subject drive, I removed the jumper, first step in testing
>>>>>> a drive in this old Compaq P166 is boot with the Compaq setup
>>>>>> disk. On bootup, got the error message "NTDLR is missing". Looked
>>>>>> up in saved data, this file is part of NT type boot sequence. The
>>>>>> computer had W95, IIRC, NT requires a lot more machine than this,
>>>>>> doubt it ever had anything but W95. The hard drive is 1 GB, not
>>>>>> sure it's history.
>>>>>
>>>>> NTLDR = NT Loader and is used for NT/2000/XP.
>>>>> It doesn't matter what the PC originally had installed for an OS,
>>>>> you're testing using a totally different drive than what was with
>>>>> it and it may have had an NT flavor OS on it.
>>>>>
>>>>> Can't you boot with a 98 boot disk to check what, if anything,
>>>>> may be on it.
>>>>>
>>>> Tried that, first get the usual Compaq "F1 to save defaults", then
>>>> get "NTDLR is missing"
>>>>
>>>> I now have 3 unknown drives that might be OK if that message and
>>>> jumpers are sorted out.
>>>>
>>>> Can I search for that file and put it on my W98 boot floppy to copy
>>>> to C: Being DOS on the drive, no windows folder to put it in. Is
>>>> that a possible way to solve this issue?
>>>>>
>>>>>>
>>>>>> I tried 2 other drives, one unknown, one known good, both now
>>>>>> give the same error message on bootup. The computer did not give
>>>>>> this message before today, using other hard drives.
>>>>>>
>>>>>
>>>>> Again, could be a non-bootable disk, the drive isn't configured
>>>>> and/or properly
>>>>> detected by the BIOS, the boot sequence isn't set properly in the
>>>>> BIOS ( you are swapping out disks and using a compuke boot disk ),
>>>>> corrupt boot sector / MBR, faulty ribbon data cable, etc.
>>>>>
>>>>
>>>> Until I get past that message, BIOS can't look at the drives.
>>>>
>>>> Advice?
>>>>
>>>> ms
>>>
>>> Well, my assessment is you probably have a fair idea of it. And,
>>> you are probably aware from input this thread that the message is
>>> coming from a hard drive attempting to boot. Therefore, the hard
>>> drive or hard drives have been assessed by the bios.
>>>
>>> Am not a real smart guy, but, I would remove all hard drives but the
>>> AC31000. Then, go from there.
>>> Dave
>>>
>>>
>>
>> I am using the AC31000 drive.
>>
>> I searched on my W2K machine, found an "image" sort of icon labeled
>> "ntdlr", and ntdetect.com (this may cause error message, see below)
>> Nothing else in W2K.
>>
>> My wife has a XP Pro machine, searched there, there are no files in
>> i386 for ntdlr. Several search engines found nothing else. The OS
>> behaves fine, so that's a puzzle.
>>
>> I put the 2 above files on a W98 boot disk, booted up, get message
>> "W2000 can't start because *** is corupted or missing." Maybe caused
>> by ntdetect.com. Of course, neither of these was ntdlr.exe.
>>
>> Searched Google, no luck for ntdlr.exe. Many posts about "missing"
>> message, a few say search in i386 folder for ntdlr.exe, not in my
>> machines.
>>
>> My intent is to wind up with FAT-32 formatted drives, when finished,
>> not NT type drives.
>>
>> Advice?
>>
>> ms
>
> Then why all the skirt around, and skirt the issue stuff. Wipe the
> AC31000 with the WD software writing zeroes to it. Be done with it.
> Then, start from scratch.
>
> I know for a fact that you know how to get a known properly working
> boot 98 startup diskette.
>
> Dave
>
#1- Downloaded from WD site the latest DOS boot disk. looked at it and
one option is to wipe the hard drive.

Booted the P166 with this WD boot disk, get the following message:
Causeway error 09- unrecoverable internal exception error, program
terminated.

#2- copied a small utility wipeout to W98 boot disk, it would write
zeros.

Booted, get the NTLDR missing message, so can't get to A prompt to run
the utility to wipe the drive.

#3- copied NTLDR and NTdetect.com to W98 boot floppy.

Booted, get message "can't start W2K .....", so again can't copy the 2 NT
files to C, so I can get to A.

I can connect another hard drive formatted with DOS 6.22, works OK with
this computer, not clear how to use this to load files, then switch hard
drives, then not see C, or A.

Advice?

ms
 

Similar threads

AWS
Unified Update Platform with ConfigMgr – Questions from the Field
Replies
0
Views
139
AWS
AWS
AWS
Hive ransomware gets upgrades in Rust
Replies
0
Views
234
AWS
AWS
AWS
September 2023 - Microsoft 365 US Public Sector Roadmap Newsletter
Replies
0
Views
167
AWS
AWS
AWS
September 2022 - Microsoft 365 US Public Sector Roadmap Newsletter
Replies
0
Views
228
AWS
AWS
AWS
FinFisher exposed: A researcher’s tale of defeating traps, tricks, and complex virtual machines
Replies
2
Views
768
allheart55 (Cindy E)
allheart55 (Cindy E)
Back
Top