Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!pacbell.com!att!ucbvax!CUNYVM.CUNY.EDU!PIRARD%vm1.ulg.ac.be From: PIRARD%vm1.ulg.ac.be@CUNYVM.CUNY.EDU (Andr'e PIRARD) Newsgroups: comp.protocols.tcp-ip.ibmpc Subject: Re: Using packet drivers under DESQview Message-ID: <9104100320.aa07323@louie.udel.edu> Date: 10 Apr 91 06:34:47 GMT References: Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 30 On Sun, 7 Apr 91 00:22:36 GMT said: >In article <27FB4B33.6083@tct.com>, chip@tct.com (Chip Salzenberg) writes: >> Well, if PC/TCP won't run under DesqView, could someone tell me how to >> make the WD8003 and IPXPKT packet drivers run under DesqView? It's a >> crime not to use DesqView with an eight-megabyte '386, but because the >> packet drivers kill DesqView, I'm stuck. Any pointers? > So how come I was able to use MS-DOS Kermit twice over/under DV, >once to the serial port and again across TES/NetWare with a Packet Driver >for a WD8003E board in a second window? As usual, load networking things >outside of DV. > Joe D. Joe, Maybe you were using a 286? The pktdrv problem under DV is upcalls not being dispatched to right 386 memory space, hence the solution to load the drivers stack *within* an application so that the hardware interrupt grabber is inside and DV will switch memory space at hardware interrupt time. The 286 cannot bank memory and works either way. It all depends on if and when and who does upcalls. I read PC/TCP kernel interface has upcalls but few applications use it. A file interface sure has none. So, sorry the safe statement is networking stuff *inside* Desqwiew unless pretty sure there's no upcall from common memory to private banked. Mind that the problem appears as the proportion of time other applications get time slices during which LAN interrupts may occur. (0% with a single application or undispatchable ones). Andr'e.