Groups > microsoft.public.scripting.vbscript > #12294

Re: using wshell.exec causes lockup while reading the output - what to do ?

From	"R.Wieser" <address@not.available>
Newsgroups	microsoft.public.scripting.vbscript
Subject	Re: using wshell.exec causes lockup while reading the output - what to do ?
Date	2020-06-21 17:46 +0200
Organization	Aioe.org NNTP Server
Message-ID	<rcnvcr$l0k$1@gioia.aioe.org> (permalink)
References	(7 earlier) <1vf0vvxzvl94a$.dnimmt0ejgd7.dlg@40tude.net> <rclf40$1rbo$1@gioia.aioe.org> <d5jtnvqdr7y1$.1uccticx73yfr$.dlg@40tude.net> <rcn04m$1d6p$1@gioia.aioe.org> <1ap5mqmz7zeqr$.g3ju1vepshc1.dlg@40tude.net>

Show all headers | View raw

JJ,

> My conclusion was that, it's an impossible job
> for TextStream.

To be honest, I could not care less what method "exec" would use to buffer 
the data. :-)   As long as it allows me do stupidly basic things like a "is 
the buffer empty", or the even better "how much data is available for 
reading" check.   And perhaps a "read as much as you can, but return 
immediatily" method.

>I ended up creating a custom native program
> to handle the program outputs.

Yeah, I was already thinking of that too*, but first wanted to make sure I 
had not overlooked some dumb thing.

*and wrap it into an ActiveX component.

Thanks for the responses.

Regards,
Rudy Wieser

Back to microsoft.public.scripting.vbscript | Previous | Next — Previous in thread | Find similar

Thread

using wshell.exec causes lockup while reading the output - what to do ? "R.Wieser" <address@not.available> - 2020-06-17 14:32 +0200
  Re: using wshell.exec causes lockup while reading the output - what to do ? "Mayayana" <mayayana@invalid.nospam> - 2020-06-17 08:48 -0400
  Re: using wshell.exec causes lockup while reading the output - what to do ? JJ <jj4public@vfemail.net> - 2020-06-17 22:12 +0700
    Re: using wshell.exec causes lockup while reading the output - what to do ? "R.Wieser" <address@not.available> - 2020-06-17 18:51 +0200
      Re: using wshell.exec causes lockup while reading the output - what to do ? JJ <jj4public@vfemail.net> - 2020-06-18 19:42 +0700
        Re: using wshell.exec causes lockup while reading the output - what to do ? "R.Wieser" <address@not.available> - 2020-06-18 17:26 +0200
          Re: using wshell.exec causes lockup while reading the output - what to do ? JJ <jj4public@vfemail.net> - 2020-06-19 21:16 +0700
            Re: using wshell.exec causes lockup while reading the output - what to do ? "R.Wieser" <address@not.available> - 2020-06-19 19:08 +0200
              Re: using wshell.exec causes lockup while reading the output - what to do ? JJ <jj4public@vfemail.net> - 2020-06-20 22:40 +0700
                Re: using wshell.exec causes lockup while reading the output - what to do ? "R.Wieser" <address@not.available> - 2020-06-20 18:56 +0200
                Re: using wshell.exec causes lockup while reading the output - what to do ? JJ <jj4public@vfemail.net> - 2020-06-21 12:33 +0700
                Re: using wshell.exec causes lockup while reading the output - what to do ? "R.Wieser" <address@not.available> - 2020-06-21 08:53 +0200
                Re: using wshell.exec causes lockup while reading the output - what to do ? JJ <jj4public@vfemail.net> - 2020-06-21 20:58 +0700
                Re: using wshell.exec causes lockup while reading the output - what to do ? "R.Wieser" <address@not.available> - 2020-06-21 17:46 +0200

csiph-web