Xref: utzoo comp.binaries.ibm.pc.d:9679 comp.windows.ms:5819 comp.sys.ibm.pc.misc:2183
Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uwm.edu!rpi!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!TCS@router.jhuapl.edu
From: tcs@router.jhuapl.edu
Newsgroups: comp.binaries.ibm.pc.d,comp.windows.ms,comp.sys.ibm.pc.misc
Subject: Re: windows 3.0 and com3:
Message-ID: <0093D877.818BD840@router.jhuapl.edu>
Date: 1 Oct 90 11:28:56 GMT
References: <26762@mimsy.umd.edu>
Sender: news@aplcen.apl.jhu.edu
Reply-To: tcs@router.jhuapl.edu
Followup-To: comp.binaries.ibm.pc.d
Distribution: usa
Organization: Johns Hopkins University/APL
Lines: 9
Nntp-Posting-Host: router.jhuapl.edu

RE: Patriot on Com3 (Com1/Com4).

I just saw a patch on a local BBS about this. I seem to recall that it said 
something about there needing to be a patch done to the comm.drv(?) since it's
looking only for Com1/Com2. If noone else suggests something, I'll bring it
the docs tomorrow and post it.

Carl Schelin
tcs@router.jhuapl.edu