From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1EJDvj-0006tC-5r
	for qemu-devel@nongnu.org; Sat, 24 Sep 2005 13:35:19 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1EJDvh-0006sv-Hr
	for qemu-devel@nongnu.org; Sat, 24 Sep 2005 13:35:18 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1EJDqT-0004i2-3u
	for qemu-devel@nongnu.org; Sat, 24 Sep 2005 13:29:53 -0400
Received: from [65.74.133.11] (helo=mail.codesourcery.com)
	by monty-python.gnu.org with esmtp
	(TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.34) id 1EJDWz-0005hg-Ea
	for qemu-devel@nongnu.org; Sat, 24 Sep 2005 13:09:45 -0400
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] video mode in windows game
Date: Sat, 24 Sep 2005 18:09:35 +0100
References: <1f198c3050923234379085d2f@mail.gmail.com>
	<20050924154649.GA20377@jbrown.mylinuxbox.org>
	<1878848186.20050924183306@ena.si>
In-Reply-To: <1878848186.20050924183306@ena.si>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="windows-1250"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200509241809.36788.paul@codesourcery.com>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org
Cc: Jernej =?windows-1250?q?Simon=E8i=E8?= <jernej@ena.si>

On Saturday 24 September 2005 17:33, Jernej Simon=E8i=E8 wrote:
> On Saturday, September 24, 2005, 17:46:49, Jim C. Brown wrote:
> > Weird. Of course, in that case it shouldn't go into fullscreen mode at
> > all - it should report the error and go back to the host's original
> > resolution.
>
> Not necessarily - especially LCDs can be sometimes very picky about the
> modes they support, eg. on one of my computers, a LCD monitor wouldn't
> display the BIOS bootup screen anymore (it just showed "Video mode not
> supported") after I switched from an on-board GFX card to a PCI one, even
> though it appeared identically on an old CRT monitor.

It's still wrong for windows to try and use modes that don't work.
Windows should know what modes are supported by your monitor and refuse to=
=20
switch to anything else. Sounds like you haven't configured windows=20
correctly.

Paul