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
jbvb@VAX.FTP.COM ("James B. Van Bokkelen") (07/16/90)
Windows 3.0 is much more of an operating system than DOS is, but still a good deal less than OS/2 is. There are a number of obstacles that you'd need to surmount to use NCSA in multiple windows, the largest being separating the TCP/IP protocol stack from the Telnet/FTP layer so they can be shared by multiple applications. We're working on it, Sun is probably working on it, TWG is probably working on it. I don't have a reliable date yet, and I haven't heard any promises from other vendors. Regarding the NETBIOS re-entrancy - if you got specifics about why it is required from Artisoft, or have someone there who can talk internals with us, let me know. The code we currently have in beta test might help too... James B. VanBokkelen 26 Princess St., Wakefield, MA 01880 FTP Software Inc. voice: (617) 246-0900 fax: (617) 246-0901
beame@maccs.dcss.mcmaster.ca (Carl Beame) (07/20/90)
In article <9007161418.AA02691@vax.ftp.com> jbvb@vax.ftp.com writes: >Windows 3.0 is much more of an operating system than DOS is, but still >a good deal less than OS/2 is. There are a number of obstacles that >you'd need to surmount to use NCSA in multiple windows, the largest being >separating the TCP/IP protocol stack from the Telnet/FTP layer so they >can be shared by multiple applications. We're working on it, Sun is >probably working on it, TWG is probably working on it. I don't have >a reliable date yet, and I haven't heard any promises from other vendors. > Beame & Whiteside Software LTD. TCP/IP , NFS and sockets interface is fully compatible with Windows 3.0 running in protected mode. Carl Beame Beame & Whiteside Software Ltd. (416) 648-6556 Beame@McMaster.CA