Change in screen?

[JimL]

XP Pro, SP3, Current updating, Thinkpad T60p

I use a couple vital DOS programs regularly. Sometimes I need one to come
up full screen. Relatively recently it has come up in full screen, but
squeezes the program into the top half of the screen. I've tried setting
window fonts without effect.

Is there a precise order of steps required to get this back to real full
screen? If so, what?

JimL

[Auric__]

Post by JimL
XP Pro, SP3, Current updating, Thinkpad T60p
I use a couple vital DOS programs regularly. Sometimes I need one to come
up full screen. Relatively recently it has come up in full screen, but
squeezes the program into the top half of the screen. I've tried setting
window fonts without effect.
Is there a precise order of steps required to get this back to real full
screen? If so, what?

First off, this group is meant for discussion of the BASIC programming
language under DOS. Questions like this would best be asked in a Windows
group -- for instance, alt.os.windows-xp.

Having said that, it sounds like the program expects 80x25 mode, while XP is
giving it 80x50 mode (or larger). Try this:
- bring up the properties of the program (right-click the title bar, then
select Properties)
- go to the Layout tab
- check the Height in the Window Size area -- if it says 50, try changing
it to 25 and then restarting the program

[JimL]

Post by Auric__

Post by JimL
XP Pro, SP3, Current updating, Thinkpad T60p
I use a couple vital DOS programs regularly. Sometimes I need one to come
up full screen. Relatively recently it has come up in full screen, but
squeezes the program into the top half of the screen. I've tried setting
window fonts without effect.
Is there a precise order of steps required to get this back to real full
screen? If so, what?

First off, this group is meant for discussion of the BASIC programming
language under DOS. Questions like this would best be asked in a Windows
group -- for instance, alt.os.windows-xp.
Having said that, it sounds like the program expects 80x25 mode, while XP is
- bring up the properties of the program (right-click the title bar, then
select Properties)
- go to the Layout tab
- check the Height in the Window Size area -- if it says 50, try changing
it to 25 and then restarting the program
--
So now we're pleading "Not Guilty by Virtue of Two Wrongs Make a Righ

Thanks for replying. I can't find what looks like a DOS oriented group and
windows groups get hostile about "backward" DOS users messing up their space
with ancient, outmoded rubbish that isn't Hot/New.

The setting you suggested should be 80x25 is and always has been 80x25.

Thanks anyway.

JimL

[Auric__]

Post by JimL

Post by Auric__

Post by JimL
XP Pro, SP3, Current updating, Thinkpad T60p
I use a couple vital DOS programs regularly. Sometimes I need one to come
up full screen. Relatively recently it has come up in full screen,
but squeezes the program into the top half of the screen. I've tried
setting window fonts without effect.
Is there a precise order of steps required to get this back to real
full screen? If so, what?

First off, this group is meant for discussion of the BASIC programming
language under DOS. Questions like this would best be asked in a
Windows group -- for instance, alt.os.windows-xp.
Having said that, it sounds like the program expects 80x25 mode, while
- bring up the properties of the program (right-click the title bar,
then select Properties)
- go to the Layout tab
- check the Height in the Window Size area -- if it says 50, try
changing it to 25 and then restarting the program

Thanks for replying. I can't find what looks like a DOS oriented group
and windows groups get hostile about "backward" DOS users messing up
their space with ancient, outmoded rubbish that isn't Hot/New.
The setting you suggested should be 80x25 is and always has been 80x25.

Then try this: open a command.com window and navigate to where the app is
(unless it's in the path, then not necessary). Press Alt+Enter to switch to
full-screen mode, then enter "mode con lines=25", then run your program. Does
*that* work? (That's a one-time-only fix, btw.)