danderer@sun.acs.udel.edu (Dave Anderer) (11/11/89)
I'm frustrated. I'm running an IBM PS/2 Model 55 with 2 Mb RAM. It has a 3Com 3c523 Ethernet card in it and is connected to our Novell SFT 2.15 LAN. I'm using the 4.0-alpha packet driver software under Netware. I'm also running the Clarkson-modified NCSA Telnet version 2.2 over the packet driver. This all works together very nicely. I'm also using DESQview 2.2 and QEMM. Again, no problems, EXCEPT that I can't make Telnet live nicely under DESQview. It works fine if it's the only program running under DESQview. It work some of the time when it is coexisting under DESQview with a 2nd program. But much of the time it will crash the machine within a few seconds of loading the 2nd program. I've crashed Telnet running it with Word Perfect 5.0, Procomm, Brief, etc. I'm no DESQview novice. I've been running comm programs under DESQview for several years. I've got the programs 'correctly' installed as I see it - Telnet can't be swapped out, it does run in background, etc. I've played with all the DESQview options for protection levels, keyboard levels, etc. I just can't get it to run. Does anyone have it working? If so, what the h*ll am I missing..??? Thanks. -- Dave Anderer Academic Computing and Instructional Technology/Research and Development University of Delaware
greg@hprnd.HP.COM (Greg Dolkas) (11/14/89)
I, too, had problems with NCSA 2.2D. I found that the standard 2.1 release didn't have near the problems under DESQview. It still crashes once in a while, but with an acceptable MTBF, and only when things get real hairy. I regularly run NCSA as the only program RUNNING in background with 6-10 other programs loaded. On occasion I let other programs run in background, and so far I haven't been able to blame any of them directly on a crash. I have an HP Vectra ES/12 (12 mhz 286) with 4 meg. My guess is that the extra features in 2.2D eat up too much CPU time, which gets the LAN driver in trouble by being timesliced in the middle of something important. If you don't need the added features, try 2.1. Greg.
ssw@cica.cica.indiana.edu (Steve Wallace) (11/14/89)
The packed driver is designed to call packet handling
routines at specific address. When you start telnet, telnet
configures the packet driver to jump to a specific memory address
when an IP packet comes in on the interface. When using desqview
to multitask, there is no guaranty that telnet is swapped in when
the packet driver receive an IP packet. If telnet isn't swapped
in that instant, the packet jumps to the code of another program
and usually hangs the computer. The Novell driver (ipx.com) is
loaded before desqview and therefore is never swapped out.
The only way to get a second program to run with telnet is
to get two ethernet cards. One card for your novell connection
and one for telnet. The packet driver for the telnet card should be loaded
within the same desqview window as telnet.
Steven Wallace
Indiana University
ssw@lavanix.bacs.indiana.edu
:q