Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!rpi!clarkson!grape.ecs.clarkson.edu!nelson From: nelson@sun.soe.clarkson.edu (Russ Nelson) Newsgroups: comp.dcom.lans Subject: Re: WNQVTNET Message-ID: Date: 23 Dec 90 01:09:38 GMT References: <2564.2770c153@waikato.ac.nz> <1990Dec22.225314.29982@ux1.cso.uiuc.edu> Sender: @grape.ecs.clarkson.edu Reply-To: nelson@clutx.clarkson.edu (aka NELSON@CLUTX.BITNET) Organization: Clarkson University, Potsdam NY Lines: 22 In-Reply-To: randy@ux1.cso.uiuc.edu's message of Sat, 22 Dec 1990 22:53:14 GMT In article <1990Dec22.225314.29982@ux1.cso.uiuc.edu> randy@ux1.cso.uiuc.edu (Randall E. Cotton) writes: Yes, seems to work fine, though WNQVTNET is a slight bit unstable - i.e. it crashes the machine hard every once in a while. Here's my setup: IBM PS/2 Model 55SX DOS 4.0 3COM 3C523 (Etherlink/MC) card 3C523 packet driver version 7.1.1, invoked with -w (windows compatibility) pktint driver (comes with WinQVT/Net - necessary, I believe) Novell revision 3 shells running in extended memory (XMSNET4) Windows 3.0 running in 386 enhanced mode WinQVT/Net version 1.31 You shouldn't need to use the -w switch. It just ensures that Windows doesn't swap your application out from under the packet driver. WinQVT/Net's pktint driver takes care of this case for you. -- --russ (nelson@clutx [.bitnet | .clarkson.edu]) FAX 315-268-7600 It's better to get mugged than to live a life of fear -- Freeman Dyson I joined the League for Programming Freedom, and I hope you'll join too.