Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!uunet!mcsun!ukc!harrier.ukc.ac.uk!zodiac.ukc.ac.uk!cur022
From: cur022%cluster@ukc.ac.uk (Bob Eager)
Newsgroups: comp.os.os2.misc
Subject: Re: COM Ports...
Message-ID: <21532.2777f0f6@cluster@ukc.ac.uk>
Date: 26 Dec 90 00:38:14 GMT
References: <9012231849.AA20609@f170.n771.z3.fidonet.org>
Organization: Computing Lab, University of Kent at Canterbury, UK.
Lines: 18

In article <9012231849.AA20609@f170.n771.z3.fidonet.org>, Andrew_Hooper@f110.n771.z3.fidonet.org (Andrew Hooper) writes:
> I am real new to OS/2 and am really just beginning to explore things. I have 
> downloaded a couple of comms programs now and can't seem to get either 
> working. My system doesn't seem to recognize my COM1 or COM2 ports. I am 
> currently using PROCOMM PLUS after booting off a DOS floppy, but that's a 
> hassle. I would far prefer to get an OS/2 comms program working. I have a 
> DEVICE=\OS2\COM01.SYS statement in my config.sys file...

I assume you're trying to run PROCOMM in the DOS box. You have to make a COM
port available for use by a DOS program under OS/2. Check out the command
SETCOM40; it's something like:
                 SETCOM40 COM1:=ON

Bob
-------------------------+-------------------------------------------------
Bob Eager                | University of Kent at Canterbury
                         | +44 227 764000 ext 7589
-------------------------+-------------------------------------------------