Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!ub!boulder!seri!wind55!marshall From: marshall@wind55.seri.gov (Marshall L. Buhl) Newsgroups: comp.windows.ms Subject: Communications resets PC Summary: WinTerm & Xtalk reboot PC when hard connected to an off switch. Message-ID: Date: 2 Aug 90 16:47:39 GMT Sender: news@seri.gov (news) Distribution: na Organization: Solar Energy Research Institute Lines: 30 I seem to have come across a very nasty "feature" of Win3. I use Com2 to directly connect to my Unix box and Com1 is connected to a switch that allows me to connect to many computers. I have no problems with Com2. I am running on a Dell 325 with DOS 4.01 and running Win3 in 386 Enhanced mode. If my switch is turned off and I try either Terminal or Crosstalk for Windows on that port, my PC reboots itself. If I turn the switch on before starting one of the programs it works fine. However, if, after connecting to a computer, I log out and turn the switch off, that also resets my PC. If I start Win3 in Real mode, the keyboard locks up and I have to cycle the power to restart my PC. I do not have these problems when running Crosstalk XVI, Mark 4 or Kermit. I called Crosstalk and they say they do not support switches with Crosstalk for Windows. Since I have the same problem with Terminal, it is a Win3 problem and not a Crosstalk problem. Excuse me - that's "feature". The Crosstalk rep told me that the Com driver needs Carrier Detect. Maybe I could make a new cable that connects CD to DTR or something like that. Has anyone else already dealt with this problem? I haven't bothered to call MS - I don't want to be put on infinite hold. -- Marshall L. Buhl, Jr. EMAIL: marshall@seri.gov Senior Computer Missionary VOICE: (303)231-1014 Wind Research Branch 1617 Cole Blvd., Golden, CO 80401-3393 Solar Energy Research Institute Solar - safe energy for a healthy future