home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.protocols.tcp-ip.ibmpc
- Path: sparky!uunet!usc!cs.utexas.edu!torn!maccs!khindria
- From: khindria@maccs.dcss.mcmaster.ca (Vivek Khindria (CSU))
- Subject: Re: 3C503 driver/NCSA Telnet problem
- Message-ID: <1992Nov6.135410.14179@maccs.dcss.mcmaster.ca>
- Organization: McMaster University, Hamilton, Ontario, Canada.
- References: <1992Oct28.191618.7365@europa.asd.contel.com> <wetzels-041192135338@wetzels_1.amc.uva.nl>
- Date: Fri, 6 Nov 1992 13:54:10 GMT
- Lines: 23
-
-
- I have had a lot of fun with the 3c503 card. I do have it working though.
-
- Here are a couple of points that may help you:
-
- 1. Determine whether your driver can support shared memory or not. If
- not make sure you set the jumper to disable on the card.
-
- 2. Next, if you do select shared memory, make sure that the selected
- memory range is excluded from programs like EMM836.exe and QEMM.sys
- and 386MAX etc.
-
- 3. While trouble shooting set the cabling option to thin, and put a
- T connector with two terminating resistors on. Use the 3c503 diag
- program to ensure all is well before using your software to test
- your configuration. (this program is available on ftp.3com.com)
-
- But now that the 3c509 card is out, you may not want to spend a lot of time
- on this.
-
- Vivek Khindria
- McMaster University, Hamilton, Ontario, Canada
-
-