From: "A. Sinan Unur" Newsgroups: comp.os.msdos.djgpp Subject: Re: conflict. Date: 9 Dec 2002 23:41:30 GMT Organization: Cornell University Lines: 26 Sender: asu1 AT cornell DOT invalid (on pool-141-149-207-220.syr.east.verizon.net) Message-ID: References: <2110-Mon09Dec2002220401+0200-eliz AT is DOT elta DOT co DOT il> NNTP-Posting-Host: pool-141-149-207-220.syr.east.verizon.net X-Trace: news01.cit.cornell.edu 1039477290 12676 141.149.207.220 (9 Dec 2002 23:41:30 GMT) X-Complaints-To: usenet AT news01 DOT cit DOT cornell DOT edu NNTP-Posting-Date: 9 Dec 2002 23:41:30 GMT User-Agent: Xnews/5.04.25 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com "Eli Zaretskii" wrote in news:2110- Mon09Dec2002220401+0200-eliz AT is DOT elta DOT co DOT il: >> Date: Mon, 9 Dec 2002 18:58:42 +0100 (MET) >> From: "Riccardo Fantoni (Pastore)" >> >> some file utilities (ls.exe for example) >> conflict with the scrollbar of the >> command shell. Is there any workaround >> for this problem ? > > I don't think there is a work-around, sorry. Any DOS program that > accesses the video memory directly will cause this unpleasant > side-effect. I consider this a misfeature of the NT family of > Windows. if the OP is referring to the scrollbar flashing, indeed we seem to be stuck with that. in any case, i would recommend setting the cmd or command window sizes to one of the standard modes such as 80x25, 80x43, or 80x50 to minimize the effect. -- A. Sinan Unur asu1 AT c-o-r-n-e-l-l DOT edu Remove dashes for address Spam bait: mailto:uce AT ftc DOT gov