Date: Wed, 29 Dec 1999 10:08:44 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: John & Susie <jdk AT sgi DOT net>
cc: djgpp AT delorie DOT com
Subject: Re: Rhide and (unspecified) long file name support.
In-Reply-To: <3866CF20.9A6A71ED@sgi.net>
Message-ID: <Pine.SUN.3.91.991229100607.11728G-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Sun, 26 Dec 1999, John & Susie wrote:

> Would not denying long filename support in DOS 6.x have anything to do
> with Rhide occasionally failing to load an Allegro .dat file when an
> executable is run from within Rhide?

I find it hard to believe that long file names could have anything to do 
with this problem.  The DJGPP library senses whether the long file names 
are supported, and if not, automatically switches to using legacy DOS 
functions for 8+3 names.

> I have an intermittent problem of
> this sort, yesterday Rhide wouldn't run a program that loads a font
> file, today it does? This makes no sense, something external is going on
> here, any ideas on what to check?

Sounds like some uninitialized memory somewhere.

I suggest to put debugging printf statements near the code which loads 
the file, and see what do they print when the file fails to load.