Solved

windows 7 increase buffer size in cmd prompt

Posted on 2010-11-18
5
2,060 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
5 Comments
 
LVL 54

Accepted Solution

by:
Bill Prew earned 500 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 54

Assisted Solution

by:Bill Prew
Bill Prew earned 500 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 54

Assisted Solution

by:Bill Prew
Bill Prew earned 500 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

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

The recent Microsoft changes on update philosophy for Windows pre-10 and their impact on existing WSUS implementations.
The Windows functions GetTickCount and timeGetTime retrieve the number of milliseconds since the system was started. However, the value is stored in a DWORD, which means that it wraps around to zero every 49.7 days. This article shows how to solve t…
This Micro Tutorial will go in depth within Systems and Security in Windows 7 and will go into detail regarding Action Center, Windows Firewall, System, etc. This will be demonstrated using Windows 7 operating system.
This Micro Tutorial will give you a basic overview of Windows Live Photo Gallery and show you various editing filters and touches to photos you can apply. This will be demonstrated using Windows Live Photo Gallery on Windows 7 operating system.

739 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