home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!psinntp!crynwr!nelson
- From: nelson@crynwr.com (Russell Nelson)
- Newsgroups: comp.protocols.tcp-ip.ibmpc
- Subject: 3COM503 & Clarkson
- Distribution: world
- Message-ID: <712114944snx@crynwr.com>
- References: <1682DBD60.CCDH001@UTXVM.CC.UTEXAS.EDU>
- Date: Sun, 26 Jul 92 01:42:24 GMT
- Organization: Crynwr Software
- Lines: 30
-
- In article <1682DBD60.CCDH001@UTXVM.CC.UTEXAS.EDU> CCDH001@UTXVM.CC.UTEXAS.EDU writes:
-
- I am having trouble getting Clarkson's TN3270 to work with a 3COM503
- Ethernet card and hope someone can help.
-
- The pc is a 286 system using Phoenix bios. There is about 1200k of RAM
- and there is a coprocessor installed. I believe it is running DOS 3.3
- though I'm not sure. It's definitely not 5.0. The system also has
- PC-TOOLS installed.
-
- Mistake number one: you didn't include the version number of the
- packet driver. This is important.
-
- I've checked things out and I've got the interrupt vector (0x66), the io
- address (0x300) and the interrupt number (3) set the same for the packet
- driver and inside the CONFIG.TEL file.
-
- Mistake number two: when you say hardware=packet, you don't need any
- other hardware-related parameters in CONFIG.TEL. In fact, using
- other parameters may confuse it.
-
- I've been able to get Clarkson's TCP/IP to work successfully on my work
- PS-2/60 and several Zenith 386's and never seen this problem. Is it
- possible that I've stumbled on some sort of address conflict?
-
- Mistake number three: You didn't say whether you were I/O mapping or
- memory mapping the 3c503. It matters. Releases prior to 10.5.1
- didn't do I/O mapping AT ALL. 10.5.1 may be found in drivers3.zip on
- simtel20.army.mil in pd1:<msdos.pktdrvr>.
-
- -russ <nelson@crynwr.com> I'm proud to be a humble Quaker!
- Crynwr Software Crynwr Software sells packet driver support.
- 11 Grant St. 315-268-1925 Voice [ if mail bounces, forward it ]
- Potsdam, NY 13676 315-268-9201 FAX [ to uuadmin@uu.psi.com. ]
-