Amiga.org

Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: iconoclaST on February 17, 2009, 07:33:23 PM

Title: A2000 CDROM Setup
Post by: iconoclaST on February 17, 2009, 07:33:23 PM: Well, I have BabelCDFS, and my CDROM device is properly set up as ID 2 and terminated. Now, what should I add in the MountList? My controller is an A2091, my CDROM is a Nakamichi MBR-7.

I tried using the example MountList entry on the BabelCDFS site, but to no avail. Any ideas?

(Admittedly, I "guessed" it would be scsi.device and not gvpscsi.device)
Title: Re: A2000 CDROM Setup
Post by: Tumbleweed on February 17, 2009, 08:48:38 PM: What version of workbench are you running? Kickstart version?
Title: Re: A2000 CDROM Setup
Post by: iconoclaST on February 18, 2009, 02:10:37 AM: I'm running Kickstart 1.3, Workbench 1.3.3.

Additional info:
My A2091 controller is working perfectly fine with my hard drive, and on boot, there is an attempt to read the CDROM (I assume to find a bootable medium).

My CDROM jumper settings:
SCSI ID 2, Terminate on, SCSI-II compatibility mode off, SCSI parity check on.

I've noticed a lot of things referring to gvpscsi.device on other posts, but as my SCSI controller is not a GVP device, I'm assuming that gvpscsi.device wouldn't be the driver to use.
Title: Re: A2000 CDROM Setup
Post by: KatManDEW on February 18, 2009, 03:28:21 AM: Went through kind of the same thing here recently. My CD wouldn't show up until I hacked around and went into Storage - DOSDrivers, and right clicked on CD0 and selected Icons - Information, and changed UNIT to match my CD device number (2 in your case).
Title: Re: A2000 CDROM Setup
Post by: Tension on February 19, 2009, 02:16:19 AM: Quote

iconoclaST wrote:
I'm running Kickstart 1.3, Workbench 1.3.3.

PFFFFFFFFFFFFFFFFFFFFFFFFT!!!!!!!!!! :roll:
Title: Re: A2000 CDROM Setup
Post by: Matt_H on February 19, 2009, 03:01:30 AM: @ iconoclaST

Are you familiar with Mountlists? They're a little tricky under 1.3.

Each entry begins with the device name, I.E., CD0: and ends with a #.

The 2091 does use scsi.device. Here's what I think your entry should look like.

Code: [Select]
CD0: Handler = L:BabelCDROMFS Startup = scsi.device/2 StackSize = 4000 Priority = 10 GlobVec = -1 #

Add it to the end of Devs:Mountlist, then type
Code: [Select]
mount CD0: in a shell. If it works, add that mount command to your startup-sequence or StartupII file.
Title: Re: A2000 CDROM Setup
Post by: iconoclaST on February 20, 2009, 04:33:28 AM: Same way I had it typed in.
However, didn't try mount CD0: before.

But, nothing came up when I tried that...
No error messages or anything from the CLI..did it twice and the second time it said it was already mounted.

However, nothing. BTW: All CD's I've tried to mount are ISO9660.

I've heard that I have to also deal with Logical Unit numbers with a Nak changer, in addition to Device IDs...What would I do about that?
Title: Re: A2000 CDROM Setup
Post by: Matt_H on February 20, 2009, 05:00:19 AM: Quote
I've heard that I have to also deal with Logical Unit numbers with a Nak changer, in addition to Device IDs...What would I do about that?

If LUNs are indeed the issue, then I think the unit numbering is going to be different - you may even need multiple mountlist entries - CD1:, CD2:, etc. There might also be a jumper to throw on the 2091.

Try unit 12, 102, or something similar. A mounter utility that does a full unit scan could tell you more, but I'm not sure what there is for 1.3. Check Aminet and the Fish Disks.