FIX: CTRL+C Is Not Trapped in GetCharQQ

 Last reviewed: September 16, 1997
Article ID: Q106562
1.00 MS-DOS kbprg kbfixlist kbbuglist

The information in this article applies to:

  • Microsoft FORTRAN PowerStation for MS-DOS, version 1.0

SYMPTOMS

The GetCharQQ function does not terminate the program when a CTRL+C or CTRL+BREAK is entered at the keyboard. Instead, the ASCII value for that key sequence is returned (ASCII 03).

STATUS

Microsoft has confirmed this to be a problem in FORTRAN PowerStation version 1.0 for MS-DOS. This problem has been corrected in FORTRAN PowerStation maintenance release version 1.0a for MS-DOS.

MORE INFORMATION

To reproduce this behavior:

  1. Build the TKEYS.FOR sample program with FORTRAN PowerStation. This file is in F32\SAMPLES\RUNTIME. No compile options are required.

  2. Run TKEYS at the MS-DOS prompt.

  3. Press CTRL+C. The following will be displayed: 

          ASCII: yes   Char:   Decimal:   3   Hex: 0003

  4. Press CTRL+BREAK. The same values will be displayed.

  5. To exit, press: 

          q y <space> <space>

FORTRAN PowerStation version 1.0 can be differentiated from the maintenance release version 1.0a by invoking the linker. Typing "link32 | more" from \F32\BIN directory will show version 2.8 for FORTRAN PowerStation version 1.0, and it will show version 1.0f for the maintenance release version 1.0a.

Additional reference words: 1.00 fixlist1.00a
KBCategory: kbprg kbfixlist kbbuglist
KBSubcategory: FORTLngIss
Solution Type : kbfix

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: September 16, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.