Re: piping / redirecting into a vbs script ?

Frank,

> It's not about filetype association, etc., but about what translates
> <filename> to <filename>.vbs *before* filetype association takes places,

Only for you and John.   For me its absolutily irrelevant.

If you think its causing the stated problem than just add the ".vbs" 
extension to the two lines in my first example see if it changes anything.

Newsflash : It doesn't.

>> He discovered the solution was to specify the .vbs extension on the
>> filename to get that handler to read the text file to run the script.
>
>  Nope, he 'discovered' no such thing. He specified the .vbs extension
> *and* he added wscript.exe to interpret the .vbs file.

He's quite the moron, isn't he ?  Still enjoying yourself trying to get him
to even just fully read what is infront of his nose (let alone correctly 
interpret it) ?   Yeah, me neither.

But "no" to the "he added wscript.exe to interpret the .vbs file" part.

The "wscript.exe" and than the ".vbs" extension can be removed (see the
first example). The vbscript gets run (interpreted by wscript.exe) in all 
cases.

Which means that the reason I, in the second example, added "wscript.exe" 
must have been quite different.

Regards,
Rudy Wieser