#Oktagon 2008 woes
5 messages in this thread
I think the info about using the Oktagon with another controller was in a
read-me file on the disk containing the Oktagon setup software Try swapping the
physical locations of the two hard disk controllers (ie., switch the slots they
occupy). Also make absolutely sure that your hard drives don't have the same
SCSI unit addresses and that more than one isn't set for autobootup (you need
to run the hard disk tools software to arrange that). Finally, it may help to
ensure that the booting hard drive has a higher priority than any others no
matter which controller they're on.
Well, I only have one controller that uses an actual slot, one being the
Oktagon and the other being the on-board IDE controller (I assume that the
4000's IDE controller is a physical part of the motherboard, since that's where
the cable connects – is this right?)
And why DOES the IDE drive show up with a scsi.device driver in the setup
screen? Could that be a problem with a real scsi controller onboard?
Can't help you with an A4000 as I don't have one, but its having an embedded
IDE controller could indeed be a problem. You could try tech support for the
Oktagon board. I believe it is handled in the US by Micro R&D in Loop City, NE,
but check me on that.
Technical support for the Oktagon and all other Alpha Data products is handled
in the U.S. by Alpha Data U.S., which is part of Micropace.
>And why DOES the IDE drive show up with a scsi.device driver in the >setup
screen? Could that be a problem with a real scsi controller >onboard?
There is nothing wrong.
The Amiga onboard IDE controller in the A1200 & A4000 uses the scsi.device
driver. IDE drives use address 0 & 1. Commodore integrated IDE support into the
scsi.device.