Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!mcgill-vision!snorkelwacker!tut.cis.ohio-state.edu!ucsd!helios.ee.lbl.gov!hellgate.utah.edu!uplherc!esunix!blgardne
From: blgardne@esunix.UUCP (Blaine Gardner)
Newsgroups: comp.sys.amiga.hardware
Subject: Re: Quantum 170S on A3000
Message-ID: <2071@esunix.UUCP>
Date: 19 Jul 90 06:04:06 GMT
References: <2069@esunix.UUCP>
Organization: Evans & Sutherland Computer Corporation
Lines: 24
X-Local-Date: 18 Jul 90 23:04:06 PDT

From article <2069@esunix.UUCP>, I wrote:
> If anyone has a Quantum ProDrive 170S working on an A3000, I'd
> appreciate some help. 

After a second day of messing with the Quantum 170S, I've got some more
information. On the A590, A2000 with Microbotics Hardframe, and the
A3000, the drive seems to work perfectly _UNDER_1.3_ONLY_. The only time I
have problems is trying to use the drive under 2.0 on the A3000. 

Since I was planning to use this drive as the boot drive for the A3000,
I've got a problem!

The drive can be accessed from the CLI under 2.0, but as soon as I type
LOADWB, I get a system error (Suspend/Reboot) requester, and from there
to the Guru. Unfortunatly I didn't write down the Guru numbers, but they
seemed to vary each time.

Why would 2.0 cause problems with an otherwise perfect drive?
(This is the release of 2.0: KS 36.141, WB 36.68.)
-- 
Blaine Gardner @ Evans & Sutherland  580 Arapeen Drive, SLC, Utah 84108
blgardne@esunix.UUCP
{decwrl, utah-cs}!esunix!blgardne
DoD #0046                               The Borg killed Laura Palmer!