KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q39187: "Bad File Name" OPENing "COM1:" with 1.5 Stop Bits

Article: Q39187
Product(s): See article
Version(s): 1.00 1.02 2.00 2.01 3.00 4.00 4.00b 4.50
Operating System(s): MS-DOS
Keyword(s): ENDUSER | B_BasicCom SR# S881207-9 | mspl13_basic
Last Modified: 5-SEP-1990

The option for 1.5 stop bits is not supported in any version of
QuickBASIC (1.00, 1.02, 2.00, 2.01, 3.00, 4.00, 4.00b, or 4.50) or in
Microsoft BASIC Compiler version 6.00 or 6.00b for MS-DOS and MS OS/2.
However, 1.5 stop bits is supported in Microsoft BASIC Professional
Development System (PDS) versions 7.00 and 7.10.

In QuickBASIC, if you try to open the serial communications port using
1.5 Stop Bits, you will get a "Bad file name" error when you run the
program in the QB.EXE editor. This error will not occur with 1.5 stop
bits in BASIC PDS 7.00 and 7.10.

The following similar error message is returned when you run an .EXE
file compiled with the BC.EXE environment that comes with QuickBASIC:

   BAD FILE NAME in module $$$ at address xxx:xx

The communications option for 1.5 stop bits is supported by GW-BASIC
versions 3.20, 3.22, and 3.23.

The following is a code example:

   OPEN "COM1:1200,N,8,1.5" FOR RANDOM AS #1

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.

Copyright Microsoft Corporation 1986-2002.