Hi Eric.
Thanks for your reply.
"hexdump" is my own program and does not have
a version. But it's the same with any program -
command.com complains before executing the
program.
The environment used to be set to the default, I
wasn't using the "shell" command. But I switched
to the max when I got the error. As you can see
from the below screenshot, that is the max.
I believe that command.com can get involved in
the CMDLINE environment variable, just like any
other program can. And if it can't, it should say
so, rather than reporting a failed attempt to set it.
Version is below also.
Also, I will be using HX as the DOS extender once I
get command.com working. The way I use it, I am
still dependent on command.com.
Thanks. Paul.
C:\DEVEL\PDOS\SRC>ver
FreeCom version 0.84-pre2 XMS_Swap [Aug 28 2006 00:29:00]
C:\DEVEL\PDOS\SRC>command /?
Starts a new copy of the FreeDOS command shell.
COMMAND [[drive:]path] [device] [/E:nnnnn] [/L:nnnn] [/U:nnn] [/P] [/MSG]
[/LOW] [/Y [/[C|K] command]]
[drive:]path Specifies the directory containing COMMAND.COM.
device Specifies the device to use for command input and output.
/E:nnnnn Sets the initial environment size to nnnnn bytes.
(nnnnn should be between 256 and 32,768).
-----Original Message-----
From: Eric Auer
Sent: Sunday, May 30, 2021 6:31 PM
To: [email protected]
Subject: Re: [Freedos-user] CMDLINE
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
_______________________________________________
Freedos-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-user
