Re: RamFast Error code

["Michael J. Mahon" <mjmahon@aol.com>]

On 10/19/2010 12:56 PM, Rich Hare wrote:
> Michael J. Mahon wrote:
> > Rich Hare <Rich113JL@gmail.com> wrote:
> > > Rich Hare wrote:
> > > > I've got a IIGS Rom 03 with a RamFast in it that has been working
> > > > great > for a couple of years. Recently I've been adding hard
> > > > drives and moving > stuff around and suddenly I'm having problems.
> > > > I'm pretty sure I'm > observing all SCSI protocol; the RamFast
> > > > provides Term Power, all drives > have unique ID's and I have a big
> > > > 50 pin terminator at the physical end > of the chain.
> snip
> > > I thought I knew everything in the RamFast Manual, but I found a
> > > different manual on:
> > >
> > > > http://apple2.org.za/gswv/a2zine/Docs/RamFASTManual.txt
> > > and it defined code 0D as "Error writing cache data to disk". That
> > > seems to be it, alright, but doesn't tell me "Why?". Any ideas?
> >
> > A likely cause is that the drive is returning write errors. Try another
> > drive if possible.
> > -michael - NadaNet 3.1: http://home.comcast.net/~mjmahon
>
> Well, I've got three drives I've been trying this on, 1.0 and 1.2 gig
> Connors. I've hooked them to the Mac and run Silverlining on them and
> they get a good bill of health there.
>
> I've tried shortening up the SCSI cable line and only connecting the
> three necessary drives (boot drive, Zip, and target drive) and the
> results are better, but I keep having problems. Right now I'm copying
> Golden Orchard from Zip disks to the target drive.
>
> If it doesn't lock up with a colored screen, I get following error message:
> "System Error ($0001) This Operation cannot be completed. Bad System
> Call Number."
>
> Any idea what that could mean in this context?

Others with more GSOS experience may be able to provide more pertinent
information.

I'm assuming that these errors occur during a long operation.  RAM
errors can appear to be virtually anything.  If your system is failing
occasionally, it could be almost anything that is causing it to operate
marginally.  Power supply degradation or higher operating temperature
are two things that come immediately to mind.

Attack intermittents by making changes in the setup and seeing if the
error frequency changes.  For example, remove the top of the computer
to lower its internal temperature and try again.  Or remove some
unneeded cards/devices and try again.  If you find some change that
makes the errors disappear and re-appear, that can be a useful indicator
of the cause of the problem.

-michael

NadaNet 3.1 for Apple II parallel computing!
Home page:  http://home.comcast.net/~mjmahon/

"The wastebasket is our most important design
tool--and it's seriously underused."