🚀 go-pugleaf

In article <AAFC138D96683AA1@vader.demon.co.uk>, chris@vader.demon.co.uk
(Chris Dabrowski) wrote:

> I recently downloaded the MacTCP 2.0.6 upgrader (from seeding.apple.com),
> but it absolutely refuses to work on my copy of MacTCP 2.0.4. The error
> message it comes up with is:
> 
> >An unrecoverable error occurred while verifying resource DRVR 22 (".ipp")
> >in the file MacTCP on System.
> >This resource needs to be patched, but its attributes aren't what was
> >expected. Please make sure that you are patching the correct file and
> >version.
> 
> I'm using a totally unmodified, ordinary version of MacTCP 2.0.4. I have 
> also tried upgrading a freshly installed copy of MacTCP and even one 
> which hasn't been booted (ie. was left out of the extensions folder).
> 
> I obtained my copy of MacTCP on a coverdisk of a UK magazine (MacFormat),
> perhaps they distributed a modified version. If so, how can upgrade?
> Can I copy the resources from the upgrader and paste them into MacTCP
> using ResEdit, or is this too risky?
> 
> Any help would be greatly appreciated.
> 
> 
> PS. I'm running system 7.0.1 (Tuneup 1.1.1) on a LC II.
> 
> 
> --
> Chris Dabrowski  -  <chris@vader.demon.co.uk>  -   Ealing, London, UK

The same thing happened to me. You can fix the problem by opening your
copy of 2.0.4 with Resorcerer or ResEdit, and clearing the system heap bit
in the .ipp DRVR resource (ID# 22), before updating 2.0.4 to 2.0.6.

I don't know how the system bit got set on this particular resource, as I
am pretty sure I started with the MacTCP I got with Adam's InterNet book,
and used the standard updaters to get to 2.0.4. I checked a couple of
copies of 2.0.4 that I have floating around, and they all had the system
heap bit set too. One does want the driver to reside in the system heap,
which it appears to do whether the system heap bit is set or not...

In any case, clearing the system heap bit from the .ipp driver resource
allows the updater to do its thing, and the resulting 2.0.6 has been
working fine on all my machines. I took a quick look at the INIT code in
2.0.6, and it messes with the resource attributes of the .ipp driver
before it loads it. (It sets bit 6, but I was too lazy to check if that's
the system heap bit or one of the other resource attribute bits).

Bill S