[comp.unix.aux] Help with SysQuest drive.

unger@cdp.UUCP (08/08/90)

Hello.

I am trying to use a PLI manufactured SysQuest removable cartradge drive
with A/UX 2.0.  I use Silver Lining to partition the drive with one 
A/UX partition.  Then, in A/UX I run dp on the disk to verify
that it has been partitioned correctly and that A/UX can read the disk.
Unfortunatly, it can't.  The error messages I get change from try to try
but most often the message says that the disk returned more data than
was expected.  Once, no error occured and dp was able to read and display
the partition map.  The map was correct.

So I called Apple Tech support.  They said the problem was with the driver
and that there was a patch that would fix it.  They thought the patch was 
called sisi-fix-error-page and was available on sumex.stanford.edu.  I looked
arround be was unable to find it.

Can any one help me with this?  I need the disk to do backups and archive
source.

Tom Unger
MITEM
cdp!unger

blob@Apple.COM (Brian Bechtel) (08/09/90)

unger@cdp.UUCP writes:
>I am trying to use a [...] SysQuest removable cartradge drive
>[Apple Tech Support] said the problem was with the driver
>and that there was a patch that would fix it.  They thought the patch was 
>called sisi-fix-error-page and was available on sumex.stanford.edu.  I looked
>arround be was unable to find it.

The file is /info-mac/util/scsi-fix-error-page.hqx
on sumex-aim.stanford.edu.

Should we start a "most-frequent-answers" message for this group?

--Brian Bechtel		blob@apple.com		"My opinion, not Apple's"

unger@cdp.UUCP (08/10/90)

Never Mind.  I found the file in info-mac/util.  Everything works fine now.

Tom Unger.

urlichs@smurf.sub.org (Matthias Urlichs) (08/10/90)

In comp.unix.aux, article <43800@apple.Apple.COM>,
  blob@Apple.COM (Brian Bechtel) writes:
< unger@cdp.UUCP writes:
< >I am trying to use a [...] SysQuest removable cartradge drive
< The file is /info-mac/util/scsi-fix-error-page.hqx
< on sumex-aim.stanford.edu.
< 
Unfortunately, that's not all that needs fixing.

- When you start A/UX, there must be a driver for the cartridge. The driver
should be loaded by an INIT, because if it's read from an inserted cartridge
(or if you have a cartridge mounted when starting A/UX) the drive is locked
and you'll be unable to swap cartridges.

- Under A/UX, when you start the MacOS system, the cartridge will be there
(provided that its error page is fixed, the partition map is correct, there's
only one partition on the drive -- it wouldn't surprise me if it'd take the
phase of moon into account too...). Don't remove a cartridge before dragging
it into the trashcan!

- How do I re-mount a cartridge (or mount another one) without restarting the
MacOS environment? This is a major pain! The Finder recognizes floppy disks
without problem (BTW: Why is the default for a valid Macintosh floppy
"A/UX data" while an invalid floppy, presumably containing a file system, can
only be ejected or formatted? Switching to the CommandShell "fixes" that
problem, but it's still (a) a major pain and (b) needlessly modal because the
Shell doesn't recognize HFS floppies as such...)
  I tried calling Mount (from the MPW Shell ;-) but all I got was an I/O
error. (The drive number was correct...) I didn't yet try posting a disk
inserted event; would that help? (I doubt it. :-( )

< Should we start a "most-frequent-answers" message for this group?
< 
Probably -- once someone figures out what the answers are... ;-)

-- 
Matthias Urlichs -- urlichs@smurf.sub.org -- urlichs@smurf.ira.uka.de
Humboldtstrasse 7 - 7500 Karlsruhe 1 - FRG -- +49+721+621127(Voice)/621227(PEP)

andyp@treehouse.UUCP (Andy Peterman) (08/10/90)

In article <g^]/e2.&92@smurf.sub.org> urlichs@smurf.sub.org (Matthias Urlichs) writes:
>- When you start A/UX, there must be a driver for the cartridge. The driver
>should be loaded by an INIT, because if it's read from an inserted cartridge
>(or if you have a cartridge mounted when starting A/UX) the drive is locked
>and you'll be unable to swap cartridges.
>
>- Under A/UX, when you start the MacOS system, the cartridge will be there
> ...
>
>- How do I re-mount a cartridge (or mount another one) without restarting the
>MacOS environment? This is a major pain! The Finder recognizes floppy disks

I'm using an APS Syquest drive with no problems.  I think the reason it
works is by accident.  The main drive I'm using for A/UX was partitioned 
with Silverlining, as was the Syquest cartridge I'm using (with two A/UX
partitions).  I think that since the Silverlining driver has already
been loaded in memory when the A/UX drive booted (with MacPartiton),
then the cartridge doesn't need to boot to use this driver (I'm guessing!!).
I can simply install the cartridge, let it come up to speed, and do
a mount on one or both of the slices I'm using.  Unmounting the cartridge
doesn't remove the driver since it's still being used the other HD.

	Andy Peterman
	treehouse!andyp@gvgpsa.gvg.tek.com

justin@Apple.COM (Justin Walker) (08/11/90)

In article <g^]/e2.&92@smurf.sub.org> urlichs@smurf.sub.org (Matthias Urlichs) writes:
>In comp.unix.aux, article <43800@apple.Apple.COM>,
>  blob@Apple.COM (Brian Bechtel) writes:
>< unger@cdp.UUCP writes:
> ...
>- How do I re-mount a cartridge (or mount another one) without restarting the
>MacOS environment? This is a major pain! The Finder recognizes floppy disks
>without problem 
	Alas, A/UX currently does not recognize "insertion events" on other
	than floppy drives.

>(BTW: Why is the default for a valid Macintosh floppy
>"A/UX data" while an invalid floppy, presumably containing a file system, can
>only be ejected or formatted? Switching to the CommandShell "fixes" that
>problem, but it's still (a) a major pain and (b) needlessly modal because the
>Shell doesn't recognize HFS floppies as such...)
>  I tried calling Mount (from the MPW Shell ;-) but all I got was an I/O
>error. (The drive number was correct...) I didn't yet try posting a disk
>inserted event; would that help? (I doubt it. :-( )
	The search for the "correct" behavior on insert events is fraught
	with pitfalls.  After a lot of discussion, we felt that a good
	compromise was to leave the behavior as is for Mac Apps, and
	for CommandShell, make the assumption that the new floppy is
	intended as an A/UX disk (e.g., Tar, file system, ...).

	Thus the default behavior is Mac-ish when you are dealing with a
	Mac App, and accounts for the Unix possibilities when dealing with
	CommandShell.

	The behavior is the same in either case if the disk is unreadable:
	you get to format or eject it.

	If it doesn't work this way for you, let us know.

>Matthias Urlichs -- urlichs@smurf.sub.org -- urlichs@smurf.ira.uka.de
>Humboldtstrasse 7 - 7500 Karlsruhe 1 - FRG -- +49+721+621127(Voice)/621227(PEP)

Regards,

Justin

Justin C. Walker, Curmudgeon-At-Large   (justin@apple.com) *
A/UX Group                              *------------------|
Apple Computer, Inc.                    |  When meetings are outlawed,
10440 Bubb Rd,                          |    Only outlaws will have meetings
Cupertino, CA 95014                     *
-- 
Justin C. Walker, Curmudgeon-At-Large   (justin@apple.com) *
A/UX Group                              *------------------|
Apple Computer, Inc.                    |  When meetings are outlawed,
10440 Bubb Rd,                          |    Only outlaws will have meetings
Cupertino, CA 95014                     *