Copy link to clipboard
Copied
Im currently using FrameMaker 7.0 and im currently experiencing a issue when saving a imported graphic. A error message is displayed stating "An internal error occurred while imported graphics in this document. The file has been saved, but has lost some image data. Please report this error to Adobe Technical Support." Can anyone help with this issue, thanks.
Copy link to clipboard
Copied
FM7 on what platform (Windows, Unix, Mac)?
What graphics file format for the problem file?
Copy link to clipboard
Copied
This week I too have begun seeing this same error for the first time ever. I'm running FM12.0.2.389 on Win7-SP1. It seems to be triggered whenever I apply a Boolean expression to control the hide/show of conditional text. Oddly enough, all text using tags set in the expression as "NOT" to show is actually getting deleted from the FM file altogether. If I had not saved and reopened one of the "odd extension" files created when FM crashed, I would have permanently lost half the content of several critical files on the highest priority project at this client. DOH!! I can forward files privately to someone if you want to take a look. Maybe I should add this to the Bugbase...?
Rene
Copy link to clipboard
Copied
Yes, you probably should – there had been issues with crashes involving conditional text in prior versions, but I thought they had been solved in FM12
Copy link to clipboard
Copied
Jeff_Coatsworth wrote:
Yes, you probably should – there had been issues with crashes involving conditional text in prior versions, but I thought they had been solved in FM12
I reported it: Bug#3802835 - Applying Boolean build expression causes loss of data tagged with condition tags that ...
Copy link to clipboard
Copied
The platform im using is Windows 7 Professional and the file format is a .PDF
Copy link to clipboard
Copied
>> Im currently using FrameMaker 7.0 ...
> The platform im using is Windows 7 Professional
> and the file format is a .PDF
Two major observations about that:
Copy link to clipboard
Copied
Edition: 2016-05-09
I'm now doing real work in FM7.0p578 (as well as Acrobat 5.05, Photoshop 7 and Illustrator 10) in XP Mode (which is not the same thing as Compatibility Mode) on Windows 7 Professional, in 64-bit mode (on Win7; XP Mode itself is 32-bit). The apps work, but there are some further things to add to the above tips.
In daily use, the only thing that you need to be aware of is, on shut down of the virtual XP system, be sure to allow time for process vpc.exe to exit before shutting down the host machine. You can use Task Manager to watch that and develop a feel for how long it takes on your system.
General Editorial:
The number of old but still useful apps I have, that refused to install native in Win7 (or wouldn't run if they did) was surprising. I would expect most DOS and Win/16 apps to not install/work, because the x86-64 ISA simply doesn't support 16-bit x86 modes, but no-joy on legacy Win/32 stuff is not going to work out well for Mr.Bill, esp. since the XP Mode dodge is officially a one-time Win7 thing. MS is telling us "yep, we've cut off your past, and there is no future", plus it looks like Win10 might be "free" with growing intrusion, and perhaps a surprise subscription later (i.e., time-bombed unless you pay a periodic Redmond tribute - yes, I know they are currently talking about free-forever, but it's hard to see how that's going to be sustainable). Even if I upgrade to the latest Adobe suites, they are themselves annoyingly subscription in key cases. I resent having my work output held for ransom with time bombs. I'll be bringing up some flavor of Linux on the old machine, and exploring what's available there and in open source apps for Win7 - already found a nice alternative to the HomeSite5 that Adobe abandoned and Win7 refused to install (but which does still work in XPM).