CompuServe Messages

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