Message-ID:	<002901c270ee$a3c43f30$0a02a8c0@p4>
From:	"Andrew Cottrell" <acottrel AT ihug DOT com DOT au>
To:	<djgpp-workers AT delorie DOT com>
References:	<10210091627 DOT AA21740 AT clio DOT rice DOT edu> <3DA5C06C DOT 8D0140D1 AT phekda DOT freeserve DOT co DOT uk>
Subject:	File UItils at Clio 2.04 Query
Date:	Fri, 11 Oct 2002 16:21:25 +1000
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2800.1106
Reply-To:	djgpp-workers AT delorie DOT com

> > I believe File Utils 4.0 built with CVS was also working fine, so there
> > is some incompatibility between the 4.1 source and how it assumes the
> > library calls will act compared to the CVS tree.  4.1 built with 2.03
> > also works?
> [snip]
>
> 4.1 built with 2.03 refresh 2 does not work all the time. I have seen it
abort
> on Windows NT 4 with short filenames under VMware 3.2. So it seems like
2k/XP
> expose the problem more frequently than under 9x/ME/NT.
I re-built FileUtils 4.0 with CVS last night and tried the rm -rf
<directory> which failed win 4.1 and it worked okay.

What do people think I should put on clio with regards to the file utilities
built with the CVS LIBC? Some example I can think of are:-
    a) Put File Utils 4.0 up there
    b) Put File Utils 4.1 with rm.exe from File Utils 4.0
    c) Put File Utils 4.1 with rm.exe from Core Utils
    d) None - get people to use the File Utils 4.1 from simtel - this is
what happens with the latest update

I can easily do any of the options outlined above, but does anyone have any
other ideas?

Andrew

- Raw text -