I have found that, when beaming from a 2100 to a 130, the 2100
needs all the heap you can muster. Resetting the 2100 before beaming
often works; in the worst case, do like the person says: reset the Newt
and prevent packages from activating. That'll save a bunch more heap.
Why the 2100 should be the unit under stress here, I don't know.
I'm guessing the comm process in the Newton OS needs bunches and bunches
of buffering to keep from overrunning the much slower 130.
The Griffith Observatory (no, not the one that does Zippy the
Pinhead) says there'll be a partial solar eclipse on Friday, Dec. 14.
It's only a small bite out of the lower part of the sun for about an
hour around 1:00 p.m. PST. However, Newton 130 owners take note: dust off
your 130s and retire your 2100s for a few moments on this day, and enjoy
the Easter Egg!
Mike O'Brien
-- This is the Newtontalk mailinglist - http://www.newtontalk.net To unsubscribe or manage: visit the above link or mailto:newtontalk-request_at_newtontalk.net?Subject=unsubscribe
This archive was generated by hypermail 2.1.2 : Wed Jan 02 2002 - 12:01:35 EST