FXDDR@ALASKA.BITNET (03/20/87)
I made up a demo file for Publishing Partner, incorporating graphics, Helvetica, and Times-Roman fonts at various sizes, saved it on disk and went on to other things. This morning I booted from my Uniterm disk, which sets up a 400K eternal ramdisk and loads Antic's Crystal desk accessory. I cranked up Pub Partner to convert my demo to PostScript on the ramdisk so I could upload it for printing. When the demo loaded, yuk! The Times-Roman was now Martian-Hieroglyphics. I checked the font menu and in place of Times-Roman was more Martian. Hmmm. After some fooling around I found that when I rebooted with a 320K ramdisk and no desk accessories, I had Times-Roman again. So it looks like when memory gets tight, the last font in the table gets grunged. However, with the 400K ramdisk and Crystal, Pub Partner's "Don't Look..." box showed free program space of about 200K and free system space of about 7K. No sign that it is worried about lack of RAM. With the smaller ramdisk and no DAs free program space is about 300K and free system space is still about 7K. The question is this: why does the font get trashed? Pub Partner doesn't seem to be upset about the amount of ram, and its display shows no shortage. Is there some sort of interaction between Pub Partner and Crystal? Or does the ramdisk mess up Pub Partner's memory allocation? My main concern is that there doesn't appear to be a way to tell when you've stepped over this line...things just start getting trashed. Any ideas? For now I will do my composing with no DAs and no ramdisk just to be safe. Don Rice University of Alaska, Fairbanks BITNET%"FXDDR@ALASKA" CIS 72337,3417 // KL7JIQ