Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!udel!haven!umd5!bchin From: bchin@umd5.umd.edu (Bill Chin) Newsgroups: comp.os.msdos.apps Subject: Re: frustration with memory problems (LONG) Message-ID: <8430@umd5.umd.edu> Date: 14 Apr 91 23:32:32 GMT References: <31945@usc> Reply-To: bchin@umd5.umd.edu (Bill Chin) Organization: University of Maryland, College Park Lines: 83 In article <31945@usc> logan@neuro.usc.edu (Christy Logan) writes: >[some parts of the description removed] >Sigmaplot seems to think there is 115K of memory available. >Another program I run, CSS (a statistical package) runs all right >but thinks there is 365K of memory available. Why the difference? >But more importantly, why can't Sigmaplot find/use the memory? >What good is 4M if my programs can't use it? Well, you're caught with the difference between extended and conventional memory. First off, SigmaPlot 4.0 (that's the version I had to deal with) likes lots of conventional memory... the stuff below 640k. The amount of memory available is shown with the "mem" command under DOS 4.0x. The amount returned by CSS and SigmaPlot is the amount left after the respective programs have loaded, ie. this is data space left. SigmaPlot likes to have ~540k of conventional memory free before it loads. A 100kb of expanded memory helps too. > When I called the computer's manufacturer (ARC) with this problem, >they suggested buying QEMM, and said that the problem was with the >way Windows set up memory. Besides the fact that I feel cheated >that I have to go out and spend more money just to get my fancy >new machine to do what my crummy old machine could do, I am >also concerned about trying QEMM because there are so many >problems with using it posted here. So what's the verdict on >QEMM? I can't tell if the problems result when people want >to do more sophisticated things than I'd be likely to want. The problem isn't really Windows... It's using DOS programs that hog conventional memory. For example, a Windows program on your system can use many megabytes of memory, or a DOS program that knows how to use XMS memory can do the same. So until SigmaPlot 5.0 that either runs as a Windows app or uses DOS resources better, here are a couple of solutions. - QEMM/386-to-the-Max/Netroom etc. are programs that take advantage of your 386 and can give you more conventional memory through some memory management tricks. Typically $75 bucks, if you run lots of memory intensive DOS apps that insist on conventional memory or have big network drivers, its money well spent. Most have good installation scripts that make its installation rather painless. - Clean out your CONFIG.SYS and AUTOEXEC.BAT of stray drivers and TSR's that you don't need. Your files should be 30, and if you are running a disk cache (SMARTDRIVE) your buffers can be put down to 10. See if this gives you the ~540k needed for SigmaPlot. - If you are close to having the ~540k needed, you can run SigmaPlot from under Windows and have Windows give SigmaPlot a couple hundred kb of Expanded memory. Read creating a PIF file. > All in all, I am extremely frustrated, to the point that >I am considering returning my computer (still in its 30 >day free return period) and buying a Mac. I've never used >one, but everyone who owns one seems to love them, something >that I haven't found among IBM users. Certainly it would be >preferrable to get my 386sx to work, but I hate the idea of just >patching things together and settling for a way of getting it >to limp along. Isn't there a way to make it *really*work*? >Is Windows 3.0 inherently flawed? If you bought a Windows app, lets say PowerPoint, then installation and use is really easy. Just point and click, pop in the diskettes, and you can do things that the Mac can't do and for much less. Windows 3.0 is great for running Windows apps. It's only fair at running most DOS apps. But its fundamental flaw is that it runs on DOS. OS/2 is definitely the way to go in the upcoming years. I wish MS will stop looking at this week's ledger and plan for the future. As for going to a Mac, then you're opening another whole can of worms. They have their own problems and wierd stuff. (as a former consultant, I *know* :-) ) BTW, after working with Macintoshes, PS/2's and clones, Vaxen, etc, I *personally* would love to own/work on/play with a NeXT. But I also love my trusty 386 clone, and would *not* trade it for a Mac. -- Bill Chin internet:bchin@umd5.umd.edu MS-Windows Programmer NeXTmail:bchin@is-next.umd.edu PCIP, Computer Science Center CompuServe:74130,2714 University of Maryland, College Park *Standard Disclaimers Apply*