On 6/15/2026 6:31 PM, Ralf Quint via Freedos-user wrote:
On 6/15/2026 11:24 AM, Thomas Desi via Freedos-user wrote:
My use scenario seems stupid, I know:

C:\echo This is my text and I keep on notating quick ideas, inital textfiles anything I would quickly jotting down. As I have a macro pad that has ONE single key which puts in the commandline  ''echo ‚‘ >> filename.txt



This is the absolutely fastet way for me to create a meaningful textfile. Faster than what I used till now:

C:\copy con filename.txt (return)
blablablabla text lore ipsum
[CTL Z]

But both are restricted obviously to that 128 character limit.
echo >> is a great method for me.

That’s why I am thinking why the hack 127 when we have so much storage and ram today?

( I am on FreeDOS bare metal )
T

Why does the size of the command line matter when you're doing a redirect of output?

It redirects the input to a file using standard redirection, it would be just like reading a file from a com port, which used to be done all the time in the early dos days, and files considerably larger than 127 bytes were certainly transferable using that method, so redirecting the keyboard to a file (which is what you're doing when using the copy con) should perform the same redirect, and the size of the command line should have no bearing on the size of the file.

perhaps buffers and/or memory sizes may impact the size of the file, but I have no idea why the command line would make any difference.




_______________________________________________
Freedos-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-user

Reply via email to