WinSpool 95 and WinSpool 98 are GPFing when started

From Support

If you have a question or seek clarification, please call Technical Support.

Problem:

The user who had this problem was running Windows NT 4.0 (SP3) and had also loaded Visual Studio/Visual Basic V6.00. WinSpool 95 and 98 were GPFing when the programs were started leading us to believe there was some sort of DLL conflict. The user also informed us they had not loaded the Visual Basic 5.0 runtime files since they already had Visual Basic 6.0 loaded. This was an incorrect assumption.

Solution:

We checked the version numbers of the following files and found out they were V6.00 which means they were probably installed by Visual Basic 6.0:

COMCTL32.OCX, COMDLG32.OCX, TABCTL32.OCX, and MSVBVM50.DLL

The first 3 files are supposedly upward compatible from the V5.00 versions we have been shipping, so we decided to check to see if the problem was with MSVBVM50.DLL. We had the user rename the MSVBVM50.DLL file and then install the Visual Basic 5.0 runtime files from our web site. After doing this, the WinSpool 95 and WinSpool 98 software work just fine.