Path: utzoo!utgpu!water!watmath!clyde!att!pacbell!lll-tis!helios.ee.lbl.gov!pasteur!ucbvax!decwrl!hplabs!sdcrdcf!trwrb!scgvaxd!ashtate!dbase!awd From: awd@dbase.UUCP (Alastair Dallas) Newsgroups: comp.sys.mac.programmer Subject: Re: problems with resources larger than 32K? Summary: See Tech Note #63 Message-ID: <412@dbase.UUCP> Date: 10 Jul 88 00:01:57 GMT References: <2028@uhccux.uhcc.hawaii.edu> Organization: Ashton Tate Development Center Glendale Cal. Lines: 22 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/