Xref: utzoo comp.windows.ms:6773 comp.windows.ms.programmer:11
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!ut-emx!ccwf.cc.utexas.edu!johnl
From: johnl@ccwf.cc.utexas.edu (John Lange)
Newsgroups: comp.windows.ms,comp.windows.ms.programmer
Subject: win3 is switching video modes - WHY?
Message-ID: <38923@ut-emx.uucp>
Date: 31 Oct 90 03:24:56 GMT
Sender: news@ut-emx.uucp
Reply-To: johnl@ccwf.cc.utexas.edu (John Lange)
Followup-To: comp.windows.ms
Organization: The University of Texas at Austin
Lines: 21

I posted a similar message a few weeks ago, but didn't get an email 
response.  It's possible someone posted an answer to comp.windows.ms,
but I don't read all of the responses there, so I apologize if this
has already been answered.  Please respond with email.

Outside of Windows, I like using a special video mode that allows 132 x 50
text.  After entering Windows, running my program, and exiting, the video
mode is switched back to the default 80 x 25.  It's not a big deal, but
it has begun to get on my nerves enough to try to find a way around it.

Another clue is that just entering Windows and exiting will leave the
video mode in 132 x 50.  Also, running the programs that come with 
Windows and the SDK don't cause mode changes.  

Has anyone else experienced this problem or tracked down the cause?
Back when I had MS support (right before it expired), I asked about this,
and their comment was, "Well, it shouldn't do that." 

I had this problem back when I was programming with Turbo-C and MetaWindows,
and got around the problem by modifying one of the library source files
for Turbo-C (we had bought the source).