Here is some more info I found after doing some debugging.

I have workstation 6.5 running. I start Quicken 2009. If I don't move my mouse outside of the Quicken window, everything is good.

If I move my mouse to any application that does not have xmlparse.dll loaded in its context, I have no problem.

If I move the mouse to the workstation 6.5 window I get the error message.

When I move the mouse in this case to the workstation window, at this time some Quicken DLL are loaded in the context of the vmware.exe process

(dll include QWWIN.DLL, QWMAIN.DLL, QWUITL.DLL etc). I think the reason why these dlls are loaded is because of some interdependency

with the 'mouse hook' function that the Quicken application installed in the OS when it started. The hook function registered by Quicken app

is defined in one of these dlls. I found which dll's are load and when by monitoring vmware.exe using the 'process explorer' tool from 'sysinternals' website.

QWUTIL.DLL depends on xmlparse.dll, but a version of this dll provided by VMWAre (different than the one provided by Quicken)

is already loaded in the context of vmware.exe.

Now one of the Quicken dll's tries to find XML_ParserCreate function inside xmlparse.dll, but it is not provided by the vmware version currently loaded.

Hence we get the message.

Note that when things were working with workstation 6.0.5 and Quicken 2008, the version of xmlparse.dll provided by vmware do contain the XML_ParserCreate function,

hence I think I did not see any error message. Even though there is no error message, this is very bad/dangerous because, the quicken dll that is calling this function is

actually running the one provided by vmware and not quicken.

When I upgraded to workstation 6.5, it installed a new version of xmlparse.dll.

In this new dll, the function has been renamed from XML_ParserCrete to xmlrpc_XML_ParserCreate. Hence after upgrade I started getting the error.

If my analysis is correct, the bottom line is as follows:

If you have Quicken and some other application which has its own version of xmlparse.dll that does not contain XML_ParserCreate function,

then you will see the error message when you move your move to the other application's window.

I think Quicken either need to get rid of the 'global' mouse hook (which is recommended by Microsoft, unless absolutely necessary)

or need to rename their version of xmlparse.dll to something, say qwxmlparse.dll

or if possible, somehow make sure that their version of xmlparse.dll is loaded along with any other version of the same dll in the context of other applications.

I have filed a bug with Quicken with the above information. Hopefully they will be able to fix this soon.

mapte

I think the reason why xmlparse.dll is needed when the mouse moves to the vmware.exe is because the 'global' mouse hook function registered with Windows by qw.exe is implemented in one of the qw DLL's that I mentioned earlier. So when the mouse moves inside the vmware.exe windows, the OS tries to load the required qw dll's that implements this function so that it can invoke hook callback to let qw.exe track the mouse movement globally.

As part of this dll dependency tree, the OS needs to load QWUTIL.dll which has a implicit dependency on xmlparse.dll because it calls some of the XML_xxx function defined in xmlparse.dll. OS finds that some version of xmlparse.dll is already loaded (in this case the vmware version of xmlparse.dll). I don't think the OS knows how to load the quicken version of this dll, so it tries to resolve the the XML_ParserCreate function dependency in the currently loaded vmware version of xmlparse.dll and does not find it.

As I mentioned earlier, I think the easiest way to solve this is for quicken to rename their dll to say qwxmlparse.dll so that OS will not find it in any process and load the quicken version correctly.

mapte