I have an application that I captured/packaged on a clean Window 7 64 bit VMWare Workstation VM using ThinApps 4.6. When I try to run packaged application's executable it fails with "A call to an OS function failed" (attached is a picture of the error). I ran a trace and the section below is where the application is failing. Has anyone else seen similar issues with ThinApps 4.6 or have any experience with troubleshooting these trace files
Which 4.6 - 4.6.0, 4.6.1, or 4.6.2? Also, do you have an option to limit the installed language to English? Are you packaging an application (called "Chronicles", from the looks of things) that was built using an Embarcadero product? Are there any COM objects? Here's a little bit of info from page 50 of the ThinApp 4.6.1 manual:
Using COM, DCOM, and Out-of-Process COM Components
Captured applications can create COM controls from the virtual environment and the system. If a COM control is installed as an out-of-process COM, the control runs as a virtual process when a captured application uses it. You can control modifications that the captured applications make.
ThinApp 4.6. There are no language options during the install. I am trying to package the Chronicles (http://www.gochronicle.com/) which is a business management application. It may have been built using a Embarcadero product. How do I figure out which COM Objects the application is using?
If you intend to run it in both 32 bit and 64 bit environment. I will suggest you to install it in some non-standard location while capture. For example after pre-scan; when you are installing the application; instead of default "program files" folder, choose some other folder, lets say c:\AppName or something.
Continue as usual and build the project.
Now try the new binary on 64 bit and report back.