Path: utzoo!attcan!uunet!know!sdd.hp.com!ucsd!wintermute!steve From: steve@wintermute.ucsd.edu ({Darkavich}) Newsgroups: comp.windows.ms Subject: Re: "Not enough memory to run" error Message-ID: <20960@ucsd.Edu> Date: 18 Oct 90 15:53:41 GMT References: <3506@ssc-bee.ssc-vax.UUCP> Sender: news@ucsd.Edu Organization: University of California, San Diego Lines: 12 Nntp-Posting-Host: wintermute.ucsd.edu In article mutchler@zule.EBay.Sun.COM (Dan Mutchler) writes: >Try making it "FILES=99". Windows appears to give "Not enough memory" >when it runs out of any system resource. I ran into this problem under >Windows 3.0 and changing the number of files seemed to fix it. One of the worst things you can do to a system is add files=99 to the enviroment. There is a big trade-off between memory and performance when you do this. I would suggest that you make buffers and files equal to 30. That is what windows expects to see. Steve Misrack steve@ucsd.edu