ID Number: Q83632
1.00
WINDOWS
buglist1.00
Summary:
PROBLEM ID: QCW9204003
SYMPTOMS
When using the QuickC for Windows Graphical Development Environment
version 1.0 with the debug version of Windows 3.1, several
FatalExit errors may occur when entering data.
STATUS
Microsoft has confirmed this to be a problem in QuickC for Windows
version 1.0. We are researching this problem and will post new
information here as it becomes available.
More Information:
After invoking QuickC for Windows, attempting to type a character in
an edit window halts Windows and causes the following to be displayed
on the debugging terminal:
err QCWIN GLOBALFREE+15: Invalid global handle: 0x0000
FatalExit code = 0x6022
Abort, Break, Exit, or Ignore?
Pressing "I" on the debugging terminal's keyboard returns control to
Windows, and updates the Edit window's display with the correct
character typed.
Closing QC/Win halts the system and causes the following errors to be
displayed:
err QCWIN LOCALFREE+C: Invalid local handle: 0x0000
FatalExit code = 0x6023
Abort, Break, Exit, Ignore?
Ignoring the error causes the same error to reoccur. If the error is
ignored again, the following is displayed:
err QCWIN GDI: GDI: Attempt to delete object owned by system
FatalExit code = 0x8400
Abort, Break, Exit, Ignore?
This error reoccurs three times, and then the final error message is
displayed:
wn QCWIN GDI: Palette not deleted: 0D46
QC/Win is then removed from Windows memory.
Additional reference words: QCWIN QCW1.00 Quick C