From: Regis BOSSUT <bossut AT isen DOT fr>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Q: How to programmatically set a dos window to full screen ?
Date: Fri, 22 Aug 1997 12:29:21 +0200
Organization: IEMN - Dépt ISEN - Acoustique
Lines: 28
Message-ID: <33FD6A01.2450@isen.fr>
References: <33FAFCDB DOT 2B6B AT isen DOT fr> <5tj9d7$ifn AT freenet-news DOT carleton DOT ca>
NNTP-Posting-Host: hpac1.isen.fr
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

Paul Derbyshire wrote:
> 
> 
> You must have found Yet Another Windows Bug (copyright 1995 Microsoft
> Inc.) :-)
> 
> I have copied a two-meg 1280x1024x256 image to the clipboard from a
> fractal app and pasted it into Microsoft Word without so much as a
> screwed-up pixel. Either the bug is in Windows (if you used
> print-screen)
> or the bug is in your screen capture app (if you used one). I have
> copied
> a 640x480x256 screen using Paintshop Pro's screen capture function
> without difficulty.

I used Print-Screen. Could it be some kind of Bios bug ?

About int 0x2f with ax = 0x168b and bx = 0 :
> And what does it do in DOS? If it's ignored, good. If it blows the
> computer's brains out all over your screen from the inside, then you'd
> better not use it without detecting Windows first using allegro's
> "i_love_bill" variable or another well-documented interrupt for
> detecting windows.

I didn't mention about detecting Windows first, as it was evident to me.
However, I didn't test it under DOS or WinNT. Should I ?... :-)

/Régis