URGENT*** Virtual IE7 explorer.exe communication ***Project Due Oct. 1st

[danpeterson]

I have a virtual package of IE7 running on Win7, this application runs an activex component that links to a windows share through an attachments button.

However there seems to be no communication from the bubble into the native machine, at first I would get and error "no such interface available."

This error was present also when I would insert the path to a file/directory in the addres bar. I resolved this by adding the following to packages.ini:

ChildProcessEnvironmentDefault=Virtual

ChildProcessEnvironmentExceptions=Explorer.exe

This made an exception to run windows explorer inside the native machine and not look for it in the bubble.

However, this workaround presented a new problem:

     Now when I try to browse for a file/fdirectory in the address bar, explorer.exe runs as a child process in the native machine BUT the address/string is      somehow dropped and the explorer just opens as a new process in my "Libraries." I've tried adding to my packages.ini:

AllowExternalProcessModifications=1

VirtualizeExternalOutOfProcessCOM=0

I have generated VMware logs using Log Monitor. I enetered an obscure name into the address bar e.g. "file:\\C:\debug" while running the monitor (i created the directory on the native machine and explorer open in libraries). I then went and searched the logs for this string. I had no problem finding this entry in the log report, but I don't fully understand what information I can pull from it to see where the application is failing, either to communicate with the native machine or if there is another issue causing this. I can send these logs via an attachment in a email to anyone who wants to view them.

Please, can anyone help to shed some light on this issue

Fast responses are appreciated!

     Thanks, Dan

Also to note, the problems don't present as an issue in Windoes XP

[shrivastavaa]

How about including XP explorer in the package as well. obviously you'll remove changes you made to package.ini.

ChildProcessEnvironmentDefault=Virtual

ChildProcessEnvironmentExceptions=Explorer.exe

I have observed in past that explorer, shell32 changes some interface from XP to Win7. By change I mean they add some interface and drop some; now if they have dropped the XP interface your aplication is looking for; it will be a problem.

[danpeterson]

Sadly, that did not work. I wish the solution could be that simple. What happens with that is no explorer window is opened, but some information seems to be getting passed, i say this because if i type a path that doesnt not exist i get an error versus typing an existing path i get nothing

[shrivastavaa]

Another thing you can try is to, from task manager kill the existing explorer.exe and than launch it virtually (using virtual CMD), than launch your application. If it still does not work; than its surly a compatility problem between explorer and active X component.