Re: [Freedos-devel] lfn in freecom?
>- Oorspronkelijk bericht -
>Van: John Elliott [mailto:[EMAIL PROTECTED]
>Verzonden: dinsdag, oktober 2, 2007 08:30 PM
>Aan: freedos-devel@lists.sourceforge.net
>Onderwerp: Re: [Freedos-devel] lfn in freecom?
>
>>
>> Ok, thanks, that's good news. I'm used to such feature in UNIX, and
>> mistrusted it would ever be possible in DOS.
>
> For argv/argc parsing, it depends exactly how the author of your compiler
>implemented it. For example, Pacific C doesn't do anything special with
>quoted strings. This program:
>
>#include
>
>int main(int argc, char **argv)
>{
> int n;
> for (n = 0; n < argc; n++)
> {
> printf("%d. %s\n", n, argv[n]);
> }
> return 0;
>}
>
>when compiled with Pacific and run with a quoted string, splits it up into
>two:
>
>C>echoargs "file name"
>0.
>1. "file
>2. name"
>
>whereas when compiled with DJGPP, it does understand quoted strings:
>
>C>echoargs "file name"
>0. c:/echoargs.exe
>1. file name
>
It works for turbo c too (does the same as djgpp).
Imre
>
>-
>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?
>
> Ok, thanks, that's good news. I'm used to such feature in UNIX, and
> mistrusted it would ever be possible in DOS.
For argv/argc parsing, it depends exactly how the author of your compiler
implemented it. For example, Pacific C doesn't do anything special with
quoted strings. This program:
#include
int main(int argc, char **argv)
{
int n;
for (n = 0; n < argc; n++)
{
printf("%d. %s\n", n, argv[n]);
}
return 0;
}
when compiled with Pacific and run with a quoted string, splits it up into
two:
C>echoargs "file name"
0.
1. "file
2. name"
whereas when compiled with DJGPP, it does understand quoted strings:
C>echoargs "file name"
0. c:/echoargs.exe
1. file name
-
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?
Ok, thanks, that's good news. I'm used to such feature in UNIX, and mistrusted it would ever be possible in DOS. Aitor 2007/10/1, Tom Ehlert <[EMAIL PROTECTED]>: > > Second is the ability of the internal commands to handle the "" properly. > > Like: > > > copy "my file.txt" a: > > > Do you mean that both have been impleneted? Is there something like a > > "standard" C library for "-parsing in commandline that we all can > > enjoy? > > the standard C library supports this (since ~1970) for argc/argv > scanning. > Of course command has to do this internally, but there should be > source available for this > > Tom > > > > > - > 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?
> Second is the ability of the internal commands to handle the "" properly. > Like: > copy "my file.txt" a: > Do you mean that both have been impleneted? Is there something like a > "standard" C library for "-parsing in commandline that we all can > enjoy? the standard C library supports this (since ~1970) for argc/argv scanning. Of course command has to do this internally, but there should be source available for this Tom - 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?
Hello Eric, 2007/9/17, Eric Auer <[EMAIL PROTECTED]>: > > 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 :-). There are two different things that I understand under the LFN. First is the ability to use the LFN API to manipulate files by the internal commands. EG: copy mylongfilenamewithoutspaces.txt a: Second is the ability of the internal commands to handle the "" properly. Like: copy "my file.txt" a: Do you mean that both have been impleneted? Is there something like a "standard" C library for "-parsing in commandline that we all can enjoy? Thanks, Aitor PS: Probably many more people would like to hear about this, in case you're thinking of writing in private. - 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?
AFAIK, this was added long before I touched the FreeCOM source, but yes it should be in the help. Unfortunately, I have no way to access CVS right now On 9/20/07, Imre Leber <[EMAIL PROTECTED]> wrote: > > >- Oorspronkelijk bericht - > >Van: Blair Campbell [mailto:[EMAIL PROTECTED] > >Verzonden: dinsdag, september 18, 2007 11:18 PM > >Aan: freedos-devel@lists.sourceforge.net > >Onderwerp: 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. > > > > That's an undocumented feature then, because the option is not listed under > dir /? help screen. > > Imre > > > > > - > 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?
>- Oorspronkelijk bericht - >Van: Blair Campbell [mailto:[EMAIL PROTECTED] >Verzonden: dinsdag, september 18, 2007 11:18 PM >Aan: freedos-devel@lists.sourceforge.net >Onderwerp: 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. > That's an undocumented feature then, because the option is not listed under dir /? help screen. Imre - 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?
>> 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? >> What I have found was very reproducable was the fact that if you have for example a directory called edit, and you do "edit file.txt" where you have the directory edit it will say: "Bad command or filename - "edit"" This might or might not be what people reported. "edit.exe file.txt" does work then however. Context out of memory is actually quite common. Imre >> 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 > > - 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
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?
>- 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?
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 ... 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. 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
