🚀 go-pugleaf

So I just got my very own Mac II at home, huzzah!

I transferred several Lightspeed C projects from my Mac Plus
to the II, and tried to open them.  I invariably got the
bug box with the message "Memory critical - proceed at your
own risk". The project did not open, but the project file
was busy, and I'd have to reboot before I could access it
again.

Since I initially had only 1 Meg of RAM, the problem seemed
obvious. But after adding a second Meg, the results didn't
change.

In the end, what worked was to start LSC without a project,
create a new project, and load all the old project's files
and libraries by hand. The new project runs like a champ.
(Kudos for your MultiFinder support: turn-around time
is *trivial*!)

So I'm up and running, and this message isn't urgent. But
I'm curious: what went wrong? The old projects were on an
unmodified MacPlus and (non-SCSI) HD20, and were from
LSC 2.01. Uh, I forget which system/finder I was using;
something earlier than 4.2/6.0, no MultiFinder.
The new machine is a stock Mac II, 2 Meg RAM,
40 Meg internal disk, 256 color monitor, running LSC 2.15
(upgraded steadily from 2.01 via the net-published upgrade
kits). The bug manifested under both Finder and MultiFinder 6.0,
under both System 4.2 and 4.3.

My only connection with Think Technologies is as a *highly*
satisfied customer (in spite of the above). Although I am
posting from Apple's Vax, this is a private enquiry,
unconnected with my employment at Apple Computer.

==========================================================================
Rick Holzgrafe			 | {sun,voder,nsc,mtxinu,dual}!apple!rmh
Communications Software Engineer | AppleLink HOLZGRAFE1    rmh@apple.com
Apple Computer, Inc.		 | "All opinions expressed are mine, and
20525 Mariani Ave. MS: 27-Y	 | do not necessarily represent those of
Cupertino, CA 95014		 | my employer, Apple Computer Inc."