NETWORK@FRSAC11.BITNET (11/10/89)
Date: 09 November 1989, 19:18:27 GMT From: NETWORK at FRSAC11 To: pcip@udel.edu I use NCSA Telnet 2.2D & 2.2tn, and the most recent version of KA9Q NOS. With the 3Com 501 Enet card NCSA runs with the packet as well as the internal driver. NOS runs with the packet driver. I cant have any of those run with a 3Com 503 packet driver. Any help ? Something special with 3C503, or is it the packet driver ? (The loading of the driver goes OK, but NCSA or NOS get stuck, no message.) Regards, Jean-Pierre H. Dumas network@frsac11 (bitnet) network%frsac11.bitnet@cunyvm.cuny.edu (arpanet) dumas@sumex-aim.stanford.edu (arpanet)
ajt@mace.cc.purdue.edu (Andy Thomas) (11/16/89)
In article <8911091338.aa14138@louie.udel.edu> NETWORK@FRSAC11.BITNET writes: > >I use NCSA Telnet 2.2D & 2.2tn, and the most recent version of KA9Q NOS. >With the 3Com 501 Enet card NCSA runs with the packet as well as the internal >driver. >NOS runs with the packet driver. > >I cant have any of those run with a 3Com 503 packet driver. > >Any help ? Something special with 3C503, or is it the packet driver ? >(The loading of the driver goes OK, but NCSA or NOS get stuck, no message.) I don't know if this will help or not. I had version 3.1 of the 3C503 packet driver. It would not work with NCSA telnet program. After looking at the source, I found that the packet driver initialization is assuming thin ethernet. I was using thick ethernet. By changing ECNTRL_THIN from 002h to 000 in the 3C503.ASM file, it will work with thick ethernet. If you don't have the source you can patch the .COM file with debug. Address Old value New value 935 3 1 938 2 0 93b 6 4 958 2 0 Andy Thomas ajt@bilbo.bio.purdue.edu
clements@bbn.com (Bob Clements) (11/16/89)
In article <3560@mace.cc.purdue.edu> ajt@mace.cc.purdue.edu (Andy Thomas) writes: > [...] I had version 3.1 of the 3C503 >packet driver. It would not work with NCSA telnet program. After looking >at the source, I found that the packet driver initialization is assuming >thin ethernet. I was using thick ethernet. > [and gives a binary patch] Yes, that was a serious boo-boo on my part, not allowing for thick-net. I based the driver on my earlier WD8003E driver where the transceiver type is selected by a jumper. In the 3C503 it is selected by software, and I forgot to deal with that. The current release of the driver (get it from Clarkson) has a command-line option to select thick versus thin. >Andy Thomas >ajt@bilbo.bio.purdue.edu Bob Clements, K1BC, clements@bbn.com