CompuServe Thread

#HEAPMGMT error?

6 messages in this thread
#33859From: Randy MaxeyFeb 20, 1992 4:37 PM
Yo, David, I've run into this three or four times in the last few days. Kicks me clear out to DOS… HEAPMGMT-heap error #4 Cheap stack dump linked in => no dump Aborting…set? Ever see this? Granted I've only got 2megs RAM on this machine, but everything was fine before. Could it be some AutoLISP routines I've been working on that were loaded at the time? Just when you think you've got a handle on things… –Randy
#33884From: Tony Tanzillo [LISP TM]Feb 20, 1992 6:39 PM
Randy – Did you happen to notice anything atypical about each case when this happened (e.g., one or a sequence of commands)? -TonyT.
#33945From: Randy MaxeyFeb 21, 1992 7:36 AM
Tony, I didn't really notice any set series of commands until the last two times it happened yesterday. These last two times it happened when I tried to access the "Modify" pulldown on the standard AutoCAD menu. I tried to repeat it, but couldn't get it to bomb. Weird. I'm using DR DOS with 4DOS (the latter after hearing your great recommendations for it, BTW). I'm using SuperStore disk compression. This particular system is an *old* ACER 1100 386-20 with 2-megs RAM, an ACER multisync monitor and an ATI VGA Wonder graphics card with 512K. The BIOS on this system is an Award BIOS ver 3.02 or something like that. IDE Controller card with integrated serial/parallel ports. 80mb Maxtor hard drive. 1.44 and 1.2mb floppies. I'm using a Calcomp 12×12 Drawing Board digitizer with their real-mode driver. The ATI Card is using ATI's protected-mode driver. Simple setup–nothing fancy. All memory configured for extended RAM. About 530K base RAM is free right after boot-up. Now, the LISP routines I had been working on load at startup and update a plotting revision block (sorta' plot stamping) and keep track of drawing time within the editor. They seem to work okay, and I don't normally bomb out during execution of these routines. I do tend to use very long variable names and I know this uses up node space, but I hadn't noticed any problems. I usually Kelvinate and Protect my final versions, anyway. I'm a not-too-technical kind of person and I've got a lot to learn about all these memory issues with swap files, paging, extended DOS, Expanded vs. Extended RAM, etc., etc. I'm working on getting two more megs of RAM, but my drawing is either a new one or less than 23k when ACAD bombs. Oughta' work! –Randy
#33958From: Tony Tanzillo [LISP TM]Feb 21, 1992 8:41 AM
Randy – You say that it happens when you try to pull-down a menu? Hmmmm. It could be the ATI display driver. If you have access to another protected-mode driver, I'd suggest swapping that out first. -TonyT.
#33961From: Mike Tajmajer [Haestad]Feb 21, 1992 8:52 AM
What your seeing is the metaware c-Heap in action… One fix would to be getting adesk to re-compile with watcom :)!! MIke
#33938From: Dave Byrnes [AEC TM]Feb 21, 1992 3:44 AM
Randy – well, that's what you get when you try to save a few bucks with a *cheap* stack dump! Buy a better one next time!! Duhhh… sorry; I've never seen that one before. Dave