Up until recently I was doing win32 builds using a WinXP VM running on Fusion. I switched to Parallels, and since Parallels was unable to convert the VM directly, I rebuilt it from scratch. I've been able to build and run executables on the new WinXP VM, without noting any problems. When I sent a copy to a beta tester, he reported getting four R6034 runtime errors, after which the program loads and functions correctly. I sent him the exact some build from the old Fusion VM, and it does not generate runtime errors for him.
Next I did a build on both VMs and compared the output line by line. The build on the Parallels VM was not finding a specific VC++ redistributable file: c:\WINDOWS\WinSxS\Manifests\x86_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.21022.8_x-ww_d08d0375... That file is in the MSVC++ 2005 Redistributables installed, so I downloaded that and installed it, and now the build output from both machines is identical. But now the executable built on the Parallels VM generates the R6034 runtime errors when run on the Parallels VM: "An application has made an attempt to load the C runtime library incorrectly..." I did a verbose build on both VMs, and the output is the same. I did a debug build on both VMs, and the output is the same (except for the runtime errors on the Parallels VM.) The executable built on the Fusion VM works fine on the Parallels VM; the version built on the Parallels VM works fine on the Fusion VM, but generates runtime errors when run on the Parallels VM or my beta tester's Win7 x32 machine. Anybody know what is causing this, or how I might do more troubleshooting? Thanks, Lynn Oliver -- You received this message because you are subscribed to the Google Groups "PyInstaller" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pyinstaller?hl=en.
