Hopefully this is not RTFM, but I haven't found reference to it yet... For our users we build MacPerl runtime versions of some scripts. MacPerl 5.2.0r4 had no problem running those Runtimes under Classic on MacOS X. Runtimes built under 5.6.1r1 launch the interpreter but do not start the script stored in the "!" TEXT resource. Those same runtimes operate just fine when the machine is booted to MacOS 9 from the same System Folder used for Classic.
Here's what I've found so far: - Not all MacOS 10.1.3 machines exhibit the behavior (my personal machine works fine) - The script content/libraries needed has no effect. Hello World fails, for example. - MacsBugs breaks in Get1NamedResource show that the runtime is the current res file, and that the resource is loaded. - The machines in question have no other verion of MacPerl, no prior MacPerl preferences, etc. Before I launch into a debug build of MacPerl (or a massive rollback of our runtime applications) has anyone encountered this problem before? If not, any tips where to start looking in the code? Thanks, Alex -- Alex Harper [EMAIL PROTECTED] Configuration Manager [EMAIL PROTECTED] "Use whatever you think of first" -- Larry Wall
