Screen Capture from cmd prompt

  • Thread starter Thread starter Kirk Shimek
  • Start date Start date
K

Kirk Shimek

Hello,

In unix there are the script and tee commands to capture
scrolling screen output . . . what are equivelant
utilities / tools / commands in windows command prompts?

Kirk Shimek UNIX Admin - Windows Integration.
 
You can pipe results to a file using >, if that's what you mean.

Like, try:

net view>file.txt

for example.

Ray at work
 
DOOHHH!!! (said Homer style from the simpsons)

Yes that is what I mean (sheepishly) Thank you.

Kirk Shimek
 
Kirk Shimek wrote in
Hello,

In unix there are the script and tee commands to capture
scrolling screen output . . . what are equivelant
utilities / tools / commands in windows command prompts?

Kirk Shimek UNIX Admin - Windows Integration.

Hmm. There is MORE command | more
There is no LESS
There is redirection Command >file
(that's STDOUT) and for STDERR command 2>file
A CMD.EXE (don't use command.com) prompt window can be customized for
the buffer and window size. Try the Control Menu "box" at the left
of the title bar. For example the initial window may be say 50 line,
but with a buffer of say 300 lines. This will give you a scrollable
"viewport" into the 300 lines of output. Also text can be
Copy/Pasted from/to the window. Insert mode can be enabled/disabled.
Many more.

A TEE.EXE for Win32 is available (3rd-party).
No BASH. :-(
other commands to try perhaps: COLOR /? TITLE /?
SET (env. vars) is really different.

What else?
 
Kirk Shimek said:
In unix there are the script and tee commands to capture
scrolling screen output . . . what are equivelant
utilities / tools / commands in windows command prompts?

If you're looking for a complete set of tools for Windows similar to
what you had on Unix, you'll need to acquire them separately. But
with a little searching via Google, you'll quickly discover the usual
suspects, Cygwin, MKS and my own product, Hamilton C shell (see
http://www.hamiltonlabs.com/cshell.htm)

The big advantage I hope you'll find in my C shell is that it's all
been written completely from scratch for Windows; I think you'll find
its performance, "fit and finish" and overall quality of integration
with Windows easily best the alternatives.

I am the author, so if you have questions, let me know and I'll do my
best to answer.

Regards,
Nicole Hamilton
Hamilton Laboratories
 
Nicole Hamilton said:
its performance, "fit and finish" and overall quality of integration
with Windows easily best the alternatives.

LOL. $395 for a glorified cmd.exe! Yer right :)
 
You will also want to take a look at TheGuardBook,
Online Reference for Cross-Platform Shell Scripting at
(http://TheSystemGuard.com/TheGuardBook/CCS-Int).

All the commands internal to cmd.exe are documented
here in "Mounted Help" pages. This includes a
color-keyed page highlighting the differences
among all internal commands in Windows NT 4, 2000,
XP and Server 2003. The "Common Help" from each OS's
help screen is also available for comparison.

See also:

(http://ntlib.com)
(http://MountCommands.com)

All of this will help you to write scripts that will work
RELIABLY and CONSISTENTLY on all four platforms.

*******
-tsg
____________________________________________________________
TheSystemGuard.com | BoomingOrFuming.com | MountCommands.com
Free and "Almost Free" Knowledge for Windows System Admins!
 
Ritchie said:
LOL. $395 for a glorified cmd.exe! Yer right :)

Then it's not for you. You'll choose something else. That's how the
market works, providing choices at both high and low price points.
What quality and service level do you require? Different people have
different needs.

That said, I think your hyperbole is reaching. Objectively, there
just plain is a quantum level difference in complexity between a
complete unix shell and utilities package and, as you say, a
"glorified cmd.exe." I don't know your background, but I've written
this stuff, so I kind of know something about it. :)

Regards,
Nicole

http://www.hamiltonlabs.com/biography.htm
 
Back
Top