Question: Why is my patch file larger than the corresponding size of the files I am patching after they have been compressed using WinZip?
Answer: WinPatch is not rocket science.  If you are only creating a patch file—not a self-extracting patch—the file size should almost always be smaller.  If there are almost no common file pieces, maybe the patch file could be larger than the compressed size (.zip format) of the corresponding files.  If you are patching large files that have minor changes between them you will find the patch file to be significantly smaller than the corresponding files that are being patched.

If you are creating a self-extracting patch, you need to add the overhead of the self-extracting executable for the convenience you gain for distributing a self-extracting patch.  The overhead is 136KB for the executable that the patch file is attached to so it can be self-extracting.  If you examine other patch products, you will find that the overhead of their self-extracting executable is larger.  I have tried to make the self-extracting program as small as possible and to that end it is constructed using Microsoft’s Active Template Library (ATL) to keep the program as small as possible.  ATL is Microsoft’s solution for developers to build ActiveX components that are small and distributable over the Internet.  The WinPatch self-extracting patch is an ActiveX executable.

Question: Will WinPatch update read-only file on the PC where the patch is applied?
Answer: Version 1.2 will update read-only files on the PC where the patch is applied. Previous versions would not.

Question: I have not really changed some of the files I am updating, but I have changed the file date.  Can WinPatch update the file's date on the user's PC for me--even if the file has not changed?
Answer: Version 1.2 of WinPatch automatically updated the file's date on the PC where the patch file is applied--even if the file has not changed.

Question: Can I execute a patch from a CD-ROM?
Answer: Yes. In version 1.2, WinPatch now creates all temporary files in the TEMP directory on your hard drive so patch files can be executed from read-only media.

Question: Can WinPatch split its update file into multiple files that can be distributed on diskettes?
Answer: Yes. this is a new feature of version 1.2.

Question: I have paid for WinPatch and now have a user ID. How do I register the program and get rid of the shareware screens?
Answer: Click on the Register button in the About dialog to register the program.

Question: Does WinPatch use error checking?
Answer: Yes. WinPatch creates two digital signatures for each file a patch object is created for. One digital signature is to identify and error-check the file before the patch is applied. The other digital signature is to make sure the patch file was applied correctly.

Question: Can a patch file be accidentally applied to the same file set twice?
Answer: No. Digital signatures and WinPatch error checking insure that a patch cannot be accidentally applied to the same file system twice.

Question: What is the best way to distribute a patch file?
Answer: Use a self-extracting WinPatch file. This option let’s you create one small, compressed file that you can distribute to users to update their file systems.

Question: Does WinPatch Apply use command-line parameters?
Answer: Yes. You can optionally specify the name of the WinPatch file on the WpApply.exe command line. This will save the user from the task of typing in or browsing to find the WinPatch file.

Question: Is WinPatch a Visual Basic program?
Answer: No. WinPatch was developed in C++ and C using Microsoft Visual C++ 4.X. WinPatch is a totally object-oriented program that was built from the ground up to only run on Microsoft Windows 95 and Windows NT 4.0 (and later) operating systems. WinPatch uses the Microsoft Foundation Class (MFC) library.  WinPatch Apply, WinPatch Apply Self-Extracting Executable, and the new WinPatch ActiveX control do not use MFC.   These components use Microsoft ATL to produce the smallest possible components.

Question: How is WinPatch so fast compared to other patch programs?
Answer: WinPatch is a totally object-oriented design for building and applying patch files that is implemented using the Microsoft Visual C++ optimizing compiler. WinPatch also uses a new copyrighted digital signature technology for analyzing files that gives it much of its speed.

Question: How do I use command-line parameters?
Answer: To use command-line parameters for WpApply, you execute the program as follows:

WpApply “c:\my_winpatch_file.wp” “c:\folder to apply patch to”
The first parameter is the name of the patch file. The second parameter is the folder to apply the patch file to. Note the quotation marks that enclose each parameter. The quotation mars are required, because long file names (and folder names) may include spaces.
Self-extracting patch files only have one parameter…the folder name of where to apply the patch file.

Question: I think the user interface to the self-extracting patch could use a face lift, is there any way I can customize it.
Answer: Purchase WinPatch Professional and you can use the WpApply control to create your own WpApply programs. To customize the self-extracting patch, you need to purchase WinPatch Enterprise Edition that includes WinPatch Professional.