From: Charles Sandmann Newsgroups: comp.os.msdos.djgpp Subject: Re: WinXP's unbreakable console cursor Date: Wed, 16 Oct 2002 11:21:35 CDT Organization: Rice University, Houston TX Lines: 18 Message-ID: <3dad920f.sandmann@clio.rice.edu> References: <3dad538f_1 AT news DOT arcor-ip DOT de> NNTP-Posting-Host: clio.rice.edu X-Trace: joe.rice.edu 1034787096 18066 128.42.105.3 (16 Oct 2002 16:51:36 GMT) X-Complaints-To: abuse AT rice DOT edu NNTP-Posting-Date: 16 Oct 2002 16:51:36 GMT X-NewsEditor: ED-1.5.9 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com > 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. > Let me guess, another function the (explitive) XP console doesn't support > (like the delay thing)? It could be it's not supported - I haven't tested it. I've looked at an alternate delay implementation. Getting timer tick resolution is fairly easy, but since uclock() is also flakey I don't have not checked in a updated delay() into the new release yet.