Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!rpi!clarkson!grape.ecs.clarkson.edu!nelson From: nelson@sun.soe.clarkson.edu (Russ Nelson) Newsgroups: comp.protocols.tcp-ip.ibmpc Subject: Re: BW-NFS, working with Packet Drivers and other software. Message-ID: Date: 12 Apr 91 02:56:30 GMT References: <9104081632.AA04236@ftp.com> <1991Apr11.141125.27490@mav.com> Sender: usenet@grape.ecs.clarkson.edu Reply-To: nelson@clutx.clarkson.edu (aka NELSON@CLUTX.BITNET) Organization: Clarkson University, Potsdam NY Lines: 27 In-Reply-To: stu@mav.com's message of 11 Apr 91 14:11:25 GMT In article <1991Apr11.141125.27490@mav.com> stu@mav.com (Stu Donaldson) writes: Is there a way to temporarily unload or put on hold, the main application? Essentially block that application from the packet driver, and start up some other application such as an email package, then enable the main application again? Possibly an alternate packet driver interrupt vector that when in use, would cause the primary vector to be on hold? Sure. Just hack at the packet driver skeleton so that it doesn't check to see if a type is already in use, and force the type search to be most-recent-first. But that's still not going to solve *all* your problems. What happens if TCP2 tries to communicate with a host that TCP1 was communicating with? Most likely, the TCP1 connections will get shut down. Yes, the user can avoid doing that, but I certainly wouldn't want to explain that restriction to all of my users. If you make this change, remember that the copyright on the Clarkson collection of packet drivers requires that you prominently state that changes have been made. No way do I want to get any questions on *this* puppy... -- --russ I'm proud to be a humble Quaker. 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.