If you have Windows Vista x64 (any edition) then you will notice then when something crashses in an x64 environment you will notice that the support is not really that "fluid" as it would be for the x32 counterpart, if you take a real world example of this then refer to the screenshot below:
[singlepic id=354 w=320 h=240 float=]
This is obviously a crash of some kind that windows "Crash Manager" has intercepted so if you ask for more information you get this:
[singlepic id=355 w=320 h=240 float=]
So instantly you can see that the error is in the "MySQLQueryBrowser" not in the "MySqlAdmin.exe" which is the host process.
[singlepic id=353 w=320 h=240 float=]
At this point Windows will attempt to find a solution to your problem....this however only works if you use main stream applications....I do not therefore this tool is essentially useless I currently have over 12 application reports outstanding...
[singlepic id=354 w=320 h=240 float=]
This is obviously a crash of some kind that windows "Crash Manager" has intercepted so if you ask for more information you get this:
[singlepic id=355 w=320 h=240 float=]
So instantly you can see that the error is in the "MySQLQueryBrowser" not in the "MySqlAdmin.exe" which is the host process.
[singlepic id=353 w=320 h=240 float=]
At this point Windows will attempt to find a solution to your problem....this however only works if you use main stream applications....I do not therefore this tool is essentially useless I currently have over 12 application reports outstanding...