Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!csd4.csd.uwm.edu!aragorn
From: aragorn@csd4.csd.uwm.edu (Steve J White)
Newsgroups: comp.windows.ms
Subject: Re: Comm trouble: Win + DOV unit
Message-ID: <11332@uwm.edu>
Date: 23 Apr 91 18:02:00 GMT
References: <1991Apr21.102731.19232@en.ecn.purdue.edu> <6553@bwdls58.bnr.ca>
Sender: news@uwm.edu
Organization: University of Wisconsin - Milwaukee
Lines: 32

In article <6553@bwdls58.bnr.ca> mlord@bwdls58.bnr.ca (Mark Lord) writes:
>In article <1991Apr21.102731.19232@en.ecn.purdue.edu> stevew@en.ecn.purdue.edu (Steven L Wootton) writes:
>...
><
><I pulled my I/O card and put in a 1200 bps Hayes compatible internal modem,
><and all of the Windows apps work.  Put the I/O card back in and attach the
><cable to the Gandalf, and everything stops again.
>
>Hmm.. almost as if there were a steady flow of interrupts (or a stuck interrupt)
>in/under windows...
>
>Is the baud rate set up correctly in windows?  (just fishin').


I see two possibilities here.  First, and most unlikely, is the trouble Win3
has with sharing IRQ lines.  I can give the details of this if you like.
Second, and MORE likely, is that the port card you are using is somehow
tying up the COM port that you want to use for the DOV unit.  It could be
that, if this is a cheaper clone port card, it is pulling some aspect f the
COM port down.  I have had the experience with some of the lesser known
brands of port cards that when they are set up for only one COM port, they
still have the (dis)ability to tie up the other COM port.  I've never quite
figured this one out.  Let us know what happens.

- steve


-- 
"Laugh and the world laughs with you... |  All disclaimers apply... 
     snore and you sleep alone."        |  except my own, of course.
  - anonymous fortune cookie thingy     | ***  Steve J. White  ***      
		<<<	aragorn@csd4.csd.uwm.edu     >>>