Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!dogie!uwvax!astroatc!nicmad!brown
From: brown@nicmad.UUCP (Vidiot)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Problem with serial port
Message-ID: <3732@nicmad.UUCP>
Date: 25 Feb 89 02:40:00 GMT
References: <10220@pasteur.Berkeley.EDU>
Reply-To: brown@nicmad.UUCP (Vidiot)
Organization: Vidiot's Hangout
Lines: 21

In article <10220@pasteur.Berkeley.EDU> foote@ernie.Berkeley.EDU (Bill Foote) writes:
<
<I have a problem with my serial port (on my Unisys AT clone).  I
<can't send output to it using fopen("com1:", "w") from Microsoft
<C, and "copy con: com1:" doesn't work (it accepts keyboard input,
<but nothing comes out of the serial port).  When I type in
<"mode com1:12,N,8,1" (or even just "mode com1:"),  I get the error
<message "invalid parameter com1".  Despite this, Procomm, Telix, and
<Crosstalk XIV all have no trouble with the serial port, and my
<diagnostics disk tells me that I do indeed have a serial port
<installed.  Does anyone have any idea what might be wrong?

Ya, MSC (5.1) doesn't support the com ports, at least not directly.  We have
the same problem where I work.  One has to write their own com port handler
or buy one of the third party C library packages that include com port
functions.
-- 
	       harvard-\	 att--\
Vidiot            ucbvax!uwvax!astroatc!nicmad!brown
	       rutgers-/      decvax--/
	ARPA/INTERNET: nicmad!brown%astroatc.UUCP@spool.cs.wisc.edu