Mail Archives: djgpp/2002/08/17/04:19:23
> 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.
- Raw text -