FrameMaker crashing when I import images

[kmrountree]

Don't know if anyine can help me with this, but I'll give it a shot...

Lately FrameMaker 7.2 has been giving me a lot of problems when I try to
import images. It cannot handle images that are NOT reduced to 256
colors or images that are saved in .psp format (I take screenshots in
Paint Shop pro and save them as .png files, but sometimes I forget and
save them as .psp). If I try to import a file that is in .psp format
or is not reduced to 256 colors, Frame crashes on me. No warnings, no
error messages, it just closes. Even if I go back and remove the
offending file from whatever directory I saved it in, FrameMaker still
crashes when I click File>Import>File and try to open that directory.
It's as if the entire directory is corrupted from one file, even if
that file is removed. So I need to create a new directory in which to
save the images I create after that. This is very time-consuming and
frustrating. Any ideas on why this is happening and how I can fix
this?

[Art_Campbell1]

Because PaintShopPro format is proprietary and has likely changed over the years, I'm not too surprised that it crashes an old version of FM; it's entirely possible you're saving as a newer format than FM has filters for.

Also, some technical details would be helpful.... You OS, amount of RAM, FM 7.2 version, and so on. Particularly whether you're Importing the graphic files by reference (recommended) or Copying them into the frame document.

[kmrountree]

Thanks, Art. My system is Windows XP Professional (Version 2002, Service Pack 2), with 1.00 GB RAM. I'm using FrameMaker 7.2, version b144 (not sure what that means, sorry!) and always import graphic files by reference.

[Art_Campbell1]

Well, the version b144 means that you haven't applied the final patch for 7.2, released about five years ago. So to start off, I'd hit the update page and download and install that...

Beyond that, there isn't any reason that I know of that a bad graphic should corrupt a directory, but that's an operating system problem, I suspect. Unless, after a reboot, you can work in that directory again. If that was the case, I'd suspect that Frame is getting bogus signals from the OS...

Just a WAG, but it's possible your limited amount of RAM (1G is the minimum with which you can do serious work) is related to the 256-color problem... if there isn't enough RAM to support a higher level of bit import, it may be stalling at that point.

[kmrountree]

Thanks for the suggestions, Art. I installed the patch and FrameMaker still crashed. I also suspect this is an

OS problem and will see if the IT guys in me my officecan help me figure it out.

[Guest]

I am seeing the same problems. I seem to have enough RAM 1.95 GB. Where can I download this patch to which you refer? I've tried the updates in Framemaker but it doesn't seem to be downloading. I am using the same OS and Framemaker version as the kmrountree.

[kmrountree]

You can download the Windows patch at http://www.adobe.com/support/downloads/detail.jsp?ftpID=3332

Hope this helps.

[Guest]

Thank you. No, it doesn't seem to have solved the problem.

I've logged a ticket with IT here, they may be able to help.

[Art_Campbell1]

If you can't get your IT guys to move you to a new box and FM 10, y'all might at least want to see if they won't do the XP SP3... that fixed a lot of issues, I recall, but again, it's been so long released I don't remember the details.