Mail Archives: djgpp/2002/08/17/12:59:13
You are right regarding these PCs NT and WIN2K. These
two PCs are set up the same. They are belonged to my
company I work for and they have the same software
installed and similar setup.
It does not happen with 'cgwin' which is installed on
these two PCs. I believe that this is something to do
with the setup or some software that is running on the
background.
The two machine have Rational Rose installed ( Clear
case, Clear quest, etc.) and also Lotus Note for
email.
One thing I have noticed is when I run 'gnu' compiler
using make file I got Rational Window open that stop
the make process and ask me to confirm my license.
After I confirm it the make (compile) continues.
The 'ls.exe' command from 'cygwin' is running OK under
CDM.EXE but not the 'ls.exe' from DJGPP. Also when I
compile and link a simple c file call hello.c: (The
computer PATH is
set PATH=C:DJGPPBIN;%PATH% and DJGPP is set DJGPP =
C:DJGPPDJGPP.ENV )
// hello.c
#include <stdio.h>
main()
{
printf(" Hello DJGPP
");
return 0;
}
It creates hello.exe. When I run hello.exe from DOS
prompt running CMD.EXE shell I could not see the
print however, running command.com shell from the
same DOS prompt prompt then run hello.exe it works
O.K. Running again CMD.EXE on the same DOS prompt and
running hello.exe it does not print. It is only
happened with these computers at works. I have PC
Millinum at home and it works (with DJGPP) with no
problem.
What is the different between cgwin and DJGPP commands
(ls.exe etc.) ?
I will continue to work on this problem.
--- Charles Sandmann <sandmann AT clio DOT rice DOT edu> wrote:
> > This is correct and true !! I force the output of
> > go32-v2 to file like that ( go32-v2 > myfile ) and
> > that is the only way I can see the results.
>
> This is very unusual - I have not see it on dozens
> of Win2K systems I've used DJGPP with. I suspect
> that
> some software you have installed on the system is
> causing a conflict. You said you also see the
> problem on Windows NT, which is also unusual - so I
> suspect you have something common in both installed
> configurations causing the problem.
>
> There is a similar open bug (00327) open in the bug
> tracking system reported for Windows NT - but this
> has not been reproducible - so we are pretty sure it
> has something to do with some other installed
> software.
> Finding what is the conflict would good to document.
> This is only the second report I've seen of this
> problem
> in 2 years (with the first being the open bug).
>
> > I run CMD.EXE date Tuesday, May 08, 2001, 8:00:00
> AM.
> > the 'ls' is:
> > -rwxr-xr-x 1 dosuser root 121344 May 26
> 2000 ls.exe
>
> This binary is too old for Windows 2000 to work
> reliably - all
> binary .exe images in your djgpp directory should be
> dated
> December 2001 or later for reliable Windows 2000 (or
> XP) operation.
> I don't think this is the cause of your output
> problem, but
> it would not hurt to make sure you have the most
> recent versions.
> Updated versions are available from ftp.simtel.net
>
> > You are right when I use command.com date
> Tuesday,
> > May 08, 2001, 8:00:00 AM it is running OK.
>
> An interesting observation - and a workaround. I
> can't explain
> it. You might try reducing the environment size
> (unSET'ing variables),
> disabling virus checkers and turning off non-native
> services to see
> if anything helps.
__________________________________________________
Do You Yahoo!?
HotJobs - Search Thousands of New Jobs
http://www.hotjobs.com
- Raw text -