?
Solved

windows 7 increase buffer size in cmd prompt

Posted on 2010-11-18
5
Medium Priority
?
2,225 Views
Last Modified: 2012-05-10
In Windows XP, 2000, or 2003 you could right click on a cmd prompt, go to properties, and set the buffer to a huge number. This allowed you to scroll up and see all the text output from a large command output. How the heck do you do the same thing in Windows 7? I've tried the old way on two different boxes with no luck (both are 64 bit, not that it should matter).
0
Comment
Question by:cajx
  • 3
  • 2
5 Comments
 
LVL 61

Accepted Solution

by:
Bill Prew earned 2000 total points
ID: 34164454
Same procedure works in Win7.  Launch a command window, left mouse click on the icon in the upper left of the window, select Properties, select Layout tab, adjust Screen Buffer Size.

~bp
0
 
LVL 61

Assisted Solution

by:Bill Prew
Bill Prew earned 2000 total points
ID: 34164459
After you changes if you want them permanent when it asks you if you want to save them for the future executions of that item say Yes.

~bp
0
 
LVL 61

Assisted Solution

by:Bill Prew
Bill Prew earned 2000 total points
ID: 34164469
You should also be able to get at these settings by right mouse clicking the icon you launch the Command Propmt window from, and selection Properties, and then Layout tab there.

~bp
0
 

Author Comment

by:cajx
ID: 34164470
Got it. It was a couple of things.

1. You have to increase the Screen Buffer height on the layout tab.
2. You have to open the cmd prompt the same way. Either by clicking on an icon every time, or by typing in "cmd" in "start run" every time, etc.

Each different way of launching CMD is it's own animal, for some reason. To quote another poster on another site:

http://superuser.com/questions/80094/why-doesnt-the-windows-command-prompt-window-maximize-to-the-full-screen-size

"The reason is that the command prompt is owned by a specific subsystem (csrss.exe) in the windows architecture which is different from the normal Windows subsystem (win32k.sys). Because of this, command prompt windows behave differently then normal windows. You'll note that amongst other annoying behavior, that setting properties for a prompt will only apply to prompts launched via whatever method that particular prompt was launched with.

Why this is, I have no earthly idea."
0
 

Author Closing Comment

by:cajx
ID: 34164518
One of the tricks was launching it the same way... was confusing.
0

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

This article explains how to install and use the NTBackup utility that comes with Windows Server.
I was prompted to write this article after the recent World-Wide Ransomware outbreak. For years now, System Administrators around the world have used the excuse of "Waiting a Bit" before applying Security Patch Updates. This type of reasoning to me …
This tutorial will show how to configure a single USB drive with a separate folder for each day of the week. This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten. The USB drive must be s…
If you’ve ever visited a web page and noticed a cool font that you really liked the look of, but couldn’t figure out which font it was so that you could use it for your own work, then this video is for you! In this Micro Tutorial, you'll learn yo…

589 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question