Operator`s manual

Version 1.21 263
/ APPENDIX D
The kind of ‘real-world’ things that can go wrong are........
A. You delete some files on the disk using the sampler - they are deleted, the sampler’s disk
cache is updated, the files don’t appear in the LOAD filelist and everything is fine.
However, the Mac/PC’s disk cache has not been updated and so it doesn’t know anything
about these changes - as far as it’s concerned, the files are still there and so it will still display
the deleted or renamed items. This isn’t a problem in itself but if you try to do anything with
them, because they have been deleted, the system may get confused, the SCSI bus might
crash and the system could lock up with a disk error and it’s possible that the Mac/PC could
cause the disk directory to be corrupted causing irreparable disk failure.
NOTE: The same could happen when renaming files.
B. You move some items from one folder to another on the Mac desktop or in Windows Explorer
in an attempt to organise your sound library more logically. You will see the changes on the
Mac/PC (of course). However....
The sampler knows nothing about the changes you made on your Mac/PC because its disk
cache has not been updated so as far as it’s concerned, the files are still where they originally
were. In the LOAD page, should you attempt to load these files, because they have been
moved elsewhere and don’t actually exist in the folders shown on the sampler anymore, you
may get a disk error, possibly a SCSI crash and maybe even a directory corruption rendering
the disk unusable.
C. If you edit a sample using a Mac/PC wave editor and save that sample back to the disk, the
sampler will not automatically know these changes have even taken place.
For example, if you chop a 1Mb sample in half on a Mac/PC wave editor, the Mac/PC’s disk
cache is updated and it knows the new filesize. The sampler, on the other hand, has no idea
that these changes have taken place - as far as it’s concerned, it’s still a 1Mb sample because
that’s the information it has in its disk cache. Should you try to load this sample into the
sampler.....
That’s right - the sampler is looking for a 1Mb file stored in a particular place on the drive, it
doesn’t find it so there will be a disk error, probably a SCSI crash and possibly even damage
to the disk.
D. The worst of all scenarios! You have the same sample loaded into your sampler AND your
Mac/PC wave editor (maybe intentionally or accidentally). You save it on the sampler and, at
the same time you save it on the Mac/PC. You now have two initiators trying to write different
data to the same point on the disk. You may as well throw the disk in the bin!
It’s a potentially ugly situation! And these are just four situations where things can go wrong. Bring
into the equation SCSI ID mismatches, incorrect termination, etc., and you have a disaster waiting
to happen!
None of this is due to limitations in the S5/6000 or the Mac/PC but is due to the fact that SCSI was
not really intended to be used in this way, as a means of networking devices (that’s why networks
of computers normally use Ethernet or something similar like AppleTalk).
You can now begin to see why sharing a disk between a Mac/PC and an S5/6000 is not
recommended - it’s possible but there are too many risks associated with it.