Re: SyQuest corruption! [was Re: HD Errors]

Thread View: comp.sys.amiga.tech

3 messages

[T] Back to Threads [V] Tree View [G] Group Articles

3 total messages Started by Thomas Elam Tue, 08 Jan 1991 02:50

#7918

Author: Thomas Elam
Date: Tue, 08 Jan 1991 02:50

40 lines
2024 bytes

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

Re: SyQuest corruption! [was Re: HD Errors]

#7943

Author: Peter da Silva
Date: Tue, 08 Jan 1991 13:52

16 lines
1322 bytes

In article <140293@pyramid.pyramid.com> telam@pyrps5.pyramid.com (Thomas Elam) writes:
> 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?

This is totally hypothetical, but since it doesn't know that you've put
the disk in until you type "diskchange" I rather doubt the requestor
would be satisfied by simply inserting the disk.

Alternatively you could use OFS on the Syquest. Does OFS handle the SCSI
diskchange protocol?
-- 
Peter da Silva.   `-_-'
<peter@sugar.hackercorp.com>.

Re: SyQuest corruption! [was Re: HD Errors]

#7963

Author: Peter Kittel GERMANY
Date: Wed, 09 Jan 1991 09:31

17 lines
1410 bytes

In article <140293@pyramid.pyramid.com> telam@pyrps5.pyramid.com (Thomas Elam) writes:
>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?

You HAVE to provide the volume name as parameter for Diskchange.
More precise: I believe it needs the physical name (e.g. df0:),
not the name you can give with the Relabel command.
It works with every Amiga device. I have used this when I tinkered
with my corrupted HD and wanted to force a validation. Diskchange
did that.

-- 
Best regards, Dr. Peter Kittel  // E-Mail to  \\  Only my personal opinions... 
Commodore Frankfurt, Germany  \X/ {uunet|pyramid|rutgers}!cbmvax!cbmger!peterk

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads