Is Uninstaller 4 backward-compatible with Uninstaller 3.5?
UnInstaller 4 can be used to restore backups and archives created with UnInstaller 3 version 3.5 (32 bit). UnInstaller 3 version 3.5 backups and archives are restored using the same procedure as UnInstaller 4 backups and archives. See Using Restore in the Help file for more information about restoring backups and archives.
How does Uninstaller 4 work on a Dual-Boot system (Windows 95 and Windows 3.1x)?
On a dual-boot system you have three distinct operating systems: DOS, Windows 3.1 and Windows 95. When UnInstaller 4 analyzes your system it uses the operating system it is running under -- Windows 95. The Windows 3.1x operating system is not loaded and its files appear as another application rather than as an operating system. Therefore, UnInstaller 4 should not be used in Windows 95 to delete applications installed under Windows 3.1x.
UnInstaller 4 can remove any application installed under Windows 95 (including MS-DOS window, 16-bit and 32-bit applications); however, it cannot remove applications installed under Windows 3.1x. If you are going to continue to run Windows 3.1x, you should use UnInstaller 3, the 16-bit version, to Delete, Move, Archive, Transport and Restore files for Windows 3.1x.
Should I keep my 16-bit version of UnInstaller after I have installed UnInstaller 4?
You should remove UnInstaller 3, the 16 bit version, if you have only Windows 95 running on your computer and do not have a dual-boot system (running both Windows 95 and Windows 3.1).
To remove UnInstaller 3, 16-bit version, use the UnInstaller 3 "UnInstall" program.
Warning: This program gives you the option to delete or keep the archives and backups created with UnInstaller 3, 16-bit version. Please read the restrictions below about restoring these archives/backups.
I have a dual-boot system (Windows 95 and Windows 3.1x), should I keep my 16-bit version of UnInstaller after I have installed UnInstaller 4?
Yes. Use UnInstaller 3, 16-bit version, to delete, move, archive and transport any applications installed while running Windows 3.1x. All applications installed under Windows 95 can be handled by UnInstaller 4.
Use UnInstaller 3, 16-bit version, to restore any archives or backups
created with UnInstaller 3, 16-bit version under Windows 3.1x.
How does Uninstaller 4 work with Norton Utilities Protected Recycle Bin?
If you have the Norton Utilities Protected Recycle Bin option installed on your computer, all files deleted using UnInstaller 4 will be "protected" by this Norton Utilities option and stored in the NProtect virtual folder under C:\Recycled. If this option is installed, you should periodically empty the Norton Protected Recycle Bin to regain disk space.
If you have the Norton Utilities Protected Recycle Bin option installed on your computer and you use the UnInstaller 4 Installation Monitor to monitor application setup programs, you will see (in the Installation Monitor report) files added in the C:\Recycled\NProtect folder. These are only temporary setup files, normally deleted after the installation of a program; this Norton Utility option protects these files and adds them to the Norton protected Recycle Bin. Again, with this option installed, you should periodically empty the Norton Protected Recycle Bin to regain disk space.
I am getting message that the standard Windows file is protected, what should I do ?
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 will only delete the shortcut, or link (LNK) file, that points to the file; UnInstaller 4 will not delete the actual file (pointed to). In most cases, you should not delete protected files.
I am having trouble transporting applications between my Windows 95 and Windows NT computers, what is wrong ?
UnInstaller 4 only supports the transport of applications from one PC
to another PC with the same operating system. For example, the
transported application's source machine and destination machine must
both have the Windows 95 operating system. UnInstaller 4 also
transports applications between PCs running Windows NT 4.0.
Why is the SmartLinks scan accessing my floppy drive ?
During the scan of your system, UnInstaller 4 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. This scan does not require a
disk to be in the drive.
I am getting a "No valid files found" error, what is happening ?
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: 1.) One of the files selected for analysis is on an unscanned drive. 2.) 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.
How do I convert 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. Follow these instructions:
- Launch an MS-DOS window.
- Change directories to the UnInstaller 4 application directory (CD \Program Files\UnInstaller 4).
- 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. Simply close that dialog, and 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 directory.
|