Re: ZipGS & Iomega Zip Drive Incompatibility?

[rubywand@aol.com (RUBYWAND)]

In article <4qva9g$kvq@zot.io.org>, crownmi@zot.io.org (Myles Fudge)
writes:

>
>>The current versions of RAMFast save the settings to the
>>hard disk (or, supposedly, Zip Drive disk) which it controls.
>
>I don't ever recall seeing a configuration file on my hard drive 
>(invisible or otherwise).  Do you know where it saves the info?
>

     According to the hardware guy at Sequential, the config is not saved
as a file. It is saved as bytes written directly to the hard disk, Zip
Drive, etc. in an early block-- I think he said Block 0.  (Unfortunately,
this makes it fairly difficult to set config when RAMFast controls only
non-writeable media, like a CD-ROM drive.) 


>>     When first starting your system, be sure to have the Zip Drive
>>powered for a few seconds before turning ON the IIgs.  
>>Rubywand
>
>Okay, however that is something I never do.  I just power on the whole 
>system at the same time and the zip drive and ramfast just take off and 
>boot into gsos.
>

     Powering up a hard disk separately can be a bother. (It's pretty easy
with a CD-ROM drive.)  The chief rationale for an early HD power-up is
that it guarantees that HD circuits are ready to respond to the interface.
Sometimes this makes a difference in whether or not a drive will be
recognized.

     An interesting possibility is that having your Zip Drive power up
along with the GS often happens to toggle latches (RAM, etc.)  which leads
RAMFast to do a Short Timeout startup. Were you to always power up the Zip
Drive a second or so early, you might find that you would consistently get
the annoying 45-second wait! On the other hand, simultaneous power-up may,
sometimes, jiggle the latches into an unfavorable setting; and, the Zip
Drive will not boot at all.  



Rubywand