Windows command size
Windows command size
Does cmd.exe has a command size limit?
( I can't execute a command with more than 123 bytes )
( I can't execute a command with more than 123 bytes )
Re: Windows command size
Hi,
Stop using DOS...![Wink ;)](./images/smilies/icon_wink.gif)
Cheers,
Brendan
DOS executables expect to find a 256 byte data structure called the PSP before their code, which is constructed by the OS. The command line arguments are stored in this structure as an ASCII string, and the ASCII string is limited to 125 bytes or something.artrecks wrote:Does cmd.exe has a command size limit?
( I can't execute a command with more than 123 bytes )
Stop using DOS...
![Wink ;)](./images/smilies/icon_wink.gif)
Cheers,
Brendan
For all things; perfection is, and will always remain, impossible to achieve in practice. However; by striving for perfection we create things that are as perfect as practically possible. Let the pursuit of perfection be our guide.
Switch to cygwin , and make the cross compiler as per the instructions specified in the wiki page, I started with DJGPP but it gave me a lot of grief, so better switch to cygwin . Actually , if you are using a floppy image , then it might be better to switch to linux, you can use mtools to put your kernel image there, mtools is not available for cygwin i think
By default, gcc in cygwin produces pe-i386 object files, and ld produces pei-i386 executables, PE being the file format used in modern Windows. If you want to target ELF, I suggest you look into building a GCC Cross-Compiler.artrecks wrote:I got some problems using Cygwin, I want to know what is the default file format for GCC in Cygwin, since files get bigger than using DJGPPs GCC compiler. =//
Any increase in size you see could be due to any number of reasons, e.g. more complex library functions, more debugging information, different alignment of sections etc.
Regards,
John.