minicom runscript

[Adam Lackorzynski]

Hi Tim,

On Fri Oct 31, 2008 at 22:39:58 +0000, Tim Smyth wrote:
> I picked your email address up off the Alioth Developer profile page on
> minicom.  I was wondering if you could answer a question regarding minicom
> runscript please?
> 
> I am trying to run a send zmodem command using a runscript (i.e. invoked in
> the prompt by minicom -S databuoy.runscript).  I am logged onto a Ubuntu
> linux box which then communicates with another linux box, running Wolvix
> (slackware) linux over a radio-modem link.
> 
> I can manually run minicom, log into the slackware box and issue the command
> 
> 
> sz -b -q -y outgoing.tar.gz
> 
> and the file download progress window pops up and then prompts me for
> "READY: press any key to continue..." when the file is downloaded.
> 
> However when I try and invoke this within runscript, no such download
> progress window is in evidence and the runscript hangs and eventually times
> out with no file downloaded.  The gist of my script is below.  I am assuming
> this is because the download progress window is sent to stderr (gleaned from
> the web) and this cannot be handled within runscript?
> 
> I would be grateful for any insight you can give me on this please?

This should not have to do anything with stderr v. stdout because this
does not affect the serial line, all's the same when it comes out on the
other side.

At which point does it bail out? When checking for the "**B00" or the
later one? Maybe the ^C?




>    send "sz -b -q -y outgoing.tar.gz"
>    expect {
>      "**B00"
>      timeout 60 goto panic
>      }
>    send "^C"
>    expect {
>       "READY: press any key to continue..."
>       timeout 60 goto panic
>      }
>    send "\r\r"



Adam
-- 
Adam                 adam at os.inf.tu-dresden.de
  Lackorzynski         http://os.inf.tu-dresden.de/~adam/