chip@tct.com (Chip Salzenberg) (04/04/91)
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?
--
Chip Salzenberg <chip@tct.com>, <uunet!pdn!tct!chip>
Brand X Industries Custodial, Refurbishing and Containment Service
When You Never, Ever Want To See It Again [tm]fks@FTP.COM (Frances Selkirk) (04/05/91)
PC/TCP does run under DesqView. The limitation involved is that you may only run one program which calls our kernel at any one time. However, there is no reason why you cannot run our telnet concurrently with something else, say, Lotus 1-2-3, using DesqView. How do the packet drivers kill DesqView? I hadn't heard of that before... Frances Kirk Selkirk info@ftp.com (617) 246-0900 FTP Software, Inc. 26 Princess Street, Wakefield, MA 01880
jackson@acf4.nyu.edu (Robert Max Jackson) (04/07/91)
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? You probably don't want the IPXPKT driver. Instead, I would guess you want the following. Before starting DV, load: 1) Clarkson packet driver (you must NOT use 61 as the packet_int_no as the FTP kernel will want it; you should use the -w parameter); 2) if you want to use Novell at the same time, now load the BYU IPX and the appropriate NET shell (properly configured)--if you don't want Novell access, skip this; 3) load the FTP kernel (ETHDRV); 4) it is best but not necessary to now load the DesqView utility called DVFTP available from the Quarterdeck bulletin board; 5) start Desqview. An alternative is to use the packet driver available from Western Digital (via their bulletin board). This comes with instructions. As far as I can tell, you MUST use DVFTP if you elect this option. It is an interesting alternative if you use Novell simultaneously because this packet driver loads after the Novell IPX and NET shell (thus you do not use the BYU ipx).
jrd@cc.usu.edu (04/07/91)
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? > -- > Chip Salzenberg <chip@tct.com>, <uunet!pdn!tct!chip> > Brand X Industries Custodial, Refurbishing and Containment Service > When You Never, Ever Want To See It Again [tm] ------------ Chip, 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.
PIRARD%vm1.ulg.ac.be@CUNYVM.CUNY.EDU (Andr'e PIRARD) (04/10/91)
On Sun, 7 Apr 91 00:22:36 GMT <pcip-request@UDEL.EDU> 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.