KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q43256: CALL INTERRUPT RegType in Manual Inconsistent with QB.BI File

Article: Q43256
Product(s): See article
Version(s): 4.00 4.00b 4.50
Operating System(s): MS-DOS
Keyword(s): ENDUSER | SR# S890406-35 docerr B_BasicCom | mspl13_basic
Last Modified: 14-DEC-1989

In the following manuals, the RegType (user-defined TYPE) documented
with the CALL INTERRUPT statement is inconsistent with the TYPE in
QB.BI, the $INCLUDE file:

1. Page 90 of the "Microsoft QuickBASIC 4.0: BASIC Language Reference"
   for QuickBASIC Versions 4.00 and 4.00b for MS-DOS and for
   Microsoft BASIC Compiler Versions 6.00 and 6.00b for MS-DOS and MS
   OS/2

2. Page 74 of the "Microsoft QuickBASIC 4.5: BASIC Language
   Reference," which is available for separate purchase after you buy
   QuickBASIC Version 4.50

To correct the inconsistency, remove the following two statements from
the RegType in the manual:

   DS AS INTEGER
   ES AS INTEGER

The RegType shown in the manual is actually the RegTypeX in the QB.BI
$INCLUDE file.

This documentation error has been corrected in Microsoft BASIC PDS
Version 7.00 for MS-DOS and MS OS/2. The TYPE descriptions in the
"Microsoft BASIC 7.0: Language Reference" for RegType and RegTypeX on
Pages 172-173 agree with the TYPE declarations in the QBX.BI $INCLUDE
file supplied with BASIC PDS 7.00.

The RegType defined in the QB.BI file (used with $INCLUDE) does not
contain the DS and ES registers. The DS and ES registers are only
needed for the CALL INTERRUPTX statement, which uses RegTypeX.

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.