jms@tardis.tymnet.com (Joe Smith) (06/29/90)
In article <9149@brazos.Rice.edu> gld@cunixd.cc.columbia.edu (Gary L Dare) writes: >We're running Framemaker 2.0 on a Sun Sparcstation 1, and we tried to open >an older file made on Frame 1.1 -- in doing so, we get the message: > 1.3binarytomif: Out of Memory! Last time we had an "out of memory" problem, I made it go away by increasing the size of the swap partion, from 16M to 32M. The other time we had a problem, the file was corrupted. Could be that framemaker was trying to allocate a humongous hunk of memory based on bogus data. Joe Smith (408)922-6220 | SMTP: jms@tardis.tymnet.com or jms@gemini.tymnet.com BT Tymnet Tech Services | UUCP: ...!{ames,pyramid}!oliveb!tymix!tardis!jms PO Box 49019, MS-C41 | BIX: smithjoe | 12 PDP-10s still running! "POPJ P," San Jose, CA 95161-9019 | humorous dislaimer: "My Amiga speaks for me."
girish@heawk1.gsfc.nasa.gov (Girish ) (07/06/90)
Increasing swap should certainly be tried. See how much swap is being used by using the command pstat -s before and after running the Frememaker. If possible, run multiple copies of Framemaker, and see swap usage. Also something else may be grabbing the swap space, so check pstat -s as soon as you get the error of " not enough memory " and see what processes are running using the ps -aux command. Good luck girish kumthekar girish@heasfs.gsfc.nasa.gov