The Parabuild installation folder (f.e.: c:\Parabuild\) contains many files for Parabuild that you do not need to know about, but some of them are worthwhile to learn what they are for.

The files of interest are explained hereafter:

  • Parabuild.exe : This file will start AutoCAD or BricsCAD, and gives it a command-line parameter to load the correct Parabuild files during startup.
  • Parabuild.cfg : This file is used by Parabuild.exe and contains the location of the Parabuild library folder that needs to be used, the language in which Parabuild should run, and also which AutoCAD or BricsCAD installation in which Parabuild should run. The file StartupSettings.exe writes this file for you so it should not be necessary to modify this file manually except in cases where the StartupSettings.exe tool would fail.
  • StartupSettings.exe : This file allows you to change the location of the library folder that Parabuild should use, and also allows you to change the AutoCAD/BricsCAD installation that Parabuild should use.
    For AutoCAD this tool also registers the Parabuild properties inside the AutoCAD installation. This registration happens inside the Windows registry which is why this tool needs and asks for administration privileges. This is a crucial step that needs to be done each time when Parabuild is run inside a different AutoCAD installation. Failure of this step will cause AutoCAD to crash when a Parabuild part is selected and the Properties panel is open. In BricsCAD this registration step is not needed because Parabuild uses a different runtime mechanism to register properties in BricsCAD.
  • SheetMgrColumnPreferences.dat : This file contains the columns and the shorting that should be shown in the sheets and model spreadsheets in the Sheets Manager. It is safe to delete this file as that will revert the columns to the defaults. This is not stored in the library because these are considered personal drafter preferences.
  • defset.dat and defset-imperial.dat : This files is created when you click on Set as default in the Global settings dialog box.
  • DynProp.dat - This file contains all of the dynamic properties that were created in the dynamic properties. This file is not stored in the library because can't be created on the fly and require a Parabuild restart after a change to one of them. Parabuild needs to register these properties inside AutoCAD/BricsCAD Properties Panel.
  • UserInterfacePreferences.dat : This file contains all of the options that you have chosen in the User Interface such as the context menu preferences. This file is not stored in the library because these are considered to be personal drafter preferences.
  • DefaultOutputSettings-English.dat and DefaultOutputSettings-Imperial-English.dat : This files is created when you click on Set as default in the Output settings. The exact filename that is written depends on the language and units in which you are using Parabuild.
  • ParabuildSpreadsheet.exe, standard.pbd, Parabuild Header.pbh, Parabuild Header.bmp, Parabuild Footer.pbh, and Parabuild Footer.bmp : This executable file is a simplistic standalone spreadsheet program delivered together with Parabuild as is and there is no license required to use it. When you generate a bill and choose the Parabuild Spreadsheet as output filetype then the bill will be stored as a ".pbs" file which can be opened with this ParabuildSpreadsheet.exe. The Parabuild spreadsheet program allows viewing, editing and printing of the bills. This executable file is also stored in the same folder as the .pbs file so that other people that do not have Parabuild can open, view, and print the bills. This tool was primarily created as an alternative for Excel, but now that many Excel programs are available for free the value of this spreadsheet has decreased. It is not being actively developed anymore for this reason. The other files with the extensions pbh and pbs are stored from within the Parabuild spreadsheet to configure the header and footer of the bill. The bitmap contains the logo on the footer and or header that needs to be created or modified manually. The pbh file puts text on that bmp file based on the pixel size of the bmp file. The file standard.pbd contains the default header, footer, text font and size that should be used for new spreadsheets. The file standard.pbd is stored when you click on Set as default inside the Print options dialog box of the Parabuild spreadsheet program.
  • PrinterPreferences.dat and PrinterPreferencesPdf.dat : This file is saved when you save your preferred device and media when plotting or publishing sheets. This information is specific for the system and is therefore not stored in the library. Do not copy these files to another system.
  • MediaCache.dat - This contains media information of the devices on the system and is therefore not stored in the library. The cache is created to speed up printing. Do not copy this files to another system. If you suspect media size issues then you can safely delete this file because it will be recreated automatically.
  • Parabuild-Help-EN.chm : This is the full Parabuild reference manual for offline viewing. It is the same manual that can be found online online here : https://www.parabuild.com/my-account/
  • ParabuildLicense.lic and Network.lic : This is the license file that Parabuild is currently using. The license is locked to the computer so it is no use to simply copy this file to another computer. Don't delete this file. But you could copy the file to another Parabuild folder on the same system to ensure the same license will work on all Parabuild installations on the system. (though a system is in place that lets Parabuild find the license on the system and put the license file there by itself).
    In the ParabuildLicense.lic the single-user license is stored. In Network.lic the cloud-controlled floating license is stored.
  • LicensePassword.dat : This file contains the license number and password when you saved them in the License management dialog box. The password is encrypted but still the information is in the file and any Parabuild installation can decrypt the information. You can copy this file to another system and that will allow activation of Parabuild even when the license number and password is not known. If your license and password have come into the wrong hands this way (for example an employee that left), you can reset your password in the license portal : https://parabuild.softwarekey.com/solo/customers/.
    To login on the license portal you will need your account number or the registered email address, and the account password. If you do not know this information then contact your reseller. If you do not have a reseller then contact Parabuild directly at : [email protected]
  • ParabuildSoftwareLicense-EN.htm and Parabuild End-User License Agreement (English).pdf : These files contain the latest End-User License Agreement to which you need to agree to before using Parabuild. The htm file is displayed when Parabuild is installed, is opened the first time or after an update. You need to click on I agree for Parabuild to start.
  • Session logXX.txt : These files will contain the commands and warnings that happened in the last 10 Parabuild sessions. They are used to track back what happened during the session so that issues can be found and debugged by Parabuild technicians.