XPost: alt.windows7.general   
   From: address@is.invalid   
      
   VanguardLH,   
      
   > In your first example, you specify "myvbscript" instead of   
   > "myvbscript.vbs".   
      
   Yes, and that was on purpose.   
      
   > Can't have a filetype association (to a handler aka   
   > script interpreter) without an extension on the filename.   
      
   the myvbscript "filename" as in my first example should have a .vbs   
   extension just like in my second example ?   My 'puter seems to disagree   
   with you.  Its able to, in the first example, start the provided vbscript   
   just fine.   
      
   > However, I'm not sure filetype association works in piped/redirected   
   > stdout, but you could try it.   
      
   Ehhh... Whut ?   
      
   You're suggesting to me to try what I posted as the problem of this thread ?   
   Really ?   
      
   > I suspect you must execute a program first to provide piping or   
   > redirection (to have stdin and stdout available by the program's   
   > process).   
      
   Hmmm ... AFAIKS that would create a different problem : the 'program thats   
   executed first' could abort due to not finding any input on its stdin, or   
   lose output because its stdout isn't connected yet.   
      
   > By the time the program (filetype handler) runs, assuming it does,   
   > you've already attempted piping or stdout before the program has   
   > loaded.   
      
   :-) That is what a (win32) pipe is for : you write stuff to it, and as long   
   as nobody is reading on the other end it just gets buffered.   
      
   > echo hello | myvbscript.vbs   
   > myvbscript.vbs < data.txt   
      
   But, that was something I hadn't tried yet (as providing the extension   
   should, in this case, not make any difference).  A quick test just now shows   
   that it doesn't change anything (no workie).   
      
   Regards,   
   Rudy Wieser   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)