Securix
Experienced Member
So until I have more time to investigate the faulty MiniScribe 3425 in my Altos 886, I obtained a couple of ST-225s to try replacing it and just re-installing Xenix.
The drives seem to be fine. The Altos Xenix 3.2f boot disk seems to find it. It says HARD DISKS [1] but when it loads the controller device driver, I get a message that says "Cannot read drive configuration." When the install menu comes up and I try to install Xenix, the same message comes up along with an I/O error line.
I tried a MiniScribe 3425P as well, which works fine in my DEC Pro 350, but it also causes this error on the Altos.
Only thing I can think of is that it needs to be partitioned and formatted for the Altos, where Xenix may require an FF partition at the MBR Track 0 containing the so-called Xenix Bad Block Table. But can't find any kind of diagnostic disk anywhere that can do this and the boot disk has no option for it.
Anyone have any idea where I can find this if it exists or if not, how to properly configure a hard drive for the Altos 886? Maybe there's some kind of ROM-based routine buried in it's ROMS accessible via the debug facility?
Thanks!
The drives seem to be fine. The Altos Xenix 3.2f boot disk seems to find it. It says HARD DISKS [1] but when it loads the controller device driver, I get a message that says "Cannot read drive configuration." When the install menu comes up and I try to install Xenix, the same message comes up along with an I/O error line.
I tried a MiniScribe 3425P as well, which works fine in my DEC Pro 350, but it also causes this error on the Altos.
Only thing I can think of is that it needs to be partitioned and formatted for the Altos, where Xenix may require an FF partition at the MBR Track 0 containing the so-called Xenix Bad Block Table. But can't find any kind of diagnostic disk anywhere that can do this and the boot disk has no option for it.
Anyone have any idea where I can find this if it exists or if not, how to properly configure a hard drive for the Altos 886? Maybe there's some kind of ROM-based routine buried in it's ROMS accessible via the debug facility?
Thanks!