Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!nstn.ns.ca!news.cs.indiana.edu!spool.mu.edu!think.com!rpi!usc!wuarchive!uunet!bfmny0!tneff
From: tneff@bfmny0.BFM.COM (Tom Neff)
Newsgroups: comp.windows.ms
Subject: Re: command.com in window size
Message-ID: <24425106@bfmny0.BFM.COM>
Date: 31 May 91 06:19:53 GMT
References: <6279@ns-mx.uiowa.edu>
Reply-To: tneff@bfmny0.BFM.COM (Tom Neff)
Lines: 18

In article <6279@ns-mx.uiowa.edu> cohen@brodmann.iaf.uiowa.edu (Gregg Cohe) writes:
>I have command.com in a window and I have noted that the window opens to a
>reasonable size and then contracts to an almost ridiculously small size.  What
>variable in which file do I change that controls the size and font in windows
>like this.

In my experience, the INITIAL size of a DOSapp window in enhanced mode
is however many rows you had up the LAST time you were in DOS -- whether
before Windows was invoked or in the last DOSapp.  So if you switch to
43 line mode before starting Windows, you will see windowed DOSapps
starting up with 43 lines briefly before they switch into whatever mode
they really want to use.

It may be more complicated than this, the above is just my empirical
observation.  There doesn't seem to be any official documentation on
Win3's behavior in this department.  What I have learned to do is start
any DOSapp needing other than 80x25 in Full screen mode, and switch it
down to a window afterward if needed.