Date: Thu, 17 Oct 2002 08:23:56 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
cc: djgpp AT delorie DOT com
Subject: Re: WinXP's unbreakable console cursor
In-Reply-To: <3dad920f.sandmann@clio.rice.edu>
Message-ID: <Pine.SUN.3.91.1021017082249.3848K-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Wed, 16 Oct 2002, Charles Sandmann wrote:

> > It seems that DJGPP compiled programs are unable to turn off
> > the cursor (making him invisible) if used under Win XP.
> 
> Screen management under Win2K and WinXP is sort of strange.  It appears
> the screen buffer and cursor is a Win32 one unless you do certain
> operations.  For example, if I write directly to the screen I warp the
> window into a fixed size (with no scroll bar) which direct reads/writes
> and other stuff works - but if I don't then sometime bios calls, and/or
> direct screen reads (like symify) don't work.

Does that mean the BIOS function to set the cursor scan lines doesn't 
work on XP?

(You could test this with the DJGPP port of Emacs, it supports cursor 
shape changes.)