Q132200

• Microsoft Visual C++ for Windows, 16-bit edition, versions 1.5, 1.51, 1.52

SYMPTOMS

When you debug an application with Visual C++ minimized, the Windows 95 MSVC taskbar entry for Visual C++ version 1.5 may not respond when you click it to restore Visual C++.

This happens only after the debuggee has been terminated while Visual C++ is minimized. It is also possible that other 16-bit applications will not respond if you choose End Task for Visual C++ version 1.5.

CAUSE

When you terminate an application that is being debugged, Visual C++ prompts for a response to this message:

   Process <process number> terminated normally (0). 

RESOLUTION

Select the MSVC taskbar item with the mouse, and press the ENTER key.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

Steps to Reproduce Problem

1. When using a sample application, press the F5 key to start debugging.



2. Minimize Visual C++.



3. Exit the sample application.



4. Double-click the MSVC entry in the taskbar. The development environment is not restored. In addition, if you press ALT+TAB to move through the process list, the development environment is not restored.



5. To prevent other 16-bit applications from responding, press CTRL+ALT+DEL.



6. Choose Microsoft Visual C++.



7. Select End Task. You are no longer able to restore the development environment or other 16-bit applications. The solution listed in the "Resolution" section of this article no longer works.

Additional query words: 1.50 tray

Keywords : kb16bitonly kbide kbVC kbVC150bug kbVC151bug kbVC152bug kbGrpDSTools
Issue type : kbbug
Technology : kbVCsearch kbAudDeveloper kbvc150 kbVC151 kbVC16bitSearch kbVC152