Each SourcePro C++ release is a replacement for, not an upgrade to, the previous version. Always perform an installation into a new area, and not into the same install directory as a previous version.
Module dependency checks are not performed in the Installer. If you attempt a build with dependencies on uninstalled components, RCB displays a warning message.
There is no uninstaller for Windows or UNIX. To uninstall SourcePro, simply delete the installation directory. On Windows, no registry entries are made. On Windows, you may need to delete the desktop shortcut and the Start Menu group for SourcePro C++ 12.0.
In the Installer Product Selection dialog box, the scrollbar arrows are very slow. You can grab the scrollbar or click on the scrollbar area to rapidly move through the list.
The user needs to have administrator privileges to run the installer. If you don't have administrator privileges, the installer will complain when you choose an install location. A solution is to create a new directory, right-click it to bring up the Properties dialog, and choose the security tab, where you can give yourself full privileges for that directory. You can then install from this new location.
UNC installation paths not supported. For network installs on Windows, using a UNC path to specify the installation location is not supported. Rather, create a mapped network drive to the desired network location. For the mapped network drive, be sure to check "Reconnect at Logon" checkbox. If this option is not selected, the mapped network drive will not appear when browsing for an install location.
Unknown or non-verified publisher message. When launching the installer, the User Access Control (UAC) dialog may indicate that the installer executable is from an "Unknown" publisher, i.e. the publisher cannot be verified. You may also encounter this message when launching RCB on some Windows platforms. This message can be safely ignored.
On 64-bit machines, installer may fail to launch. When inserting the 12.0 installer DVD into a Windows 64-bit machine, the installer may fail to launch automatically. To launch the installer manually, go to the root directory of the DVD and run setup.bat.
The installer will warn the user that the "unzip" utility is not present in the system path. The installer will then proceed without issue. This warning message is purely cosmetic.
UTF-8 locale results in erroneous text boxes that may obscure GUI. On Solaris, when invoking the installer with the LANG environment variable set to a UTF-8 locale (i.e. en_US.UTF-8), a series of small boxes with the word "iiimx" and/or "English/European" may be generated while navigating through the installer, possibly obscuring portions of the GUI. These boxes can be suppressed by unsetting the LANG variable or setting it to another locale (i.e. C, POSIX, en_US.ISO8859-1).
Installer leaves behind several temporary files. Approximately a dozen files are left behind in the temporary directory after the installer exits, each about 300 bytes in size. This is caused by a bug (#IOA-000064318) in the software suite "InstallAnywhere" used to create the installer. The default temporary directory is created in /tmp with the name installer.dir.<process> where process is the process ID of the executing installer.
Copyright © Rogue Wave Software, Inc. All Rights Reserved.
The Rogue Wave name and logo, and SourcePro, are registered trademarks of Rogue Wave Software. All other trademarks are the property of their respective owners.
Provide feedback to Rogue Wave about its documentation.