From: Andrew Newsgroups: comp.os.msdos.djgpp Subject: Re: long filename under DJGPP 2.04 alpha 1 Date: Tue, 06 May 2003 18:34:13 +1000 Organization: ECLiPSE Lines: 23 Message-ID: <2csebv4m2m356b81go436kpko6728mc366@4ax.com> References: NNTP-Posting-Host: p81-tnt7.syd.ihug.com.au Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: lust.ihug.co.nz 1052210057 25591 203.173.144.81 (6 May 2003 08:34:17 GMT) X-Complaints-To: abuse AT ihug DOT co DOT nz NNTP-Posting-Date: Tue, 6 May 2003 08:34:17 +0000 (UTC) X-Newsreader: Forte Agent 1.92/32.572 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com >I have readed list of changes and features but I'm confused about long >file name support under NT4 in 2.04 alpha. Is that supported or not? >I'm trying to start some bash script using current alpha version and >behaviour about file names not changed from 2.03. Is there anything >specific about turning this on? NT 4.0 is a completly different Windows code base compared to Win 9x and to a lesser extent 2K and XP. Do not assume that NT 4.0 in any way shape or form is similar to Win 2K or XP when dealing with LFN as it does not support the low level API that is avaialble with Win 9X, 2K or XP. The 2.04 alpha 1 fixes Win 2K and XP LFN and a stack of other issues that forced the 2 releases of the 2.03 by Charles. Allot of the code changes when you look at them does not differentiate between NT 4.0, W2K or XP because using the low level API there is no way to tell the differences as far as we could find. If you do know of a way that allows you to find out if you are running on NT 4.0, 2K or XP using standard int86 functions then please let us know as it will help out allot. See the other emails for getting LFN working on NT 4.0. Andrew