bhudack@orion.oac.uci.edu (Bob Hudack) (11/10/90)
---- I'm running Windows on an AST Premium 386 with 4MB. After the usual amount of fussing, I got Windows up and running, along with non-Windows apps, etc. Everything works great EXCEPT Telnet. It starts all right, but freezes my PC within a minute after I start it. Often the screen goes blank. Win/QVT NET works great, but I have to support users who do data entry and want the larger standard screen type that Telnet uses. If it makes any difference, I'm using a packet driver and am also connected to a Novell network. I thought setting BIOS=YES in my config file would take care of the problem, but it didn't. Telnet works great outside of Windows. Any ideas? PIF or CONFIG.TEL settings? Any help you can give will be greatly appreciated. -- Bob Hudack Microcomputer Services Group Computing Facility University of California, Irvine RJHUDACK@UCI.BITNET
margan-aleks@cs.yale.edu (margan-aleks) (11/10/90)
In article <273AF6CC.476@orion.oac.uci.edu> bhudack@orion.oac.uci.edu (Bob Hudack) writes: >---- >I'm running Windows on an AST Premium 386 with 4MB. After the usual amount of >fussing, I got Windows up and running, along with non-Windows apps, etc. > >Everything works great EXCEPT Telnet. It starts all right, but freezes my PC >within a minute after I start it. Often the screen goes blank. > >Win/QVT NET works great, but I have to support users who do data entry and want >the larger standard screen type that Telnet uses. > >If it makes any difference, I'm using a packet driver and am also connected >to a Novell network. I thought setting BIOS=YES in my config file would take >care of the problem, but it didn't. > >Telnet works great outside of Windows. Any ideas? PIF or CONFIG.TEL settings? >Any help you can give will be greatly appreciated. >-- >Bob Hudack >Microcomputer Services Group >Computing Facility >University of California, Irvine RJHUDACK@UCI.BITNET I had the same problem when loading the drivers before starting windows. By creating a batch file that loads the drivers first and then starts NCSA Telnet I solved my problem. The sessions still die, however, when I leave them in- active (i.e. make another window active) for more than 10 minutes.