Launching Cincom® VisualWorks®
- The “standard” way
- VisualWorks-1.15 (preview)
- VisualWorks Launchpad
The Standard Way
On Windows, .im extensions are associated with VisualWorks.exe. The VisualWorks.ini file (found in the same directory as the .exe) contains the image signature, which identifies the version of the image as well as the full path and vm to run it. Normally you edit the .ini file to reflect your installation.
So an entry might look like:
77 01 c:\Program Files\Cincom\vw7.7.1\bin\win\vwnt.exe
Launching a 64-bit image is accommodated too:
79 128 c:\Program Files (x86)\Cincom\vw7.9\bin\win64\vwnt.exe
You provide an entry for each version of VisualWorks that’s installed, or even an entry for each version of the image you may be using. You can usually use newer VMs on older images within the major family.
This variant can be found in the preview/bin directory on Windows platforms. This is especially useful if you are a VWDev participant and need to distinguish between versions at a finer granularity. Note that you can find the VisualWorks-1.15 functionality on OSX and Unix platforms as VisualWorks.sh in the preview/bin directory.
The differences are:
- A more detailed signature
- Specification of the home directory as well as the correct VM (the second parameter after the “?” is used to set the VISUALWORKS variable)
An entry in this ini file looks like: (each entry all on one line)
79 0 0 0 C:\Program Files (x86)\Cincom\vw7.9\bin\win\visual.exe?C:\Program Files (x86)\Cincom\vw7.979 128 0 0 C:\Program Files (x86)\Cincom\vw7.9\bin\win64\visual.exe?C:\Program Files (x86)\Cincom\vw7.9
The last two numbers in the signature are used in identifying interim builds, as in the weekly builds in the developer program. Some recent build entries I have look like this:
79 0 20 4 S:\Cincom\vw7.10\bin\win\visual.exe?S:\Cincom\vw7.1079 128 21 4 S:\Cincom\vw7.10\bin\win64\visual.exe?S:\Cincom\vw7.1079 0 04 4 S:\Cincom\vw7.9.1\bin\win\visual.exe?S:\Cincom\vw7.9.179 129 04 4 S:\Cincom\vw7.9.1\bin\win64\visual.exe?S:\Cincom\vw7.9.1
This is useful for making sure that you are running the exact new VM along with the development build. This is what I am using currently for testing our weekly development builds.
A third way to start an image is with the VisualWorks Launchpad. The Launchpad is a very useful application that lets you create and name images (32 or 64 bit), and also store them in the proper manner on Windows and OSX (a directory in a read-write area). The icon to start the Launchpad gets installed on your desktop, so it is easy to find, and it makes it simple to find and create new images. The Launchpad will evolve to be even more useful for configuring and creating images. The Launchpad also has a configuration file, and is rather capable, flexible and configurable. A development engineer is working on an article describing this, so I will not delve into it here.
I hope this article gives you some ideas on how to more effectively start and use VisualWorks.
If you have any questions, please send them to me at firstname.lastname@example.org.