Paul Edwards

> Isn’t bios.exe a 32-bit PE? Why would you want to load it with dpmild16? It works once you use dpmild32. Not sure why you think bios.exe (there's one famous...

That works! (on both Windows 10 and HX). But where are you getting that syntax from? I don’t see it mentioned when I run “cmd /?” and I don’t see...

Unfortunately when I tried to do something more substantive than “dir”, it didn’t work: C:\DEVEL\pdos\src>dlltwin -S aswin -k --export-all-symbols -D kernel32.dll kernel32.o -l kernel32.a cmdproc is XC:\COMMAND.COMX cmdbuf is Xc:...

Please put this on hold. I found out that the “c:” should be “c:\command.com” and made that change already, but I still get the same problem when running dlltwin, but...

It seems it is documented for Windows after all: If both lpApplicationName and lpCommandLine are non-NULL, .... Because argv[0] is the module name, C programmers generally ***repeat the module name...

It looks like when one Win32 program (pdmake) calls another (pdptest3), via command.com, the HX GetCommandLine() function is picking up the original call to command.com instead of what command.com generated....

I’d like to hear from Japheth first. I think it’s more likely to be an HX problem than a Freecom problem. I showed Freecom doing the right thing too, when...

Note that I committed this change: https://sourceforge.net/p/pdos/gitcode/ci/bdc03feb4b265073caa49f09ab44377ff09732a9/ to kludge around the presumed HX bug. Basically this: + /* kludge for presumed HX bug */ + if (strncmp(p, "C:\\COMMAND.COM /c", 17)...

I have built my own distribution of Freedos, based on the recently released 1.3 RC5, with the fixed command.com, and if you would like to see the problem for yourself,...

> Maybe you can add it in a future release? For the time being, I copied the DLL to the relevant HX directory. Is there something wrong with using the...