If it's the Linguistics issue that keeps recurring, then it's possible that there may be hardware issues on that platform, i.e. disk write caching isn't working properly - getting flushed before operations complete, or bad tracks/sectors on the disk or some other gremlins.
Having multiple versions installed concurrently isn't an issue for FM (I have all versions going back to 6.0 on one machine). However, I'm kind of wondering if concurrently running more recent versions, like FM9 & FM10, might also be contributory factor. AFAIK, there's only one Linguistics folder for each user that gets setup, so if both apps are vying for the same files, there may be collisions and possibly corruptions taking place. Any specific reason why both versions need to be open at the same time?
Thanks for the info Arnis. I think for now I'll inform the user to try using only one FrameMaker software at a single time to see if it helps. As far as I know, the reason why she uses both currently because of compatibility issues between the two versions and working in both version concurrently would be more efficient.
I have Frame 9 patched fully, patch 4, in Windows 7 Ultimate running in VMmare Fusion fully updated. I get this error every time I start Frame.
I have the same Frame version and updates running in the same Windows Ultimate running on Parallels Desktop 9, fully updated and it runs fine, no issues at all.
I have removed Frame in VMware several times. completely, with YourUninstaller which cleans all files, folders, and registry entries to no avail. I have deleted and/or renamed the Linguistics folder several times. Changed the maker.ini "sitedictionary=" entry to no avail, (I saw this in another post on another discussion site", didn't work... A side note, Frame 12 runs fine on the VMware machine...
I am at a loss other than Frame 9 and VMware Fusion are not compatible for some crazy reason. Any ideas?
I really don't know about this type of configuration, other than a number of reports of greater instability of FM under a virtual machine on Macs.
If FM12 is running fine in that configuration, then why use FM9? It was the first (worst) implementation with the OWL interface and most of the bugs/glitches have been cleaned up by the time FM12 rolled around.
From FM12 you can always save as MIF, which FM9 can read (it will just ignore any newer features, such as Object Styles). If you get Cudspan's SafetyMIF utility, it will always save a MIF file along with the FM binary. See: Cud Project: CudSpan Plug-ins Page
When you launch FM9 in your VM environment, watch the Splash screen. It numerates the major modules as they load. Noting at which one (if it's consistent) FM crashes may provide some additional clues as to which direction to proceed. Also, if you have any third-party plug-ins loaded, you might want to comment these out of your maker.ini and/or remove them from the fminit\plugins folder(s).