Path: utzoo!attcan!uunet!lll-winken!ames!mailrus!tut.cis.ohio-state.edu!rutgers!bellcore!texbell!merch!cpe!hal6000!trsvax!don
From: don@trsvax.UUCP
Newsgroups: comp.sys.ibm.pc
Subject: Re: Problem with serial port
Message-ID: <216100084@trsvax>
Date: 27 Feb 89 15:54:00 GMT
References: <10220@pasteur.Berkeley.EDU>
Lines: 27
Nf-ID: #R:pasteur.Berkeley.EDU:10220:trsvax:216100084:000:1053
Nf-From: trsvax.UUCP!don    Feb 27 09:54:00 1989


<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?

A simple solution is

	copy con aux

This does what you were trying to do with the copy con com1 command.  I
redirect debugging output from symdeb to a terminal, and the above command
is a simple test to see that everything is set properly, such as baud rates
and null modem.

% make me stop
don't know how to make me.  Stop.

Don Subt			The opinions expressed above are
Tandy Corp.			strictly mine, not my employer's.

817-390-3068			...!killer!ninja!sys1!trsvax!don