syap@ur-tut (James Fitzwilliam) (06/30/88)
I recently downloaded the System Tools 6.0 release from GEnie. There were
no problems transferring the files (in fact, all 2290 blocks of the System
were sent with no retransmissions!)
I moved the System and Finder to a blank floppy, placed them into a System
Folder, then added the "entourage" -- General, Keyboard, Mouse, etc. etc.
This disk will not boot. The happy face appears, the startup screen says
"Welcome to Macintosh," then a dialog with a System icon appears saying
"Can't load needed resource" with a Restart button. However, cmd-opt-
doubleclicking on the Finder works just fine.
It seems that something is missing from the System or the System Folder,
but I can't determine what. And yes, I did try with another disk.
I'm running a Mac Plus with the usual bells and whistles.
This is extremely mystifying and not a little embarrassing ("Hey Joe -
get a load of this guy who can't make a startup disk!") so any suggestions
are greatly appreciated.
James
domain: syap@tut.cc.rochester.edu
path: rochester!ur-tut!syap "Piano is my forte" (-:
GEnie: FITZWILLIAM
========================================================================6029334@pucc.Princeton.EDU (Robert G. Trevor) (06/30/88)
In article <2232@ur-tut.UUCP>, syap@ur-tut (James Fitzwilliam) writes: >I recently downloaded the System Tools 6.0 release from GEnie. There were (stuff deleted) >This disk will not boot. The happy face appears, the startup screen says >"Welcome to Macintosh," then a dialog with a System icon appears saying >"Can't load needed resource" with a Restart button. However, cmd-opt- >doubleclicking on the Finder works just fine. > >It seems that something is missing from the System or the System Folder, >but I can't determine what. And yes, I did try with another disk. You need the *new* boot blocks. There are two easy ways to do this: use the Installer and associated scripts which are part of Sys 6.0 release; or drag System/Finder as you did, but *only* after booting with the new System. The first is probably easiest, unless you don't have a hard drive or a second drive - then you will probably get a lot of wrist exercise :-) Rob Trevor MaBell: (609) 452-4051 Bitnet: 6029334@PUCC UseNet: 6029334@PUCC.Princeton.Edu
lsr@Apple.COM (Larry Rosenstein) (07/01/88)
In article <5555@pucc.Princeton.EDU> 6029334@pucc.Princeton.EDU writes: >In article <2232@ur-tut.UUCP>, syap@ur-tut (James Fitzwilliam) writes: > >>I recently downloaded the System Tools 6.0 release from GEnie. There were >(stuff deleted) >>This disk will not boot. The happy face appears, the startup screen says >>"Welcome to Macintosh," then a dialog with a System icon appears saying >>"Can't load needed resource" with a Restart button. However, cmd-opt- >>doubleclicking on the Finder works just fine. > >You need the *new* boot blocks. There are two easy ways to do this: I don't think this is the problem. According to Tech Note #134, a happy Mac means that valid boot blocks were found. If you get to "Welcome to Macintosh", then the System file must have been opened, since that string comes from there. My guess would be that one of the patches could not be found. Open the System file and look at the PTCH and ptch resources. There should be 5 PTCH resources (-1, 0, 117, 376, and 630), and 4 ptch resources (0, 1, 2, 3). If those are in place, then try adding a debugger and see where it crashes. The error message is put up by the System Error Handler (the SysError trap). Set a trap breakpoint on SysError. Also, SysError saves the return address in a global variable, so you can go back after the error and see what code failed. (To find the global variable, disassemble the SysError trap and look at the code. You have to do this without MultiFinder running, because MultiFinder patches SysError.) The only complication in this detective work is that if the crash is too early, the keyboard driver might not be loaded, and you won't be able to use a debugger. If you were using Macsbug, however, it should be possible to customize things to execute a few commands when entering the debugger, and reveal what went wrong. Larry Rosenstein, Object Specialist Apple Computer, Inc. 20525 Mariani Ave, MS 27-AJ Cupertino, CA 95014 AppleLink:Rosenstein1 domain:lsr@Apple.COM UUCP:{sun,voder,nsc,decwrl}!apple!lsr
ir10@sdcc6.ucsd.EDU (Donald R. Fredkin) (07/01/88)
I discovered more or less by accident that the installer increases the
size of the system heap to 80K above the old standard. If you change it
back to the old standard value or 16K above and reboot, you get exactly
the error message described.
I modify the system heap size with a program called widgets that came with
disktop. You could also do it with Fedit+ or the equivalent.
UUCP {ihnp4,decvax!ucbvax,dcdwest,ucbvax}!ucsd.edu!drfredkin
Internet drfredkin@ucsd.edu or drf%sdph2@ucsd.edu
Bitnet drfredkin@ucsd
--
UUCP {ihnp4,decvax!ucbvax,dcdwest,ucbvax}!ucsd.edu!drfredkin
Internet drfredkin@ucsd.edu or drf%sdph2@ucsd.edu
Bitnet drfredkin@ucsd