1problem solved, a new prob occured..argh

[Amigaz]

I have sorted out the trouble I had with my non booting amiga.
The cause was the transparent plastic on the drive tray which had pushed on one side of my Cyberstorm MKII board so it wasn't connected properly so now my A3000 is booting..*phew*
Now another problem showed up, it seems like my CS MKII stops my HDD from booting..
I can partion it and put file systems on it with HDINSTTOOLs and HDTOOLBOX but when I reboot the partions aren't showed.
I did a test to be sure the cause really is the CS MKII, I removed the board and partioned and formatted the HD and installed WB3.1 and the computer booted into WB without and problems.
I then installed the CS MKII software and installed the board again and it didn't boot into WB just into the plain WB insert disk screen.
The board came with the Cyberscsi module which have been used with the CS MKII board in an A4000.
Can only find one jumper in the CS MKII which I think is for write enabling the rom on the board.
Can anyone please shed some light o this and help me, I'm so close now getting my A3000 to work.
Next step after everything's working is to add my external SCSI cd-rom and install OS3.9 and then my Cybervision 3D card.

[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).

[Amigaz]

Hi,

I already have the box, manual for both the CS MKII and Cyberscsi module.
I don't want to use the module since I can't/don't want to perform the INT2 hack.
The CS MKII runs at 50mhz, it's a 68060 fitted on the board..not a 68040.
It says something about that you have to update the firmware on the CS mKII board before you can use the cyberscsi module.
Does this update force me to only use the cyberscsi module?

[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.

[Amigaz]

^bump^  :-)

[X-ray]

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

[Amigaz]

My specs:

A3000D '030 25mhz
2mb Chip
4mb fast ram
3.1 kick roms

4.3 gig SCSI HDD connected to the SCSI controller on the motherboard

The SCSI boots straight into WB3.1 without the CS MKII connected.
And I can see and partition the HDD with HDINSTTOOLS & HDTOOLBOX with the CS MKII connected if I boot the A3000 with my WB3.1 disk but after I reboot I can't see the partitions I've created.

[Amigaz]

 :-(  ^bump^   :-o

[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.

[Amigaz]

Thanks for helping me, really appreciate it
Can I put the libs on my WB3.1 install disk or do I have to make a custom boot disk? If that's the case can you please give me a crash course on how to make one.

[Amigaz]

^b*ump^

[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

[Noster]

Hi,

wasn't there a switch in the Early-startup useable to deactivate/activate the onboard-SCSI ?
The onboard-SCSI might be disabled, if no drive is attached to speed up the booting.

Noster