Date: Wed, 19 Mar 1997 12:27:04 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Dan Hirschberg <dan AT verity DOT ICS DOT UCI DOT EDU>
cc: djgpp AT delorie DOT com, dan AT verity DOT ICS DOT UCI DOT EDU
Subject: Re: novice errors? dpmi, info, groff, df 
In-Reply-To: <9703180934.aa23073@paris.ics.uci.edu>
Message-ID: <Pine.SUN.3.91.970319122639.19845A-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Tue, 18 Mar 1997, Dan Hirschberg wrote:

> 27MB is likely to be far more than I would need for the foreseeable
> future.  The reason I was concerned is because, allegedly, the
> information provided was supposed to tell me the limits of what
> is available and therefore suggests that, even if I wanted to,
> I could not use more than 27MB because no virtual memory is
> available.

Probably so.  But since 27MB is enough, you shouldn't worry.

> and see if that works.  I should note that, I believe, the filenames
> were left unchanged by my unzipping.  That is to say, I believe that
> the filename of that file on my system really is tmac.pspic
> but that the NT system maintains dual names, one that is long and
> one that is 8.3 compliant.

The problem is that NT doesn't support the LFN API (which lets DOS
programs use the long filenames on Windows 95).  If it were, you would
only need to turn on LFN support in DJGPP, and then you could use the
long filenames as you unzipped them.  But since NT doesn't support the
LFN API, you have no choice but to use an unzip program that truncates
the long names to 8+3 limits (thus preventing NT from adding the
numeric tail when it truncates names) and disable the LFN support in
DJGPP; otherwise, the things won't work.