Complete Program Deleter for Windows Version 4.0

Note: If you do not have word wrap on, please click on 
EDit/Word wrap to view this document properly.

	Have you ever installed a program on your hard drive using the INSTALL (or SETUP, or whatever) utility that came with the program, decided that you did not like the program, and then tried to remove it? If you are like me (and most other computer users), you probably found that you only recovered a fraction of the hard disk space you had before you installed the program. This is because the installation procedure scattered dozens (or even hundreds) of files all over your drive. Some went into subdirectories created by the installation process itself, and some went into subdirectories that already existed, such as the \WINDOWS and WINDOWS\SYSTEM subdirectories. You may also have found that you did not recover all of your RAM memory that you had before you installed the program. This is because many of the installation programs modify AUTOEXEC.BAT, CONFIG.SYS, WIN.INI, and SYSTEM.INI to load programs or drivers into memory automatically.
	If you simply delete all the files you can file that seem to be related to the program you wish to remove, you may find additional problems. You may get  error messages when you tried to start up your computer again, or tried to run Windows. You may even have found that you could not run Windows at all because it said that you were missing vital files. The reason for this is that the AUTOEXEC.BAT, CONFIG.SYS, WIN.INI, and SYSTEM.INI files are still trying to load the files you deleted. After you delete the files associated with your program (those that you can find), these configuration files cannot find them when they try to load them. If you try to restore the AUTOEXEC.BAT, CONFIG.SYS, WIN.INI, or SYSTEM.INI files manually, you may accidentally delete some lines necessary for other programs to run, making it impossible to run programs that you really need.
	Complete Program Deleter is the solution to this problem. It will delete all the files installed by your program's installation program, remove all subdirectories created by that program, and restore the AUTOEXEC.BAT, CONFIG.SYS, WIN.INI, and SYSTEM.INI files to their original condition. (Some restrictions may apply in some cases. See the "Limitations" section below.)

Paying for Complete Program Deleter

	Before getting on to the details of how to operate Complete Program Deleter (CPD), a few words about money are in order. This program is being distributed as shareware. This does not mean that it is free. It means that you are given the program to try it out for a 30-day trial period to see if you like it enough to continue using it. ("Nag screens" will remind you to pay for the program.) An additional 30 days after the trial period ends, the program will actually stop working until you pay for it. If you do decide that CPD is worth using, you are required to pay for it by sending $25.00 to:

                    Leithauser Research
                    3624 Royal Fern Circle
                    DeLand, FL 32724

	If you install CPD on several computers, you need to register it for each computer. If you have a large number of computers, contact Leithauser Research for site licensing arrangements.
	Once you pay for the program, you will receive a letter telling you how to turn off the nag screens and restore the program functioning if your trial time has run out, you will receive a disk containing the latest version of Complete Program Deleter, in case any improvements have been made recently. This disk will also be full of other handy shareware programs created by Leithauser Research. (Be sure to specify that you want the Windows disk if you want Windows programs.) As with all shareware, you can try out these programs to see if you they are worth paying for. In addition to all these incentives, if you pay for this program we will be able to afford to spend more time creating additional helpful shareware programs and also improving this one.
	Regardless of whether you decide to continue using CPD, you are free to distribute CPD and the other shareware programs to all your friends and associates, provided that you include all files that came with CPD (WCPD.EXE, WCPD.TXT, etc.).
	Now that we have that out of the way, we can get on to the good stuff.

Operation

	When you run CPD, you will see the main menu. To make a selection from this menu, just click on the button of your choice. (You will also find that the options on the buttons are duplicated in the menu at the top of the main form.) The options controlled by these buttons are explained below. Note: you may notice that some of the buttons have their text in gray instead of black, indicating that you cannot use that button. This is because the operations must be performed in a certain order, and disabling the buttons in this way prevents you from trying to do things in the wrong order. For example, you cannot create an AFTER file until you have created a BEFORE file, and you cannot delete safety files until CPD has created some.

Quick Instructions

	This option simply gives you a one-screen explanation of how to use the program. It is not intended to replace reading these instructions, which include information on safety procedures as well as much more detailed information on how to use the program. However, it does serve as a quick start to using the program and it can be a helpful reminder of the basic procedure while using CPD.

Create BEFORE File

	When you are about to install a new program, especially one that uses its own installation, select this option. Note: It is recommended that you exit any other Windows programs you are running before you use CPD to create a BEFORE or AFTER file. This is because the other programs may be creating files while they are operating. For example, a communications program may be downloading a file. This can cause problems for CPD. If  a file is created by another program between the creation of the BEFORE and AFTER files, CPD may think that these files were created by the installation process of the program you are about to install. These files could therefore be erased if you later choose to delete the program you are about ot install.
	CPD will ask for the name of the program you are about to install. Type the name and press ENTER. You do not need to be precise about this name. Just type something short that describes the program. This name is just used to refer to the program on future menus.
	CPD will then ask for the drive or drives that the program is being installed on. Normally this will be C, the default answer. If the program is being installed on another drive, such as drive D, type that drive letter before clicking on the Ok button or pressing the ENTER key. If the program will be installed on several drives, type the letters of all the drives and then press ENTER. For example, if the program is going to be installed on drives C and D, type CD and then press ENTER. This is most likely to happen is you have Windows on one disk, such as C, and you install the Windows program on another drive, such as D. In this case, the program directory and most of the files would be installed on drive D, but the program's INI and DLL files would probably be installed in the WINDOWS and WINDOWS/SYSTEM directory on drive C.
	CPD will then create a BEFORE.DAT file for the program you are about to install. This file contains information about your disk configuration before the installation of the new program. This BEFORE file can be fairly large (several hundred Kilobytes), but it will not be on your disk long (see Create AFTER File below). CPD will display information on what it is doing as it creates this BEFORE file. After creating this file, CPD will return to the main menu. When you get back to the main menu, you can minimized CPD by clicking on the minimize button in the upper right corner of the main window to get it out of the way when you install your new program.

Create AFTER File

	After you create the BEFORE file and minimized CPD, install your new program using that program's installation procedure. Then run the new program to allow it to create any configuration files that it creates the first time it is run. Once you have done this, exit the new program and restore CPD by double-clicking the CPD icon. Click on the "Create AFTER File" button on the main menu. CPD will then create an AFTER file that describes the changes that were caused by the installation of your program. This file will be several kilobytes in size. Because you can have many AFTER files (one for each program you install), the AFTER files are numbered, such as AFTER1.DAT, AFTER2.DAT, and so on. CPD will also delete the BEFORE file that described the configuration of your disk before your new program was installed. You can have only one BEFORE file on your disk at a time.
	CPD will display a report of what it is doing as it creates the AFTER file. It also will display a report after it has created the AFTER file listing the changes it found on your disk.
	Once you have created the AFTER file for your new program, you can either exit CPD from the main menu or you can immediately delete the program using the "Delete Program" option on the main menu if you have already decided that you do not want it.
	It is very important that you create the AFTER file using CPD as soon as you have installed your new program and run it once. If you install or run any other programs between the time you create the BEFORE and AFTER files, any files created in that process and any changes in AUTOEXEC.BAT, CONFIG.SYS, WIN.INI, or SYSTEM.INI will be lost if you decide to delete the program you have just installed. CPD will warn you to create an AFTER file if you try to exit it after you have created the BEFORE file if you have not created the AFTER file.
	On some extremely rare occasions, CPD may be unable to read a directory that it found during creation of the BEFORE file. This is most likely to occur if the directory was deleted after the BEFORE file was created and before the AFTER file is created. In this case, CPD will display a message saying that it cannot read the directory and ask you to click on the Ok button (you can also press ENTER). CPD will then resume creation of the AFTER file.
	Note: The creation of the AFTER file may take several minutes for very large drives or slow machines. During some periods of this time, no operations (such as hard drive access) may be visible, even though the program is working. CPD will not allow other Windows operations to occur during this this time, to prevent the creation of files which can confuse CPD while it is storing file names. Your computer is not locked up. DO NOT reboot or otherwise attempt to exit CPD during this time. This could leave open files on your hard drive, with undesirable results.

Delete Program

	If you decide to delete a program for your disk, run CPD and select this option from the main menu. CPD will show you a list of the programs that you have created AFTER files for. Select the program you want to delete from your hard disk and click on the Ok button. You can cancel the "Delete Program" operation by clicking on the "Cancel" button or pressing the Esc key.
	Once you select a program to delete, CPD will load the AFTER file containing the information about the changes that were made in your hard disk when the program was installed. It will delete any subdirectories that were created when the program was installed, as well as any files these subdirectories contain. If the program's installation utility added any files to any subdirectories that already existed (such as the root directory or the Windows System subdirectory), it will delete these files also. Before doing this, however, it will ask you if you want to confirm deletion of each of these files in preexisting directories. If you Yes, it will ask for your permission to delete each file by name before deleting it. If you select No, CPD will immediately delete all these files without asking for your permission for each file. Note that only files added to your drive between the time you created the BEFORE file for that program and the time you created the AFTER file for that program will be deleted.
	CPD will then look at the AUTOEXEC.BAT, CONFIG.SYS, WIN.INI, and SYSTEM.INI files. For each file, there are several situations that can exist. The first situation is where the installation did not modify the file at all. In that case, CPD will not even mention the file. In the second situation, the installation process modified the file, but the file has not been modified since then. In that case, CPD will inform you that the original file can easily be restored and ask if you want to proceed. If you select Yes, CPD will restore the file to its original condition from before the new program was installed. If you select No, CPD will not restore the file.
	The third situation is where the file was modified by the installation process and has also been modified since then. This would most likely occur if you installed another program after the one you are now trying to delete. This is the most complicated situation. In this case, CPD will display a menu that gives you three options:
1) Do not attempt to restore file - If you select this option, CPD will leave the file as it is now, with all changes made by the first installation and any changes made since then remaining.
2) Replace file with original file - If you select this option, CPD will remove any changes made in the file. This includes both changes made by the installation of the program you are deleting and any changes made since then. If you do this, programs installed since the one you are currently deleting may not function properly.
3) Attempt to restore file while maintaining recent changes - If you select this option, CPD will analyze the original file from before the program you are deleting was installed, the file immediately after it was installed, and the file as it is right now. It will attempt to remove the changes made by the installation of the program you are deleting and still keep the changes that were made afterward. This can be tricky, but it can be done. There will be a message above the menu describing CPD's analysis of the files. This message will either say that there is a high probability that CPD can restore the original file while keeping changes made since the installation, or it will warn you that there is a possibility that there is a possibility that the original file cannot be completely restored. The file can be generally be completely restored when lines were merely added to it. The situation where it may not be possible to restore the original file completely occurs when lines from the original file were either deleted or radically changed when the program was installed.
	Despite all these disclaimers, I recommend that you select the third option. There are two reasons for this. First, CPD is actually very good at removing changes made during the first installation process while maintaining changes made since then. For example, if the installation process changed your AUTOEXEC.BAT's PATH=C:\DOS line to PATH=C:\DOS;C:\NEWPROG, CPD could restore it to PATH=C:\DOS. Second, CPD takes several precautions when it changes the file. First, it creates a copy of the file as it is now before making any changes in the file. This file will have the same root name as the file being restored and be in the same directory, but will have the extension CPD. For example, if CPD is restoring the AUTOEXEC.BAT file in the root directory, it will create a file called AUTOEXEC.CPD in the root directory before making the changes in AUTOEXEC.BAT. If CPD is restoring WIN.INI in the Windows directory, it will create a file called WIN.CPD in the Windows subdirectory. The CPD file will be the same as the file before CPD started making changes. If you find that CPD has damaged the file in some way, such as losing important changes made since the installation of the program you are deleting, you can always reverse the changes by deleting the file damaged by CPD (such as WIN.INI) and renaming the CPD file (such as WIN.CPD) to the old name. For example, if the AUTOEXEC.BAT file were not working properly after CPD tried to restore it, you would type
DEL \AUTOEXEC.BAT
REN \AUTOEXEC.CPD AUTOEXEC.BAT
at the DOS prompt and AUTOEXEC.BAT would be back where it was before CPD attempted to reverse the modifications made when it deleted the program you had installed.
	An additional safety precaution that CPD takes is that if CPD finds any lines in the original file that are totally missing or changed beyond recognition in the current file, it writes this lines into a file with the same name and location as the file it is changing, but with the extension MIS. For example, if CPD found that some lines that had been in WIN.INI before the installation were missing from WIN.INI now, it would create the file WIN.MIS in the WINDOWS subdirectory. you could then manually reinsert them into WIN.INI if you wanted to. You could use WIN.CPD as a guide to see if it gives any clues as to where to put these lines by looking for similar lines in that file. Note: If you installed program A and then program B and then deleted program A and then program B using CPD, you would expect there to be missing lines from your files when you delete program B. These are lines deleted by CPD when it deleted program A. You do not want to put these back into the file.
	There is one additional suggestion about deleting Windows programs. If you do decide to delete a Windows program using CPD, it is better if you first delete the icon or program group from Windows manually before using CPD to delete the files and correct the INI files. Deleting the icons is very easy in Windows. Most Windows programs create a program group when you install them. To get rid of this, first minimize the group to an icon. Then click on the group icon to give it the focus. Then click on the Program Manager's Files menu and click on Delete on the pull-down menu that appears. Windows will ask if you want to delete the program group, and you click on Yes. If the program is only installed as an icon in an existing program group, simply click on that icon to give it the focus, then click on Program Manager's Files menu and then the Delete option.
	When you delete a program group or icon from Windows this way, Windows automatically adjusts tab order and other management activities internally. If you do not delete a program group before using CPD to delete the program, the next time you run Windows, you probably will get a message saying something like "Group File Error. Cannot open program group file C:\WINDOWS\FILENAME.GRP. Do you want Program Manager to try to load it in the future?" There will be a Yes and a No button on this message. You should click on the No button. If the program was only an icon instead of a program group, the icon will still be there when you run Windows. If you click on it, you will get an error message saying that Windows cannot find a necessary file. You can delete the icon as described before. As I said, it is generally easier to delete the icon or program group from Windows before using CPD to clean up your disk.

Delete AFTER file

	If you have used a program for a while and decided that you want to keep it, you can delete the AFTER file that allows CPD to delete the program from your disk. This saves disk space, reduces clutter in the CPD menus when it asks you which program to delete, and eliminates the chance of you accidentally deleting a program by choosing the wrong program from the menu.
	If you choose this option from the main menu, CPD will display a list of programs that it can delete. Select the one that you have decided that you will not be wanting to delete with the cursor keys, and click on the Ok button. CPD will delete the AFTER file for that program from your disk. This program will no longer appear on the list of programs under the Delete Program option, and you will no longer be able to delete this program from your disk using CPD.
	It is a good idea to remove old programs from the CPD menu in this way, since it gets progressively harder to delete old programs without endangering changes made by more recent installations as you add more and more new programs.


Delete BEFORE file

	Occasionally you may create a BEFORE file for a program and decide, after you have installed the program and given it a quick try, that you absolutely love it and will never want to uninstall it. You might also conceivably create a BEFORE file and forget to create an AFTER file for it for a long time (despite CPD's reminders). If this happened, any AFTER file you created would include all the programs and files you added to your disk since you created the BEFORE file, most of which you would not want to erase. In such a case, you might not want to risk deleting the program for fear of erasing some of these files. In either of these cases, you might want to delete the BEFORE file you had created without ever creating an AFTER file for it sicne you never intend to use the AFTER file. The Delete BEFORE file option allows you to do this.

Delete safety backup files

	As described above, CPD creates safety backup files when it modifies one of the configuration files (AUTOEXEC.BAT, CONFIG.SYS, WIN.INI, or SYSTEM.INI) while deleting a program form your disk. Files with the extension CPD are complete copies of the file as it was before CPD deleted the program from your disk. Files with the extension MIS contain lines that were in the original file before you installed the program you used CPD to delete and which were missing after you installed it. You will not usually have any of these MIS files. CPD only creates an MIS if it is unable to safely replace the missing lines into the restored file, which is rare.
	Once you have used CPD to delete a program and have tested your computer to make sure that everything (including Windows) is working properly, you have no further need for these files. As is befitting a program used to delete unwanted files from your disk, CPD will delete all these files if you choose this main menu option.

Display Report

	This function displays a report on what changes occurred when a program was installed. When you select this option from the main menu, it displays a list of the programs installed using CPD. Select a program just as you selected programs to delete. CPD will display a window that shows the number of directories created when that program was installed, the number of files added to existing directories, and whether AUTOEXEC.BAT, CONFIG.SYS, SYSTEM.INI, and WIN.INI were changed.
	For anything that did change (such as subdirectories added), a "Details" button will appear next to the statement. Clicking on these buttons will give more details on a specific area. For example, clicking the Details button next to the number of files added to existing directories will display a list of the files added. Clicking on the button next to the statement that changes were made in WIN.INI will display a list of lines added to this file and lines removed from this file. Note that in some cases, lines added will resemble lines removed. This happens when the installation procedure changes a line. For example, you might see that the line "FILES=30" was added to the AUTOEXEC.BAT file and the line "FILES=20" was removed. This means that the installation program changed the setting for the maximum number of files that can be opened. When you have displayed detailed information on a change, you can click on the Print button to get a hard copy printout of these changes.

Exit

	This option on the main menu obviously exits CPD.

Getting Help

	At the top of CPD's main window, there are two pull down menus. One is Files and the other is Help. The Files menu duplicates the buttons that are visible on the main windows. The Help menu contains some options for getting information about CPD. The first option duplicates the Quick Instructions button. The second option, Complete Instructions, displays this instruction manual. The About option displays the title page containing information about the version number and so on.

Limitations

	I do not recommend using CPD on a networked computer. This is because other computers in the network could be creating files on the drive you are installing a program on. If one person is putting a file on a disk at the same time as another person is installing a program that you have created a BEFORE file for, there is no way for CPD to know that the files put on the disk are not part of the installed program. These files would therefore be deleted in you use CPD to uninstall the program. Because of this, CPD will warn you if you appear to be trying to create a BEFORE file for a networked drive. You may ignore this warning at your own risk.
	As was mentioned previously, there are several limitations on the ability of CPD to restore your drive. These limitations are as follows:

1) If the installation of a program overwrites an existing file on your hard disk by installing a new one with the same name, CPD cannot restore the old file. (For that matter, neither can any other method. Once a file is overwritten it is gone, gone, GONE.) For example, if you had a file called ROUTINES.DLL in your Windows System subdirectory and the new program overwrote that file with a file of the same name, CPD could not recover the old ROUTINES.DLL file. It will just leave the new one in place, in hopes that this is just a more recent copy of the same file.
2) Suppose that you create a BEFORE file, install program A, create an AFTER file, and then install another program. Suppose further that Program A installs a file (probably in the Windows System subdirectory) and that Program B either overwrites that file with an identical file or sees that the file already exists and therefore does not reinstall it even though it needs that file. CPD has no way of knowing that program B uses that file, since it sees that the file was installed by program A, not program B. If you use CPD to delete program A, it will delete that file. Program B will then not work properly. You would then need to reinstall that file, either by copying the file from program B's disk or by reinstalling Program B entirely. This situation is not very likely to happen, but you should be aware of the possibility in case a program suddenly stops working properly after you have used CPD to delete a previously installed program.
	This potential problem is the reason you have the option of having CPD ask you for permission to delete any files placed in subdirectories that the program you are deleting did not create when it was installed. Judicious use of this option should help avoid this problem. Just press N when CPD asks if it should delete any file that you think might be used by any program you installed after the one you are deleting. In addition, this option allows you to keep any files that you might find useful later. For example, any programs created by MicroSoft Visual Basic 2.0 require a file called VBRUN200.DLL. If you find that your program has installed this file, you might want to keep it when you delete the program because you may later acquire a different program that needs it but does not have it in the package (a common situation with shareware programs).
3) The same situation as described in #2 above applies to alterations in the AUTOEXEC.BAT, CONFIG.SYS, WIN.INI, and SYSTEM.INI files. That is, if program A makes a change and program B would have made the same change, CPD has no way of knowing this when it reverses the changes made by program A. It would reverse the changes made by program A and program B may not work properly. That is where the *.CPD file can save the day, by renaming it to the original name as described above.
4) Windows sometimes can create complex relationships between all the files (mostly INI files) that is uses. Deleting a file from Windows can have broad effects, and CPD cannot always anticipate all these effects, especially if you use some third party Windows desktop programs instead of the normal Windows Program Manager. Trying to have CPD do all the work of deleting a Windows program could theoretically cause conflicts between these files. That is why it is STRONGLY recommended that you remove the program icons and group using the normal Windows procedure described above. Then you can use CPD to delete the programs files from your hard disk and clean up WIN.INI and SYSTEM.INI, which deleting the Windows icon and program group does not do.
5) Changes made by CPD in WIN.INI or SYSTEM.INI may not take effect until you have exited Windows and started it again. Changes made in AUTOEXEC.BAT and CONFIG.SYS will not take effect until you have rebooted your computer.
	As you can see, most of the potential problems that could develop using CPD are the result of using it to delete programs after you have installed other programs. For this reason, CPD is most effective when used to delete a program within a reasonable period of time after the program has been installed. However, CPD can be used at any time after the program has been installed, and is much more effective than attempting to delete a program by hand or using most competing products. CPD will not delete files created by other programs after the AFTER file was made (such as data files), unless they are put into a subdirectory created during the installation of the program you are deleting, which would be EXTREMELY unlikely (like impossible).
	CPD seems to be having some trouble with unusual disk features like inivisble or protected directories, certain rare types of protected files, and so on. In more cases CPD will be able to handle these. Sometimes, however, CPD will be unable to read or erase a file or directory. In most cases, CPD will be able to bypass the problem and continue with its operation. For example, if it is unable to delete a directory during an uninstall process, it will display a message giving you the name of the directory that it could not delete and advising you to delete it manually (you can do this using File Manager). If it has trouble reading a directory while creating an AFTER file, it will not add this file to the list of directories to be deleted if you uninstall the program. These precautions are designed to insure that at the very worst, CPD will fail to uninstall some of the files created when a program is installed, rather than accidentally erasing files that you do not want it to. The worst that can happen if your disk has such unusual features is that CPD will not run on your system. In any case, these problems seem to be very rare, occuring on less than 1% of computers.

**** DISCLAIMERS ****

	Complete Program Deleter has been tested and every effort has been made to make it safe and effective. It has been found to be safer and more effective than trying to delete a program by hand or using a competing product that costs far more. However, any removal of files or modification of configuration files (AUTOEXEC.BAT, CONFIG.SYS. WIN.INI, and SYSTEM.INI) does contain a certain inherent risk. This risk must be borne by the user of the Complete Program Deleter. The Complete Program Deleter is provided "AS IS". In no event shall Leithauser Research or any person associated with the creation or distribution of this product be responsible for any damages, including but not limited to loss of business profits or loss of information, that results from the use or misuse of the Complete Program Deleter.

	Sorry about that folks, the lawyers made us say that. However, CPD is believed to be safe and effective when used as directed, subject to the limitations described in the above section on "Limitations".


Update Report

	This is a report on the differences between the various versions:

Version 1.2 - First public release (1.0 and 1.1 were beta versions).
Version 1.3 - Fixed a bug that caused the program to not work if the Windows subdirectory was not on C drive or the subdirectory name was not \WINDOWS. Also corrrected minor mistakes in the documentation, such as referring to files by incorrect names.
Version 1.4 - Adds code to make absolutely sure that BEFORE and AFTER files are placed in the Windows subdirectory. In previous versions it was theoretically possible for those files to be put in other subdirectories under some unusual circumstances.
Version 1.5 - Adds the ability to uninstall programs that are installed on several drives at the same time.
Version 1.6 - Adds error trapping to prevent program from crashing if unable to read a directory during the creation of an AFTER file. This is most likely to happen if the directory was deleted between creation of the BEFORE file and creation of the AFTER file.
Version 1.7 - Adds more error trapping to prevent program from crashing if unable to delete a directory during the deletion of a program. This can sometimes happen if the directory contains certain unusual types of protected files.
Version 2.0 - The Delete BEFORE file option was added. The ability to display this instruction manual from within the program was added. The ability to display the About box was added. The top menu bar (which mostly duplicates the buttons) was added. Buttons and menu options are now disabled when they cannot be used. Lots of features are added to prevent the user from doing things in the wrong order. Error trapping is added to handle unusual circumstances. Cosmetic improvements. Lots of safety features like warning you if you are running CPD on a network computer or you have other programs running while you are creating the BEFORE file and reminding you to create the AFTER file before you exit CPD. Generally, the look and feel is much improved and the program is made safer and easier to use by making it harder for the user to do things wrong or forget to do things.
Version 2.1 - Fixed a bug that caused CPD to crash on computers where Windows was set to use a date format other than the US date format of Month/Day/Year.
Version 2.2 - Took out some of the warnings installed in version 2.0 because of too many annoying false alarms. Version 2.2 will no longer warn on startup if you are running on a networked computer, although it will still warn if the specific drive you are creating a BEFORE file for appears to be a network drive. Also, it will no longer warn you of other programs running in the background, because too many types of background drivers and controllers caused false alarms.
Version 2.3 - Increased number of directories that CPD can record and save information on. This improvement is designed to allow for the newer, larger hard disks.
Version 2.4 - Same improvement as 2.3, only more so. Program redesigned to automatically adjust to ever-increasing hard disk sizes, as long as memory is available.
Version 2.5 - Improved ability of CPD to reconstruct control files (WIN.INI, AUTOEXEC.BAT, etc.) when installation procedure makes complex changes in them.
Version 2.6 - Added ability of CPD  to deal with corrupted AFTER files.
Version 2.7 - Fixed bug in error trapping.
Version 3.0 - Added the "Display Report" function. Added new setup program. Fixed minor bug that caused program to think that changes had been made in control files when the changes were inconsequential, such as spaces added in lines. Fixed bug in option for handling corrupted AFTER files.
Version 4.0 - Converted entire program to 32 bits. WCPD will no longer run on Windows 3.1, but works much better on Windows 95/98/2000/NT.

Bug Reports, Suggestions, Requests, etc.

	I am very interested in hearing about any problems you may have with this program. Please be ready to give as much information as possible about the circumstances under which the problem occurred. I would need to know which operation you were performing (Create BEFORE file, Create AFTER file, etc.), where  in th operation the error occcurred, what the error message was, etc. I am also interested in hearing any suggestions anyone may have for improvements or additional features. I can be contacted at the postal address given near the beginning of this document for sending shareware payments (notice how I subtly inserted a reminder about shareware payments again). I can also be reached at the EMAIL addresses Leithauser@aol.com

	In emergencies, I can be reached by phone at 904-738-0418. The best times to call are from 11 AM to 11 PM Monday through Saturday.

Custom Programming

	One of the functions of Leithauser Research is creating custom programs to customer specifications. If you would like a DOS or Windows program created to your specific needs, either for your own use or for resale, please contact David Leithauser at Leithauser Research at one of the above postal or EMAIL addresses.