Hi Jeremy.
I just realized that the bug fix you have already committed
is enough to unblock what I am doing.
All I need to do is run “pdmake –n” to produce a batch file,
and then I don’t need command.com to accept a long
parameter. It would certainly be nice if it did, but it is not
necessary.
I wa
Resending – I think it didn’t get through ...
Hi Jeremy.
I just realized that the bug fix you have already committed
is enough to unblock what I am doing.
All I need to do is run “pdmake –n” to produce a batch file,
and then I don’t need command.com to accept a long
parameter. It would certainly b
> Hi Jeremy, while you are at it:
>
> Wondering how Jerome could test whether the current shell
> is FreeCOM without needing temp files, ... FWIW, at one time I was trying to
> figure out a way to automatically determine whether my executable program was
> being called from the commend line (any
FWIW, in my programs (written in ASM) what I do while parsing the command line
is look at the length stored at PSP:80h. If it is less than 126, I use the
data stored at PSP:81h up to the first 0Dh (Carriage Return) character. If the
length is 126 or more, I look for the CMDLINE environment var
Hi Jeremy, while you are at it:
Wondering how Jerome could test whether the current shell
is FreeCOM without needing temp files, I found out that
half of the SET options are not yet listed in SET /? help.
The currently available actual options of SET would be:
SET test=one results in TEST=one
S
> Yes, I had hoped to get a release out already but ran
> into build issues getting all compilers to build which
> was just fixed*. I will look into the cmdline issue,
> already filled a bug for it. Then post the release.
Hi Jeremy. Thanks for filing the bug report. Could you
please hold off doi
Yes, I had hoped to get a release out already but ran into build issues
getting all compilers to build which was just fixed*. I will look into the
cmdline issue, already filled a bug for it. Then post the release.
* More improvements are needed, but that's a different issue.
Jeremy
___
IMO it's a bug in FD command.com. If a command
line exceeds 126 bytes, the value at [PSP:80h]
"should" be 0x7Fh ( and a 0x0D "should" be placed
at [PSP:FFh] ) - that's at least what COMMAND.COM
of Win95/98 does. The environment variable
CMDLINE will then contain the full command line.
It's documen
Hi Paul,
> When I run a long command, e.g.
>
> pdptest ... (to exceed 126
> characters), and it is a Win32 executable so HX
> gets involved, I get a crash.
You write that Japheth writes:
> IMO it's a bug in FD command.com. If a command
> line exceeds 126 bytes, the value at [
Hello.
When I run a long command, e.g.
pdptest ... (to exceed 126
characters), and it is a Win32 executable so HX
gets involved, I get a crash.
Japheth has debugged it and reported his
findings.
Could someone please confirm that his analysis
below is correct and it is a Freeco
10 matches
Mail list logo
