[comp.windows.ms] Trouble with window size for Non-Windows apps.

mds@duke.cs.duke.edu (Mark David Shattuck) (09/14/90)

	I would like to be able to set the size of a DOS
window in win3 enhanced mode.  I want a 132x44 characters
window.  Can this be done??

	I found in sysini.txt file the flag Pagelength= which
is under [non-windows], but setting this to 44 and restarting
did not help.  I have looked in the manual and could not find
anything useful, though I have not finished reading it cover 
to cover.  

Info on my setup:

    Hardware:
	DTK PEM2500 386 25MHz 64K cache
	4MB RAM
	ATI VGA Wonder V3 512K (running windows in 800x600x16)
	NEC 3D
	DTC 2FD/2HD 16-bit RLL controller

    Software:
	Windows 3.0 (running in Enhanced Mode)
	DOS 3.3
	
	-mark shattuck (mds@cs.duke.edu)
	

mds@duke.cs.duke.edu (Mark David Shattuck) (09/14/90)

In article <653258385@globe01.cs.duke.edu> mds@duke.cs.duke.edu (Mark David Shattuck) writes:
>	I found in sysini.txt file the flag Pagelength= which
                                            ^^^^^^^^^^^
>is under [non-windows], but setting this to 44 and restarting
>did not help.  I have looked in the manual and could not find
>anything useful, though I have not finished reading it cover 
>to cover.  

	I meant ScreenLines= not PageLength=.
Also, I can get 80x50 by switching to that mode,
but It won't seem to handle 132 columns.


	-mark shattuck (mds@cs.duke.edu)
	

jls@hsv3.UUCP (James Seidman) (09/14/90)

In article <653258385@globe01.cs.duke.edu> mds@duke.cs.duke.edu (Mark David Shattuck) writes:
>	I would like to be able to set the size of a DOS
>window in win3 enhanced mode.  I want a 132x44 characters
>window.  Can this be done??

Nope, 'fraid not.  There is only support for "standard" text modes, i.e.
those which can be done on true-blue IBM video cards.  That means 80x25,
80x43, and 80x50 (and some 40-column modes).  I've gotten some other
extended 80 column modes, like 80x60 to work, but it's unreliable (random
cases of areas of the screen getting cleared, the cursor winding up in
the wrong place, etc.).

The problem is that the screen display is handled by Windows' Virtual
Display Driver (VDD) which isn't set up for proprietary extensions.
Unless your VGA manufacturer has rewritten it (which I *strongly* doubt)
then you're out of luck.
-- 
Jim Seidman (Drax), the accidental engineer.
"There's a certain freedom to being completely screwed." - The Freshman
UUCP: ames!vsi1!headland!jls
ARPA: jls%headland.UUCP@ames.nasa.arc.gov