Going over the list, I noticed that Scott Weaver <sweaver@bluenova.com> reported a problem with saving runtimes with MacPerl5. If he or anyone else is still running into similar problems, here is some information that may be useful: If you are using 68K-only MacPerl5, you probably aren't having problems. If you are using PowerPC-only MacPerl5, you may have runtime applications that are real small and don't load. You can try copying the contents of the data fork from the MacPerl app to your runtime application and see what happens. This worked for me with a simple hello world runtime. If you are using Fat MacPerl5, you may have runtime applications that are oh-so-close to working, but don't. You can do one of two things: copy the data fork as suggested for PowerPC-only runtimes above, in which case you will have a fat runtime. Or, you can delete the cfrg resource, in which case you should have a working 68K runtime. All of this is the result of some very brief testing, and I would appreciate confirmation from anyone who really knows what's going on. In summary, it would be nice if a future version insured that when saving a runtime, the cfrg resource and the PEF in the data fork went hand-in-hand: either have them both or neither at all. Would it be difficult to have packages for 68K-only, PPC-only and Fat runtimes? (limited of course by what MacPerl application is running) -- Robert Coie Implementor, Intrigue Corporation rac@intrigue.com