{"id":2383,"date":"2010-08-16T13:23:51","date_gmt":"2010-08-16T21:23:51","guid":{"rendered":"http:\/\/www.sapien.com\/blog\/?p=2383"},"modified":"2010-08-16T13:24:00","modified_gmt":"2010-08-16T21:24:00","slug":"moving-to-64-bit-running-powershell-files-in-64-bit-from-primalscript-2009","status":"publish","type":"post","link":"https:\/\/dev.sapien.com\/blog\/2010\/08\/16\/moving-to-64-bit-running-powershell-files-in-64-bit-from-primalscript-2009\/","title":{"rendered":"Moving to 64 bit: Running PowerShell files in 64 bit from PrimalScript 2009"},"content":{"rendered":"

Last time we looked at running VBScript files in 64 bit from within PrimalScript 2009. As you may recall, the only thing required was to provide a path to the 64 bit CScript.exe or WScript.exe and substituting “sysnative” for “system32”. The rest was all automatic.<\/p>\n

As I mentioned last time, PowerShell requires some extra work. PrimalScript redirects stdin, stdout and stderr when capturing the output of a process and PowerShell.exe does not react well to that. This has been a PowerShell problem since V1 and wasn’t fixed with V2. Basically the PowerShell process will just hang and do nothing when you redirect stdin. I am assuming that if PowerShell sees a redirected stdin stream it just awaits commands from there and ignores anything else.<\/p>\n

I have created a little helper app that will take care of that:<\/p>\n

ftp:\/\/ftp.sapien.com\/exec64.zip<\/a><\/p>\n

Download and extract the executable to your PrimalScript 2009 installation folder.<\/p>\n

\"Posh64bit\"<\/a><\/p>\n

Right click anywhere in the tools browser and select \u201cCustomize\u2026\u201d and add a new tool in a group of your choice.<\/p>\n

Name the new tool “PowerShell (64 bit) or whatever your like and set the properties as follows:<\/p>\n

Command line: Exec64<\/p>\n

Arguments: C:\\Windows\\System32\\WindowsPowerShell\\V1.0\\powershell.exe -NonInteractive \\”&’$File$’\\”<\/p>\n

Initial Directory: $FileDir$<\/p>\n

Check “Capture Output”<\/p>\n

In order to run the current script in 64 bit mode you only have to click on the icon.<\/p>\n","protected":false},"excerpt":{"rendered":"

Last time we looked at running VBScript files in 64 bit from within PrimalScript 2009. As you may recall, the only thing required was to provide a path to the 64 bit CScript.exe or WScript.exe and substituting “sysnative” for “system32”. The rest was all automatic. As I mentioned last time, PowerShell requires some extra work. […]<\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[283,410,21,25],"tags":[525,28,37],"class_list":["post-2383","post","type-post","status-publish","format-standard","hentry","category-howto","category-primalscript-software-news","category-software-news","category-windows-powershell","tag-64-bit","tag-powershell","tag-primalscript"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t