VmAwareness
Contributor
Contributor

Hopefully these tips will help you out, and some may be already known.

1) Know your app intimately from an installer/runtime  perspective. Or, get someone that really knows it and drag them along  kicking/screaming into the thin-apping process.

2) 32bit App on 32bit OS, 32bit App on 64bit OS, 32bit thinapp on 64bit OS, etc... = headache

If you can, use the lowest common supported OS and avoid using default C:\Program Files or C:\Program Files (x86) directories. To sometimes increase your chances of ThinApp success for a 32bit app on 64bit Windows 7 OS... then

  •   Use a clean Windows 7 32bit machine (Or even Windows XP 32 bit)
    • I had an app that needed the XP centric msvbvm60.dll, olepro32.dll to run properly that did or did not install depending on the capture base OS. See POINT 1.
      *** I had a 32bit app that would locally install and run on a 32bit and  64bit versions of XP and 7. But would not run as a ThinApp on 64bit  Windows 7 unless it was captured on 32 bit Window7. 32bit/64bit XP, and  64bit 7 captured versions would all have runtime errors.
  •   Install the app in any other folder than C:\Program Files\ or C:\Program Files (x86).  Best to install it on a non standard non defaultly created folder.
    • ThinApp  runtime sometimes get confused on the %Program Files% environmental  variable when running on 64bit or 32bit OSes. Just remove the headache  and don't use the default directories.
      *** With that said, I had an  app that functioned properly at launch when not using the default  directory, BUT internal functions failed because because it was hard  coded to use the %Program Files% ENV VAR. Again, please see POINT 1.

3) Try copying missing DLLs like  msvbvm60.dll, olepro32.dll to the %SystemSystem% in the capture folder. Your 64bit OS might not  have these, the app might need these, and the logs might not show that  it is needed. Search the community for these dlls as key words for more  info. Again, see POINT 1

4) Try editing the Package.ini before creating the final package. Possibly relavant entries are -

;VirtualizeExternalOutOfProcessCOM=0

;Wow64=0

This may or may not help. Search the forums for additional details on what these do. However, please see POINT 1.

Good luck!

Reply
0 Kudos