Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!apple!voder!pyramid!telam
From: telam@pyrps5.pyramid.com (Thomas Elam)
Newsgroups: comp.sys.amiga.tech
Subject: Re: SyQuest corruption! [was Re: HD Errors]
Message-ID: <140293@pyramid.pyramid.com>
Date: 8 Jan 91 02:50:28 GMT
Sender: daemon@pyramid.pyramid.com
Organization: Pyramid Technology Corporation, Mountain View
Lines: 40

In article <41017@nigel.ee.udel.edu> new@ee.udel.edu (Darren New) writes:
>>Hey! Aren't SyQuest drives a removable media drive?!?!?!!?
>>Since when did FFS support removable media?!!?
>
>Since the DiskChange command was written.
>
>>The only places I have seen a SyQuest work properly are with a GVP
>>controller using a *** Specially hacked FFS *** to deal with removable
>>media, and under 2.0.
>
>Actually, it isn't *hacked* at all. The device driver periodically asks the
>drive (via a SCSI command) whether it is ready, and if not it issues a
>diskchange command.
>
>>PS, I borrowed a SyQuest from a friend, and proved to myself the
>>commodore controller couldnt handle the removable media. And
>>YES, I got read write errors galore! WB2.0 fixed this!
>
>Then you didn't diskchange.  I've done this for months with never
>a problem.  "Use your wheels, it is what they are for."
>     -- Darren

Darren:

Then does this mean, for example, that Commodore's A2091 would work
fine with a Syquest drive and that after each insertion, I would just
type "diskchange"?  Wouldn't this cause problems if the system asked
for a particular disk volume (via a standard requestor), and accessed
the disk as soon as I put it in?

I hope you answer soon, since I've got an A2091 at home but a TrumpCard
on order.

>-- 
>--- Darren New --- Grad Student --- CIS --- Univ. of Delaware ---
>----- Network Protocols, Graphics, Programming Languages, 
>      Formal Description Techniques (esp. Estelle), Coffee, Amigas -----
>              =+=+=+ Let GROPE be an N-tuple where ... +=+=+=

Tom