<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#336666">
<div class="moz-cite-prefix"><font face="Verdana">Wow .. Alan ..
that's a good one. If this was April 1, I'd think you were
joking.<br>
<br>
I can't imagine what would affect both FM11 and FM12
simultaneously. FM10 is OK? Are these part of a Tech Com Suite
or standalone programs? To me that indicates that the problem
lies in some shared resource of some kind. I know there is some
sharing of resources .. but have no idea what they are. I assume
you've rebooted the VM?<br>
<br>
Maybe Creative Cloud has gone haywire (naw), and attacked some
FM resources?<br>
<br>
I have a feeling that you'll need to push this to Adobe ..
someone on the FM dev team might have some ideas.<br>
<br>
I hate to say it but you may need to reinstall.<br>
<br>
...scott<br>
</font>
<pre class="moz-signature" cols="72">
</pre>
On 6/19/14 8:25 AM, Alan Houser wrote:<br>
</div>
<blockquote cite="mid:53A300F9.10805@groupwellesley.com" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
Hi All,<br>
<br>
Windows 7 running on MacOS/Parallels; FM 11 and 12 fully patched.<br>
<br>
I'm getting immediate failure of structured Framemaker 11 and 12
on startup. ("Internal Error ... FrameMaker has detected a serious
problem and must quit").<br>
<br>
The apps start fine in unstructured mode.<br>
<br>
I've tried:<br>
- Removing the user-specific ini files
($HOME/AppData/Roaming/Adobe/FrameMaker)<br>
- Disable all third-party plugins<br>
- Disable "LoadStartupScripts" setting in maker.ini<br>
<br>
This happened suddenly; I don't know what might have triggered it.<br>
<br>
Any ideas?<br>
<br>
-Alan<br>
<div class="moz-signature">-- <br>
<small>Alan Houser<br>
Group Wellesley, Inc.<br>
Consultant and Trainer, Technical Publishing<br>
arh on Twitter<br>
412-450-0532</small> <br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
<br>
</body>
</html>