🚀 go-pugleaf

Hello Violaine,
MIF2GO seems to be the best way, but Frame should still not crash when you export to RTF. You should note that the heavy CPU usage seems to be normal for the RTF output. It generally takes quite a few minutes to handle even a small document. During this time Frame "appears" to have died. It could be that you're simply not waiting long enough for FM to complete it's activity.

For example I was trying RTF export a few weeks ago and a fifty page document with only a few EPS graphics took more than 15 minutes on my machine. Admitted at 64MB RAM and Win 2000 Pro I was using a lot of disk swapping.

I have just tried a sample FM 5.5.6 file. It's twenty pages of tables with about 5 or 6 Object embedded Visio Graphics in it. It took more than 10 minutes - most of the time at 100% CPU usage. But I got an RTF in the end. Of course the graphics were useless but all the tables and text came through (sort of).

Maybe you just need to wait a little bit longer if your people really insist on RTFs.
Cheers
Ian