Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!spool.mu.edu!uwm.edu!linac!midway!msuinfo!convex.cl.msu.edu!jap
From: jap@convex.cl.msu.edu (Joe Porkka)
Newsgroups: comp.sys.amiga.hardware
Subject: Re: HELP! A590 Harddrive Problems.
Keywords: A590, Broken
Message-ID: <1991Feb12.174642.24462@msuinfo.cl.msu.edu>
Date: 12 Feb 91 17:46:42 GMT
References: <1991Feb12.014521.24270@cs.UAlberta.CA>
Sender: news@msuinfo.cl.msu.edu
Organization: Michigan State University
Lines: 26

c315-25@cs.UAlberta.CA (Huisman Kenneth M) writes:

>I could use some assistance in determining what is wrong with my
>A590.  In short, when loading *anything*, it comes up with
>"Volume Workbench has a read/write error".  This is especially bad
>when I boot off the hard drive, but the drive is somewhat stable
>when I boot of a floppy.  When this problem first began to appear, I could
>"resolve" it by repeatedly clicking on the 'retry' button, and eventually
>the error would seemingly go away and the program would load.  Lately, this
>method hasn't been at all successful.


I had this problem too. Its a SOFTWARE problem, as in a BUG.

As I recall, something like the following will cuase it troubles...
	in a script file, in S:, say S:TEST, place a cd command.
	For example, in S:TEST, place "cd dh0:utilities"
	reboot, without executing S:startup-sequence,
	type "execute s:test" from the initial CLI, try
	executing something, like "dir", or notepad, and BOOM.


Basically, the solution is to put a "cd sys:" near the top of your
startup sequence, right after setpatch.
If that does not work for you, remove all "cd" commands from
your scripts, or any program that may do a "cd".