Sender:	bill AT taniwha DOT tssc DOT co DOT nz
Message-ID:	<37369250.D04A2DF4@taniwha.tssc.co.nz>
Date:	Mon, 10 May 1999 20:01:20 +1200
From:	Bill Currie <bill AT taniwha DOT tssc DOT co DOT nz>
X-Mailer:	Mozilla 4.05 [en] (X11; I; Linux 2.2.6 i486)
MIME-Version:	1.0
To:	djgpp-workers AT delorie DOT com
Subject:	Re: LFN and RAMDRIVE (was: Re: LFN=y and MS-RAMDRIVE)
References:	<199905090745 DOT JAA25001 AT father DOT ludd DOT luth DOT se>
Reply-To:	djgpp-workers AT delorie DOT com

Martin Str|mberg wrote:
> 
> I have just tried out Franck Uberto's XMSDSK (downloaded from
> simtel). It's really strange. It exibits exactly the same symptoms as
> MS-RAMDRIVE, i. e. RAMDISK up to 8MB works fine, while a size of 16MB
> makes it loose LFN ability.
> 
> Does anybody have any idea how to have a RAMDISK which is 16MB with
> LFNs?

Hmm, very strange indeed.  As to your question, I'ld first like to
answer with another question: why would a > 8MB ramdisk loose lfn in the
first place?

I just though of something: could it be something to do with fat size
(ie 16 vs 12 bit)?  This would be a bug in Win9* I guess.  I really
can't see why ramdisk size would be a factor.

Ob lfn: anybody want to give my lfn driver a go?  All the main
filesystem functions are there (open file, find first/next, delete, etc)
but rename is untested as yet.  Also, most of the extra functions (get
file info, get short name, get volume info etc) are either not
implemented, incomplete, or otherwise not particularly usefull (vet
volume info is just functional enough to enable lfn in djgpp).

Source can be had from my home page (http://www.tssc.co.nz/~bcurrie/ ). 
Look for the M$ DOG LFN driver.  My copy of djasm will be needed as my
latest patches have not been applied to the CVS tree yet (too my
knowledge).

DJ: any chance I can have cvs write access?  I admit I don't really do
enough to warrant it, but it would make things easier for both of us.

Bill
-- 
Leave others their otherness.

- Raw text -