#syquest help
4 messages in this thread
Steve, It is a brand new commodore contoller… oh, yeah, and we're running
2.0 amigados… Is there anything I can do?
I would guess the way CBM controllers mount their disk is via "mount" (GVP
uses "gvpscsictrl"). I'd say just leave it out of your Startup-Sequence
completely, and when you want to use the Syquest, run the "mount" command
from the CLI.
Steve
Steve:
As far as I know, the mount command will only mount devices that have a
mountlist entry in the devs:Mountlist file. To mount a device from the RDB
(which is why you'd use gvpscsictrl on a gvp controller) isn't something
that C= provides a program to do. I have a program called SCSIMounter which
will scan the SCSI bus and allow you to mount an device it finds. I use
this when I want to boot AMAX so that my SyQuest's device will become AMAX:
(from the RDB on the Amax Syquest cartridge). When I had a GVP controller
in my 2000 I usually mounted it from the mountlist rather than from an RDB
simply so that I didn't have to have a cart in the drive at boot time, but
the drive was still available as soon as I put a cartridge in (well at
least as soon as it spins up). Unfortunately with the 3000 unless I have a
cart in the drive at boot time it polls the drive for 30 seconds before
continueing on with the boot process. At the moment I have 4 drives that
have removable media, and when I boot I make sure they all have media in
them, otherwise I'd have to add 2 minutes to the boot time!
-Mike Schiller
In sunny Fort Lauderdale
Mike,
On bootup, all drives described via the Rigid Disk Blocks are
mounted. If you wish to add partitions that aren't described in the RDBs
or (as in your case) a removeable that isn't there on bootup….you can add
it via a MOUNT command with an appropriate entry in devs:mountlist (or
other specified file). That presumes the device is there and responds, but
no disk in it at that point in time.
Don