[Date Prev][Date Next][Thread Prev][Thread Next] [Search] [Date Index] [Thread Index]

Re: [MacPerl] 68k droplets, failed to launch ...



At 9:40 AM +0200 on 12/2/96, Axel Rose wrote:


}Hi Mac-Perlers!
}
}"Failed to launch MacPerl (possibly because of a memory problem)."
}still persists!
}
}
}>>Sorry - but rebuilding the desktop has no effect.
}>
}>Oops, sorry, failed to read the mail properly.
}>
}Never mind - it's a miracle anyway how you manage to answer
}all those messages and writing up your thesis at the same time.
}
}>>> - give MacPerl more memory,
}>
}>The "memory problem" message hints at the opposite: That the droplet
}>application takes up so much memory that there is not enough heap space
}>to launch MacPerl.
}
}Saving a file from MacPerl5[07|10r2] gives me a file
}Type=APPL, Create=MrPL, size 9k, memory - suggested: 64k
}minimum: 64k, preferred: 64k.
}MacPerl itself is APPL/McPL, all memory size settings 2048k.
}Playing around with memory settings doesn't change anything.
}
}"About this Macintosh ..." shows about 14.000k largest free memory
}block.
}Fragmentation seems unlikely because I tested immediately after
}a restart.
}
}It's a puzzle to me.
}And let me repeat it - the droplet will work if MacPerl is already
}running.
}
}Matthias: would it make sense if you give me a suitable break-point
}for MacsBug?
}
}
}>Weren't you the person who had droplets fail because you dropped lots
}>of files on them? The solution to that is to give the droplet more
}
}No - the not working droplet is a single line statement (unlink)
}but all other droplets fail to work as well.

Since we're grasping at straw here...

Last week, I don't remember exactly what day, Apple recommended that 68k
users swap the 68k version of the Code Fragment Manager (CFM68k) out and
not use it.  Now when I tried to use BigMacPerl after swapping out CFM68k
with Symbionts, I immediately got dumped into MacsBug with a unimplemented
trap the first time I launched a MacPerl droplet.  Which isn't a "failed to
launch", but we are grasping at straws...  I'm still running with CFM68k
installed because of this, and my scripts are running just fine under
BigMacPerl 5.10r2.

Your first message about this was last Thursday.  Is this something that
suddenly started last Thursday, and could it be due to someone removing
CFM68k from a machine where it once ran?

}
}
}Axel
}
}---
}Axel Rose              | In the novel I never wrote, I wanted the hero
}SPRINGER & JACOBY      | to be a computer programmer because it was the
}Werbung GmbH           | most poetic and romantic occupation I could
}rose@internet.sj.com   | think of... -- John Updike, "The Music School"
}

--------
Paul J. Schinder
NASA Goddard Space Flight Center
Code 693
Greenbelt, MD 20770
schinder@pjstoaster.pg.md.us