Path: utzoo!attcan!uunet!timbuk!cs.umn.edu!msi.umn.edu!src.honeywell.com!sol.ctr.columbia.edu!bronze!cica!ogre!greg From: greg@ogre.cica.indiana.edu (Gregory TRAVIS) Newsgroups: comp.sys.amiga.hardware Subject: Re: More info on A2091 woes Message-ID: <10051@cica.cica.indiana.edu> Date: 25 Jan 91 15:08:55 GMT References: <9696@cica.cica.indiana.edu> <1991Jan14.193336.13387@convex.com> <1991Jan15.155835.5230@javelin.es.com> <14480@june.cs.washington.edu> <2627@excelan.COM> <2642@excelan.COM> Sender: news@cica.cica.indiana.edu Lines: 31 Some followup on A2091 woes, now that the ball is rolling. Unfortunatly it appears, contrary to Randell's suggestions, that turning off reselection on both drives does not make the problem go away. It does VASTLY improve the situtation however. First, some data: 1) I'm not a bonehead. I have verified a number of ways that no-reselection is written into the parameters on BOTH drives and I had to re-do my paritions and everything. 2) There IS a marked improvement in reliability. I was convinced the problem had gone away for a week UNTIL... 3) Last night I was putting some stuff together in ProPage and UUCP kicked in. I wrote some stuff out of ProPage at the same time UUCP was going for my USR: disk. BAMMO, it locked up with the light on. 4) I thought it might have been a freak, or a bug in ProPage, so I went to bed last night while my machine ran two copies of a little program I wrote that just reads from files randomly. One copy ran from one drive, the other on the other drive. AND 5) When I woke up this morning, the controller was locked up. So, to protect myself and my work, I've got to go back pretending the Amiga is a single-tasking machine. Mondo Depresso. Unfortunatly, I don't have the $$$ for another (GVP) controller for my other drive. And if I did, I'd spend it on a Loran for my plane... -- Gregory R. Travis Indiana University, Bloomington IN 47405 greg@cica.cica.indiana.edu Center for Innovative Computer Applications Disclaimer: Everything I say is true and I never lie.