From: bgeer Newsgroups: comp.os.msdos.djgpp Subject: Re: Win2k on dual processor - help? Date: Wed, 16 Apr 2003 19:27:07 +0000 (UTC) Organization: XMission http://www.xmission.com/ Lines: 38 Message-ID: References: <3e95632a DOT sandmann AT clio DOT rice DOT edu> <3e9870ad DOT sandmann AT clio DOT rice DOT edu> <3e9b2edf DOT sandmann AT clio DOT rice DOT edu> NNTP-Posting-Host: xmission.xmission.com X-Trace: terabinaries.xmission.com 1050521227 17071 198.60.22.20 (16 Apr 2003 19:27:07 GMT) X-Complaints-To: abuse AT xmission DOT com NNTP-Posting-Date: Wed, 16 Apr 2003 19:27:07 +0000 (UTC) User-Agent: nn/6.6.3 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Charles Sandmann writes: >> >I would need the date and size of the binary to be sure, but this >> >sounds correct. >> >> -rw-rw-r-- 1 bgeer bgeer 648704 Mar 1 02:19 bash.exe >This is wrong. The current bash.exe on Simtel is 573,440 bytes and is >dated 12/24/2001. >If you could find a DJGPP image which runs slowly, and do a little >debugging it would be nice to know what procedure it's calling which >is slow. bash is not the only program exhibiting extreme sluggishness. Using "less" to display a file within cmd.exe is slow. Typing 'q' to quit less is very prompt, even before display begins. I'm now convinced that it is the actual display of stdin/stderr output which is slow. Using MS "more" within cmd.exe is quick. emacs display is very sluggish, yet typing the exit command gives instantaneous result. This problem appears isolated to the dual processor machine to which I have access, & I only have access to 1 now. I may soon get a chance to try on another. As I noted before, all these same programs work very well on single processor machines. Wierd. -- <> Robert Geer & Donna Tomky | |||| We sure |||| <> <> bgeer AT xmission DOT com | == == find it == == <> <> dtomky AT xmission DOT com | == == enchanting == == <> <> Albuquerque, NM USA | |||| here! |||| <>