Hi Paul,
commands with their arguments are indeed limited in length in DOS. As far as I remember, if you use DJGPP based apps (including for example BASH as shell) then they can exchange longer command line arguments with each other by storing them in environment variables, but I do not think that command.com participates in this method. Also, I am not sure whether /E:32768 is possible. There could be a lower limit for allowed env sizes. Which command.com version and which version of hexdump are you using? As far as I remember, neither MS DOS nor FreeDOS command.com use the CMDLINE mechanism, maybe you mean the shell (terminal) window of Microsoft Windows? Regards, Eric > Can someone please explain the below: > > C:\>hexdump > aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa > aaaaaaaaaaaaaaaaaaaabbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb > > bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbcccccccccccccccccccccccccccccccccccccccccccc > Commandline longer than 125 characters. > Can not set environment variable 'CMDLINE'. > Environment full? > C:\>grep shell config.sys > File CONFIG.SYS: > shell=c:\command.com /p /l:1024 /e:32768 > C:\> > > "hexdump" is just a simple MSDOS program and it doesn't > make any difference which program I try to execute. > > It looks to me like command.com is doing the exact right > thing, trying to set the CMDLINE variable for the long > parameter, but I have no idea why it would fail to set it. _______________________________________________ Freedos-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-user
