Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!wuarchive!uwm.edu!uwvax!puff!rt7.cs.wisc.edu!blochowi
From: blochowi@rt7.cs.wisc.edu (Jason Blochowiak)
Newsgroups: comp.sys.apple
Subject: Re: IIgs Software Reboot
Message-ID: <4118@puff.cs.wisc.edu>
Date: 19 Dec 89 07:33:01 GMT
References: <3388@sage.cc.purdue.edu> <0ZWjDCW00WAB00WG8F@andrew.cmu.edu>
Sender: news@puff.cs.wisc.edu
Reply-To: blochowi@rt7.cs.wisc.edu (Jason Blochowiak)
Organization: U of Wisconsin CS Dept
Lines: 21

In article <0ZWjDCW00WAB00WG8F@andrew.cmu.edu> bh1e+@ANDREW.CMU.EDU (Brendan Gallagher Hoar) writes:
>just a word of warning: Apple changed the boot block on system 5.0 to allow
>the loading of sparse PRODOS files.
[Mentions concern about SmartBoot 8/16 causing problems]
>If someone could explore the problems and possibilities of adding the
>new boot block code to Smartboot 8/16, I'd appreciate it!

	First off, SmartBoot 8/16 is just a boot block - something of a
technicality. I've had SB installed for quite awhile now (I think since
System Software 4.0), and I've yet to have any problems with it, up to
System 5.0.2. As someone else pointed out, it would seem strange to have a
sparse ProDOS file, but apparently somebody out there did.

	As for looking into it - I don't think it'd be all that difficult to
disassemble Apple's new boot code just to see what it does differently, and
then add that to SB 8/16, but as far as distributing it, I dunno. I suppose
that I could manually generate a psuedo-diff file (what lines to delete, what
to add), but that'd probably be a pain. Anyone have other suggestions?
--
      Jason Blochowiak - blochowi@garfield.cs.wisc.edu or jason@madnix.uucp
       "Education, like neurosis, begins at home." - Milton R. Sapirstein