Path: utzoo!attcan!uunet!mailrus!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!van-bc! From: lphillips@lpami.wimsey.bc.ca (Larry Phillips) Newsgroups: comp.sys.amiga.hardware Subject: Re: Quantum 170S on A3000 Message-ID: <1805@lpami.wimsey.bc.ca> Date: 20 Jul 90 13:26:34 GMT Lines: 35 Return-Path: To: van-bc!rnews In <2071@esunix.UUCP>, blgardne@esunix.UUCP (Blaine Gardner) writes: >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.) Sounds like a corrupted file somewhere. It could be anything to do with the WB, including the 2.0 kickstart. If it works from the CLI in 2.0, it should work under WB. I can't think of any reason that the drive would be accessed any differently just because some WB stuff is doing the accessing. -larry -- The raytracer of justice recurses slowly, but it renders exceedingly fine. +-----------------------------------------------------------------------+ | // Larry Phillips | | \X/ lphillips@lpami.wimsey.bc.ca -or- uunet!van-bc!lpami!lphillips | | COMPUSERVE: 76703,4322 -or- 76703.4322@compuserve.com | +-----------------------------------------------------------------------+