Xref: utzoo comp.sys.mac.programmer:1354 comp.sys.mac:17397 Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!husc6!bbn!uwmcsd1!ig!agate!ucbvax!decwrl!nsc!voder!apple!dan From: dan@Apple.COM (Dan Allen) Newsgroups: comp.sys.mac.programmer,comp.sys.mac Subject: Re: system 6.0 upgrade problem Keywords: system 6.0 upgrade boot cms Message-ID: <12596@apple.Apple.COM> Date: 21 Jun 88 17:47:49 GMT References: <912@parcvax.Xerox.COM> <12376@apple.Apple.COM> <2420@cxsea.UUCP> <914@parcvax.Xerox.COM> <614@osupyr.mast.ohio-state.edu> Reply-To: dan@apple.apple.com.UUCP (Dan Allen) Organization: Apple Computer Inc, Cupertino, CA Lines: 21 In article <614@osupyr.mast.ohio-state.edu> gae@osupyr.mast.ohio-state.edu.UUCP (Gerald Edgar) writes: > >I have a CMS 80meg drive, and a Mac Plus. I don't have the 6.0 release, yet. >This exact problem (reaching the "Welcome to Macintosh" screen, then hanging) >happened to me when I first got the drive. It seems that using both >Macsbug and StartUpScreen was a problem. CMS said merely "There is a bug >in the original MacPlus ROMs". Once upon a time, a long time ago, there was a conflict between a now very old version of MacsBug and the StartUpScreen INIT that keeps the StartupScreen around all the time. Any version of MacsBug since 5.3 should work fine, and no, there is not a bug that I am aware of in the Mac Plus ROMs that is related to this issue. Ideally you should be using MacsBug 5.5, which works on the Mac Plus, Mac SE, and Mac II, and with any RAM size from 512K to 4 MB (8 MB on a Mac II). Dan Allen Software Explorer Apple Computer