Installing a CSMKIII in a 3000D

[amesie2]

I am awaiting the return of a CSMKIII from JJ in France that he repaired for me. He is very good to work with and might be a little pricy but he deffinately has the know how to repair the stuff for Amiga's.

I plan on installing this in a 3000D when I get it back.

The current system does have real 3.1 roms along with a fresh install of OS 3.1 which will be upgraded to 3.9 once I get the accel. installed.

I know I need the 060 libraries installed for the board to work but is there other modifications other than changing the jumpers on the motherboard for external clock etc. that I might have to do? The 3000D motherboard is a rev 6.1 or would it be better to use my other 3000D that is rev 7.3?

I am also aware of the int2 mod. that would have to be done to use the CSMKIII SCSI port which I probably won't do right away until I have the system running then maybe tackle the int2.

I haven't done much with the 3000D and it is a little different it seems than the 2000 and 4000 I am used to. Any advice would be helpful in getting this running or problems you might have run into. I will be getting this board back by Fri. hopefully or early next week.

Thanx in advance

[Jope]

It will not boot without the INT2 mod.. SCSI is active from poweron and can't be disabled.

It's just one wire to solder.. You can do it some evening while waiting for the CSMK3 to arrive. :-)

[Amigaz]

Jope wrote:
It will not boot without the INT2 mod.. SCSI is active from poweron and can't be disabled.

It's just one wire to solder.. You can do it some evening while waiting for the CSMK3 to arrive. :-)

It will boot but the UWSCSI won't work on it

Have tried my CS MKIII in my A3000 before it died and I had to send mine to JJ too

[Crisisdog]

I wish you the best of luck.  I had the rare honor of attempting to get both a MKII and a MKIII working in my desktop A3000, but neither would let the A3000 see its very own built in SCSI controller.  I have a habit of wanting to connect my external devices through the built in port, but no-go.  Yes, did the INT2 patch, still nothing.  Finally ended up getting a full size WarpEngine 4040 "hacked" into the case with no issues.  A 68060 would have been nice though...

 :-D

[Argus]

Crisisdog wrote:
I wish you the best of luck.  I had the rare honor of attempting to get both a MKII and a MKIII working in my desktop A3000, but neither would let the A3000 see its very own built in SCSI controller.  I have a habit of wanting to connect my external devices through the built in port, but no-go.  Yes, did the INT2 patch, still nothing.

That's odd, I have a CSPPC with both the UWSCSI and the A3000's on-board SCSI working fine in mine.  I only use the on-board for an external scsi cdrom.  Are you sure you have termination set up properly on both? That's usually the issue with dodgy scsi setups.  I had to add an active 50-pin terminator on the A3000's internal scsi cable to get the external cdrom to work but other than that it runs fine.

[Orjan]

I didnt have any trouble with my MkIII and SCSI either.. Had one drive connected to the MkIII, one to the internal connector of the 3000, and one external CD-ROM.. Worked without a hitch..

[wheels]

I have an MKII in a 3000D as well. No INT2 change and am using the onboard SCSI to boot and the external port for a couple of other devices. The on board SCSI is fast enough for me and I haven't felt the pressure to up-grade.

The active terminator is a good try if you have problems. My system didn't need it but it helped me on another 3000 with a Warp Engine.

JLW

[Crisisdog]

Thanks for the replies, but I sold the boards well over a year ago.  Yes, I'm quite certain the SCSI bus was terminated properly, as the built in SCSI continued to work with both the A3640 and WarpEngine 4040 without changing a thing.  It was more than a termination issue, as any SCSI utility I pointed to "scsi.device" just did not see it there.  No clue, ended up getting the WarpEngine working without a hitch...

 :roll:

[vk3heg]

Crisisdog wrote:
Thanks for the replies, but I sold the boards well over a year ago.  Yes, I'm quite certain the SCSI bus was terminated properly, as the built in SCSI continued to work with both the A3640 and WarpEngine 4040 without changing a thing.  It was more than a termination issue, as any SCSI utility I pointed to "scsi.device" just did not see it there.  No clue, ended up getting the WarpEngine working without a hitch...

 :roll:

Try "cyberscsi.device" for the CS's on board scsi port.

[zipper]

Try "cyberscsi.device" for the CS's on board scsi port.

cybscsi.device

[alexh]

What kinda prices have you been paying for CSMKIII repairs?

Ball park figures?

[Amigaz]

it's cybppc.device on CS MKIII/PPC cards

[doctorq]

Or if in doubt, start HDToolbox with the ASKDEVICE tooltype.

[zipper]

Yes, cybscsi on Mk I / II.

[amesie2]

@alexh

The repair for my CSMKIII was $280.00 with shipping back to me from France.


I don't think I will use the SCSI on the CS at least not yet I think the onboard SCSI will work good enough for me.