Re: [Freedos-devel] lfn in freecom?
- Oorspronkelijk bericht - Van: Eric Auer [mailto:[EMAIL PROTECTED] Verzonden: maandag, september 17, 2007 09:03 PM Aan: freedos-devel@lists.sourceforge.net Onderwerp: Re: [Freedos-devel] lfn in freecom? Hi Imre, Does anybody know what the status is of long file name support in freecom. There is absolutely a compile time option you can use, but does it work (well)? FreeCOM 0.84 arguably has far too many changes with far too little review (compared to 0.82pl3) but those changes do mean that it has LFN support all over the place and this LFN support is also compiled into the default binary used in FreeDOS 1.0 :-). If you want to do some testing: Try if both doslfn and shsucdxes cdrom-lfn work okay, and try if FreeCOM works okay in situations where some drives have LFN and others have not. For example in dosemu, you can enable LFN for the virtual / redirect / Linux directory based drives, without loading doslfn for the FAT / diskimage drives, or vice versa :-). Everybody else is invited to test, too. I think you can SET LFN=N (or Y) to dynamically block and re-enable the built-in LFN support of FreeCOM 0.84 ... Well if it is in freecom 0.84 pre 2 then it realy does seem to do something, when setting LFN=Y. Which is consistent with djgpp compiled binaries. But if I do md 1234567890, I get a directory that is called 123456~1 when I do dir. So it isn't quite working for the dir command. This is something I might be looking into next then. I wanted to have LFN support for an idea that I had. Also it might no be so difficult to get: attrib find move more replace xcopy sort tree to have lfn support through the io95 library. With: diskcopy chkdsk defrag recover already supporting lfn's most of FreeDOS should then have full lfn support. But then there are quite some commands written in assembly so I would not like to change those. Something which definitely does need testing: Sometimes FreeCOM 0.84 just stops running external commands (opening com / exe / ...) while internal commands like DIR keep working. Nobody has yet found a way to force this bug to trigger, but when it happens, the only way to get out of the situation is to reboot, so we should really fix it. I have been working with 0.84 pre 2 for well over a year now, and I have not found a problem with external commands not being executed. Imre Eric - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] lfn in freecom?
Use dir /lfn to get long filename directory listings. Also, dir.c should use lfn findfirst so that dir 123456789 will work. On 9/18/07, Imre Leber [EMAIL PROTECTED] wrote: - Oorspronkelijk bericht - Van: Eric Auer [mailto:[EMAIL PROTECTED] Verzonden: maandag, september 17, 2007 09:03 PM Aan: freedos-devel@lists.sourceforge.net Onderwerp: Re: [Freedos-devel] lfn in freecom? Hi Imre, Does anybody know what the status is of long file name support in freecom. There is absolutely a compile time option you can use, but does it work (well)? FreeCOM 0.84 arguably has far too many changes with far too little review (compared to 0.82pl3) but those changes do mean that it has LFN support all over the place and this LFN support is also compiled into the default binary used in FreeDOS 1.0 :-). If you want to do some testing: Try if both doslfn and shsucdxes cdrom-lfn work okay, and try if FreeCOM works okay in situations where some drives have LFN and others have not. For example in dosemu, you can enable LFN for the virtual / redirect / Linux directory based drives, without loading doslfn for the FAT / diskimage drives, or vice versa :-). Everybody else is invited to test, too. I think you can SET LFN=N (or Y) to dynamically block and re-enable the built-in LFN support of FreeCOM 0.84 ... Well if it is in freecom 0.84 pre 2 then it realy does seem to do something, when setting LFN=Y. Which is consistent with djgpp compiled binaries. But if I do md 1234567890, I get a directory that is called 123456~1 when I do dir. So it isn't quite working for the dir command. This is something I might be looking into next then. I wanted to have LFN support for an idea that I had. Also it might no be so difficult to get: attrib find move more replace xcopy sort tree to have lfn support through the io95 library. With: diskcopy chkdsk defrag recover already supporting lfn's most of FreeDOS should then have full lfn support. But then there are quite some commands written in assembly so I would not like to change those. Something which definitely does need testing: Sometimes FreeCOM 0.84 just stops running external commands (opening com / exe / ...) while internal commands like DIR keep working. Nobody has yet found a way to force this bug to trigger, but when it happens, the only way to get out of the situation is to reboot, so we should really fix it. I have been working with 0.84 pre 2 for well over a year now, and I have not found a problem with external commands not being executed. Imre Eric - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel -- 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 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] lfn in freecom?
On 9/18/07, Imre Leber [EMAIL PROTECTED] wrote: - Oorspronkelijk bericht - Van: Eric Auer [mailto:[EMAIL PROTECTED] Verzonden: maandag, september 17, 2007 09:03 PM Aan: freedos-devel@lists.sourceforge.net Onderwerp: Re: [Freedos-devel] lfn in freecom? Hi Imre, Does anybody know what the status is of long file name support in freecom. There is absolutely a compile time option you can use, but does it work (well)? FreeCOM 0.84 arguably has far too many changes with far too little review (compared to 0.82pl3) but those changes do mean that it has LFN support all over the place and this LFN support is also compiled into the default binary used in FreeDOS 1.0 :-). If you want to do some testing: Try if both doslfn and shsucdxes cdrom-lfn work okay, and try if FreeCOM works okay in situations where some drives have LFN and others have not. For example in dosemu, you can enable LFN for the virtual / redirect / Linux directory based drives, without loading doslfn for the FAT / diskimage drives, or vice versa :-). Everybody else is invited to test, too. I think you can SET LFN=N (or Y) to dynamically block and re-enable the built-in LFN support of FreeCOM 0.84 ... Well if it is in freecom 0.84 pre 2 then it realy does seem to do something, when setting LFN=Y. Which is consistent with djgpp compiled binaries. But if I do md 1234567890, I get a directory that is called 123456~1 when I do dir. So it isn't quite working for the dir command. This is something I might be looking into next then. I wanted to have LFN support for an idea that I had. Also it might no be so difficult to get: attrib find move more replace xcopy sort tree to have lfn support through the io95 library. With: diskcopy chkdsk defrag recover already supporting lfn's most of FreeDOS should then have full lfn support. But then there are quite some commands written in assembly so I would not like to change those. Something which definitely does need testing: Sometimes FreeCOM 0.84 just stops running external commands (opening com / exe / ...) while internal commands like DIR keep working. Nobody has yet found a way to force this bug to trigger, but when it happens, the only way to get out of the situation is to reboot, so we should really fix it. I have been working with 0.84 pre 2 for well over a year now, and I have not found a problem with external commands not being executed. I have encountered it once or twice but it is more or less as difficult to get as the context out of memory error (also in previous versions). Perhaps they are both caused by a memory leak somewhere? Imre Eric - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel -- 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 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel