ST-225 help needed

From: Marvin Johnston <>
Date: Mon Jul 22 16:09:01 2002

One way to actually see if the HD is being recognized by the system is
to use fdisk, option 4 (display ...). If fdisk doesn't see it, then
there is a hardware problem someplace ... bad cable, wrong jumper
settings on the HD and/or controller, bad HD controller, bad HD, etc.

If both drives are being recognized, there will be an option to change
drives when viewing the parameters for the first drive to view the
parameters for the second drive. Also, if a disk manager was used on the
second drive, fdisk could show a non-dos partion on the second drive.

If there is a motherboard problem, why not just use an AT motherboard
with the CMOS set to no drives? Besides being able to read the HDs, you
will be able to use high density floppys.

I don't recall the parameters for your HD controller ... the older ones
needed to have a jumper set on the controller for each drive, while some
of the newer ones did that with software and some information put on the
HD itself.

How do you know the motherboard is a fault for not being able to read
the 360K drive?

Glen Goodwin wrote:
> > From: Don Maslin <>
> > To: classiccmp <>
> > Subject: Re: ST-225 help needed
> > Date: Monday, July 22, 2002 3:53 PM
> >
> >
> > Is the WD controller the same one that the drives running on in the XT?
> > If not, it is possible that you will not be able to boot/read the
> > drives.
> It is the same controller that originally wrote the data to the drives.
> > Assuming that this is not a problem, and assuming that you are using a
> > cable with a twist, both drives should be set as the second DS and the
> > bootable one should be connected beyond the twist. Be sure that you
> > connect the proper 20 pin connectors to the appropriate drives.
> No problem there. Both drives are set to second channel, and the cable has
> a twist, but the controller does not see the second drive. Now I need to
> know how to configure this controller for a dual-drive setup.
> > Set
> > the BIOS to no hard drives and let the BIOS on the controller handle
> > the drives. Boot 'er up.
> Hmm, no BIOS setup program on XT-class machines ;>)
> > Hopefully, you will be able to write to a floppy, or it might be
> > difficult to save your data from the data disk.
> Actually, the system can't write to a floppy, but the system does recognize
> a SCSI drive connected to an 8-bit controller, so I can move the data to
> the SCSI drive and then put the SCSI drive into a system with a usable
> floppy drive.
> Thanks --
> Glen
> 0/0
Received on Mon Jul 22 2002 - 16:09:01 BST

This archive was generated by hypermail 2.3.0 : Fri Oct 10 2014 - 23:35:02 BST