Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!elroy.jpl.nasa.gov!swrinde!mips!samsung!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!zardoz.eng.ohio-state.edu!agvax2.ag.ohio-state.edu!GAYNOR From: gaynor@agvax2.ag.ohio-state.edu Newsgroups: comp.sys.mac.system Subject: Re: System 7.0: Problem with VM on SE/30 Message-ID: <1991May16.120708.2944@zardoz.eng.ohio-state.edu> Date: 16 May 91 12:07:08 GMT References: <1991May15.150525.29796@zardoz.eng.ohio-state.edu> Sender: news@zardoz.eng.ohio-state.edu (Usenet news) Reply-To: gaynor@agvax2.ag.ohio-state.edu Organization: Ohio Cooperative Extension Service Lines: 58 Nntp-Posting-Host: agvax2.ag.ohio-state.edu In article <1991May15.150525.29796@zardoz.eng.ohio-state.edu>, gaynor@agvax2.ag.ohio-state.edu writes: >%Synopsis of problem: > >SE/30 with release version of 7.0 bombs with "Not enough memory is >available..." error when booting with Virtual Memory enabled. This >only occurs after the Mac has been Shut Down from the Special Menu. Okay, it's fixed. While I don't know what the problem was, I went ahead and erased that particular install of System 7.0 from my HD. Then I re-installed, but rather than doing the Custom Install I had done before, I let Installer do the "Easy Install", which consisted of "System Software for all Macs", "All Printer Drivers", and "File Sharing." After that install, everything worked fine. The Custom Install I had done earlier was: "System Software for Mac SE/30" "StyleWriter" "LaserWriter" "ImageWriter" So, to hypothesize, the problem was either just a "bad install" with some resources getting corrupted during the installation, or there is an error somewhere in the Install Script(s) that I used for my Custom Install - an error that isn't present in the scripts used by the "Easy Install". Various Suggestions Received: - Update the HD driver from HD SC Setup (had already done so) - Check the HD with Disk First Aid (had done so, no errors) - Rebuild your desktop (done frequently) - The VM file may be corrupted (I turned off VM and deleted the VM file twice. No effect) - Your HD may be highly fragmented - defrag it. (Norton said it was "moderately fragmented". Defragged anyway. Error still occured.) * Reinstall System 7.0 (This is what I did, using Easy Install rather than a Custom Install) - Reformat your HD (Didn't have to go that far, thank the powers.) Thanks to all the people who helped, especially Bill Coderre, Philip Machanick, and Gail at the Apple Upgrade Line. For those who have been worrying, the people (well, at least Gail) at the Upgrade Line were courteous, knowledgeable, and helpful. I was very impressed, and Gail wasn't afraid to say "I don't know, I'll have to research that and call you back." And she did, with just about every suggestion that I listed above. %Case Closed --- Jim Gaynor - AgVAX System Manager - Academic Computing - Ohio State University VMS: UNIX: Disclaimer : All opinions expressed here are mine and only mine. So there! Witty Quote: "Think, think, think, think..." - Winnie-the-Pooh, Taoist Bear.