reynolds@milton.u.washington.edu (Michael Reynolds) (07/14/90)
Hey, has anyone found any solutions for my problem? Our campus uses NCSA Telnet and Clarkston 3c503.com drivers for Etherlink II cards on Zenith 386s. I use MS Windows 3.0 and want to be able to keep an ftp session going at the same time as my telnet. It seems to me that I'll at least need a 3c503 packet driver that I can load before Windows, so that all my DOS sessions have access to it. Steve Wallace at Indiana Univ (wallaces@ucs.indiana.edu) has made one that does that, but it still won't let more than one program access it at a time. Is this wanting too much? I became hopeful when I heard about the code that people came up with to allow Novell and Telnet to share the packet driver. Would it be possible (has it been done?) to do the same thing with ftp and telnet sharing the packet driver? Have I got my concepts all wrong (I'm totally novice at packet driver programming)? What would really be nice is a Windows- specific Telnet that spawns new sessions in their own Windows, or better yet lets two or more copies share the packet driver. I know this isn't Windows-specific for Windows newsgroup, but along the same lines, I would also like to be able to use NetBios with my Ethernet card at the same time to communicate with a LANtastic network. Artisoft tells me that I need a full implementation of a reentrant NetBios. I've found one company (Performance Technologies, 918-663-9907) that can sell me a re-entrant NetBios that doesn't use packet driver, and FTP Software, who can sell me a NetBios for packet driver that isn't reentrant. Does anybody know if someone has written/is working on such a program? Is this even possible? Thanks for any help. I'll post a summary of replies if there's interest. Mike Reynolds Libraries Computer Operations University of Washington Seattle, WA reynolds@milton.u.washington.edu
davidr@hplsla.HP.COM (David M. Reed) (07/19/90)
I do not know about your packet driver, but I have a comment about trying to run multiple telnet sessions under MSWindows 3.0. MSWindows3 does not have true multi-tasking, particularly in support of MS-DOS programs running under MSWindows (in comparison to MSWindows applications). There are many things that can delay or stop an MS-DOS program that is running in the background from getting any clock ticks. Since telnet requires a constant communication (I do not know how frequent, but it is regular) it is quite common to have any telnet sessions running in the background to close. This happens with the telnet in PC-NFS from Sun, and the one in PC/TCP from FTP Software, both of which access the LAN card via device drivers. So, while you can start up several sessions, you will probably not like having such connections drop randomly, irregularly.
ssw@cica.cica.indiana.edu (Steve Wallace) (07/20/90)
Using a modified packet driver and windows in enhanced mode, it is possible to run telnet in the background WITHOUT loosing connections. You must set detect idle time off and Lock application memory on. We have tested telnet in the background for 72 hours without losing a connection. Durring the test we ran all sorts of windows and dos applications (including formating a disk) and never lost the connection. Durring the test we had a unix host ping the telnet client and record the results. Telnet did drop some of the ping packets, but not more than 20 percent. Steven Wallace Indiana University wallaces@ucs.indiana.edu
kleonard@gvlv1.gvl.unisys.com (Ken Leonard) (07/20/90)
In article <ssw.648412409@cica> ssw@cica.cica.indiana.edu (Steve Wallace) writes:
* Using a modified packet driver and windows in enhanced mode, it is possible
..........^^^^^^^^^^^^^^^^^^^^^^
-----which? how? where-to-get?
--
* to run telnet in the background WITHOUT loosing connections. You must
* set detect idle time off and Lock application memory on. We have tested
......^^^^^^^^^^^^^^^^.........^^^^^^^^^^^^^^^^^^^^^^^
-----parameters of what program? ...win3?
--(I don't have my copy of win3, yet)
--
* telnet in the background for 72 hours without losing a connection. Durring
-----not too shabby!
--
* the test we ran all sorts of windows and dos applications (including
* formating a disk) and never lost the connection. Durring the test we
* had a unix host ping the telnet client and record the results. Telnet
* did drop some of the ping packets, but not more than 20 percent.
---------------
curiously,
Kenssw@cica.cica.indiana.edu (Steve Wallace) (07/21/90)
Packet drivers, modified to support applications running under MicroSoft's Windows 3.0 enhanced mode, are available via anonymous ftp from 129.79.16.96 /pub/network/packets/alpha. The testing has been moderate and no problems have been reported. These packet drivers will also work in a non-Windows environment. Please read the read.me file and report any problems to: Steven Wallace wallaces@ucs.indiana.edu