Where are parameters for the window a bat file opens

[micky[_2_]]

Using XP
Where are parameters for the window a bat file opens

Earlier, in one of these groups iirc, I showed how to make a cmd box or
a TCC/LE box fill the screen, and have a scroll bar on the right, by
creating an icon that calls either cmd or tccle, and by setting the
Properties/Layout Width to 240, or at least some value higher than 80.

And how one could change the background color and the font size in other
properties tabs.

That works great, except I have to start the box first and then type in
the name of my bat file.

I'd like to just click on the .bat file like I used to, but then it
doesn't matter what settings some uninvolved icon has.

So I figured it would be in Associations and I looked at Folder Options
/ File Types to see what settings I could change for .bat files.

Well, it turns out .bat doesn't have an entry in File Types. Neither
does .exe, com, sys, or scr. I guess that's why they call it FILE
types and not EXTENSIONS.

So where are the parameters for a window opened up when one clicks on a
bat file. Specifically I want to make changes to the layout width, the
background color, (maybe the text color), and the font size. I know
they're in there somewhere.

TIA

[Paul]

micky wrote:
> Using XP
> Where are parameters for the window a bat file opens
>
> Earlier, in one of these groups iirc, I showed how to make a cmd box or
> a TCC/LE box fill the screen, and have a scroll bar on the right, by
> creating an icon that calls either cmd or tccle, and by setting the
> Properties/Layout Width to 240, or at least some value higher than 80.
>
> And how one could change the background color and the font size in other
> properties tabs.
>
> That works great, except I have to start the box first and then type in
> the name of my bat file.
>
> I'd like to just click on the .bat file like I used to, but then it
> doesn't matter what settings some uninvolved icon has.
>
> So I figured it would be in Associations and I looked at Folder Options
> / File Types to see what settings I could change for .bat files.
>
> Well, it turns out .bat doesn't have an entry in File Types. Neither
> does .exe, com, sys, or scr. I guess that's why they call it FILE
> types and not EXTENSIONS.
>
> So where are the parameters for a window opened up when one clicks on a
> bat file. Specifically I want to make changes to the layout width, the
> background color, (maybe the text color), and the font size. I know
> they're in there somewhere.
>
> TIA

They say to use "Properties" of the window here.
There are some adjustments in the resulting dialog.
Kinda like the controls on XTerm.

http://www.7tutorials.com/how-customize-command-prompt

And HKCU\Console may contain some registry settings here.
This procedure is for deleting the settings, but you
can use it to have a look instead.

http://www.7tutorials.com/how-reset-looks-command-prompt-or-powershell-window

I looked in my WinXP registry, and there is only
one customized window type in there. And that is
used for the GhostScript console window. The
registry entries are

ColorTable00
....
ColorTable15
CursorSize
FaceName
FontFamily
FontSize
FontWeight
FullScreen
HistoryBufferSize
InsertMode
NumberOfHistoryBuffers
PopupColors
QuickEdit
ScreenBufferSize
ScreenColors
WindowSize

I suspect if you customize Command Prompt,
there would be a window position option as well.

Paul

[micky[_2_]]

In microsoft.public.windowsxp.general, on Fri, 04 Sep 2015 19:08:58
-0400, micky > wrote:

>Using XP
>Where are parameters for the window a bat file opens
>
>Earlier, in one of these groups iirc, I showed how to make a cmd box or
>a TCC/LE box fill the screen, and have a scroll bar on the right, by
>creating an icon that calls either cmd or tccle, and by setting the
>Properties/Layout Width to 240, or at least some value higher than 80.
>
>And how one could change the background color and the font size in other
>properties tabs.
>
>That works great, except I have to start the box first and then type in
>the name of my bat file.
>
>I'd like to just click on the .bat file like I used to, but then it
>doesn't matter what settings some uninvolved icon has.
>
>So I figured it would be in Associations and I looked at Folder Options
>/ File Types to see what settings I could change for .bat files.
>
>Well, it turns out .bat doesn't have an entry in File Types. Neither
>does .exe, com, sys, or scr. I guess that's why they call it FILE
>types and not EXTENSIONS.
>
>So where are the parameters for a window opened up when one clicks on a
>bat file. Specifically I want to make changes to the layout width, the
>background color, (maybe the text color), and the font size. I know
>they're in there somewhere.

I don't know where they are stored, but I found out where to set them.

I
Click on a .bat file to have it open a cmd window. Then right click
the upper left corner and left click Properties. I had sort of assumed
that the properties were as fleeting as the window, but they're not.

In Layout, I was able to change Width to 240, and I was able to make the
font larger (It was hard to read where I was sitting. It might have
been big enough now that I'm here.) but I wasn't able to make the
background blue. The options were not exactly the same as when there
was a shortcut,

I'm on a new computer now, and the resolution is lower, I think, so
instead of turning 80 to 240, I think I had to use 198 or 200. Trial
and error. Only has to be set once.


>TIA

You're welcome. Of course I'm the OP!

[J. P. Gilliver (John)]

In message >, micky
> writes:
>In microsoft.public.windowsxp.general, on Fri, 04 Sep 2015 19:08:58
>-0400, micky > wrote:
>
>>Using XP
>>Where are parameters for the window a bat file opens
>>
>>Earlier, in one of these groups iirc, I showed how to make a cmd box or
>>a TCC/LE box fill the screen, and have a scroll bar on the right, by
>>creating an icon that calls either cmd or tccle, and by setting the
>>Properties/Layout Width to 240, or at least some value higher than 80.
[]
>I don't know where they are stored, but I found out where to set them.
>
>I
>Click on a .bat file to have it open a cmd window. Then right click
>the upper left corner and left click Properties. I had sort of assumed
>that the properties were as fleeting as the window, but they're not.
>
>In Layout, I was able to change Width to 240, and I was able to make the
[]
Does this remember if you select true character mode, with Alt-Enter?
--
J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

As we journey through life, discarding baggage along the way, we should keep
an iron grip, to the very end, on the capacity for silliness. It preserves the
soul from desiccation. - Humphrey Lyttelton quoted by Barry Cryer in Radio
Times 10-16 November 2012

[micky[_2_]]

In microsoft.public.windowsxp.general, on Sat, 26 Sep 2015 10:18:14
+0100, "J. P. Gilliver (John)" > wrote:

>In message >, micky
> writes:
>>In microsoft.public.windowsxp.general, on Fri, 04 Sep 2015 19:08:58
>>-0400, micky > wrote:
>>
>>>Using XP
>>>Where are parameters for the window a bat file opens
>>>
>>>Earlier, in one of these groups iirc, I showed how to make a cmd box or
>>>a TCC/LE box fill the screen, and have a scroll bar on the right, by
>>>creating an icon that calls either cmd or tccle, and by setting the
>>>Properties/Layout Width to 240, or at least some value higher than 80.
>[]
>>I don't know where they are stored, but I found out where to set them.
>>
>>I
>>Click on a .bat file to have it open a cmd window. Then right click
>>the upper left corner and left click Properties. I had sort of assumed
>>that the properties were as fleeting as the window, but they're not.
>>
>>In Layout, I was able to change Width to 240, and I was able to make the
>[]
>Does this remember if you select true character mode, with Alt-Enter?

Isn't alt-enter the same thing as right clicking on the upper left
corner? I think so, so yes, it remembers. Hmmm. I haven't checked
if it remembers after you close Windows and restart, and my computer
failed last Sunday, and I'm on another one with no bat files yet. So I
can't check. But changing the width doesn't take much time and it
woudl be worth it to me to have the wider page even if I have to do it
each windows session. Plus the scroll bar I like, and I used, even
though one can only scroll back a couple hundred lines.

Although the scroll bar actually covers up 2 or 3 characters if a line
is that long. and there might not be a left-right scroll bar. .

[J. P. Gilliver (John)]

In message >, micky
> writes:
>In microsoft.public.windowsxp.general, on Sat, 26 Sep 2015 10:18:14
>+0100, "J. P. Gilliver (John)" > wrote:
>
>>In message >, micky
> writes:
>>>In microsoft.public.windowsxp.general, on Fri, 04 Sep 2015 19:08:58
>>>-0400, micky > wrote:
>>>
>>>>Using XP
>>>>Where are parameters for the window a bat file opens
[]
>>>I don't know where they are stored, but I found out where to set them.
>>>
>>>I
>>>Click on a .bat file to have it open a cmd window. Then right click
>>>the upper left corner and left click Properties. I had sort of assumed
>>>that the properties were as fleeting as the window, but they're not.
[]
>>Does this remember if you select true character mode, with Alt-Enter?
>
>Isn't alt-enter the same thing as right clicking on the upper left

Not on my system (XP SP3): I open a command window (Start | Programs |
Accessories | Command Prompt, or Start | Run | "cmd"). If I right-click
on the upper left corner, it does the same as if I left-click: brings up
a menu with restore (I'm not going to keep typing capital letters),
move, size, minimise, maximise, close, edit, defaults, and properties.
If I Alt-Enter, in contrast, it gives me true full-screen - not the same
as maximise. (For those who haven't seen this before and find it
alarming: Alt-Enter again restores matters.)

>corner? I think so, so yes, it remembers. Hmmm. I haven't checked
[]
> Although the scroll bar actually covers up 2 or 3 characters if a line
>is that long. and there might not be a left-right scroll bar. .

Alt-Enter removes all trace of scroll bars ... (-:
--
J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

"It ain't those parts of the Bible that I can't understand that bother me, it's
the part that I do understand." - Mark Twain

[micky[_2_]]

In microsoft.public.windowsxp.general, on Sat, 26 Sep 2015 12:05:15
+0100, "J. P. Gilliver (John)" > wrote:

>In message >, micky
> writes:
>>In microsoft.public.windowsxp.general, on Sat, 26 Sep 2015 10:18:14
>>+0100, "J. P. Gilliver (John)" > wrote:
>>
>>>In message >, micky
> writes:
>>>>In microsoft.public.windowsxp.general, on Fri, 04 Sep 2015 19:08:58
>>>>-0400, micky > wrote:
>>>>
>>>>>Using XP
>>>>>Where are parameters for the window a bat file opens
>[]
>>>>I don't know where they are stored, but I found out where to set them.
>>>>
>>>>I
>>>>Click on a .bat file to have it open a cmd window. Then right click
>>>>the upper left corner and left click Properties. I had sort of assumed
>>>>that the properties were as fleeting as the window, but they're not.
>[]
>>>Does this remember if you select true character mode, with Alt-Enter?

Sorry. I misread your question and answered as if you had asked about
Alt-Space. I also don't know the term true character mode.
>>
>>Isn't alt-enter the same thing as right clicking on the upper left
>
>Not on my system (XP SP3): I open a command window (Start | Programs |
>Accessories | Command Prompt, or Start | Run | "cmd"). If I right-click
>on the upper left corner, it does the same as if I left-click: brings up
>a menu with restore (I'm not going to keep typing capital letters),
>move, size, minimise, maximise, close, edit, defaults, and properties.
>If I Alt-Enter, in contrast, it gives me true full-screen - not the same

Right. It's not a box, but the full screen. In my XP system, however,
the characters were a bit fuzzy and maybe wider, giving less on the
screen, plus there is no vertical (or horiz) scroll bar, which I found
useful in reviewing XXCopy's list of files that did not get copied.

Last Sunday my XP system failed. I spent a lot of Monday trying to
repair it (another thread I hope to start) and Monday night I moved to
my only spare computer that had a HDD and an OS. A friend who upgraded
his office gave me a Dell Vista computer,

and now in Vista when I try to do Alt-Enter, I get "This system does
not support fullscreen mode". This is with Start | run | cmd or a
shortcut that calls tcc/le. (I have no bat files except autoexec.bat
which doesn't pause in the middle, and whose box disappears right away)

>as maximise. (For those who haven't seen this before and find it
>alarming: Alt-Enter again restores matters.)

>>corner? I think so, so yes, it remembers. Hmmm. I haven't checked
>[]
>> Although the scroll bar actually covers up 2 or 3 characters if a line
>>is that long. and there might not be a left-right scroll bar. .
>
>Alt-Enter removes all trace of scroll bars ... (-:

If only we could have a format with the best of all 3 possible formats!
(JK, I'm pretty much satisfied, at least if it remembers the width in
the next windows session.)

[J. P. Gilliver (John)]

In message >, micky
> writes:
>In microsoft.public.windowsxp.general, on Sat, 26 Sep 2015 12:05:15
>+0100, "J. P. Gilliver (John)" > wrote:
[]
>>>>Does this remember if you select true character mode, with Alt-Enter?
>
>Sorry. I misread your question and answered as if you had asked about
>Alt-Space. I also don't know the term true character mode.

Not surprising, as I made it up; I'm not sure what the "official" name
for that mode is, if there is one. I called it that because, on some
systems at least, I think it actually changes the mode of the graphics
hardware, to an 80 by 25 character mode that's there from days long ago.
[]
>Right. It's not a box, but the full screen. In my XP system, however,
>the characters were a bit fuzzy and maybe wider, giving less on the

Unless it's a laptop, that's probably your monitor: some modern
(especially non-CRT) monitors won't even display this old mode - the
ones that do aren't optimised for it. (Pressing the auto-adjust button -
or manually tweaking the monitor - might make it less fuzzy. But then
you'd have to redo that when you got back into graphics mode, so don't
bother.)
[]
>Last Sunday my XP system failed. I spent a lot of Monday trying to
>repair it (another thread I hope to start) and Monday night I moved to
>my only spare computer that had a HDD and an OS. A friend who upgraded
>his office gave me a Dell Vista computer,
>
>and now in Vista when I try to do Alt-Enter, I get "This system does
>not support fullscreen mode". This is with Start | run | cmd or a
>shortcut that calls tcc/le. (I have no bat files except autoexec.bat
>which doesn't pause in the middle, and whose box disappears right away)

I _think_ that's how .bat files have run in the Windows environment
since '95 - when they've finished, their command window closes. But if
you run them from an already-opened command prompt, e. g. by typing

\autoexec

at the command prompt, they _won't_ disappear when they finish (or
rather the command window won't).
[]
>If only we could have a format with the best of all 3 possible formats!
>(JK, I'm pretty much satisfied, at least if it remembers the width in
>the next windows session.)
--
J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

After a typical day at the BBC you want something to take your mind off work,
although in the end, decent people being eaten alive by heartless monsters
running amok proved no distraction. - Eddie Mair, RT 2015/7/4-10

[micky[_2_]]

In microsoft.public.windowsxp.general, on Sun, 27 Sep 2015 00:36:07
+0100, "J. P. Gilliver (John)" > wrote:

>In message >, micky
> writes:
>>In microsoft.public.windowsxp.general, on Sat, 26 Sep 2015 12:05:15
>>+0100, "J. P. Gilliver (John)" > wrote:
>[]
>>>>>Does this remember if you select true character mode, with Alt-Enter?
>>
>>Sorry. I misread your question and answered as if you had asked about
>>Alt-Space. I also don't know the term true character mode.
>
>Not surprising, as I made it up;

Well then, I'm glad I commented. I almost didn't, thinking Why should
one comment on something he doesn't know?

> I'm not sure what the "official" name
>for that mode is, if there is one. I called it that because, on some
>systems at least, I think it actually changes the mode of the graphics
>hardware, to an 80 by 25 character mode that's there from days long ago.
>[]
>>Right. It's not a box, but the full screen. In my XP system, however,
>>the characters were a bit fuzzy and maybe wider, giving less on the
>
>Unless it's a laptop, that's probably your monitor: some modern

It's a Viewsonic thin screen monitor, and until I get back to XP I can't
try it with anythihng else, including the Dell Trinitron CRT I'm using
now.,

>(especially non-CRT) monitors won't even display this old mode - the

Yeah, non-CRT.

>ones that do aren't optimised for it. (Pressing the auto-adjust button -
>or manually tweaking the monitor - might make it less fuzzy. But then
>you'd have to redo that when you got back into graphics mode, so don't
>bother.)
>[]
>>Last Sunday my XP system failed. I spent a lot of Monday trying to
>>repair it (another thread I hope to start) and Monday night I moved to
>>my only spare computer that had a HDD and an OS. A friend who upgraded
>>his office gave me a Dell Vista computer,
>>
>>and now in Vista when I try to do Alt-Enter, I get "This system does
>>not support fullscreen mode". This is with Start | run | cmd or a
>>shortcut that calls tcc/le. (I have no bat files except autoexec.bat
>>which doesn't pause in the middle, and whose box disappears right away)
>
>I _think_ that's how .bat files have run in the Windows environment
>since '95 - when they've finished, their command window closes. But if

Yeah, that's fine. I just meant that because of that, I can't adjust
the size of the screen or try alt-enter.

>you run them from an already-opened command prompt, e. g. by typing
>
>\autoexec
>
>at the command prompt, they _won't_ disappear when they finish (or
>rather the command window won't).

Right, but to go back a ways, I'll have to wait until I have a bat file
with a pause of some sort in it, to adjust the width a window opened by
clicking on a bat file, and then to see if the new value lasts from one
windows session to another. A lot of other things to do first**, (like
copying over my Firefox history and password files. And the cookies
from a web order I was assembling.)

**Well, I get impatient. I put a "pause" in autoexec.bat (which had
only one line it it before) and set the screen width to 126 and now the
cmd window is the same width as the screen. I'll check after rebooting
if it has stayed that way.

>>If only we could have a format with the best of all 3 possible formats!
>>(JK, I'm pretty much satisfied, at least if it remembers the width in
>>the next windows session.)

[Todd Vargo]

On 9/4/2015 7:08 PM, micky wrote:
> Using XP
> Where are parameters for the window a bat file opens
>
> Earlier, in one of these groups iirc, I showed how to make a cmd box or
> a TCC/LE box fill the screen, and have a scroll bar on the right, by
> creating an icon that calls either cmd or tccle, and by setting the
> Properties/Layout Width to 240, or at least some value higher than 80.
>
> And how one could change the background color and the font size in other
> properties tabs.
>
> That works great, except I have to start the box first and then type in
> the name of my bat file.
>
> I'd like to just click on the .bat file like I used to, but then it
> doesn't matter what settings some uninvolved icon has.
>
> So I figured it would be in Associations and I looked at Folder Options
> / File Types to see what settings I could change for .bat files.
>
> Well, it turns out .bat doesn't have an entry in File Types. Neither
> does .exe, com, sys, or scr. I guess that's why they call it FILE
> types and not EXTENSIONS.
>
> So where are the parameters for a window opened up when one clicks on a
> bat file. Specifically I want to make changes to the layout width, the
> background color, (maybe the text color), and the font size. I know
> they're in there somewhere.
>
> TIA
>

On my XP system, the settings for a cmd window opened by dbl-clicking a
batch file are located in the registry at this key.

HKEY_CURRENT_USER\Console\%SystemRoot%_system32_cm d.exe

This is the default location where settings are read when a cmd window
is opened without using a shortcut (ie. dbl-clicking a .bat file or DOS
program). This is completely different from Win95 systems which used a
special default .pif shortcut which was located in the windows\system
folder.

..bat does indeed have a file type. Its called "MS-DOS Batch File" which
can be found in the registry. To add/modify different actions (i.e.
change editor) you have to do it manually in the registry. Microsoft
does not want people to be messing with application types so easily from
the File Types applet because you might break something.

In another post, Atl+Enter was mentioned, specifically, that full screen
mode was not working on a Win Vista system. This is because that system
is 64-Bit. On a 32-Bit system it does indeed work. I have full screen
cmd prompt working just fine on a Win7 32-Bit system.

HTH
--
Todd Vargo
(Post questions to group only. Remove "z" to email personal messages)

[foxidrive[_3_]]

On 28/09/2015 07:54, Todd Vargo wrote:
> In another post, Atl+Enter was mentioned, specifically, that full screen
> mode was not working on a Win Vista system. This is because that system
> is 64-Bit. On a 32-Bit system it does indeed work. I have full screen
> cmd prompt working just fine on a Win7 32-Bit system.

Todd, that's real strange because it's never worked for me on a 32 bit
Windows system after XP, up to Win 8.1 32 bit.

We're talking full screen with no title bar, edges or scroll bars, yeah?

[foxidrive[_3_]]

On 28/09/2015 12:58, foxidrive wrote:
> On 28/09/2015 07:54, Todd Vargo wrote:
>> In another post, Atl+Enter was mentioned, specifically, that full screen
>> mode was not working on a Win Vista system. This is because that system
>> is 64-Bit. On a 32-Bit system it does indeed work. I have full screen
>> cmd prompt working just fine on a Win7 32-Bit system.
>
> Todd, that's real strange because it's never worked for me on a 32 bit
> Windows system after XP, up to Win 8.1 32 bit.
>
> We're talking full screen with no title bar, edges or scroll bars, yeah?

Just after posting I tested NT, Vista and Win7 all 32 bit VM's in
virtualbox and yes indeed, they all went to full screen using alt-enter.


My Win 8.1 32bit which hosts the vitualbox doesn't change display, instead
popping up a box saying "This system does not support fullscreen mode.".

I'm pretty sure that has been my experience with Win 7 32 bit that I had on
a physical machine also.

Are yours on a virtual machine Todd, or can other's verify the behaviour on
physical machines?

A quick search says it is due to changes in graphic drives in vista and
later - and I read a sentence that suggests if you use "XP Mode" then you
can go full screen.

See here: https://support.microsoft.com/en-us/kb/926657

[Todd Vargo]

On 9/27/2015 11:18 PM, foxidrive wrote:
> On 28/09/2015 12:58, foxidrive wrote:
>> On 28/09/2015 07:54, Todd Vargo wrote:
>>> In another post, Atl+Enter was mentioned, specifically, that full screen
>>> mode was not working on a Win Vista system. This is because that system
>>> is 64-Bit. On a 32-Bit system it does indeed work. I have full screen
>>> cmd prompt working just fine on a Win7 32-Bit system.
>>
>> Todd, that's real strange because it's never worked for me on a 32 bit
>> Windows system after XP, up to Win 8.1 32 bit.
>>
>> We're talking full screen with no title bar, edges or scroll bars, yeah?
>
> Just after posting I tested NT, Vista and Win7 all 32 bit VM's in
> virtualbox and yes indeed, they all went to full screen using alt-enter.
>
>
> My Win 8.1 32bit which hosts the vitualbox doesn't change display,
> instead popping up a box saying "This system does not support fullscreen
> mode.".
>
> I'm pretty sure that has been my experience with Win 7 32 bit that I had
> on a physical machine also.
>
> Are yours on a virtual machine Todd, or can other's verify the behaviour
> on physical machines?
>
> A quick search says it is due to changes in graphic drives in vista and
> later - and I read a sentence that suggests if you use "XP Mode" then
> you can go full screen.
>
> See here: https://support.microsoft.com/en-us/kb/926657
>
>

Not virtual. Not set up for XP mode either. Its Win 7 Pro 32-Bit running
on a 32-Bit machine. It is a fresh install so no tweaks or other
enhancements performed to make it work.

--
Todd Vargo
(Post questions to group only. Remove "z" to email personal messages)

[foxidrive[_3_]]

On 29/09/2015 13:12, Todd Vargo wrote:
>> >A quick search says it is due to changes in graphic drives in vista and
>> >later - and I read a sentence that suggests if you use "XP Mode" then
>> >you can go full screen.
>> >
>> >See here:https://support.microsoft.com/en-us/kb/926657
>> >
>> >
> Not virtual. Not set up for XP mode either. Its Win 7 Pro 32-Bit running
> on a 32-Bit machine. It is a fresh install so no tweaks or other
> enhancements performed to make it work.

I'm assuming that you mean that there are no scrollbars or border or
titlebar visible, Todd.

The microsoft link says it's not possible on Windows 7 - but there could be
a video driver which you are using which supports it.

Can you please advise which video card you are using and driver release
version?

[Todd Vargo]

On 9/29/2015 4:39 AM, foxidrive wrote:
> On 29/09/2015 13:12, Todd Vargo wrote:
>>> >A quick search says it is due to changes in graphic drives in vista and
>>> >later - and I read a sentence that suggests if you use "XP Mode" then
>>> >you can go full screen.
>>> >
>>> >See here:https://support.microsoft.com/en-us/kb/926657
>>> >
>>> >
>> Not virtual. Not set up for XP mode either. Its Win 7 Pro 32-Bit running
>> on a 32-Bit machine. It is a fresh install so no tweaks or other
>> enhancements performed to make it work.
>
> I'm assuming that you mean that there are no scrollbars or border or
> titlebar visible, Todd.

Nothing to assume. I said, "full screen".

>
> The microsoft link says it's not possible on Windows 7 - but there could
> be a video driver which you are using which supports it.

That info is misleading. Its intended for Vista and Win 7 64-Bit users.
I don't have a Vista 32-Bit to test/confirm for you but I'd bet full
screen would work on a 32-Bit non-virtual installation.

>
> Can you please advise which video card you are using and driver release
> version?

Its the Dell Dimension 3000 on board video, and the driver is
Microsoft's Standard VGA Adaptor installed by Windows 7 setup. Nothing
fancy. No Dell drivers installed.

Please confirm that you tested in a non-virtual, 32-Bit installation.

--
Todd Vargo
(Post questions to group only. Remove "z" to email personal messages)

[foxidrive[_3_]]

On 30/09/2015 13:07, Todd Vargo wrote:
>> I'm assuming that you mean that there are no scrollbars or border or
>> titlebar visible, Todd.
>
> Nothing to assume. I said, "full screen".
>
>>
>> The microsoft link says it's not possible on Windows 7 - but there could
>> be a video driver which you are using which supports it.
>
> That info is misleading. Its intended for Vista and Win 7 64-Bit users.

The document states 32 bit.

Microsoft cocks up stuff in their tech data too, but I confirm that it was
on a 32 bit Win 7 and 32 bit Win 8.1 system and neither will enter full
screen mode.

>> Can you please advise which video card you are using and driver release
>> version?
>
> Its the Dell Dimension 3000 on board video, and the driver is
> Microsoft's Standard VGA Adaptor installed by Windows 7 setup. Nothing
> fancy. No Dell drivers installed.

You probably don't want to play in this way - but if you loaded Dell
drivers, would it still go full screen? A full image backup is the only
safe way to test, and get back to where you are.

> Please confirm that you tested in a non-virtual, 32-Bit installation.

Yes. Ditto in Vista 32 bit physical machine, unless I'm becoming senile.

[foxidrive[_3_]]

On 30/09/2015 13:17, foxidrive wrote:
> I confirm that it was
> on a 32 bit Win 7 and 32 bit Win 8.1 system and neither will enter full
> screen mode.
>
>> >Please confirm that you tested in a non-virtual, 32-Bit installation.

> Yes. Ditto in Vista 32 bit physical machine, unless I'm becoming senile.

I had some time to play... fresh Vista install and fresh Win 7 install,
and Windows 8.1 install.

http://astronomy.comoj.com/windows-fullscreen/index.html

[B00ze[_2_]]

On 2015-09-30 01:21, foxidrive > wrote:

> On 30/09/2015 13:17, foxidrive wrote:
>> I confirm that it was
>> on a 32 bit Win 7 and 32 bit Win 8.1 system and neither will enter full
>> screen mode.
>>
>>> >Please confirm that you tested in a non-virtual, 32-Bit installation.
>
>> Yes. Ditto in Vista 32 bit physical machine, unless I'm becoming senile.
>
> I had some time to play... fresh Vista install and fresh Win 7 install,
> and Windows 8.1 install.
>
> http://astronomy.comoj.com/windows-fullscreen/index.html

At least you get an error message! No amount of Alt-Entering will do
anything at all on my Win7 laptop (64bits). Still, I learned today that
even if, as I had planned, I multi-boot a Win7-32 for DOS purposes, I
won't be able to go full-screen, boooo :-(

--
! _\|/_ Sylvain /
! (o o) Member-+-David-Suzuki-Fdn/EFF/Red+Cross/Planetary-Society-+-
oO-( )-Oo CAPITALISM: Man exploiting man. SOCIALISM: The reverse.

[foxidrive[_3_]]

On 1/10/2015 11:59, B00ze wrote:
>> http://astronomy.comoj.com/windows-fullscreen/index.html
>
> At least you get an error message! No amount of Alt-Entering will do
> anything at all on my Win7 laptop (64bits).

My Win 7 64 bit does exactly the same - nothing.

> Still, I learned today that
> even if, as I had planned, I multi-boot a Win7-32 for DOS purposes, I
> won't be able to go full-screen, boooo :-(

It's clear from Todd's experience, and implied in the Microsoft support
link, that if you load a certain kind of video driver then it will enter
full screen - in the 32 bit version at least.

[foxidrive[_3_]]

On 30/09/2015 13:17, foxidrive wrote:

>> >Nothing to assume. I said, "full screen".
>>> >>
>>> >>The microsoft link says it's not possible on Windows 7 - but there could
>>> >>be a video driver which you are using which supports it.
>> >
>> >That info is misleading. Its intended for Vista and Win 7 64-Bit users.

> The document states 32 bit.


Todd, I guess you're either too busy to reply to the thread or maybe you
think I was being argumentative for the hell of it to your last comment.

Read the paste here. The only place it mentions 64 bit is to say that the
article doesn't apply to 64 bit because they can't run 16 bit programs.

SYMPTOMS
You may find that some 16-bit DOS-based programs do not run in full-screen
mode in Windows Vista and in Windows 7. You cannot set a Command Prompt
(CMD) window to display in full-screen mode.

Note This symptom only applies to 32-bit versions of Windows Vista and of
Windows 7. 16-bit programs are not supported on 64-bit versions of Windows
Vista or of Windows 7.

[Todd Vargo]

On 10/1/2015 2:02 PM, foxidrive wrote:
> On 30/09/2015 13:17, foxidrive wrote:
>
>>> >Nothing to assume. I said, "full screen".
>>>> >>
>>>> >>The microsoft link says it's not possible on Windows 7 - but there
>>>> could
>>>> >>be a video driver which you are using which supports it.
>>> >
>>> >That info is misleading. Its intended for Vista and Win 7 64-Bit users.
>
>> The document states 32 bit.
>
>
> Todd, I guess you're either too busy to reply to the thread or maybe you
> think I was being argumentative for the hell of it to your last comment.
>
> Read the paste here. The only place it mentions 64 bit is to say that
> the article doesn't apply to 64 bit because they can't run 16 bit programs.
>
> SYMPTOMS
> You may find that some 16-bit DOS-based programs do not run in
> full-screen mode in Windows Vista and in Windows 7. You cannot set a
> Command Prompt (CMD) window to display in full-screen mode.
>
> Note This symptom only applies to 32-bit versions of Windows Vista and
> of Windows 7. 16-bit programs are not supported on 64-bit versions of
> Windows Vista or of Windows 7.

Sorry, time limitations called me away in the middle of composing a
response. Yes, I have read the page, and understands what it says.
However, full screen works on my installation, hence, my "misleading"
comment. Microsoft's KB's are not always 100% accurate you know.

Not only does full screen work for me on Win 7, I can create shortcuts
to open cmd in full screen mode as well. This is contrary to the KB page
info. It would be nice if Microsoft provided a list of known programs
that do not run in full screen mode so those claims can be confirmed.

--
Todd Vargo
(Post questions to group only. Remove "z" to email personal messages)

[foxidrive[_3_]]

On 3/10/2015 13:02, Todd Vargo wrote:
> Sorry, time limitations called me away in the middle of composing a
> response.

No worries.

> Yes, I have read the page, and understands what it says.
> However, full screen works on my installation, hence, my "misleading"
> comment. Microsoft's KB's are not always 100% accurate you know.

It's not misleading because you will also know that the page indicates that
it is a video driver change that causes it to happen, and that it can be
worked around.

[Todd Vargo]

On 10/3/2015 4:23 AM, foxidrive wrote:
> On 3/10/2015 13:02, Todd Vargo wrote:
>> Sorry, time limitations called me away in the middle of composing a
>> response.
>
> No worries.
>
>> Yes, I have read the page, and understands what it says.
>> However, full screen works on my installation, hence, my "misleading"
>> comment. Microsoft's KB's are not always 100% accurate you know.
>
> It's not misleading because you will also know that the page indicates
> that it is a video driver change that causes it to happen, and that it
> can be worked around.

I did not change to an XP video driver. Its the one that Win 7
installed. It also says "You cannot set a Command Prompt (CMD) window to
display in full-screen mode.", but I can without making any OS
modifications or driver substitutions. Because the page contains a
mixture of information that contradict with my installation and user
experience, we will just have to agree to disagree with our opinions of
the accuracy of the page content.

[foxidrive[_3_]]

On 4/10/2015 05:45, Todd Vargo wrote:

> I did not change to an XP video driver. Its the one that Win 7
> installed. It also says "You cannot set a Command Prompt (CMD) window to
> display in full-screen mode.", but I can without making any OS
> modifications or driver substitutions.

Yes Todd, and I don't want to argue without any point.

I'm not sure how closely you deal with hardware - but it's clear that the
video subsystem in your computer is of a type that made Windows load the
type of drivers which allowed you to switch to full screen. The Dell
machine you have is a 'speshul' hardware combination.

Nobody else cares enough to comment on how their Win 7 32 bit behaves so
that'll just remain the way I interpret the results, as a hardware engineer.