Problem initializing the Smart Links database
If UnInstaller keeps rescanning the same file soon after starting the UnInstaller, you may be experiencing an infrequent, but known problem with initializing the Smart Links database update. This scan error reoccurs at a specific file, usually a .DLL file, but the file being rescanned is different for each customer. The problem seems to be caused by having too little disk space to store temporary data or by database corruption. The only fix at the moment is to reboot the computer, remove UnInstaller 4.5, reboot the computer, and then reinstall UnInstaller 4.5.
Norton Utilities Recycle Bin
All files deleted using UnInstaller 4.5 will be protected and stored in the NProtect virtual folder under C:\Recycled. If you have the Norton Utilities Protected Recycle Bin option installed on your computer you should empty the Norton Protected Recycle Bin periodically to regain disk space. Also, if you use the UnInstaller 4.5 Installation Monitor to monitor application setup programs, you will see temporary setup files added in the C:\Recycled\NProtect folder in the Installation Monitor report.
Installation Monitor
When an application's setup/installation program is finished, typically it asks you whether you want to start the application. If the UnInstaller 4.5 Installation Monitor is active, let the setup program finish without starting the application. If a setup program does not give you a choice and launches the application automatically, close the application immediately. The Installation Monitor cannot complete its analysis and generate the database information required by UnInstaller until the application is closed.
Installation Monitor and application suites
We recommend that you temporarily deactivate the Installation Monitor before installing a software suite. Installation of suites, such as Office '97 or Lotus SmartSuite, takes a long time and the monitoring process extends that time. The next time that UnInstaller 4 scans your hard drive, UnInstaller 4 will automatically recognize the suite and its components. This approach saves you time, and ensures you a complete knowledge of your system.
Update issues
If you use CompuServe or America Online as your Internet service provider, start the service and access the Internet before running the Update function from the main UnInstaller screen.
Using Update
UnInstaller requires a specific version of Oil Change in order to update itself. UnInstaller 4.5 will check your version of Oil Change upon installation and offer to install a modified version, if necessary.
If you already have Oil Change installed and choose NO to the newer version, you will be able to run Oil Change but the UnInstaller 4.5 Update function will not work. If you receive an error message when you click the Update button, or if you choose not to install Oil Change during your initial install, you will need to install the version of Oil Change that is included on the UnInstaller CD-ROM.
To install Oil Change:
- Insert the CyberMedia UnInstaller 4.5 CD-ROM in the CD-ROM drive and close the drive door. If the Windows 95 AutoPlay feature is enabled, CyberMedia UnInstaller 4.5 Setup screen will come up automatically.
- If you don't see the CyberMedia Setup screen, click the Start button, select Run, click the Browse button then select your CD-ROM drive from the Look In drop-down box.
- Double-click the file, SETUP.EXE, then click OK in the Run dialog box
- On the CyberMedia Setup screen, click Install Other Software Products.
- Click the CyberMedia Oil Change icon to start the Oil Change installation program.
The Oil Change Setup program will provide you with detailed installation instructions and suggestions.
Note: If you are running the Windows NT operating system, you will not be able to use the Update feature.
Changing Update connection settings or using Update with a proxy server:
- Run Oil Change and select the Options button.
- In Options, click the Connection tab.
- Change connection and proxy server settings, as required.
Microsoft's COMCTL32.DLL file
Installation of UnInstaller 4.5 installs the latest COMCTL32.DLL file distributed by Microsoft. If your computer's COMCTL32.DLL has not previously been updated to this latest version, UnInstaller 4.5 creates a backup of your system's original file [COMCTL32.BAK] in the Windows\System directory and installs the latest copy of the file. Replacing the COMCTL32.DLL file requires UnInstaller 4.5 to reboot your system.
Standard protected Windows files
In most cases, you should not delete protected files. During analysis of some applications that contain shortcuts, or links, to various standard Windows files, you may receive one or more messages that the standard Windows file is protected and you will be asked if you want to delete it. If you choose to delete these files, both the file and the shortcut, or link (LNK) file will be deleted. If you do not choose to delete these files, UnInstaller 4.5 will only delete the shortcut, or link (LNK) file, that points to the file; UnInstaller 4 will not delete the actual file (pointed to).
Transporting applications
UnInstaller 4.5 only supports the transport of applications from one PC to another PC with the same operating system. For example, if the transported application's source machine is running Windows 95, the destination machine must also be running the Windows 95 operating system.
SmartLinks database-building
During the scan of your system, UnInstaller 4.5 may try to access the A:\ drive. This is a result of analyzing shortcuts (LNK files) found in the \Windows\Recent folder. Any OLE drag/drop activity and other embedded objects that have pointed to the A:\ drive will be sought out during the scan. This scan does not require a disk to be in the drive.
"No valid files found" error message
During analysis of one or more applications, you may receive the following error message: UnInstaller 4 cannot complete the operation because no valid files were found. This message occurs for two reasons:
- One of the files selected for analysis is on an unscanned drive.
- The main application directory could not be determined.
During Move, the main application directory may not be determined if the program group selected has shortcuts (LNK files) that point to two different directories. For example, many programs add a shortcut to the application's uninstall program and that executable may be located in the Windows directory, not the program directory. The solution is to select the main program shortcut in the program group for analysis only. During Transport, the main application directory may not be determined if an application installs more than one directory on the root drive. For example, Test application installs two directories: C:\Program Files\Test and C:\Extra.
Hardware devices and related drivers
It is recommended that you not use UnInstaller 4.5 to uninstall hardware programs, devices and/or related drivers. UnInstaller 4.5 has no way to determine what drivers are replaced during the installation of a hardware program, therefore deleted drivers cannot be replaced when the hardware program is removed. Hardware related programs should be removed by Add/Remove Programs in the Control Panel, if available. Otherwise, remove them manually after being properly advised by a representative of the manufacturer or after consulting the manual for the product. Hardware drivers should also be removed through Control Panel or manually after being properly advised by a representative of the manufacturer.
Windows 3.x items
The UnInstaller 4 manual and Help File make references to a Windows 3.x Items group available in the File Cleanup utility. This option is not available.
Conversion of previous UnInstaller custom.rul files
Your custom.rul file, generated by Setup Monitor from previous versions of UnInstaller, can be converted for use with UnInstaller 4.5 by following these instructions:
- Launch an MS-DOS window.
- Change directories to the UnInstaller 4.5 application directory (CD \Program Files\CyberMedia UnInstaller).
- Type the following command: rconvert /lm
- Press the Enter key. This will bring up the RUL File Update dialog.
- Select "Add RUL...".
- Browse for the custom.rul file in the UnInstaller 3.x application directory.
- Select the custom.rul file and select OK.
- Highlight that file in the RUL File Update dialog.
- Select the Convert! button.
When the program is finished, a small error dialog will appear. It reads, "Final error returned: 0." This is normal and expected. Close that dialog box, exit the RUL File Update dialog, and the conversion will be complete. A custom.dtb will be created or the existing custom.dtb will be updated in the UnInstaller 4.5 directory.
File Links Properties tab for files on unscanned drives
If you right-click an application file (.EXE file) or application extension file (.DLL file) in Windows Explorer and choose Properties, you will see a File Links tab on the Properties dialog. UnInstaller 4.5 uses this tab to display File Links, which are files that are "Smart-Linked" to the selected file. If any of these files is located on a drive that has not been scanned by UnInstaller 4.5, the proper File Links will not be displayed.
Quick View
Quick View is an optionally installed component of Windows 95 that lets you view a document without starting the program that created it. If you want to check the contents of a file quickly, you can do so within UnInstaller if you have Quick View installed.
|
