delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1999/10/17/20:00:17

From: "A. Darrow" <msmsh AT freewwweb DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Newbie frustration: headers not found
Date: Sun, 17 Oct 1999 18:26:12 -0700
Organization: Posted via Supernews, http://www.supernews.com
Lines: 78
Message-ID: <s0kmp3ukr0176@corp.supernews.com>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 991017141635 DOT 25053N-100000 AT is>
X-Complaints-To: newsabuse AT supernews DOT com
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2014.211
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote in message
news:Pine DOT SUN DOT 3 DOT 91 DOT 991017141635 DOT 25053N-100000 AT is...
>
> On Thu, 14 Oct 1999, A. Darrow wrote:
>
> > I beg to differ, the LFN's are still there according to
> > Diskedit they just don't show up in the DIR command
> > listing. Did you alter your dir command through
> > programming or a different DOS command interpreter?
>
> No, I used the stock version of the DIR command built into
> COMMAND.COM.  You do use COMMAND.COM as your shell, do you?

    Nope, same as you!


> If you also used DIR from COMMAND.COM, then I suspect that long file
> names are somehow disabled in your version of Windows.  I'm attaching
> below a simple test program that checks long file name support.
> Please compile it, like this:
>
> gcc -Wall -O2 -o tlfn tlfn.c
>
> then run it like this:
>
>         tlfn
>
> and tell here what did it print.

    _USE_LFN reports 0 at startup
Flags: 0, MaxFile: 13, MaxPath: 80, FSName:
_USE_LFN reports 0 when _CRT0_FLAG_NO_LFN is set
_USE_LFN reports 0 when LFN is set to Y
_USE_LFN reports 0 when LFN is set to N

Perhaps you could also explain what this means.


> > I tried unzip32 with the result that there were no LFN
> > entries at all, not even those pesky numeric tails. All
> > entries longer than the standard 8+3 were all truncated.
>
> This is another sign that long file name support is disabled, at least
> as far as DJGPP programs are concerned.  You should, at least, to be
> able to compile C++ proghrams now, if you set LFN=n in the environment.
>
> Can you create a file with a long file name with some Windows utility,
> like Notepad?

    Yes, I have always been able to do that and it still works after I ran
    your program. Long file names have always shown up in Win95
    Explorer and the 8+3 numeric tails in DOS. Norton Diskedit reveals
    Long file names and the DOS truncated names contiguous to one
    another on the disk. This may or may not be important, but the LFN
    entry has only the V (volume) attribute set, whereas the DOS entry
    has Archive set along with any other depending on how the file was
    saved.


> And, sorry for asking the obvious, but you are running Windows 9X, not
> Windows NT or Windows 2000, right?

    Win95 OSR2 HP OEM version; see original posting

> > Oh this is just so much fun!!
>
> Your case is somehow very special, I have never seen one like it, not
> on Windows 9X.  Please keep looking into it.  We will solve it,
> eventually.
>
    Sorry for the editorial comment, but it is frustrating. Thanks for
hanging
    in there.




- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019