Microsoft KB Archive/176167

From BetaArchive Wiki

Article ID: 176167

Article Last Modified on 10/20/2003



APPLIES TO

  • Microsoft Visual J++ 1.1 Standard Edition
  • Microsoft Visual InterDev 1.0 Standard Edition



This article was previously published under Q176167

SYMPTOMS

The Results List window shows the results of searches or queries in the online books. When you start Developer Studio and before you do any searches or queries, the Results List window is empty.

If you double-click in the white part of an empty Results List window or click the Next button for an empty Results List, the following error message appears:

MSDEV.EXE - Application Error
The instruction at "0x513161360" referenced memory at "0x00000042". The memory could not be "read".

The same problem occurs with the the October 1998 MSDN Library. The following error is generated in the October 1998 MSDN Library:

IV5.EXE - Application Error
The instruction at "0x513161360" referenced memory at "0x00000024".
The memory could not be "read".

RESOLUTION

Leave the Results List closed until after you have done a search. Once you have done a search, the Results List will never again be empty until you close down and restart the application (Developer Studio or the MSDN Library).

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was corrected in VisualStudio version 6.0.


MORE INFORMATION

Steps to Reproduce the Problem

  1. Start Developer Studio (MSDEV.EXE) or the MSDN (IV5.EXE).
  2. If the Results List Window is not displayed, select Results List from the View menu.
  3. Since you have not done any searches, the Results List will be empty.
  4. Note that the Next button is active. It should be gray and inactive for an empty Results List. Click the Next Button (blue down arrow) or double-click in the white area.
  5. Developer Studio or the MSDN crashes (Application Error message appears).


Keywords: kberrmsg kbbug kbfix kbinfoviewer kbvs600fix KB176167