Mail Archives: djgpp/2003/04/13/20:45:08
Charles Sandmann <sandmann AT clio DOT rice DOT edu> writes:
>> GNU bash, version 2.04.7(1)-release (i686-pc-msdosdjgpp)
>> Copyright 1999 Free Software Foundation, Inc.
>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
>> &, as I wrote in my original post, it works fine on single processor
>> Win2k machines, but m-u-c-h s-l-o-w-e-r on a dual-processor Win2k
>> machine that actually has much faster processors.
>I believe this is something else in your environment which is the
>problem.
I would not be surprised. This is my first experience with a dual
processor Win2k machine; indeed I have little experience with Win2k at
all [since Linux/Unix is my platform of choice but this project
assignment wasn't my choice]. I executed "set" in cmd.exe & didn't
see anything that aroused my naive suspicion.
>I've run DJGPP on dual processor machines many times and
>I don't see any response issues. Maybe you could be more specific?
This verifies that it's likely something in my setup & nothing
inherent to DJGPP vs. dual Win.
DJGPP is stored on a share being served by SAMBA & it is responsive on
a single processor Win2k machine on the same network. Only this dual
machine has shown any anomaly.
_bashrc & djgpp.env are on the local disk & I have verified TMPDIR &
TEMP point to local disk. I even copied bash.exe to local disk but no
improvement in responsiveness.
Much obliged, Bob
--
<> Robert Geer & Donna Tomky | |||| We sure |||| <>
<> bgeer AT xmission DOT com | == == find it == == <>
<> dtomky AT xmission DOT com | == == enchanting == == <>
<> Albuquerque, NM USA | |||| here! |||| <>
- Raw text -