1problem solved, a new prob occured..argh

[X-ray]

The CyberSCSI comes in two pieces, one attaches to the MKII directly, and the other is attached via a ribbon cable (this one has the external SCSI port). PM me your email address and I will send you the MKII manual and the CyberSCSI manual. It will be quicker than explaining all the jumpers and termination here.

Also: if you use the CyberSCSI module, you must not overlock the MKII because it will crash (the CyberSCSI module only likes 50mHz).

[X-ray]

No the update won't force exclusive use of the CyberSCSI (at least it did not do that on my A4000T). I ran both the A4091 on-board SCSI and the CyberSCSI together, no problems).
I don't know what limitations you will have without the INT 2 fix though.

Edit: I see what you are getting at now: it shouldn't make a difference whether the previous owner had it set up to use the SCSI module, because I had mine attached and then removed, and moved drives from one controller to the other, and all was fine. The CyberSCSI is optional, even afer you install it.

[X-ray]

How are your drives currently attached? What is your full config?

[X-ray]

This is a strange one...the drive is recognised on the A3000 scsi but goes away when you have the MKII connected?

Alright, can you make a bootable floppy disk with all the proper 040 and 060 libraries on it, and HDToolbox, and boot from that with the MKII connected and see if you can partition and save changes to the drive like that.
Next reboot....check Early Startup to see what devices are detected. If all devices present, let it boot again from the floppy and see if your hard disk shows up.
If no devices seen at Early Startup, I am stumped as to what the reason is.

[X-ray]

Did you get any install disks with that MKII?
On there should be the libraries.
Also what do you see on Early Startup at the moment?

Edit: ignore that about the libraries and boot floppy, just tell me what you get in Early Startup when the MKII is connected.


Also check out this
thread