From: sandmann AT clio DOT rice DOT edu (Charles Sandmann) Message-Id: <10108071458.AA17574@clio.rice.edu> Subject: Re: Windows 2000 LFN issues To: eliz AT is DOT elta DOT co DOT il (Eli Zaretskii) Date: Tue, 7 Aug 2001 09:58:03 -0500 (CDT) Cc: acottrel AT ihug DOT com DOT au, djgpp-workers AT delorie DOT com In-Reply-To: from "Eli Zaretskii" at Aug 07, 2001 10:55:49 AM X-Mailer: ELM [version 2.5 PL2] Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > > Just to give you hope, out of the zip "touch" works with LFNs on XP RC1. > > So they occasionally fix some things :-) > > Sorry, I don't understand: what is this ``out of the zip "touch"''? > Do you mean that you reported the bug and it already got corrected? ;-) The touch executable doesn't work on Windows 2000 if LFN is on, but it does work without modifictions or rebuilding on XP. I didn't report it, just noticed it works... > Btw, if XP behaves differently from W2K, we will need a way to > distinguish between them. Right now, it's not possible, AFAIK, > without some heavy and dangerous processing that is inappropriate for > libc.a. Right now I haven't found anything new under XP to require different behavior. But we do have 3 environments which are very similar from DOS version but may require differences in code: 1) Windows NT 4.0 with LFN TSR 2) Windows 2000 3) Windows XP (I haven't tried the personal version, just pro) The difference between 1 and 2 worries me. > So the IOCTL interface is botched as well. Sigh... > > This probably means that the only practical way is to go through SFN > open/create functions. Otherwise, we will find out that things begin > to fall apart all over the place, since IOCTL is used in many library > functions. Yes, I was surprised it works as well as it does currently. I was also thinking about what happens if we don't fix create handles. the IOCTLs break - so it looks like a file on drive A (not too bad). We don't create devices. The utime stuff may be fixable with the direct call.