PillarSoft

Add any setup strings for objects you need to create in this field. These are Rexx "SysCreateObject" calls and you can add as many as you want as long as they are on separate lines. The variable "InstDir" can be used in your setup string to denote the installation directory name without the trailing slash.

• First line - one setup string (a folder maybe)
• Second line - another string (your program object/icon)
• Third line - another string (your readme.1st object/icon)
• and so on...
• and so on...

I'm sure most of you are familiar with them but... just in case... Example setup strings are included and loaded when the program is started and will continue to load at startup until such time that new default settings are saved. When you save default settings you will be saving any setup strings in the entry field over the top of the old ones. If the original strings are in the entry field they will be saved otherwise your changed strings will become the defaults loaded at startup.

In order for the uninstall script to work, all of your creations will need an OBJECTID included in the setup string. The setup tool will warn you if an OBJECTID is missing but will still build the archive. The three example strings included at program start show how to create a folder and two program objects. Feel free to modify the examples to fit your installation requirements. Remember to do them in the proper order. You'll need to create the folder (if you need one) before you can place program objects in it.

A one line string isn't as pretty as a nicely formatted one in a cmd file but it will work this way. The installer doesn't know what your strings are but can execute them if they are formatted properly. Take a look at the examples, the ini.rc file in your \os2 directory or the OS/2 Procedures Language 2/Rexx for some further insight into setup strings.

Remember: Choose OBJECTID's carefully. Do not use the same ones anyone else may use. This will only cause trouble between applications. Your OBJECTID's should be something no one else will use so be sure to choose wisely. Also, be sure to change or delete the examples before you build an archive. You won't want any of them to go with your application.