From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,a0c763cf7df38121,start
X-Google-Attributes: gid103376,public
From: tmoran@bix.com
Subject: Re: Can't control COM port pins in DOS Window
Date: 2000/03/10
Message-ID: <NN%x4.492$34.9257@news.swbell.net>#1/1
X-Deja-AN: 595490539
References: <QUMx4.15586$W5.196264@typhoon.nyroc.rr.com>
X-Complaints-To: abuse@swbell.net
X-Trace: news.swbell.net 952666349 207.214.211.143 (Thu,
 09 Mar 2000 23:32:29 CST)
Organization: SBC Internet Services
NNTP-Posting-Date: Thu, 09 Mar 2000 23:32:29 CST
Newsgroups: comp.lang.ada
Date: 2000-03-10T00:00:00+00:00
List-Id: <comp.lang.ada>

>However, although it runs fine under plain DOS, it will *not* make the pin
>voltages change when run in a DOS window in Windows 98.
  Sounds like Windows 98 is keeping control over that hardware resource
and not letting your program touch it.  Does your program run OK under
Windows 95?  Note also that the virtualizing makes IO commands run
much much slower.  Does timing matter to your program?