Re (2): Netbooks screen aspect-ratio: suspect problem?

[no.top.post]

References: <[email protected]>

Paul wrote:-
What I did, is ran cmd.exe (a command prompt) as a program.

Yes. BTW there are 3 `cmd.exe` files.

Right click the command prompt title bar. Yes

Select "Properties" from the menu. Yes

An option is offered there, to go full screen.

Yes, the FIRST TIME I did this, and it removed the
"does not support full screen mode" problem.
Unfortunately there was a reference to G: which:
previously a USBstik was unplugged; and the system
hung; not necessarily because of the "G:" error.

It makes your monitor "look like a DOS window".

Power Shell also starts a fullScreen DOSwindow, but it
goes smaller and gives the error with my app.
But your method didn't go smaller nor show the error.

==== some log-notes:--
Wow DOSbased == 'Native Oberon booting' hangs without <full screen error>
Ctl/Alt/Del does not reboot.
Removing the battery-pack allows <escape> and reinserting, prompts for
<re-login-click> and PREVIOUS apps are ALL STILL THERE ?!!
Of the 11 'CmdPrompt' screens THIS ONE is still there!?
=> there are 3: cmd.exe all of the same size
C:\Windows\system32\cmd.exe
C:\Windows\winsxs\x8ebe11.163
C:\HP\BIN
=> there are 2: command.com all of the same size
C:\Windows\system32\command.com 50'648 09-07-13
C:\Windows\winsxs\x8ebe11.163\command.com 50'648 09-07-13
=> anti virus program prevented `restore` from completing. need to disable antivirus.
=> uninstall : 46 now installed : leave setting to reinstall Nortons later
restored to: 2011/01/25 !! YES
!! All MY OWN added since 2011/01/25 *.exe. & *.bat are deleted/LOST !!
====

What REALLY confused me, was that after I recovered
from the 'hang', the system was usable, except the
'Command Prompt' icon didn't open a 'terminal'.

Now -> CmdPrompt -> MR @ Frame-top -> Properties
does NOT show any "FullScreen",
like I saw the first time, before the crash.
Luckily I make written notes, else I'd imagine that I didn't
see it [and select it] the first time.
So, when I get to an inet-connection, I'm going to
goog: "Command+Prompt"+Win7+Properties

BTW goog didn't give 'your' procedure for:
Win7+Fullscreen; so it seems NOT to be well known.

Since NOW: -> Properties doesn't show any "FullScreen",
I'm thinking that that option becomes available only
after I've set some other non-default; which are now cleared
from the restore-procedure
And I'm guessing that YOU TOO set it, because you've been
experimenting with the Fullscreen facility.
That's why/how you know about this rare adjustment?

Thanks,

== Chris Glur.

 

[Paul]

References: <[email protected]>

Paul wrote:-
What I did, is ran cmd.exe (a command prompt) as a program.

Yes. BTW there are 3 `cmd.exe` files.

Right click the command prompt title bar. Yes

Select "Properties" from the menu. Yes

An option is offered there, to go full screen.

Yes, the FIRST TIME I did this, and it removed the
"does not support full screen mode" problem.
Unfortunately there was a reference to G: which:
previously a USBstik was unplugged; and the system
hung; not necessarily because of the "G:" error.

It makes your monitor "look like a DOS window".

Power Shell also starts a fullScreen DOSwindow, but it
goes smaller and gives the error with my app.
But your method didn't go smaller nor show the error.

==== some log-notes:--
Wow DOSbased == 'Native Oberon booting' hangs without <full screen error>
Ctl/Alt/Del does not reboot.
Removing the battery-pack allows <escape> and reinserting, prompts for
<re-login-click> and PREVIOUS apps are ALL STILL THERE ?!!
Of the 11 'CmdPrompt' screens THIS ONE is still there!?
=> there are 3: cmd.exe all of the same size
C:\Windows\system32\cmd.exe
C:\Windows\winsxs\x8ebe11.163
C:\HP\BIN
=> there are 2: command.com all of the same size
C:\Windows\system32\command.com 50'648 09-07-13
C:\Windows\winsxs\x8ebe11.163\command.com 50'648 09-07-13
=> anti virus program prevented `restore` from completing. need to disable antivirus.
=> uninstall : 46 now installed : leave setting to reinstall Nortons later
restored to: 2011/01/25 !! YES
!! All MY OWN added since 2011/01/25 *.exe. & *.bat are deleted/LOST !!
====

What REALLY confused me, was that after I recovered
from the 'hang', the system was usable, except the
'Command Prompt' icon didn't open a 'terminal'.

Now -> CmdPrompt -> MR @ Frame-top -> Properties
does NOT show any "FullScreen",
like I saw the first time, before the crash.
Luckily I make written notes, else I'd imagine that I didn't
see it [and select it] the first time.
So, when I get to an inet-connection, I'm going to
goog: "Command+Prompt"+Win7+Properties

BTW goog didn't give 'your' procedure for:
Win7+Fullscreen; so it seems NOT to be well known.

Since NOW: -> Properties doesn't show any "FullScreen",
I'm thinking that that option becomes available only
after I've set some other non-default; which are now cleared
from the restore-procedure
And I'm guessing that YOU TOO set it, because you've been
experimenting with the Fullscreen facility.
That's why/how you know about this rare adjustment?

Thanks,

== Chris Glur.

Well, I can't add too much more to the previous results.

I probably tested in my WinXP desktop.

So I decided to also test in a virtual machine that has Win2K loaded.
The normal desktop resolution of that environment is 1152*864.

In Win2K, the same "Properties" exists, with the option to go "Full Screen".

The interesting result was, that when "cmd" fills the screen, it
requests the desktop dimensions to change. And by comparing the
size of that virtual machine session, "cmd" must be requesting 640x480,
because the session frame became smaller. Based on the appearance of
the letters on the screen, it looks pretty well exactly the same
as it did in native WinXP. So I guess what I was seeing before, was
the "cmd" full screen switched my monitor to 640x480. And the desktop
icons don't get messed up, when you exit from "cmd" after you're finished.

Both WinXP and Win2K seem to be equal in this behavior. By using
a virtual machine, it made it easier to determine the resolution
requested from the graphics card, which seems to be 640x480. And
I would think your netbook would need to provide a mechanism for
such a resolution as well.

Paul