Hi, On Mon, Oct 26, 2015 at 7:42 AM, Jerome E. Shidel Jr. <[email protected]> wrote: > > Maybe, but since the screen is limited to 80 character width normally,
What is the maximum anyways? VESA 130x60?? I just use 80x43, plenty good enough for my needs. > 256 leaves lots of room for color changing and stuff. Don’t forget > that DOS limits the command-line to 127 characters. Basically, it > doubles that. Also, there is no reason multiple vecho /n commands > cannot be issued to keep writing on the same line. Just for clarity, although I'm no expert, .... I don't think 127 is exactly the limit (for us). I think FreeCOM inherited the method of putting the cmdline in %CMDLINE% if longer than 127 (up to 255??), similar to how it was done in Win9x (but not XP). I think DJGPP even natively supports such a feature. For example, one of my own .BATs used a really long (DJGPP) "wget.exe http://..."; URL, which was easily over 127 chars long. A quick check shows 132, yet it still works (although calling wget.bat instead would fail). At least, I "think" that's the explanation. IIRC, it's something weird like "cmp byte ptr [PSP:80h], 7Fh ... ja check_env_var". (Or maybe 80h, not sure.) Well, it doesn't majorly matter here, but just saying ... and many tools (e.g. DJGPP) support @blah.rsp response files as well, so it shouldn't be a huge issue. (In fact, most DJGPP tools transparently handle extremely long cmdlines just because it's so common in *nix programs. Also, old snapshots of FPC ppcross8086.exe had problems with smartlinking under HX because of the normal DOS cmdline limit due to Wlink not being DJGPP compiled.) ------------------------------------------------------------------------------ _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
