Nope, you don't have to install drivers. Thinapp doesn't support driver virtualization. I think you should try to do following: Have clean WXP Install printer driver Run Thinapp Install IE 7...
See more...
Nope, you don't have to install drivers. Thinapp doesn't support driver virtualization. I think you should try to do following: Have clean WXP Install printer driver Run Thinapp Install IE 7.0 Run Legacy Application and try print Do the Capture Then remove old sandbox from W7 and run new virtualized IE and test printing.
Please, try to set different default printer and run virtualized IE again with other printer set as default. I had this kind of problem o native installed IE and it was caused by printer driver.
I think problem is is isolation mode of registry keys. I think you should do it following way: Pre-installation snapshot Run Internet Explorer and try to print some document Post-installation...
See more...
I think problem is is isolation mode of registry keys. I think you should do it following way: Pre-installation snapshot Run Internet Explorer and try to print some document Post-installation snapshot capturing IE 10 When you run your printing and also set needed settings, all those settings will be in virtual package and you should not have a problem. Try it and let us know,
Can you, please, check where this file is located when application is installed natively? Then you can check if this file is in Thinapp package on same location.
You wrote it correctly. When you run DFS client machine pics only one "hiden" share under DFS. When this share fails application fails also. SMB 3.0 is available and DFS transparent failover only...
See more...
You wrote it correctly. When you run DFS client machine pics only one "hiden" share under DFS. When this share fails application fails also. SMB 3.0 is available and DFS transparent failover only in Windows 8 and higher. You are absolutely right.
IMHO there is a problem with DLL library winscard.dll: 006017 0000126c 00000808 vmwsci.dll :73e72957int=0h (DWORD dwFlags=1h, LPCWSTR lpModuleName=*73E808F8h->L"winscard.dll", *phModule=*18E...
See more...
IMHO there is a problem with DLL library winscard.dll: 006017 0000126c 00000808 vmwsci.dll :73e72957int=0h (DWORD dwFlags=1h, LPCWSTR lpModuleName=*73E808F8h->L"winscard.dll", *phModule=*18E080h->*0h ) *** GetLastError() returns 126=0x7e [0]: The specified module could not be found. It is looking for this DLL file in some places. Can you, please, chcek if such a file is located on your computer? Please, also chceck on native installed application locations. Looking forward to hear from you,