CleanSweep 95 version 2.02 README File Thank you for purchasing Quarterdeck's CleanSweep 95! This file includes tips and information to help you get the most out of the package, a listing of some known problems, and last-minute corrections that did not make it into the manual. We recommend that you print this file and keep it with your printed documentation for future reference. Table of Contents Late Changes and Additions What's New in Version 2.02 Information Specific to Windows NT 3.51 Info and Tips Known Issues Contacting Quarterdeck Late Changes and Additions - The CleanSweep Install Monitor now has an option to manually start and stop the logging process. To activate this feature, simply maximize the Install Monitor program from the Windows 3.1x icon or the Windows 95 system tray, and then select the "Start Logging" option. The Install Monitor will ask you to confirm that you want to start logging changes made to the computer, and then minimize to a flashing icon. To stop the logging, click on the flashing icon, and then choose the "Stop Logging" option. Install Monitor will then record all changes that were made to your system. What's New in Version 2.02 - CleanSweep now supports Windows 3.1, Windows for Workgroups 3.11, Windows 95, and Windows NT 3.51 Server and Workstation. In addition, CleanSweep 95 is currently compatible with the Windows NT Preview Shell and has been tested with early betas of Windows NT 4.0. - An integrated install routine, which means that there is one set of install disks for three separate versions of Windows (Windows 3.x, Windows NT and Windows 95)! - Improved registry awareness when uninstalling 32bit applications in Windows NT and Windows 95. - A new, faster compression engine for backing up, archiving, and transporting applications and files. This also resolved several issues, including a situation when backing up to a floppy disk would not complete properly. - A more robust Install Monitor which includes support for the AutoPlay feature of Windows 95 and enhanced automated activation features. - The Orphan Finder is improved for enhanced accuracy. - CleanSweep 95 2.02 has enhanced support for 16-bit applications. - CleanSweep's ability to handle alternate shells has been augmented. Supported shells include PC Tools 2.0, Sidebar, the Windows NT Preview Shell, and Norton Navigator for Windows 95. - There is a new, completely updated Help file for CleanSweep 2.02 for greater online assistance for our users! Information Specific to Windows NT 3.51 - The Windows NT version of CleanSweep 95 does not contain a Usage Monitor or Install Monitor. These monitors will be implemented in a future release of CleanSweep. - CleanSweep for NT currently supports the Intel x86 platform only. - The Windows NT version of CleanSweep 95 does not contain file viewers since we currently rely on the viewers provided by Windows 95. Info and Tips CleanSweep and Slack Space When CleanSweep displays the amount of disk space that will be saved by deleting programs or files, it will often note that more disk space will be saved than the files seem to occupy. This is a result of the scheme that is used to store files on a disk. A physical hard drive contains one or more "partitions". Each partition is subdivided into "clusters", whose size is largely dependent on the size of the partition; sizes of 4K to 32K are common. Each file on your hard drive is stored in one or more clusters. Regardless of how much of the cluster is used, the whole cluster is allocated to the file; thus a one-byte file might take 8K of storage space on your hard drive. A file (or the last portion of it) rarely fills a cluster exactly; instead, it is common for many clusters to contain "slack" space - the difference between the size of the cluster and the amount of space that a file is using. A great deal of space may be reclaimed from your hard drive by deleting a large number of files, even if the files themselves are relatively small. Stacker 4.0 and DoubleSpace 3 contains technology that dramatically reduces the amount of slack space on your hard drive. CleanSweep's calculations may not take Stacker's savings into account. CleanSweep's View Option (Windows 95 and 3.x only) CleanSweep 95 uses different file viewers for Windows 3.1x and Windows 95. The Windows 3.1 file viewers are included with CleanSweep and do not require any special Windows configuration. In Windows 95, CleanSweep's View option support is limited to those viewers supplied by Windows 95 itself. Some Windows installation options, including floppy disk distributions of Windows 95, do not install all of these viewers by default. When you try to view a file for which your Windows viewer is not yet installed, CleanSweep will notify you and, at your option, lead you through the process of installing the complete set of Windows viewers. The following file formats are supported by the Windows 95 QuickView feature: Ami Pro; ASCII; Bitmaps, Cursors, and Icons; CorelDraw 2.x-5.x; Micrografx .DRW; Programs (.EXE, .DLL, and .COM); Freelance Graphics for Windows; Microsoft Multiplan 4.x; Microsoft Word (all versions through 7.0, including DOS and Windows); Microsoft Write; Microsoft PowerPoint; Quattro and Quattro Pro (for both DOS and Windows); Rich Text Format (RTF); WordPad; Lotus 1-2-3 1.x-5.x (for both DOS and Windows) Lotus Symphony 1.0; VP-Planner; Mosaic Twin; Generic WKS format; MS Works (spreadsheets, database, and word processing for both DOS and Windows); Windows Meta File (.WMF); Microsoft Word for Macintosh (4.x, 5.x); WordPerfect 4.x-6.x (for both DOS and Windows); Microsoft Excel 3.x-5.x; Microsoft Excel Charts 2.x-4.x; and Hex. Oddly, Windows 95 provides no viewers for .ZIP and other forms of compressed files, nor for .GIF, .TIF, or .PCX graphics files; nor for .DBF or other database files. There is no viewer support in Windows NT, although this is expected to be improved by the inclusion of the QuickView feature in Windows NT 4.0. Install Monitor (Windows 95 and Windows 3.x only) The Install Monitor provides an "append" feature, so that you can link and log the installation of two programs that might not be installed at the same time. For example, you might install a database program, and later install a program to produce specialized reports from that database. When you monitor the installation of the reporting program, you might like to use the Append feature so that it's easy to uninstall both programs together if you wish. You may still use CleanSweep's standard methods to uninstall one program at a time. The Install Monitor is very helpful to CleanSweep's Uninstall and Move functions. In particular, CleanSweep requires the assistance of the Install Monitor to correctly modify the location of files listed in the Windows Registry. Usage Monitor (Windows 95 and Windows 3.x only) When you start CleanSweep, the Usage Monitor will alert you if there are files that have been unused for the period of time you specify in Options / Configure CleanSweep / Usage Monitor / Alert. The File Usage Monitor icon, in the lower right corner of the screen, will also flash if you have checked the "Alert if any file is unused for days" option. If you change your system's internal clock to a date earlier than the current date, CleanSweep's File Usage Monitor will not adjust its tables of files to reflect the change. For example, a file that is listed as being unused for 10 days will continue to be listed as such even if you adjust your system's date to some point 10 days in the past. Conversely, if you switch your system clock to some point in the future, the number of days that the file has been unused will be increased. There is no way to reverse this increase. CleanSweep's File Finders By default, CleanSweep will search local hard drives with its File Finders. You may choose to include floppy drives, network drives, or removable drives in the search. CD-ROM drives may also be included in the Duplicate File Finder. Files created during the CleanSweep session will not be displayed in various CleanSweep Finders until you close CleanSweep and start it again. Orphan File Finder According to CleanSweep, an orphan program in Windows 95 is a program that is not on the Start menu or one of its submenus. In Windows 3.1 or Windows NT, an orphan program is a program that is not referenced in the shell. If you are using the Orphan Finder with the PC Tools 2.0 multiple desktop feature, only the programs referenced in the currently active desktop will be included in CleanSweep's analysis. View Savings Report CleanSweep's View Savings Report is intended to give a general overview of CleanSweep's usefulness, rather than to detail every action on your hard drive. When you delete a program or file and back it up, CleanSweep will calculate the space saved as the amount of space taken by the uninstalled components, minus the size of the backup, and will add this to the Savings log. However, when you delete the backup, CleanSweep will not add this figure to the savings log. Similarly, if you choose to restore the component, CleanSweep will not subtract the original savings from the savings log. In addition, if you choose to place the backup in a location other than the default backup folder, the size of the backup will not be included in the savings log. If you delete a file from a source drive and back it up to a different target drive, the log will reflect the savings on the source, and will not account for size of the backup on the target. (In many cases, the target will be a floppy drive.) Known Issues If you are using the Norton Protected Recycle Bin along with CleanSweep, and you encounter an error dialog from CleanSweep that reads "Error creating backup of the selected items. Drive is possibly full. [Error 16].", empty both the Windows Recycle Bin and the Norton Protected Recycle Bin, close and restart CleanSweep, and retry the operation. This is due to the way Norton Utilities protects deleted files. If using Windows NT with an HPFS volume, you should not place CleanSweep backups in a directory on the HPFS volume that does not conform to the 8.3 standard naming conventions of DOS (ie. CLNSWEEP.DIR). CleanSweep's Installation Monitor may have difficulty logging the installation of the Microsoft Plus Pack and other system-level software that reboots the machine before the installation process is complete. Such software does not install itself in the same way that applications do. We recommend extra care in uninstalling these packages. If you are installing CleanSweep 95 on a Windows 95 system, and you are experiencing sluggish performance from the install program, please try emptying the Norton Protected Recycle Bin. If that does not improve the performance, restart Windows 95 in Safe Mode and proceed with installation. When you are asked if you want to restart the machine, allow it to restart normally. Windows (95, 3.x and NT) will not permit you to delete files that are currently in use. Therefore, CleanSweep is unable to delete files that are in use. Do not move long file names to a drive (file system) that does not support long file names. If you transport a program from a Windows 95 machine to a Windows NT or Windows 3.1x machine, the Start Menu and Desktop components from Windows 95 will not be added to the Windows NT or 3.1x shell. The network decoy feature will not run if a copy of CleanSweep is already running. A network decoy created by Windows 95 or Windows NT will not run on a Windows 3.x machine. In addition, you should not run decoys created in Windows 3.x on a Windows 95 or Windows NT machine. Installing CleanSweep to a drive that is not available when Windows 95 loads will cause Install Monitor and Usage Monitor to report an error. Examples of these devices include Bernoulli drives and some ZIP drives. Microsoft Office 95 users who have upgraded from Microsoft Office 4.x will notice that some Word 6.0 objects are listed as Orphaned OLE Objects. This is not an error. Microsoft's upgrade program simply neglects to remove these. You can safely remove these orphans with CleanSweep with no ill effects. CorelDraw 6 users may notice that CleanSweep 95 flags the Corel Presents Runtime Player as an Orphaned OLE Object. This turns out to be a issue with the manner in which Corel 6 makes registry entries, and cannot be corrected by CleanSweep 95. If you have problems printing a CleanSweep 95 log or report, you can save the report to a text file and then print it using your favorite text editor or word processor. There have been reports of incompatibilities with some Epson Stylus inkjet printers. If you have a system that dual-boots between Windows 95 (or Windows NT) and Windows 3.1, you should run the CleanSweep Install in each environment in order to use both the 16-bit and 32-bit versions of CleanSweep. Windows 3.1x has a limit of 8,192 items that can be displayed in a list box. If you have more than 8,192 files that are to be listed in the Low File Usage Finder, then only the first 8,192 files will be displayed. The Low File Usage Finder will list all files in any folder called BACKUP. This can be a issue with some tape backup software. Contacting Quarterdeck Visit the Quarterdeck forum on CompuServe (GO QUARTERDECK), or Quarterdeck's World Wide Web site (http://www.qdeck.com/). Update news and patches, if any, will be available there. Those using more traditional means of communication should contact: Quarterdeck Corporation 13160 Mindanao Way Marina del Rey, CA 90292-9705 USA (310) 309-3700 (Sales) (310) 309-4250 (Technical Support)