If the WinHelp you create is used on Windows 9x or Windows ME systems, WMF graphics can eat up all GDI resources with amazing speed. An operating-system defect causes a GDI resource leak, which can crash the system when a user pages through a WinHelp file that contains WMF graphics.
The GDI resource leak happens with all WMF graphics, regardless of source. This can rule out WMF as a graphics format if you have clients using Windows 9x or Windows ME. The problem does not occur on Windows NT, Windows 2000, or Windows XP; nor does it occur with formats other than WMF.
If you have FrameMaker graphics that include just a single bitmap and no other elements, you can get around the problem by mapping any non-BMP formats to BMP (see §29.3.2 ). Do not direct Mif2Go to wrap BMP graphics in WMF (see §29.2.6 ); that is, make sure [Graphics]EmbedBMPsInWMFs=No.
1. In a first conversion pass, allow Mif2Go to create WMF files from the graphics in your FrameMaker document; see §220.127.116.11 .
2. Create matching BMP files with an external program that can import the WMF files; see §18.104.22.168 .
3. In a second conversion pass, set [Graphics]NameWMFsAsBMPs=Yes to make the RTF output refer to the BMP files instead of to the WMF files; see §22.214.171.124 .
- Direct Mif2Go to use FrameMaker export filters to make BMP graphics instead of WMF graphics; see §126.96.36.199 .