Posts Tagged ‘64 bit’


2014 Software: Do I choose 32 Bit or 64 Bit?

Tuesday, May 20th, 2014 by David Corrales
The question you have to ask when you decide to download the 2014 version of our products is: Which platform do I download? 32 bit or 64 bit? Most people with a 64 Bit OS will probably download the 64 bit version, but is this the correct choice? It may not be, depending on your needs. Here are some factors you need to consider:   1. Do I use Source Control? If you are using a Source Control provider, you have to determine if supports 64 bit or 32 bit only? For example, if you have an existing source…   More »

All SAPIEN Software will be 64 bit

Tuesday, February 5th, 2013 by Alex Riedel
With some of our smaller free tools, for example PrimalPad, we started creating 32 bit and 64 bit versions quite some time ago. There is no capacity reason for a text editor to be 64 bit, after all, your script probably won’t exceed 4 GB anytime soon. Users of our current versions know that, PrimalScript 2012 and PowerShell Studio 2012 which are 32 bit executables, fully support 64 bit OS varieties and languages. But there is just something to be said for running software that is native to your operating system. Eliminating subsystem layers and folder redirections are just two…   More »

PrimalScript 2012: What’s new? (Part 5)

Wednesday, May 2nd, 2012 by Alex Riedel
As promised last time we take a look at the new version of the Object Browser in PrimalScript 2012. As soon as you click on the PowerShell node you will notice two things: It opens a LOT faster. PrimalScript 2012 loads its information from a cache rather than instantiating a slow starting copy of PowerShell. This will actually come in handy in other aspects, which we will cover later. You see a 32 bit and a 64 bit node. While PrimalScript 2011 already supported both platforms in almost every aspect, the PowerShell browser was a strictly 32 bit affair. Not…   More »

PrimalScript 2011 and Windows 2003 Server (64 bit)

Tuesday, May 17th, 2011 by Alex Riedel
PrimalScript and PrimalForms 2011 make heavy use of the "sysnative" virtual folder to access 64 bit operating system tools and files. Under the 64 bit versions of Windows 2003 Server and Windows XP that virtual folder is not available by default. In order to ensure proper installation and operation we recommend that you install the following Microsoft hotfix prior to installing PrimalScript 2011 or PrimalForms 2011.…   More »

Feature Peek PrimalScript 2011: 32/64 bit debugging

Thursday, February 10th, 2011 by Alex Riedel
You probably already guessed that we did not just stop with executing scripts in either 32 or 64 bit mode. Debugging your scripts in either environment is just as simple. With just the flick of a switch you can launch the 32 or the 64 bit debugger and run, step, examine and probe your variables at your leisure. The screenshots below illustrate how easily you can go from 32 to 64 bit. …   More »

Feature Peek PrimalScript 2011: Bridging the gap, Part 3

Wednesday, January 5th, 2011 by Alex Riedel
Last time we learned how you can pre-determine where your script is executed by using meta-comments inside your code. While this third installment also deals with execution in either 32 or 64 bit environments, the main gap being addressed today is between script development and working in a shell. For us developer types, the use of an IDE is pretty clear cut: We write code and we want as little dependency on our development machine as possible. Administrators once again live in two worlds: Of course you develop scripts that will run on other machines and, just as us, should…   More »

Feature Peek 2011: Bridging the gap, Part 1

Monday, November 22nd, 2010 by Alex Riedel
The question about a 64 bit version of PrimalScript has been raised a few times in our support forum. The question was, however, not really about what platform PrimalScript uses, but what platform the scripts run on. As software transitions from 32 to 64 bit you need a development environment that works on BOTH sides, not exclusively on either side. Many administrators are tasked with supporting legacy 32 bit software and bleeding edge 64 bit server components, some even on the same machine. PrimalScript 2011 will do just that, work on both sides, indifferent to its own "bitness". A little…   More »

Moving to 64 bit: Running PowerShell files in 64 bit from PrimalScript 2009

Monday, August 16th, 2010 by Alex Riedel
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. 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…   More »

Moving to 64 bit: Running a 64 bit PowerShell console inside PrimalScript 2009

Tuesday, July 20th, 2010 by Alex Riedel
PrimalScript 2009 is a 32 bit application, so by default it uses the 32 bit version of PowerShell even on a 64 bit machine for the embedded console. If you are dealing with mostly 64 bit server software you may want to make the embedded shell use the 64 bit version of PowerShell. The default installation of PowerShell under Windows 7 is at C:\Windows\System32\WindowsPowerShell\v1.0 And yes, that is still true for PowerShell V2. The system32 folder is mapped to SysWOW64, which is the actual 32 bit version of the that folder. I know, the numbering scheme is a bit confusing.…   More »

New packaging options for PrimalScript 2009

Thursday, February 11th, 2010 by Alex Riedel
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…   More »