kasper@iesd.auc.dk (Kasper Osterbye) (09/06/89)
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? Forever wondering, Kasper -- Kasper Osterbye Internet: iesd!kasper@uunet.uu.net Institute for electronic systems UUCP: ...!mcvax!iesd!kasper Strandvejen 19, 9000 Aalborg DENMARK. (W) +45 98 13 87 88-285 (H) +45 98 37 30 65
andy@cbmvax.UUCP (Andy Finkel) (09/07/89)
In article <1989Sep6.123302.9638@iesd.auc.dk> kasper@iesd.auc.dk (Kasper Osterbye) writes: >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? It's a bug. There is a subroutine in Workbench called GetAllMem() which the Workbench uses to get enough memory for the recursive copy. For 1.4 we will rename the routine to "GetJustEnoughMem()" which will solve the problem. And people say that routine names don't make a difference! :-) andy -- andy finkel {uunet|rutgers|amiga}!cbmvax!andy Commodore-Amiga, Inc. Life gets pretty complex the minute you stop mooing. Any expressed opinions are mine; but feel free to share. I disclaim all responsibilities, all shapes, all sizes, all colors.
erk@americ.UUCP (Erick Parsons) (09/07/89)
>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/ --------------------------------------------------------
efb@dvnspc1.Dev.Unisys.COM (Ed Bacon) (09/08/89)
E M E R G E N C Y ! ! ! I was testing a program that went beserk. It was in a loop and writing to disk. I had not put in a way to abort the program so I warm booted. Well it was writ- ing to my hard drive. Now when I try to Mount (using ARP Mount), the disk thrashes through some recovery process and the Amiga 'goes south' ... hello guru I tried to hide l:Disk-Validator, but every time Mount gurus. I just want to get rid of that trashed file. How oh how ??? do I get may partition back. Before you say it, I was at the end of my period of periodic backup. It has been a productive period ... I stand to loose a lot.
brianr@tekig5.PEN.TEK.COM (Brian Rhodefer) (09/09/89)
In article <7848@cbmvax.UUCP> andy@cbmvax.UUCP (Andy Finkel) writes: >In article <1989Sep6.123302.9638@iesd.auc.dk> kasper@iesd.auc.dk (Kasper Osterbye) writes: >>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? > >It's a bug. There is a subroutine in Workbench called GetAllMem() >which the Workbench uses to get enough memory for the recursive >copy. For 1.4 we will rename the routine to "GetJustEnoughMem()" which will >solve the problem. And people say that routine names don't make >a difference! :-) I wonder if this is related to a problem I've noticed with Workbench-driven disk copying: While demonstrating my Amiga A2000 to a friend (who later bought an A2500), the question came up, "How do you duplicate disks?" "Simple" I told her, "You can either use the keyboard-entry command, OR you can do it this really convenient mouse&icon way..." I then double-clicked the "DiskCopy" icon in my System drawer, and followed the resulting advice on how to perform the diskcopy: inserted original disk in drive, single-click-selected that disk's Workbench icon, and then selected the "Duplicate" Workbench menu item. A requester opened up, with a cheerful countdown of all the tracks from the original disk that were were being buffered up in memory. Since the foregoing had adequately demonstrated the proceedure, and I really didn't want another copy of that disk, I clicked on the requester's "Cancel" gadget. Kaboom! "This is what we Amiga users refer to as a 'visit from the Guru'", I explained. Brian Rhodefer