uwekeim / wintee Goto Github PK

Sometimes there is no stdout/stderr found. For example, when run with "psexec 
-i".
In that case wtee exists with code 255.

It would be nice to write to specified file anyway.

What version of the product are you using? On what operating system?
wtee 1.0.1
Windows 7

What steps will reproduce the problem?
1. write a script that outputs a line every few seconds;
2. run it, redirecting its output to a file using wtee.

You would expect to see the output to appear when the program generates it, or 
with not much delay. But instead, you do not see anything for a long time on 
the console or in the target file.

I am using wtee 1.0.1 on Windows XP.

It would be great if the buffer was flushed to all targets (console, target 
files) upon receiving new text if a certain amount of time (e.g. 1 or 2 secs) 
have passed since the previous flush.

When using wtee a single extra character is printed as the very first
character, both on standard out and in the file.

In the file, it's ascii character 0C.  On the screen, it shows as the woman
symbol (circle with cross below)

What steps will reproduce the problem?
1. cl /O2 /GF /Fetee.exe wintee.c /link 
2. Observe errors

What is the expected output? What do you see instead?
Expected output is to create the executable.
There are two errors:

1. #include <rb\queue.h> does not work, because there is no "rb" directory. 
Should be #include "queue.h".

2. disable() is not defined (unresolved external). Perhaps it is defined in 
some obscure library, but it was not a very important feature, so I just 
removed it.

What version of the product are you using? On what operating system?
Windows 7, Visual Studio 2012. Got latest code from SVN as of November 16, 2013.

Please provide any additional information below.

What steps will reproduce the problem?
1. echo Hello World | wtee output.txt
2. echo Heyo | wtee output.txt

What is the expected output? What do you see instead?
The expected contents of output.txt are "Heyo", seeing "Heyo\norld" instead.

What version of the product are you using? On what operating system?
1.0.1, Windows 7 64 bit

Please provide any additional information below.
This makes capture of cron job logs very difficult to read, because it is 
unclear where the end of the newest log actually is.

Calling:

Batch.bat | wtee file.txt

Is the same as calling:

SETLOCAL
Batch.bat
ENDLOCAL

But sometimes you don’t want to work with local variables. And wtee gives you 
no option…

Is it possible to get stdout into the output file as well? 

Thanks,

Eelco

What steps will reproduce the problem?
1. create a long file
2. redirect the output of a program to this file using wtee; length of program 
output should be shorter than that of the previous content

You would expect the target file to be completely overwritten.
But instead, the end of the content will remain their.

I am using wtee 1.0.1 on Windows XP.

You can work around this issue by deleting the target file before running wtee 
of course, but it is not convenient, plus new users may have problems before 
realizing this is what they need to do.

When the COLOR command is used in the piped batch file, the color of
standard out is not changed.

Sample:

::test.bat
::------------------
@echo off
cls
color 4c
echo WARNING !
pause
::------------------

If you execute "test.bat" alone, the output is red text on a dark red
background.

But "test.bat | wtee test.log" leaves the screen black with white text.

Every time I use wtee with –i wtee crashes. 

If I use it without –i, and try to stop the batch with <crtl> + <C>, nothing 
happens except “^C” is printed on the console. If I <crtl> + <C> a few 
times more, I get this:

^CThe process tried to write to a nonexistent pipe
^CThe process tried to write to a nonexistent pipe
The process tried to write to a nonexistent pipe.
The process tried to write to a nonexistent pipe.
The process tried to write to a nonexistent pipe.

If I press <y>, and then <Enter> I get:

y
^CTerminate batch job (Y/N)?

If I then press <y>, and then <Enter> the batch stops and shows me the prompt.

I am using Windows 7 64bit.

Is there a workaround for this in windows/command prompt? 

What is the expected output? What do you see instead?

I would like to see the errorlevel of the command instead of always getting a 0 
for wtee successfully writing output to my log file


What version of the product are you using? On what operating system?

Windows 2003 Server, Windows 7

Please provide any additional information below.

What steps will reproduce the problem?
1. Try using the wintee command with the %date% variable for filename creation
2.
3.

What is the expected output? What do you see instead?
echo %date:~4,10% | wtee C:\Users\%username%\Desktop\test-%date:~4,10%-log.txt"


What version of the product are you using? On what operating system?

Running Windows 8.1 x64, wtee 1.0.1


Please provide any additional information below.

Tried creating batch file with wintee to a show console output and output to 
file by date-filename creation. Couldn't get the Windows Command Line %date% to 
work properly with wintee.

It would be nice if there were an option to suppress the additional output
to stdout.

Great program, but I have some issues.

I am always experiencing problems with stdout which shows pogress.

For example a simple program will output on one line: “Progress: x%”. 
“x” will normally increase until it reaches 100. Then it will continue to 
print other messages.

Now what I get when using wtee is this: “Progress: 3%Progress: 30%Progress: 
54%Progress: 88%Progress: 100%”. This i get for a process that lasts for 
about two seconds. For processes that last a few hours, the output will be 
clogged up with such messages.

I tried this with ffmpeg, mkvmerge, etc.

I assume the problem is not hard to fix?

What steps will reproduce the problem?
1. cgrep 8361  *.*|wtee axe.txt
2.
3.

What is the expected output? What do you see instead?
  File #1 (checked file #14) ==> D3032.HTM <==
○○○○○○○○○○○○○○○○○○○○○○8361
  43 files checked - 1 matching file found.

Nothing in axe.txt

What version of the product are you using? On what operating system?
cgrep - Version 1.3 (30-Jun-97) by O. Schoenfeldt
 - F R E E W A R E - no WARRANTIES.

XP Sp2


wtee 1.0.1
There is NO WARRANTY, to the extent permitted by law.

Written by: Ryan Buhl


Please provide any additional information below.
Was using cgrep to find a particular number from any files. So need to capture 
the output irrespective of the result.

It might be related to the issue on color as the output has color which 
is not reproduced above.