Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!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: <2074@esunix.UUCP>
Date: 20 Jul 90 06:22:20 GMT
References: <2071@esunix.UUCP>
Organization: Evans & Sutherland Computer Corporation
Lines: 29
X-Local-Date: 19 Jul 90 23:22:20 PDT

From article <2071@esunix.UUCP>, by blgardne@esunix.UUCP (Blaine Gardner):
> 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. 

The story gets even better, somehow I've messed up the stock Q105S so
that it also crashes under 2.0. I was trying Andy Finkel's suggestion of
turning off reselect on all the drives, and managed to wipe out the
Quantum 105 completely. (Turning off reselect doesn't seem to make any
difference.)

Booting the A3000Install disk under 2.0 produced a consistant Guru of
8000 0004 07C3A5F0. To get the system back, I modified the install script
and ran it under 1.3. Now under 2.0 I get a 8000 0004 07C356D0 or
8000 0004 07C34868 Guru after Startup-Sequence does either BindDrivers
or LoadWB.

Any ideas? (And again, e-mail would be prefered since my site is still
losing news articles.)
-- 
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!