Fairlight-CMI

I am new to my CMI III/MFX and can fully access one drive, but do not know the ID of a 
second drive I know to be installed, what is the operation to Identify the names of the 
drives in the system? 

Anyone who can help me with this, I'd greatly appreciate it. This may be fundamental, but 
I'm just learning and could use some friendly advice.

Peace.

Andrews

DIRTY HALO www.dirtyhalo.com

--- In Fairlight-CMI@yahoogroups.com, "dirtyhalo007"
<dirtyhalo007@y...> wrote:
>Hi,
Your second drive may well be /c200.
Try this first. I'll try to find listing commands for you.
CJ
> I am new to my CMI III/MFX and can fully access one drive, but do
not know the ID of a 
> second drive I know to be installed, what is the operation to
Identify the names of the 
> drives in the system? 
> 
> Anyone who can help me with this, I'd greatly appreciate it. This
may be fundamental, but 

> I'm just learning and could use some friendly advice.
> 
> Peace.
> 
> Andrews
> 
> DIRTY HALO www.dirtyhalo.com
>

Hopefully this will help:

Device IDs

Fundamental to the way a disk is referenced is the SCSI ID that it
(the device) uses.

Your boot Disk will have SCSI ID 0. Other hard disks can be assigned
to SCSI ID's 2 and 4 and 6. The Internal Tape drive used SCSI ID 1,
with the WORM drive taking SCSI ID 3.

The Fairlight then assigns IDs to these devices as /scx0 where x = the
SCSI ID; hence your boot disk will be /sc00 and a second disk assigned
to SCSI ID 2 will be /sc20. You can access the devices from the shell
command prompt using the command 'chd /scx0'

Partitions

Each disk device can (or will be) partitioned into a number of
partitions called either /k partitions or /c partitions. This is
similar to the way in which a PC disk can be split into c: d: and e:
etc. partitions. (There is also the concept of Logical Units or LUNs,
but this can confuse matters, so I'll leave it for now).

K partitions hold the system files and mirror the size of the original
8" floppies (~1MB). Hence it is usual to find at least 3 /k partitions
on a hard disk, each containing the files from one of the 3 Rev x boot
floppy disks.

C partitions on the other hand  are where your sound data is stored
and hence represent the bulk of a disk. You can have multiple c
partitions on one physical disk as well, useful if you want to
segregate your sounds. 

In terms of how these partitions are assigned, the nomenclature
refrences the physical disk that the partition is assigned to. So for
/sc00, the partitions will be named as follows:

/k000
/k001
/k002
/k003
....
/c000
/c001
/c002 etc

and for device /sc20, the partitions will be:
/k200
/k201
/k202
...
/c200
/c201
/c202 etc.

All of the partitions can be accessed from within the CMI software
(using the odir command; for example odir /c200/fairlight_library
opens the back-up library on my second disk), or from the shell using
the chd command. 

If you need any further info, please shout.

Whilst on the subject of Series III disks, I would like to say a huge
thank you to Klaus Michael Indlekofer for his cmios9 tool and updating
the tool to reach a state where it is able to be used to export and
import complete /c partitions from other disks. I have now used this
to back-up my Rev9.34 boot disk and image this to 3 other drives so I
can now sleep well at night knowing my sound data is backed up to my
PC and copied to a number of other disks that I can use in my Series III.

Regards,
Chris.

--- In Fairlight-CMI@yahoogroups.com, "dirtyhalo007"
<dirtyhalo007@y...> wrote:
>
> I am new to my CMI III/MFX and can fully access one drive, but do
not know the ID of a 
> second drive I know to be installed, what is the operation to
Identify the names of the 
> drives in the system? 
> 
> Anyone who can help me with this, I'd greatly appreciate it. This
may be fundamental, but 

> I'm just learning and could use some friendly advice.
> 
> Peace.
> 
> Andrews
> 
> DIRTY HALO www.dirtyhalo.com
>

I think the command to scan the drives is 'inq'. Probably only on Rev 
>= 9. To get to a shell from the CMI type $ or #.

Chris Alfred

--- In Fairlight-CMI@yahoogroups.com, "chaworth012000"
<christopher.haworth@u...> wrote:
>
Hi,
Great info; but does this help identify drives on the SCSI bus(?)

CJ

> Hopefully this will help:
> 
> Device IDs
> 
> Fundamental to the way a disk is referenced is the SCSI ID that it
> (the device) uses.
> 
> Your boot Disk will have SCSI ID 0. Other hard disks can be assigned
> to SCSI ID's 2 and 4 and 6. The Internal Tape drive used SCSI ID 1,
> with the WORM drive taking SCSI ID 3.
> 
> The Fairlight then assigns IDs to these devices as /scx0 where x = the
> SCSI ID; hence your boot disk will be /sc00 and a second disk assigned
> to SCSI ID 2 will be /sc20. You can access the devices from the shell
> command prompt using the command 'chd /scx0'
> 
> Partitions
> 
> Each disk device can (or will be) partitioned into a number of
> partitions called either /k partitions or /c partitions. This is
> similar to the way in which a PC disk can be split into c: d: and e:
> etc. partitions. (There is also the concept of Logical Units or LUNs,
> but this can confuse matters, so I'll leave it for now).
> 
> K partitions hold the system files and mirror the size of the original
> 8" floppies (~1MB). Hence it is usual to find at least 3 /k partitions
> on a hard disk, each containing the files from one of the 3 Rev x boot
> floppy disks.
> 
> C partitions on the other hand  are where your sound data is stored
> and hence represent the bulk of a disk. You can have multiple c
> partitions on one physical disk as well, useful if you want to
> segregate your sounds. 
> 
> In terms of how these partitions are assigned, the nomenclature
> refrences the physical disk that the partition is assigned to. So for
> /sc00, the partitions will be named as follows:
> 
> /k000
> /k001
> /k002
> /k003
> ....
> /c000
> /c001
> /c002 etc
> 
> and for device /sc20, the partitions will be:
> /k200
> /k201
> /k202
> ...
> /c200
> /c201
> /c202 etc.
> 
> All of the partitions can be accessed from within the CMI software
> (using the odir command; for example odir /c200/fairlight_library
> opens the back-up library on my second disk), or from the shell using
> the chd command. 
> 
> If you need any further info, please shout.
> 
> Whilst on the subject of Series III disks, I would like to say a huge
> thank you to Klaus Michael Indlekofer for his cmios9 tool and updating
> the tool to reach a state where it is able to be used to export and
> import complete /c partitions from other disks. I have now used this
> to back-up my Rev9.34 boot disk and image this to 3 other drives so I
> can now sleep well at night knowing my sound data is backed up to my
> PC and copied to a number of other disks that I can use in my Series
III.

> 
> Regards,
> Chris.
> 
> --- In Fairlight-CMI@yahoogroups.com, "dirtyhalo007"
> <dirtyhalo007@y...> wrote:
> >
> > I am new to my CMI III/MFX and can fully access one drive, but do
> not know the ID of a 
> > second drive I know to be installed, what is the operation to
> Identify the names of the 
> > drives in the system? 
> > 
> > Anyone who can help me with this, I'd greatly appreciate it. This
> may be fundamental, but 
> > I'm just learning and could use some friendly advice.
> > 
> > Peace.
> > 
> > Andrews
> > 
> > DIRTY HALO www.dirtyhalo.com
> >
>

--- In Fairlight-CMI@yahoogroups.com, "dirtyhalo007"
<dirtyhalo007@y...> wrote:
>Hi,
Are you running 9.34 software on your CMI? If so try the following.
Switch on the machine. On start-up, as the cursor rotates in the
bottom left corner of the screen, press esc. This will take you to
Waveform Supervisor diagnostics. Scroll to "print devices on SCSI bus".
This should give you the data you need.
All the best,

CJ
> I am new to my CMI III/MFX and can fully access one drive, but do
not know the ID of a 
> second drive I know to be installed, what is the operation to
Identify the names of the 
> drives in the system? 
> 
> Anyone who can help me with this, I'd greatly appreciate it. This
may be fundamental, but 

> I'm just learning and could use some friendly advice.
> 
> Peace.
> 
> Andrews
> 
> DIRTY HALO www.dirtyhalo.com
>