X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f X-Recipient: djgpp AT delorie DOT com Message-ID: X-Originating-IP: [131.107.0.73] From: Jay To: , Subject: Re: window blinks every time when i run the linux commands (like gcc/make/ls, etc) using DJGPP Date: Wed, 6 Aug 2008 04:20:06 +0000 Importance: Normal In-Reply-To: <200808060405.m76452Y7020764@delorie.com> References: <200808060405 DOT m76452Y7020764 AT delorie DOT com> Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 X-OriginalArrivalTime: 06 Aug 2008 04:20:07.0090 (UTC) FILETIME=[B5113120:01C8F77B] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id m764KDxv021767 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 Clarification: What people were suggesting when they say to sit in command.com instead of .cmd is that: The blink occurs upon transition either from a 32bit program to a 16bit program, or vice versa. That is, if you are in cmd, and run a 16bit app such as ls, either starting it and/or exiting it will "blink". Since cmd is 32bit and you'd be transition from it to ls to start ls and from ls to cmd upon ls ending. So a solution, if you can find a tolerable 16 command line editor, is to sit in a 16 bit shell. Such as command.com, or bash, or 4dos. command.com might be a little funny and not seem to work. Look at \windows\system32\autoexec.nt or \windows\system32\config.nt maybe for settings to "help". (and what are those ntdos.sy and ntio.sys files..hm..) > DJGPP images run under a DOS virtual session, and it only supports > certain screen sizes. Try a standard DOS screen size 25x80, 43x80, > 50x80; and see if the flicker is more tolerable. The blink happens > when the scroll-back screen buffer is cleared. Aha! Thanks. mode con cols=80 lines=24 ? - Jay