As 64 bit Windows versions become more common, you need to deploy scripts automating 64 bit software as well as maintaining 32 bit versions of the same script.
PrimalScript 2009 has always included a script packager that allowed you to wrap a variety of script types into 32 bit executables.
With today’s service release (5.0.627) you also get the option to build 64 bit executables out of the same script.
If there are any differences between your 32 and 64 bit environments you will, of course, need to adapt your script accordingly.
Building a 64 bit package is as simple as checking the “Target 64 bit systems” check box and you are ready to roll out your script.
If you prefer to package your VBScript/JScript files quickly with the push of a button, VBS2EXE has a new command line switch,
-64, which you can set in Tools-Options-Languages as a default per language.
The 64 bit package option is available for every supported host, whether you use VBScript, JScript, HTA, or PowerShell in a Windows or command line version.
This update is part of the normal monthly service update and free for all registered PrimalScript 2009 users.
So head over to my.sapien.com and download the latest version.
After installing this service release, I am no longer able to package scripts with source files. I am able to package scripts only, but as soon as I add any source files to the package, it will not run when created. it will extract the first file of the source files and then lock up with windows telling me it has to end the program. I reverted to the earlier version (5.0.625), and it is all working great again.
Thanks, but please note that you should *always* report bugs and problems in the dedicated support forum at http://support.sapien.com. Only then is it certain that your report is seen and acted upon in a timely fashion.