General XMetaL Discussion
patrickq February 6, 2009 at 7:10 pm
XMetaL Fails to StartFebruary 6, 2009 at 7:10 pmParticipants 1Replies 2Last Activity 13 years, 8 months ago
Occasionally, when I try to open XMetaL, it does not appear. Sometimes I try a few times. Process Explorer shows several instances of xmetal.exe at 0 cycles.
Any ideas what causes this? It has happened to several developers here.mag3737 February 6, 2009 at 7:51 pm
Reply to: XMetaL Fails to StartFebruary 6, 2009 at 7:51 pm
Is this XMetaL 5.1? There was an issue that had something to do with arbitrary other Windows applications and their use/release of system window resources which caused XMetaL to fail to start. For example, one time that this was happening to me, I simply closed Firefox (and killed the xmetal process via the Task Manager), and then XMetaL started just fine. (I don't think it was just Firefox, I think it could be any other applications, too. I just got lucky with a random guess that one time.)
My understanding of the problem was so poor that I don't even know if I have made a misstatement in what I said above. Perhaps one of my colleagues will weigh in with a correct technical explanation.
But I do know this issue was fixed in XMetaL 5.5. If you're seeing this in 5.5, it could be something else, and if you don't get an answer here you should drop a line to our support team via the Support page of the website.Derek Read February 7, 2009 at 12:09 am
Reply to: XMetaL Fails to StartFebruary 7, 2009 at 12:09 am
This is a known issue in 5.1 that does not affect 5.5 or versions previous to 5.1.
The issue is that when XMetaL Author Enterprise launches it checks for other instances of the xmetal51.exe running and if it finds one passes any request to open a file over to it. Then it closes itself and lets the first copy of the EXE take over. To do this it asks every running application to respond (standard Windows stuff) saying what it is, however, the xmetal51.exe will wait forever in cases where a 3rd party application doesn't respond (it is busy or is simply not coded to do so). When this occurs the xmetal51.exe will appear hung in the Task Manager and the UI will not load because it is waiting for a response that will never arrive.
This only affects some users and may occur randomly because most applications are written to respond to these types of requests. If your other applications always respond then you will never see the problem (it has only been reported to us by a few clients). However, this behavior is incorrect and has been fixed.
XMetaL Author Enterprise 5.5 (and 5.0 and earlier) times out when a response is not immediate and will continue with the launch process.
Upgrading to 5.5 is the best solution for this problem. If you are unable to do that for whatever reason XMetaL Support can provide you with a patched version you can use until you are able to upgrade to 5.5. Contact XMetaL Support through the standard channels.
- You must be logged in to reply to this topic.