Re: [Freedos-user] Command Line Parsing
Jack Jackson wrote: I've noticed a difference in command line parsing between FreeDOS and PC-DOS. Both FreeDOS and PC-DOS put the command line, starting with the character after the executable, in a buffer at offset 0x80 in the PSP. The behavior difference I see with FreeDOS is if the first non-blank character after the executable is a left parenthesis, then FreeDOS sets 0x80 in the PSP to zero so the rest of the command line is not available. Examples of what is in PSP 0x80: Command Line: SOMEPROG (aa bb cc FreeDOS: \0 DOS: (aa bb cc\0 Command Line: SOMEPROG abc (cc dd ee FreeDOS and DOS: abc (cc dd ee\0 Does anyone know why FreeDOS behaves differently when the first character after the executable is a left parenthesis? Hi Jack, I not know how to determine the value PSP 0x80, but when I try this simple program (compiled/linked with OpenWatcom): #include stdio.h #include stdlib.h void main(int argc, char const *argv[]){ int ii; for(ii=0; iiargc; ii++){ printf(argv[%d] = %s\r\n, ii, argv[ii]); } } then parameters seems be fine: E:\pokusydosparm argv[0] = E:\POKUSY\DOSPARM.COM E:\pokusydosparm p1 (p2 argv[0] = E:\POKUSY\DOSPARM.COM argv[1] = p1 argv[2] = (p2 E:\pokusydosparm (p1 (p2 argv[0] = E:\POKUSY\DOSPARM.COM argv[1] = (p1 argv[2] = (p2 It is tested with FreeDOS 1.1 under DOSEMU, probably no reason why it would be different in pure FreeDOS. Franta Hanzlik -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] Command Line Parsing
I've noticed a difference in command line parsing between FreeDOS and PC-DOS. Both FreeDOS and PC-DOS put the command line, starting with the character after the executable, in a buffer at offset 0x80 in the PSP. The behavior difference I see with FreeDOS is if the first non-blank character after the executable is a left parenthesis, then FreeDOS sets 0x80 in the PSP to zero so the rest of the command line is not available. Examples of what is in PSP 0x80: Command Line: SOMEPROG (aa bb cc FreeDOS: \0 DOS: (aa bb cc\0 Command Line: SOMEPROG abc (cc dd ee FreeDOS and DOS: abc (cc dd ee\0 Does anyone know why FreeDOS behaves differently when the first character after the executable is a left parenthesis? -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Command Line Parsing
Hi, On Thu, May 15, 2014 at 2:57 PM, Jack Jackson j...@pebbleridge.com wrote: I've noticed a difference in command line parsing between FreeDOS and PC-DOS. The behavior difference I see with FreeDOS is if the first non-blank character after the executable is a left parenthesis, then FreeDOS sets 0x80 in the PSP to zero so the rest of the command line is not available. Does anyone know why FreeDOS behaves differently when the first character after the executable is a left parenthesis? No idea, that's very weird. Please try both 0.82 and 0.84 to confirm this bug exists in both. (I assume 4DOS doesn't have this problem.) Feel free to make an official bug report on SourceForge: http://sourceforge.net/p/freedos/bugs/ -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user