Re: [Freedos-user] LFN Support in DOS4GW Environment
Thanks for your response.
I tried adding the LFN macro however I still only have a short file name
created in the hard disk.
File:
#define __WATCOM_LFN__
#include
void main(void)
{
FILE *fptr = fopen("e:\\aerosystems.txt", "w");
fprintf(fptr, "Genesys\n");
fclose(fptr);
} // END main()
Output:
[image: image.png]
Whether the DOSLFN driver is still visible in the DOS4GW environment?
Could anyone help to create a long file name using a simple C program in
FreeDOS?
Thanks,
Anand
On Tue, Aug 4, 2020 at 10:37 AM TK Chia wrote:
> Hello Anand,
>
> > I wrote a small program in C to create a file with a long file name as
> > follows.
> >
> > void main(void)
> > {
> > FILE *fptr = fopen("e:\\aerosystems.txt", "w");
> >
> > fprintf(fptr, "Genesys\n");
> > fclose(fptr);
> > } // END main()
> >
> > And then I compiled using the Watcom compiler:
>
> It seems the Watcom libraries do not use long file name support by
> default. Perhaps you can try to see if LFNs work if you define a macro
> __WATCOM_LFN__ before including system header files?
>
> #define __WATCOM_LFN__
> #include
> ...
>
> Thank you!
>
> --
> https://github.com/tkchia
>
>
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] LFN Support in DOS4GW Environment
Hello Anand,
I wrote a small program in C to create a file with a long file name as
follows.
void main(void)
{
FILE *fptr = fopen("e:\\aerosystems.txt", "w");
fprintf(fptr, "Genesys\n");
fclose(fptr);
} // END main()
And then I compiled using the Watcom compiler:
It seems the Watcom libraries do not use long file name support by
default. Perhaps you can try to see if LFNs work if you define a macro
__WATCOM_LFN__ before including system header files?
#define __WATCOM_LFN__
#include
...
Thank you!
--
https://github.com/tkchia
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] LFN Support in DOS4GW Environment
Hi All,
I'm using FreeDOS with a DOSLFN driver loaded through autoexec.bat. The
harddisk is formatted with a FAT32 single partition.
I wrote a small program in C to create a file with a long file name as
follows.
void main(void)
{
FILE *fptr = fopen("e:\\aerosystems.txt", "w");
fprintf(fptr, "Genesys\n");
fclose(fptr);
} // END main()
And then I compiled using the Watcom compiler:
@wcc386 main.c -d1 -w4 -e25 -zq -fp5 -fpi87 -5s -bt=dos -mf -we -okl+mnt
-wcd=201
@wlink name TEST d all SYS dos4g op q op st=64k FILE Main.obj
When I execute this program, the file is created as expected however the
filename appears to be a short name instead of a long file name.
Here is my understanding. I have already loaded the DOSLFN at startup.
Therefore, I was expecting the above program to create a file called
"aerosystems.txt" (with a long file name). Instead, I see the file name as
"aerosyst.txt" in the hard disk. I also manually looked at the directory
sector in the hard drive and ensured the program is creating the short file
name only and not long file name.
Could someone please help to understand what is going on here? I looked at
the Q before I posted here. I didn't see any similar questions.
Therefore, request help from the FreeDOS experts.
Thank You!
Thanks,
Anand
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] LFN in FreeDOS kernel? - was: aimed compatibility?
Hi, LFN for FAT and for NTFS are working stable in Linux. Could a FreeDOS developer grab this free knowledge from Linux and improve DOSLFN this way? very unlikely. Linux drivers are too different from DOS kernel or DOS TSR to be useful What about bringing the FUSE interface to DOS? Would it be possible to port libfuse and then write a system driver to support FUSE drivers? FUSE is targeted towards Linux and supports things that DOS does not need and cannot support. You can use the already existing network redirector interface, int 2f, ah=11, al=function number to implement drivers for any network or local non-FAT filesystem. Enjoy :-) Eric -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] LFN in FreeDOS kernel? - was: aimed compatibility?
Hi Michael, indeed, MS LFN started with version 7 (Win9x)... What about FreeDOS kernel and LFN? Wouldn't it make sense also to add LFN to the FreeDOS kernel? Yes but: The DOSLFN license does not allow it so you would have to re-implement LFN from scratch and there is also a risk to get nagging from MS because some LFN things are still patented by Microsoft. For now, the DOSLFN way works very well, although not perfect, for my few LFN needs. it also seems doslfn is not the answer and needs bugchecking by a third developer. Quite possible - ask the doslfn maintainer whether he wants help. For sure, if LFN goes into the FreeDOS kernel it would make much sense to add also LFN support to the FAT driver. Is this already the case? LFN lives at the level of directory entries, it does not care whether they are FAT12, FAT16 or FAT32 directory entries :-) But of course the kernel FAT driver does both, FATs and DIRs. Eric -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] LFN in FreeDOS kernel? - was: aimed compatibility?
Blair Campbell schrieb: Also according to http://www.unet.univie.ac.at/~a0503736/php/drdoswiki/index.php?n=Main.Compatibility it also seams doslfn is not the answer and needs bugchecking by a third developer. Even kernel support would have some of those issues, it seems only not very fast and risk to crosslink files or trash the filesystem (ask A.P.) (I have never experienced this) apply. Overall I would recommend doslfn if you want to use long filenames. Kernel support would be nice, but for the most part I think only speed would improve. Compatibility issues with Windows and such would remain even if lfn support was in the kernel. Yes, by putting it into the kernel the compatibility issues go not away instantly. LFN for FAT and for NTFS are working stable in Linux. Could a FreeDOS developer grab this free knowledge from Linux and improve DOSLFN this way? To stay maximum compatible the LFN code could be disabled in config.sys with LFN=0/1. -mr -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] LFN in FreeDOS kernel? - was: aimed compatibility?
It is strongly recommended that you use MS-DOS version 7.0 (the version of MS-DOS that ships with Windows 95/98), since it is the only version that will allow you to use long filenames with your NTFS drives. Using earlier versions of MS-DOS restrict you to using file names in 8.3 format. Only because NTFSDOS doesn't (didn't) translate NTFS original LFNs (that were stored without SFNs) to accessible SFNs. Refer to how DOSLFN does this for CDFS filenames that are too long, so it is indeed possible. (Might be more difficult with NTFSDOS Professional's R/W access though.) and Many people believe that MS-DOS doesn’t support long file names at all, but that isn’t the case. It is the MS-DOS FAT file system driver that lacks support, rather than MS-DOS itself. If you prefer to refer to the kernel as the MS-DOS FAT file system driver only, that's true. (So that MS-DOS itself here means all other programs.) Else it isn't true, because the kernel doesn't contain any LFN support at all, and it is in fact made up of more than a FAT driver. Regarding this you have to remember the redirector interface, too. When used with a file system that supports long file names MS-DOS handles them fine, The kernel doesn't care. as do MS-DOS applications that are written to take advantage of the support. What they tell you is that NTFSDOS horribly hacks into Int21 to provide the LFN services on it's own. Because the redirector interface (which is else used by NTFSDOS) was never updated to provide LFN services. It must be a horrible hack because the redirector was designed so that the driver (here NTFSDOS) doesn't have to hack into Int21 and provide any direct Int21 services by itself. Author was Mark Russinovich / Bryce Cogswell so I believe the statement was correct. They were supposedly Windows experts, weren't they? What about FreeDOS kernel and LFN? Wouldn't it make sense also to add LFN to the FreeDOS kernel? If someone has enough time for this.. Also according to http://www.unet.univie.ac.at/~a0503736/php/drdoswiki/index.php?n=Main.Compatibility it also seams doslfn is not the answer and needs bugchecking by a third developer. Someone able to do this? For sure, if LFN goes into the FreeDOS kernel it would make much sense to add also LFN support to the FAT driver. Is this already the case? For sure, if LFN services would be added to Int21 only but not the filesystem driver(s) it would be a complete waste of effort. DOS-C's FAT driver is probably LFN-aware (shows correct volume label even with LFNs etc.) but doesn't contain more support. [There's however this LFN helper API but I don't know what it's supposed to do and there's no documentation.] Regards, Christian -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] LFN in FreeDOS kernel? - was: aimed compatibility?
Christian Masloch schrieb: LFN for FAT and for NTFS are working stable in Linux. Could a FreeDOS developer grab this free knowledge from Linux and improve DOSLFN this way? FAT and FAT32 are already supported by DOSLFN, even some CD-ROM filesystems are. NTFS is not supported by any free DOS driver, so you can't extend DOSLFN to support it. I did mean more, the knowledge to get a stable FAT32 LFN read/write support could be extracted from the Linux FAT32 LFN knowledge as theirs is stable since years. While bugfixing the compatibility issues with DOSLFN it could be used as reference. -mr -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] LFN in FreeDOS kernel? - was: aimed compatibility?
LFN for FAT and for NTFS are working stable in Linux. Could a FreeDOS developer grab this free knowledge from Linux and improve DOSLFN this way? very unlikely. Linux drivers are too different from DOS kernel or DOS TSR to be useful Tom -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] LFN in FreeDOS kernel? - was: aimed compatibility?
On Mon, Mar 30, 2009 at 2:00 PM, Tom Ehlert t...@drivesnapshot.de wrote: LFN for FAT and for NTFS are working stable in Linux. Could a FreeDOS developer grab this free knowledge from Linux and improve DOSLFN this way? very unlikely. Linux drivers are too different from DOS kernel or DOS TSR to be useful Tom -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user What about bringing the FUSE interface to DOS? Would it be possible to port libfuse and then write a system driver to support FUSE drivers? -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] LFN in FreeDOS kernel? - was: aimed compatibility?
Christian Masloch schrieb: Which kind of compatibility does FreeDOS aim for? I mean compatible with which MS-DOS version? 6.22, 7.10, 8.00? As far as I can tell, 8.00 is the same as 7.10 plus some restrictions (I used to have a PC with Windows Me). Yes, well 8.00 can load Win ME. http://www.unet.univie.ac.at/~a0503736/php/drdoswiki/index.php?n=Main.MS-DOS 6.22 doesn't include LBA, FAT32 and LFN-aware command line, so FreeDOS mostly aims to be compatible to 7.10. The site where I originally found the following statement is gone, but there is a mirror. http://arcadecontrols.com/Mirrors/mirror/www.sysinternals.com/Utilities/NtfsDosProfessional.html It is strongly recommended that you use MS-DOS version 7.0 (the version of MS-DOS that ships with Windows 95/98), since it is the only version that will allow you to use long filenames with your NTFS drives. Using earlier versions of MS-DOS restrict you to using file names in 8.3 format. and Many people believe that MS-DOS doesn’t support long file names at all, but that isn’t the case. It is the MS-DOS FAT file system driver that lacks support, rather than MS-DOS itself. When used with a file system that supports long file names MS-DOS handles them fine, as do MS-DOS applications that are written to take advantage of the support. Author was Mark Russinovich / Bryce Cogswell so I believe the statement was correct. What about FreeDOS kernel and LFN? Wouldn't it make sense also to add LFN to the FreeDOS kernel? Also according to http://www.unet.univie.ac.at/~a0503736/php/drdoswiki/index.php?n=Main.Compatibility it also seams doslfn is not the answer and needs bugchecking by a third developer. For sure, if LFN goes into the FreeDOS kernel it would make much sense to add also LFN support to the FAT driver. Is this already the case? -mr -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] LFN in FreeDOS kernel? - was: aimed compatibility?
Also according to http://www.unet.univie.ac.at/~a0503736/php/drdoswiki/index.php?n=Main.Compatibility it also seams doslfn is not the answer and needs bugchecking by a third developer. Even kernel support would have some of those issues, it seems only not very fast and risk to crosslink files or trash the filesystem (ask A.P.) (I have never experienced this) apply. Overall I would recommend doslfn if you want to use long filenames. Kernel support would be nice, but for the most part I think only speed would improve. Compatibility issues with Windows and such would remain even if lfn support was in the kernel. -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] LFN
Blair Campbell wrote: extract doslfn.com (or exe) and the .cp? I can't remember the extention but there's a few codepage tables afair that the extension begins with .cp How about cp*.tbl? Those need to go in the bin directory. I assume you mean C:\FDOS\BIN Then lh doslfn should do fine. That gets me: DOSLFN 0.40e ( haft): enabled. Last error: 43 - Was that to be expected? I don't see any change in LFN access. Ray -- SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] LFN
Ray Davison wrote: Boot screen says: DOSLFN 0.40c Kernel is 20 Sept 07 Neither NC or VC 4.05 or DIR display LFNs. Don't know about NC, but only VC 4.99.08 supports LFN. You can also try http://www.ritlabs.com/en/products/dn/index.php?phrase_id=642999 or http://www.dnosp.com/download/e_dnosp.php. (ndn.muxe.com is dead for me currently.) Robert Riebisch -- BTTR Software http://www.bttr-software.de/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] LFN
Robert Riebisch wrote: Ray Davison wrote: Boot screen says: DOSLFN 0.40c Kernel is 20 Sept 07 Neither NC or VC 4.05 or DIR display LFNs. Don't know about NC, but only VC 4.99.08 supports LFN. You can also try http://www.ritlabs.com/en/products/dn/index.php?phrase_id=642999 or No on VC 4.99.08a or DN Ray - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] LFN
try dir /lfn On Thu, Feb 14, 2008 at 7:12 PM, Ray Davison [EMAIL PROTECTED] wrote: Boot screen says: DOSLFN 0.40c Kernel is 20 Sept 07 Neither NC or VC 4.05 or DIR display LFNs. What am I missing? Ray - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- Fall is my favorite season in Los Angeles, watching the birds change color and fall from the trees. David Letterman (1947 - ) See ya - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] LFN support?
On Sat, 7 Feb 2004, Aitor Santamaría Merino wrote: In my understanding, there's no LFN support at all, except in the DIR command of FreeCOM, where an existing LFN is searched and displayed. No. There is no LFN support in FreeCOM. And there will be none, unless available for all commands. Bye, -- Steffen Kaiser --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn ___ Freedos-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] LFN support?
Hi, I do worry LFN is the user's heaven, the programmer's hell. regards, BAHCL --- Aitor_Santamar_Merino [EMAIL PROTECTED] Hi John, John Price escribi#65533;: I've seen some mention of LFN support in FreeDOS. I wonder exactly how much support we are talking about... Is it supported in the kernel, or just command.com? In my understanding, there's no LFN support at all, except in the DIR command of FreeCOM, where an existing LFN is searched and displayed. Can I boot a machine with a kernel that has LFN support and command.com that supports LFN and then use long filenames on that system or is it more complex than that? You would have to look for third party support. For a while I used DOSLFN and seemed to work ok... I assume that if this is all true that I will have to use different DOS calls for findfirst/next as well as other file handling functions or will they all be happy to take my long filenames without problems? Yes, see functions AH=71h of 21h. Aitor --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn ___ Freedos-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-user _ ... http://us.rd.yahoo.com/evt=22281/*http://ringtone.yahoo.com.hk/ --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn ___ Freedos-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-user
