02-27-2010 01:41 PM
When I launch a simulator in Windows 7 64-bit I am unable to close it without going to the task manager and killing the process. When I close the simulator with the X button it just freezes and is unresponsive. I've tried the instructions on these forums for setting up the Java Eclipse plug-in on Windows 7 64-bit, but it has not remedied the problem.
My solution right now is to a batch file to kill the process with one click.
taskkill /f /im "fledge.exe"
I put it in the QuickLaunch which I had to do some fiddling to get back in Windows 7. Here's some instructions for getting the QuickLaunch back: http://www.sevenforums.com/tutorials/888-quick-lau
Is there a way to solve this simulator problem without killing the process?
Solved! Go to Solution.
02-27-2010 05:21 PM
This is a known issue and the only other way is to press "Disconnect" when in the Debug perspective but it effectively does the same as terminating the process (it might be a little safer; not sure).
02-27-2010 05:57 PM
03-03-2010 07:55 PM
10-27-2010 08:18 AM
Could you help me regards closing the Simulator in Windows Vista. I read the above solutions but dint understand.. could you explain me how to do a safe close of the simulator...
06-02-2011 11:45 PM
Another possible solution:
Interestingly enough I think I know why its not closing.
First the FledgeHook.exe shows up in the Microsoft Administrator Events log as an Application Error.
It must be able to be launched.
First close Eclipse
Secondly locate the executable:
Login as Admin right click the FledgeHook.exe select properties,
Click on the Compatibility tab
Click button Change settings for all users
Click check box to run application as Administrator.
Launch your Eclipse
Run your application through the simulator
Click on the 'X' on the upper right.
FledgeHook.exe is a program that detects if your simulator has been closed, then it is able to really shut it down. When FledgeHook.exe keep having errors and not able to be run the simulator runs by itself. It needs FledgeHook.exe.
It seems to work for me. Remember to check your Microsoft Events log to see any other application errors.
Here is where I found out about FledgeHook.exe,
I hope this help folks.