WinView 95 is GPF'ing when being started under Windows NT 4.0 with NT Service Pack 4.0

From Support

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

Problem:

You are is starting WinView/400 95/NT and the program is GPF'ing and causing a Doctor Watson error. When you reinstall from scratch the software works just fine, however after a week you started getting the same problem again.

Solution:

The main speculation is that you installed additional software after installing WinView.

This is not an iron clad answer, but we checked the Visual Basic 5.0 runtime file MSVBVM50.DLL that was installed with NT Service Pack 4.0 and the version is as follows: Version: 5.02.8244 (SP2) Modified Date: 10/15/98 You have to rename the MSVBVM50.DLL file and will reinstall the Visual Basic 5.0 runtime files to install the MSVBVM50.DLL that we're currently shipping which is: Version: 5.00.4319 (SP2) Modified Date: 7/19/97

The following miscellaneous items can also be checked:

Check the version numbers of the following files: If they are V6.00 it means they were probably installed by Visual Basic 6.0 or NT Service Pack 4.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 software should hopefully work just fine.