Also when I launch Word it sometimes will raise my CPU utilization to 50% when I try and type anything and then lockup for anywhere around 1 minute to 5 minutes. This wouldn't be such a problem if it wouldnt keep happening sometimes at random when using the program. First off often I get various MSI Installer error that display in the event viewer and also the installer sometimes will show up while using the program. It worked fine in the virtual desktops I have setup (with or without Office 2003 installed) but as soon as I move it to a physical test or production machine I see the following issues (with Office 2003 installed locally). I have used a vm test machine that is "clean" with Windows XP SP2. I have followed step-by-step instructions listed on the how to ThinApp O2K7 to the T and even tried various other ways that where not listed. No, I misunderstood - I thought someone changed the installed directory of the app, not the source it was installed from.I have been playing with ThinApp 4.0.2 and 4.0.3 versions attempting to Office 2007 for our office. Several of them included the mscomctl.ocx file (but all thru using the same MSM).If Windows Update (or another install) had modified the version to be a later version then I can see that our install might kick off to do a repair, but I doubt that this file has been updated by windows update and I think we are probably using the latest version of mscomctl.ocx (v 6.1.97.82). The MSI bears this out and we use the standard VS6 SP6 MSMs in the MSI.The only thing that could have broken mscomctl.ocx is that our app is made up of several MSIs which are installed in turn.
The only thing that was renamed was the location that the install was run FROM (X.UNTESTEDR5CDBP).Surely if simply removing/renaming the install source kicked off a repair then all those CD installs that people do would have the same problem all the time?I'm 100% certain that mscomctl.ocx is installed into the system folder.
0 kommentar(er)
