When the WingDir setup program is run, the following error message is received:

"An error occurred while registering the file C:\windows\system\ccrpbd.ocx"

This is a WingDir 4.7 specific problem. WingDir 4.7 is a Visual Basic 6 application, but the "CCRPBD.OCX" file requires the VB5 runtime files.

Download the Visual Basic 5 RunTime files (msvbvm50.exe) here.

After downloading the msvbvm50.exe file (about 1.3 mb) double click it. The VB5 runtime files will be installed on your PC. Then reinstall WingDir 4.7.

Note: This problem has been fixed in WingDir 4.8

When you run the WingDir setup program, you receive the following error message:

"Failure writing to the system registry. The registry may be corrupt, or you may not have the required permissions to write to the registry."

This is not a problem with WingDir, but with Windows. The problem occurs on computers running Windows 95 when the Setup program tries to add an entry to a registry key and the key will exceed 64K in size as a result. Registry keys are limited to 64K in Windows 95.

The size of the registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDLLs" is too large and must be reduced.

Microsoft Knowledgebase Article ID: "Q186897" discusses the problem in more detail and explains how to fix the problem.

The article can be found at "http://support.microsoft.com/support/kb/articles/q186/8/97.asp" or you can view a copy here.

This problem is caused by specifying the "/s" and "/t" switches on the command line for the source and target directories. The "/s" and "/t" command line switches were removed in 4.5 so that WingDir could be used as a SendTo target from Windows Explorer. The Help file indicates that they are still used, but the Help file is wrong. The Source directory can still be specified on the command line, but don't use the "/s".

To use the Windows Explorer SendTo put a "wingdir.lnk" shortcut in the "c:\windows\sendto" directory. Pass the source directory to WingDir from Windows Explorer by using the SendTo option when you right-click a directory name.

WingDir fails with a "6-Overflow" error when trying to calculate the amount of disk freespace when the drive has greater than 2GB of freespace.

Until recently DOS & Windows 95/NT were unable to allocate a disk partition larger than 2GB. Now with Windows/95 (OSR2) and Windows/NT (NTFS) disk partitions can easily exceed 2GB. WingDir's freespace calculation was physically unable to exceed 2GB causing a "Size Overflow" when the freespace was greater than 2GB.

WingDir 4.4 has been fixed to accommodate larger calculation results, but there is still an occasional reported problem even with 4.4. In the event that the error still occurs there is a file, "OVERFLOW.REG", in the WingDir directory (probably "c:\program files\wingdir). Double clicking "OVERFLOW.REG" will add an entry to the WingDir Registry settings that will tell WingDir to skip the freespace calculations. Applying the "OVERFLOW.REG" entry will result in WingDir showing "0" as the amount of freespace for both Source and Target directories.

Please let me know if the "6-Overflow" error occurs with WingDir 4.4 or newer. Especially if you have applied the "OVERFLOW.REG" entry.

This problem appears to be caused by a having a very large number of Fonts. WingDir was unable to load all the names into the drop down box on the Settings Form. It has been fixed in WingDir 4.5.

This problem occurs when accessing the Settings Menu. It is caused by WingDir not being able to find the "MS Sans Serif" Font. It was fixed in WingDir 4.3a.

WingDir ships with the latest system files at time of release. In most cases the system files are more current than those found with the latest service releases for Windows 95/NT. This is because Microsoft updates its system files for Visual Basic more often than for Windows 95/NT.

When the install starts Windows 95/NT checks the files in the install. If any of the "core" files are newer than what Windows has it will update those first before it will complete the install. Windows will copy the files in question to the "Temp" directory and ask to reboot the PC. During the reboot process Windows copies the files in the "Temp" directory to the "c:\windows\system" directory.

After the "updating" is done and the PC is finished rebooting, the install needs to be run again. This time it shouldn't say that it has files that need updating.

Caution - When Windows wants to update your files as a result of installing WingDir it is important to be aware of how the update occurs. Windows places the new files in the TEMP directory and copies them to their permanent location during the reboot process. If the TEMP directory is erased during the reboot, as some people do, from the AUTOEXEC.BAT, the update will not occur.

When Windows puts the "new/updated" files in your TEMP directory (probably "C:\TEMP" or "C:\WINDOWS\TEMP") it gives them names like RBT6142.TMP, RBT6194.TMP, RBT61A1.TMP, etc.

It then builds a file "WININIT.INI" that gets executed/applied before Windows starts the next time. After Windows reboots it renames the file to "WININIT.BAK". In your Windows directory there should be a file "WININIT.BAK" that will look something like:

[rename]
C:\WINDOWS\SYSTEM\MSVBVM50.dll=C:\WINDOWS\TEMP\RBT6142.TMP
C:\WINDOWS\SYSTEM\StdOle2.tlb=C:\WINDOWS\TEMP\RBT6194.TMP
C:\WINDOWS\SYSTEM\OleAut32.dll=C:\WINDOWS\TEMP\RBT61A1.TMP
C:\WINDOWS\SYSTEM\OlePro32.dll=C:\WINDOWS\TEMP\RBT61B1.TMP
C:\WINDOWS\SYSTEM\AsycFilt.dll=C:\WINDOWS\TEMP\RBT61B5.TMP

This will show you what files Windows is trying to update and where to find the "new/update" version.

WingDir uses a "date" format when comparing date/time stamps. Sometimes when copying files from a network drive or a CD-Rom the file date/time stamp is not copied correctly, being off by a second.

This is not a WingDir problem but a known Windows bug that can be recreated with Windows Explorer. It is still an outstanding issue for WingDir.