This article will require some basic knowledge of computers, Network Configuration, and Windows Operating Systems. The Installation Packages for Pervasive can be acquired by contacting Windward Support.
This wiki page gives you the installation steps specifically for Version 12, but the steps are pretty much the same for V11 and V12, just the instructions on the installation screens may be a bit different. To minimize the chance of errors during the install, Pervasive should always be installed by Right-clicking on the installation executable, and run as administrator.
If you are installing pervasive on your server, you would download and run PSQL-Server-12.00.032.000-win.exe, and when you run it as an administrator, you would choose to Unzip on the first screen, then Install PSQL v12 Server Engine on the following menu. Unless you have a specific need to install it in a very specific location, you can accept the defaults all the way through the installation. If you do need to change where pervasive is installed, choose the Custom install when prompted, and enter the directory you want to install it to when you are asked. And again accept the defaults for the remainder of the installation.
If you are installing pervasive on a Workstation, you would again download and run PSQL-Server-12.00.032.000-win.exe, and when you run it as an administrator, you would choose to Unzip on the first screen, then Install PSQL v12 Client Only on the following menu. Again, unless you have a specific need to install it in a very specific location, you can accept the defaults all the way through the installation. If you do need to change where pervasive is installed, choose the Custom install when prompted, and enter the directory you want to install it to when you are asked. And again accept the defaults for the remainder of the installation.
If you are re-installing System Five, and have a copy of the bin folder from a current installation, (bin folder on the server or another workstation) you can use any version of the System Five installer to have it create the folder structure and registry entries. Then to convert your installed version to the version that is on all the other computers on your network, you just need to take your original bin folder (from the server or another workstation) and replace the one created by the install.
On the server, the bin folder will usually reside in the following path. C:\Windward\System5\Bin
On the workstation, the bin folder will usually reside in the following path. C:\System5\Bin
If you do not have an installation package, you need to contact Windward Support to get a current release of the installation package, and then the installation will be treated like a new install.
Right-click on S5Install.exe and run as administrator.
This will start the Install Wizard.]
Click on the checkbox next to “I accept the license agreement”. Click Next.
If you need to modify what is installed, or you do not want to install a training version, you can turn those features off by clicking on each of the two components. This will give you the following dropdowns. If you are not sure what you want to install, then just accept the defaults by clicking Next.
Now you are prompted to choose the installation path. We recommend on a server that the installation path be set to: c:\Windward\System5 or D:\Windward\System5 We recommend this folder or directory structure because it is the Windward folder that should be shared and made available to each workstation. These folders can reside within another folder if your IT people prefer to put all shared folders within another folder on your server’s hard drives. As an example: D:\UserData\Windward\System5. But really this is up to you and your IT Person, as every server’s data structure can be different. We also recommend that you do not have spaces in your directory/ folder names, as it can cause some issues with Pervasive and System Five. However, dashes and underscores are acceptable.
On a workstation, we recommend accepting the default folder structure of C:\System5. Click Next
The start menu options here should be pretty straight forward. We recommend that you leave these settings alone and just click next.
Next, Microsoft XML 4 will be automatically installed. This is a necessary component and must be installed. Click Next.
Click Next to begin the installation.
If all goes well, you should see the “XML 4 Install has been successfully installed” screen. Click Finish> button.
A couple of screens will pop up and automatically close, and you should then see the “System Five has been installed successfully” screen. Click Finish> button.
Next, the Borland Database Engine installation will automatically start. Click Next.
Accept the defaults by clicking Next.
Again Click Next
Accept the defaults again by clicking Next.
The installation has been completed. Click Finish.
You should now see a System Five icon on your desktop.
The last step is to link to an existing dataset. If this is a workstation, you will first need to make sure that you have a mapped drive pointing to the Windward folder on your server. You may need assistance from your IT people to configure this if you do not have sufficient Windows Security privileges, or are unable to do this yourself.
With Windows 8 and up, you will need to either be logged into the workstation as a network administrator, or you will need to right-click on the System Five Icon and click Run as Administrator. On the log-in screen click on the install button on the top right.
Click on Link to existing data
Browse to the W drive that you or your IT person mapped to the Windward Folder on the server. In my computer, the data is on my local D drive but would be on the W drive in a network installation. Select the W drive from the dropdown, and then double click on System Five, Double Click on Data and then click on the _datafiles folder to highlight it. You should see the path appear in the right-hand window. Click Next
Select your terminal in the list and click next
Enter or change the Station Name if needed, otherwise, click Next.
Click Finish, and you are done.
If in the event where a network dropout or a computer failure will 'lock' a terminal, and the user will not be able to log into System Five until the lock is reset. This is a Windows issue that can be easily resolved. You can refer to this article for further details.