tag:blogger.com,1999:blog-7977773.post8943011394075028607..comments2024-01-11T13:34:12.385-07:00Comments on Trentent -- One and Only.: AppV5 - When Application Compatibility Toolkit doesn't workTrententhttp://www.blogger.com/profile/15791628156004881187noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-7977773.post-38468769274733939692015-11-29T22:16:10.108-07:002015-11-29T22:16:10.108-07:00Hi Tim,
That's where I was getting confused. ...Hi Tim,<br /><br />That's where I was getting confused. iexplore.exe wasn't loading, but it's embedded components do in the application. The only process launched *was* prowin32.exe. <br /><br />I know there are 'objects' exclusions and maybe one of them is used by this program but I didn't have enough time with the user to narrow it down more accurately.Trententhttps://www.blogger.com/profile/15791628156004881187noreply@blogger.comtag:blogger.com,1999:blog-7977773.post-3633765839804795842015-11-27T18:25:03.569-07:002015-11-27T18:25:03.569-07:00Yes. The shim applies only to the targeted exe, no...Yes. The shim applies only to the targeted exe, not the rest of the VE. While you could duplicate the shim to IE as a solution (since IE wouldn't otherwise concern itself with this odd folder), sometimes the better solution can be simpler. When the file is unique to the use, I often prefer to use a start/end VE script to deal with this kind of stuff.<br /><br />TimAnonymoushttps://www.blogger.com/profile/05660745834714225135noreply@blogger.com