Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!border3.nntp.dca.giganews.com!Xl.tags.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local2.nntp.dca.giganews.com!nntp.posted.nuvoxcommunications!news.posted.nuvoxcommunications.POSTED!not-for-mail NNTP-Posting-Date: Tue, 13 Dec 2011 10:58:14 -0600 Newsgroups: comp.protocols.kermit.misc References: Organization: Gizmos & Gadgets, Ltd. Subject: Re: Sending from script to serial port in K95g X-Newsreader: trn 4.0-test77 (Sep 1, 2010) From: bonomi@host122.r-bonomi.com (Robert Bonomi) Originator: bonomi@host122.r-bonomi.com (Robert Bonomi) Message-ID: Date: Tue, 13 Dec 2011 10:58:14 -0600 Lines: 32 X-Usenet-Provider: http://www.giganews.com NNTP-Posting-Host: 204.87.227.120 X-Trace: sv3-NWcJrO09hyhWNMsKUcFXyiYLyZamkF7P05os/kVMurysXD5bIwDheZL3QYVol3/jwyIQxhwggFnF04G!YxaSk2/LWJcIQW+I4hRhpRNJMvwTYccHJhp7kPYJlMBAnKnYi60S/JZA8n7cnKEnbSDD0KFNh8e6!4aqGjFlW02JCgUlCBg4Bc1M52Pu6vS61lQkUtax/lLn9 X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.40 X-Original-Bytes: 2629 Xref: x330-a1.tempe.blueboxinc.net comp.protocols.kermit.misc:19 In article , John wrote: >The following is a partial script I developed under Windows XP to set >up a ham radio >Terminal Network Controller (tnc). It works under XP. I'm trying to >use the same USB serial >dongle on a new machine running Windows 7 Home Premium. Under W7, the >script outputs gibberish to the tnc. If I type the lineout commands >one at a time, >at the Kermit prompt, the commands go to the tnc and it responds >correctly. But >the same lineout commands running in the script result in gibberish. >The same >thing happens with two very dissimilar tncs (A Kenwood TM-D700A and an >AEA >PK-232MBX; if you don't recognize the tnc, don't worry about it. I >can't imagine >that's where the problem could be.) Any Kermit gurus have an idea why >this would be? Some obvious things to try. 1) turn on _complete_ logging, *show* the log results of 'doing things manually' where it works AND the results of the scripted run, where things are garbled. (in both cases, show -everything- from the beginning of the session. what happens -before- the problem shows up is significant_ 2) see what happens with just a -single- command to the TNC where the string of 'telltnc' calls is? 3) try a 'sleep 1' after every lineout, and/or 'telltnc' >The serial port is a USB dongle with the Prolific innards, using the >latest driver.