Xref: utzoo comp.sys.mac.programmer:1714 comp.sys.mac:18520 Path: utzoo!utgpu!water!watmath!clyde!bellcore!decvax!mandrill!gatech!rutgers!mailrus!utah-gr!utah-cs!cs.utexas.edu!utastro!werner From: werner@utastro.UUCP (Werner Uhrig) Newsgroups: comp.sys.mac.programmer,comp.sys.mac Subject: weird problem booting OS Release 6.0 from Peak-80+ ..... Keywords: worried ... Message-ID: <2933@utastro.UUCP> Date: 24 Jul 88 10:44:16 GMT Organization: U. Texas, Astronomy, Austin, TX Lines: 53 I run the following configuration: Mac+ with 2.5Meg (generic), Peak-80+ with OS-6.0, a bunch of INITs, etc ... but I don't think I ever get that far when .....: The latest horror-story in my "Sundays with my Macintosh": After I Shutdown and power-down and get some sleep, I will get up after my usual nightmares featuring prominently my Macintosh, mingling with the various candidates for political office.... ...and I will power up my home-computer center, only to be greeted by a SadMac with code 020020 .... (it's been happening ever since 6.0) the Mac-screen does not even show the expected delay of the memory-test performed by the ROM-code at cold-boot. but, get this, when I boot from my OS-6.0-boot floppy I have prepared for such emergencies, Minny, after the appropriate blank screen and delays taken up by the ROM-originating RAM-memory-test, shows a "smiley" and gives me a DeskTop with Peak mounted, thank you kindly. it gets stranger: I Shutdown, the floppy gets ejected, and reboot from the Peak-80+ works just fine (without the delay for the ROM-memory test, of course); Another ShutDown, and power-off of Peak and Mac to force the ROM-memory test ..... works just fine, even after a Power-off of several minutes ... Now, rumour has it, that the voltage which maintains the PRAM-values in RAM somewhere takes between 5 and 10 minutes to dissipate enough for the values to be lost; after which the battery maintained PRAM-values are needed at BOOT-time... Could it be that I am looking at a bug in OS-6.0 or is there an explanation for this difference in behavior between booting from floppy and booting from Hard Disk centering around a "too old" battery, or, possibly, something wrong in the software or hardware of the Peak ... the problem worries me more than it, actually, irritates me .... Anyone with a good answer is urgently requested to post a follow-up; anyone who just likes to speculate and kick around this topic is invited to send me E-mail .... PS: yes, voltage is adjusted to 5.0V; no, OS was not "installed", but OS-5.0 was removed from Peak before OS-6.0 was copied onto the Peak (BTW, I am under the impression that the BOOT-block version-number was not updated by this process and I went in with FEdit+ and changed it "the hard way") -- -------------------->PREFERED-RETURN-ADDRESS-FOLLOWS<--------------------- (INTERNET) werner%rascal.ics.utexas.edu@cs.utexas.edu (DIRECT) werner@rascal.ics.utexas.edu (Internet: 128.83.144.1) (UUCP) ...{backbone-sites}!cs.utexas.edu!rascal.ics.utexas.edu!werner