Date: Wed, 18 Sep 1996 15:12:21 +0200 (MET DST) From: Mark Habersack Reply-To: grendel AT ananke DOT amu DOT edu DOT pl To: Cesar Scarpini Rabak cc: Alexander Lehmann , djgpp AT delorie DOT com Subject: Re: LFN In-Reply-To: <1.5.4.16.19960918095131.372fa606@dmeasc.rc.ipt.br> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 18 Sep 1996, Cesar Scarpini Rabak wrote: >At 12:57 18/09/96 +0200, Mark Habersack wrote: >>On 17 Sep 1996, Alexander Lehmann wrote: >> >>>When you are running djgpp v2 programs under Win95 (not DOS7), they >>>support LFN if the environment variable LFN is set to y. If you are >>>running only DOS7 without Win95 or DOS6.22, it is not available >>>(neither in Win NT 4.0). There have been some discussion on the list >>>recently if it would be possible to add LFN support functions to old >>>DOS maybe with a TSR, but nothing has been done yet (I think). >>Well, actually I have written a lib to read LFNs on any DOS. I think I'll be >>ready to release it next week. Now, as we speaking about that, do you think >>that supporting CREATION of LFN entries on any DOS makes sense? It requires >>writing virtually all access routines - DOS can't help here... >> > >I have not a formed opinion still, but as food for thought: >when one downloads some nice package originally delopped w/u**x in mind, >several filenames are longer than 8+3; to have means of doing that would >easy the work on the port, given this support could be incorported in (at >least) one port of some shell (e.g., bash), the decompressing utility (more >often than not, gzip) and of course, make. > >All the above comes from a concrete case. A downloaded the lclint package >mentioned in an earlier post, and I am spending a lot to hacking the stuff >in order to be able to compile w/DJGPP! The problem is that the code will probably run ONLY on DOS/Win95. I still don't have any info on WinNT support for INT25h/INT26h/BIOS calls. Another thing is that using INT25/26h to create directory entries is painfully slow. I have to allocate a special transfer buffer (actually two) in conv memory every time I read/write using these ints. Another solution is to allocate the buffer once at startup, but this is a waste of memory and non-reentrant. So... Mark ********************************************************************** So if you ask me how do I feel inside, I could honestly tell you we've been taken on a very long ride. And if my owners let me have free time some day, with all good intention I would probably run away! Clutching the short straw... ******************* http://ananke.amu.edu.pl/~grendel ****************