Shell output logging in Win9X???

I need to log everyting that happens in a command shell to show around how exactly an application is misbehaving when called in debug mode from the command line.

I have been told that all I need to do to redirect shell traffic to a file is to open a shell and issue the following command:

{application call} > {path}{filename}

where the ">" sign redirects output to the selected location and file. This would be identical to what you do in most Unix shells. Needless to say, it does not work, and the debugging text output scrolls in a shell window, from where I can't save it to file...

QUESTIONS:

- Is this SUPPOSED to work in Win9X? If so, what could be wrong?
(Note: I kept folder and file names fully DOS compliant, NO long names. Problem must be elsewhere.).

- If this is NOT supposed to work, is there any shell logger you would recomend?
(Note: I already trawled the web for hours and only found either KEYLOGGERS, which I do not need, or NETWORK LOGGERS, i.e. apps that file logs to a remote server. I want a logger that produces a local plaintext file of CLI output, not some other unrelated thing with a vaguely similar name, which Google discovers in great abundance!)

TIA, + I hope this is of use to others.

 

Thank you , TonyT !

I have DebugView running now, and I see it can captures the following, depending on the Windows version: OutputDebugString, Out_Debug_String, _Debug_Printf_Service etc.

This adds yet another "similar but not quite" category to those I had found by myself: debugging output loggers - oh, my, you never stop learning!

In DebugView I see no option for capturing simple shell traffic, i.e. the characters that you input via keyboard in a CLI (command line interface) a.k.a. a terminal window, a.k.a. a DOS shell or emulation thereof, together with the characters that appear IN THE VERY SAME PLACE as a result of some application's activity.

I need to capture the flurry of stuff shot onto a CLI window where I am running a CLI application, so I need to capture in-window text traffic. But, my ingorance being both deep and far-reaching, I dunno how!

________________________________________


Can anyone tell me if there is any application that actually produces a local plaintext file of CLI output, as opposed to some other thing with a vaguely similar-sounding name?


Or, is it true, as suggested to me elsewhere, that Windows, like in *nix, you should be able to make such text files with a command like:

{application call} > {path}{filename}

....which doesn't work on any of my comps .

________________________________________


These questions may be irrelevant, given the ethos, demographics, and teleology of the Windows world, but not terribly difficult...


TIA again for any well meaning answer, however tentative !


.

 

Thank you TonyT!

I had tried several times but wrongly assumed output would go to .\ rather than to \ , and also didn't specify .txt ending, but I see that's immaterial.

Invaluable!

I just hope I have not dumped large amounts of extremely sensitive info into files I've forgotten about... :-0