les@chinet.chi.il.us (Leslie Mikesell) (04/10/91)
Are there any terminal emulators that will run under Windows 3.0 that will allow several simultaneous connections via Starlan to different unix machines on the net? I'm currently using the virtual terminals on the console of a '386 running unix to accomplish this, but for several reasons I would like to run Windows locally and have all the unix sessions elsewhere. The terminal screens don't have to be sizable, but they do have to be updated in the background, and I need to maintain at least 6 sessions without bothering the foreground application too much when they are not busy. Les Mikesell les@chinet.chi.il.us
norm@cfctech.cfc.com (Norman J. Meluch) (04/12/91)
les@chinet.chi.il.us (Leslie Mikesell) writes: {L} Are there any terminal emulators that will run under Windows 3.0 {L} that will allow several simultaneous connections via Starlan to {L} different unix machines on the net? I do believe that the KERMIT.EXE that is supplied with the LAN on your attutil drive should be good for such a purpose. If you run multiple copies of that emulator they are smart enough to keep separate name table entries for their business. Admittedly six copies of kermit running is a bit RAM intensive, but it should work. - Norm. -- |~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Norman J. Meluch ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| | Mail: norm@cfctech.cfc.com Fax:(313)948-4975 Voice:(313)948-4809 | | Note: The opinions expressed here are in no way to be confused with valid | |_______ideas or corporate policy.____________________________________________|
les@chinet.chi.il.us (Leslie Mikesell) (04/12/91)
In article <1991Apr11.191057.25489@cfctech.cfc.com> norm@cfctech.cfc.com (Norman J. Meluch) writes: >les@chinet.chi.il.us (Leslie Mikesell) writes: >{L} Are there any terminal emulators that will run under Windows 3.0 >{L} that will allow several simultaneous connections via Starlan to >{L} different unix machines on the net? >I do believe that the KERMIT.EXE that is supplied with the LAN >on your attutil drive should be good for such a purpose. If you >run multiple copies of that emulator they are smart enough to >keep separate name table entries for their business. Admittedly >six copies of kermit running is a bit RAM intensive, but it >should work. That's what I wanted to hear, but when I tried it a while back, I couldn't switch out of a connected session with the <alt><tab>. Now I just tried it again and everything works fine. I'm testing on someone else's 386 with Windows, so I don't know what has changed in the Windows setup. Anyway, it looks like it can be done. The screens don't appear to update while you are switched out the way the unix virtual consoles do, but they don't lose anything either (and unlike AT&T's 386 console, you can set the background color sensibly). If anyone else has tried multiple kermits with windows, maybe they can share the setup tricks. Les Mikesell les@chinet.chi.il.us
jbreeden@netcom.COM (John Breeden) (04/14/91)
In article <1991Apr10.153533.17603@chinet.chi.il.us> les@chinet.chi.il.us (Leslie Mikesell) writes: >Are there any terminal emulators that will run under Windows 3.0 >that will allow several simultaneous connections via Starlan to >different unix machines on the net? I'm currently using the >virtual terminals on the console of a '386 running unix to accomplish >this, but for several reasons I would like to run Windows locally >and have all the unix sessions elsewhere. The terminal screens >don't have to be sizable, but they do have to be updated in the >background, and I need to maintain at least 6 sessions without >bothering the foreground application too much when they are not busy. Got TCP-IP running on the hosts? Try this: WinQVTNET (shareware TCP-IP for Windows). Available on cira.cira.indiana.edu. You say you have Starlan, could mean a few things: 1. You have Starlan hardware (1meg/1base5 or 10meg/10baseT) and no network operating system. Then you need the Clarkson Packet Driver for the AT&T Starlan card (1 or 10 mb) (winqvt runs on top of the packet driver which runs ontop of the Starlan card). You can get the packet drivers from sun.soe.clarkson.edu. The name of the Starlan card packet driver is at&t.com. 2. You are running Starlan hardware AND StarGROUP software, well you need: A. StarGROUP Version 3.3 OR HIGHER (must be Lan Man/X). B. If you are using Starlan cards, you need the StarGROUP NDIS MAC driver (attcsma.dos) version 3.4 OR HIGHER (get that from the hot line). C. You need the Packet Driver to NDIS driver adapter DIS_PKT.DOS version 1.6 (get that from netlab.usu.edu). WinQVT talks to DIS_PKT.DOS which talks to the NDIS MAC driver, which talks to the Starlan card. The real "spiffy" thing about this setup is both StarGROUP and WinQVT run concurrently without needing to re-boot - all under Windows (that's why you need the NDIS MAC driver V3.4 - it's a multiprotocol NDIS driver, supports multiple, cuncurrent protocols through a single card, in this case StarGROUP/LMX and tcp-ip). BTW: WinQVTnet supports 12 concurrent telnet sessions. -- John Robert Breeden, jbreeden@netcom.com, apple!netcom!jbreeden, ATTMAIL:!jbreeden ------------------------------------------------------------------- "The nice thing about standards is that you have so many to choose from. If you don't like any of them, you just wait for next year's model."
brad@bradley.bradley.edu (Bradley E. Smith) (04/19/91)
jbreeden@netcom.COM (John Breeden) writes: > Got TCP-IP running on the hosts? Try this: > > WinQVTNET (shareware TCP-IP for Windows). Available on cira.cira.indiana.edu. > 2. You are running Starlan hardware AND StarGROUP software, well you need: > > A. StarGROUP Version 3.3 OR HIGHER (must be Lan Man/X). > B. If you are using Starlan cards, you need the StarGROUP NDIS MAC driver > (attcsma.dos) version 3.4 OR HIGHER (get that from the hot line). > C. You need the Packet Driver to NDIS driver adapter DIS_PKT.DOS version > 1.6 (get that from netlab.usu.edu). > > WinQVT talks to DIS_PKT.DOS which talks to the NDIS MAC driver, which > talks to the Starlan card. I have all this and still get 'Network Initialization Error' when I try to use the program. My questions are following: 1. What does your config.sys look like? 2. What does your lanman.dos/drivers/star10/protocol.ini look like? 3. What does your qvt_tcp.rc (or what ever) look like? -- Bradley Smith Network & Technical Services @ Bradley University, Peoria, IL brad@bradley.edu --- 309-677-2337
les@chinet.chi.il.us (Leslie Mikesell) (04/19/91)
In article <1991Apr13.202940.6393@netcom.COM> jbreeden@netcom.COM (John Breeden) writes: >Got TCP-IP running on the hosts? Try this: >WinQVTNET (shareware TCP-IP for Windows). Available on cira.cira.indiana.edu. No, but I'm beginning to wish I did... >You say you have Starlan, could mean a few things: It only meant one thing back when I got it. >2. You are running Starlan hardware AND StarGROUP software, well you need: > > A. StarGROUP Version 3.3 OR HIGHER (must be Lan Man/X). > B. If you are using Starlan cards, you need the StarGROUP NDIS MAC driver > (attcsma.dos) version 3.4 OR HIGHER (get that from the hot line). > C. You need the Packet Driver to NDIS driver adapter DIS_PKT.DOS version > 1.6 (get that from netlab.usu.edu). > > WinQVT talks to DIS_PKT.DOS which talks to the NDIS MAC driver, which > talks to the Starlan card. > > The real "spiffy" thing about this setup is both StarGROUP and WinQVT > run concurrently without needing to re-boot - all under Windows (that's > why you need the NDIS MAC driver V3.4 - it's a multiprotocol NDIS driver, > supports multiple, cuncurrent protocols through a single card, in this > case StarGROUP/LMX and tcp-ip). What about the unix end? What do I need to run TCP/IP over the 1Mb starlan card, and can it run concurrently with the StarGROUP OSI protocol? I'm currently running SysVr3.2.1 and the 3.2 DOS server and was not planning to change anything until I can switch to SysVr4. Will all these things run under r4 and will they still talk to 3B2s running 3.2? Oh, some of the machines I want to log into are the 3B2's - is there a TCP/IP suite for the 1M starlan boards there as well? Les Mikesell les@chinet.chi.il.us