patman@lotus.com (Pat Mancuso) (01/05/91)
I have been trying to get the nb.com packet driver working with WinQVTNet (and NCSA Telnet) without success. I'm mainly interested in getting WinQVTNet working, but I've been trying Telnet just to reduce the number of variables. I can get both to work just fine with the 3c503 driver, so I think that the rest of my config files are OK. The problem with the hw driver is that it kills any pre-existing network stuff (3com or Novell for ex.). As soon as I change from the 3c503 driver to the nb driver, it stops working. I'd like to have the 3open network (or Novell) facilities available to me in addition to the tcp stuff (via the netbios packet driver). Is this possible? From what I've read (nb.not), I've only heard this driver working on top of a sytek netbios... I'm trying to use the netbios driver on top of a 3open netbios facility (although I've also tried Novell with similar results...)- config.sys: device=protoman.dos /I:<path> device=elnkii.dos device=xnstp.dos autoexec: nbp netbind config.tel: netmask=255.255.0.0 ... hardware=packet address=6 ioaddr=0 ... mtu=512 maxseg=440 rwin=440 ... startup: nb 0x7e my.ip.ad.dress 1024 telnet All I get is a bunch of s's (lowercase) across the top of the screen. Looking at the source for the nb driver, that says it's sending, but I can never get it to connect to anything. I'm using the latest version of nb.com (the version with the -w -d -n stuff) dated 8-29-90. The fact that there's an 's' coded into the driver (and other things) leads me to think that the nb driver isn't quite 'done' and it might not work with non-sytek netbioses. True? What's the deal? Is it possible to get both 3open and tcp working at the same time with the nb.com driver? HOW????!?!?!?!?! signed- Frustrated. -- Pat Mancuso - patman@lotus.com