Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!uwm.edu!linac!att!rutgers!cbmvax!cbmehq!babylon!rbabel
From: rbabel@babylon.rmt.sub.org (Ralph Babel)
Newsgroups: comp.sys.amiga.hardware
Subject: Re: GVP FaaastROMs <--> 68020 :-(
Message-ID: <08215.AA08215@babylon.rmt.sub.org>
Date: 31 May 91 16:25:35 GMT
Article-I.D.: babylon.08215.AA08215
References: <91151.130031LEIF@SLACVM.SLAC.STANFORD.EDU>
Reply-To: cbmvax.commodore.com!cbmehq!babylon!rbabel (Ralph Babel)
Lines: 32

In article <91151.130031LEIF@SLACVM.SLAC.STANFORD.EDU>,
LEIF@SLACVM.SLAC.STANFORD.EDU writes:

> I would get intermittant, but very frequent, failure of
> the OS to recognize the harddrive on boot-up.  After
> several reboots, or after booting from a floppy, I would
> get some (but usually not all) of my partitions up, with
> the remaining partitions comming up bad (eg dh3:bad).

If a hard drive doesn't get recognized after a cold boot,
I'd normally assume that the driver gives up too soon (i.e.
very slow drive). But in this case, it really must be
something else, since it worked on a standard 68000-based
machine (there are no processor-dependent timing loops in
the driver). And partitions showing up as "bad"? Yuck!

FaaastROM has been tested successfully on other '020s (such
as the Hurricane '020, the A2620), not to mention the '030s,
so I'd really assume a hardware problem. Please give us some
more information on your configuration: amount of memory
(32-bit-wide?), brand of '020 board, etc.

> I decided on a hunch to replace the new GVP FaaastROM
> eprom with my old eproms to see if it helped.  Of course
> the problem went away ENTIRELY!

Weird! Please disable the ROMs and try the BindDrivers
version of both the old (pre-FaaastROM) and the new
(FaaastROM) driver software. You might also try a later
version of FaaastROM.

Ralph