kirk%enterprise@Sun.COM ('Captain' Kirk DeHaan) (03/18/89)
I recently bought an internal 2400b modem. I also have 2 com ports in my system. My problem is that I want to maintain the two RS-232 ports as com1 and com2 while having the modem at com3. Using procomm+ allows me to do just this but a problem arises when trying to dial in to a unix system. Regardless of the settings I get nothing but garbage from the unix system. If I move the modem to com1 or com2 and use telix it works great. The modem internal with procomm+ works fine when calling all the other systems I have access to. I guess I have two questions then. 1. Is there a fix for the procomm+ problem? I'm not sure what the cause is but it is definately related to procomm+. Using a different modem (USR Courier) gives the same problem. 2. Can Telix (3.11) be made to work with com3? The docs say yes but trying to do so results in a hung system. Looking at the telix.cnf file shows the values assigned to the port addresses but I can't figure out how they are used. They are listed as 1000 for com1 and 1016 for com3. BTW, I would prefer to use Telix. It has zmodem capabilities built in and seems to have the bells and whistles I desire. I am new to DOS so any help would be appreciated. ******************************************************************** * 'Captain' Kirk DeHaan "There's a lot to be said * * Sun Microsystems Inc. For a blow to the head" * * * * kirk@sun.com Blue Oyster Cult * * * ********************************************************************
rong@cwsys2..CWRU.Edu (Rong Chen) (03/19/89)
In article <94545@sun.Eng.Sun.COM> kirk%enterprise@Sun.COM ('Captain' Kirk DeHaan) writes: >I recently bought an internal 2400b modem. I also have 2 com >ports in my system. My problem is that I want to maintain the >two RS-232 ports as com1 and com2 while having the modem at >com3. Using procomm+ allows me to do just this but a problem >arises when trying to dial in to a unix system. Regardless >of the settings I get nothing but garbage from the unix system. >If I move the modem to com1 or com2 and use telix it works great. >The modem internal with procomm+ works fine when calling all >the other systems I have access to. > >I guess I have two questions then. > >1. Is there a fix for the procomm+ problem? I'm not sure what the >cause is but it is definately related to procomm+. Using a >different modem (USR Courier) gives the same problem. > >2. Can Telix (3.11) be made to work with com3? The docs say yes but >trying to do so results in a hung system. Looking at the telix.cnf file >shows the values assigned to the port addresses but I can't >figure out how they are used. They are listed as 1000 for com1 and >1016 for com3. > >BTW, I would prefer to use Telix. It has zmodem capabilities built >in and seems to have the bells and whistles I desire. > Some hints: "industry standard" port address and interrupts: port i/o address interrupt ------------------------------------------------- com1 3F8 hex 4 com2 2F8 hex 3 com3 3E8 hex 4 com4 2E8 hex 3 therefore if you use interrupt driven software at com1, e.g. a mouse, then the communication software(no matter which one you use, Telix or Procomm) at com3 will conflict with com1 since they use the same interrrupt when the bus drivers on both serial ports are turned on at same time. If you configure the communication software( Telix or Procomm) on com3, and do not use the com1 port, you should have no problem. To remind you, following are almost always interrupt-driven applications: * communication programs * laptop/desktop file transfer programs * serial port LANs * bulletin board programs * remote access programs * PC fax softwares DOS MODE command redirect program(i.e. MODE LPT:=COM1:) is not interrupt- driven program. Hope these will help you. Rong Chen rong@cwsys2.cwru.edu
goes@oregon.uoregon.edu (Jim Goes, Univ of Oregon) (03/25/89)
In article <94545@sun.Eng.Sun.COM>, kirk%enterprise@Sun.COM ('Captain' Kirk DeHaan) writes: > 2. Can Telix (3.11) be made to work with com3? The docs say yes but > trying to do so results in a hung system. Looking at the telix.cnf file -- I've had the same problem with Telix. I can get Procomm Plus to recognize the COM3 port but not Telix, even though I use the same IRQ and interrupt settings for both. I referred this problem to Colin (author of Telix) and he said COM3 should work as long as there are no conflicts (i.e. a mouse running on COM1 or something). Even with nothing on COM1 I can't get Telix to work on COM3. I finally gave up, and have been using Telix on COM1 exclusively. _______________________________________________________________________________ Jim Goes | InterNet GOES@OREGON.UOREGON.EDU Graduate School of Management | UUCP: {fav backbone}!uoregon!oregon!goes University of Oregon | MaBell: (503) 686-3309 ________________________________________________________________________________ Grad School. Its not just a job, it's an indenture...
goes@oregon.uoregon.edu (Jim Goes, Univ of Oregon) (03/27/89)
In article <341@oregon.uoregon.edu>, I wrote: > In article <94545@sun.Eng.Sun.COM>, kirk%enterprise@Sun.COM ('Captain' Kirk DeHaan) writes: >> 2. Can Telix (3.11) be made to work with com3? The docs say yes but >> trying to do so results in a hung system. Looking at the telix.cnf file > -- > I've had the same problem with Telix. I can get Procomm Plus to recognize the > COM3 port but not Telix, even though I use the same IRQ and interrupt settings -- Just a quick note that Keith Peterson sent me a copy of RS232OFF.ARC which solves this problem. RS2320FF is available in com.binaries.ibm.pc or on SIMTEL20 in PD1:<MSDOS.MODEM>. Thanks again, Keith. _______________________________________________________________________________ Jim Goes | InterNet GOES@OREGON.UOREGON.EDU Graduate School of Management | UUCP: {fav backbone}!uoregon!oregon!goes University of Oregon | MaBell: (503) 686-3309 ________________________________________________________________________________ Grad School. Its not just a job, it's an indenture...