Firewalker82
Fri Jul 04 04:32:00 CDT 2008
Thanks urkec,
I looked at the example on MSDN and implemented this into my script. It
returned an echo box with all stdout information. I am now starting to think
that this app (synctoy 2.0) does not write file synchronisation errors to the
stderr stream as the msdn script should pick all this information from the
streams up and display them. Another thought on this one is that the
application is doing what it is supposed to as it does perform a sync fine
and reports problematic files that it couldnt copy. This is the information
that I would like to read in the script so that I can see which files
(including names and locations) did not synchronise, rather than a summary
displaying how many files didn't complete.
thanks anyway
--
Firewalker82
"urkec" wrote:
> "Firewalker82" wrote:
>
> > An anybody provide me with the answer to the following;
> >
> > I am calling an wshshell.exec to execute a program. I can read the stdout
> > perfectly from this, but I would like to read the stderror so that it
> > provides more information as to what went wrong. I have tried playing around
> > with vbs and reading the stderr stream, but nothing seemes to be streamed
> > into this property. If I can get this to work then I would probably output
> > it to screen or a text file for further troubleshooting.
> >
> >
> > Thanks
> >
> > --
> > Firewalker82
>
>
>
> There us a sample here:
>
>
http://msdn.microsoft.com/en-us/library/ye284tb8(VS.85).aspx
>
> --
> urkec