mra@srchtec.uucp (Michael Almond) (07/20/90)
David Barts recently asked about running both Novell and PC-NFS together. Well, I have a similar question: Has anyone tried running both 3Com network software and NCSA Telnet on the same PC? I currently have two config.sys files and two autoexec.bat files on the PC and the users switch between the two and reboot to go from 3Com to Telnet. However, many of them are griping about having to reboot their machines. If anyone could help, I would GREATLY appreciate it. Thanks in advance. - Michael R. Almond - mra@srchtec.UUCP (registered) - search technology, inc. - norcross, ga 30092 - (404) 441-1457 (work)
krumseea@tardis.ohio-state.EDU (Art Krumsee) (07/21/90)
>Has anyone tried running both 3Com network software and NCSA Telnet on the same >PC? I finally got this working last week and am very pleased with the results. To make it work you need a couple of pieces. From Clarkson you need the most current beta of CUTCP, their variant of NCSA. Second, from ftp Software you need their device driver which converts packet driver calls to NDIS calls. NDIS is a standard board level interface for software, much like the packet driver standard. I received a copy of this with the NDIS version of PC/TCP but my understanding is that FTP Software plans to place this conversion driver into the public domain. The file name is named DISPKTPM.DOS. The newest beta of CUTCP fixes a bug in older versions and in NCSA which prevents it from working with DISPKTPM.DOS. Once you have these pieces, the following instructions will get it working: The following instructions assume you are already working at a computer that is running 3+Open. Insert the statement device=DISPKTPM.DOS at the end of your CONFIG.SYS. Edit the 3Com PROTOCOL.INI file to include the following lines: [PKTDRV] drivername=PKTDRV bindings=XXXXXX intvec=0x65 XXXXXXX here refers to the header line in PROTOCOL.INI for the particular board you are using. Mine, for example, reads Etherlink/MC since that is the name in square brackets which precedes the description of my board in the adapter section of PROTOCOL.INI. With these changes in place you should be able to load CUTelnet and run. Be sure your CONFIG.TEL specifies: interface=packet interrupt=0 address=0 ioaddr=65 That should do it for you. Art Krumsee Ohio State University a_krumsee@osu.edu.