Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!cs.utexas.edu!sun-barr!ames!amdahl!pacbell!sactoh0!americ!erk
From: erk@americ.UUCP (Erick Parsons)
Newsgroups: comp.sys.amiga
Subject: Re: Duplicating using WB??
Message-ID: <1830.AA1830@americ>
Date: 6 Sep 89 22:27:03 GMT
Followup-To: comp.sys.amiga
Distribution: na
Lines: 22


>From: kasper@iesd.auc.dk (Kasper Osterbye) Message-ID: <1989Sep6.123302.9638@iesd.auc.dk>
>
>What are the idea that duplicating (using WB) requires all
>the memory on the machine? If I pick the drawer `empty' and
>say duplicate, it eats all available ram, and then gives it back
>again - why is that?

I noticed the same thing but only when using Memclk supplied with the
3.4b version of the Aztec C compiler. The WB titlebar does not reflect
this (feature ?). The first time I noticed it I braced for a Guru as I
saw the Fastmem dwindle down to zero followed by the chip ram completely
dissapearing (0). But then it mysteriously popped back to the original
values, nothing missing ?!? Aside from the first initial scare I've had
absolutely no problems with this... hmmm.

--
-------------------  // ----------------------------------------------------
 Erick Parsons      // .Knowledge is little more than  knowing the questions
 -------------     //  .erk@americ.UUCP or ..ames!pacbell!sactoh0!americ!erk
 Sacramento Ca \\ //   .GEnie: E.PARSONS      %-)       Hamatuer Radio N6RZB
--------------  \X/ --------------------------------------------------------