mikem@uhccux.uhcc.hawaii.edu (Mike Morton) (07/07/88)
An old Macintosh Technical Note (#54, dated late '85) describes problems
with resources larger than 32K bytes. Specifically, WriteResource didn't
work for certain sizes above that limit.
The current list of Notes says that #54 is "obsolete". Does anyone know
if this means the problem is fixed by some versions of the System file?
If so, which versions?
In general, are problems likely when attempting to create and use large
resources (say, 100K or more) ?
-- Mike Morton // P.O. Box 11378, Honolulu, HI 96828, (808) 456-8455 HST
Internet: msm@ceta.ics.hawaii.edu
(anagrams): Mr. Machine Tool; Ethical Mormon; Chosen Immortal; etc.olson@endor.harvard.edu (Eric K. Olson) (07/09/88)
In a recent article Mike Morton writes: >An old Macintosh Technical Note (#54, dated late '85) describes problems >with resources larger than 32K bytes. Specifically, WriteResource didn't >work for certain sizes above that limit. This was fixed in the 128K (Mac Plus) ROMs. -Eric Lexington Software Design: Tomorrow's Software Yesterday Eric K. Olson olson@endor.harvard.edu harvard!endor!olson D0760 (Name) (ArpaNet) (UseNet) (AppleLink)
awd@dbase.UUCP (Alastair Dallas) (07/10/88)
In article <2028@uhccux.uhcc.hawaii.edu>, mikem@uhccux.uhcc.hawaii.edu (Mike Morton) writes: > > An old Macintosh Technical Note (#54, dated late '85) describes problems > with resources larger than 32K bytes. Specifically, WriteResource didn't > work for certain sizes above that limit. > > The current list of Notes says that #54 is "obsolete". Does anyone know > if this means the problem is fixed by some versions of the System file? > If so, which versions? The old Tech Note was followed within a few months by Tech Note #63, which described the patch required to fix it. It also notes that the problem only occurs on 64K ROMs, and states that it does not exist on 128k ROMs. The size of each resource is stored in a long, suggesting a 2 billion-byte size limit. You should be aware of Tech Note #141, however, which mentions that a resource fork is effectively limited to 2,727 resources and that performance degrades significantly as the number of resources becomes "very large." This note doesn't say what happens to performance when the size of a particular resource gets "very large." /alastair/