Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!nic.MR.NET!umn-d-ub!rutgers!apple!oliveb!amiga!cbmvax!andy
From: andy@cbmvax.UUCP (Andy Finkel)
Newsgroups: comp.sys.amiga
Subject: Re: flakier amigas
Message-ID: <6170@cbmvax.UUCP>
Date: 7 Mar 89 17:50:39 GMT
References: <3011@hplabsz.HPL.HP.COM>
Reply-To: andy@cbmvax.UUCP (Andy Finkel)
Distribution: na
Organization: Commodore Technology, West Chester, PA
Lines: 25

In article <3011@hplabsz.HPL.HP.COM> dleigh@hplabsz.UUCP (Darren Leigh) writes:
>I tried "diskdoctor hr:" only to get a "Not enough memory" error
>message (with and without the 2 Meg board installed).  I get the same
>message when I do a diskdoctor on "boot:" (my tiny OFS partition) so
>apparently diskdoctor wants a look at the whole disk.  Is there some

Well, DiskDoctor 1.3.4 is getting a track buffer in chip ram,
rather than using bufmemtype (I'll have this fixed).  But that's
probably not the problem, since you should have more than enough
chip ram for a quantum.  DiskDoctor uses 2 arrays, each 1 longword
per block of drive.  With your 2 meg card you should have
enough for that as well. (unless your memory is fragmented;
use avail to check)  The problem is probably you are
asking DiskDoctor to run on a volume node, instead of a
device node, like running it on SYS: instead of DF0: .  DiskDoctor
is giving an incorrect error message.
-- 
andy finkel		{uunet|rutgers|amiga}!cbmvax!andy
Commodore-Amiga, Inc.

"Question of the Day : When will we get a device independent graphics standard
 that is fast enough to actually be useful as a window system ?"

Any expressed opinions are mine; but feel free to share.
I disclaim all responsibilities, all shapes, all sizes, all colors.