Hi, You're both right, of course, but I think I know of an easy solution (even though I haven't looked closely at any of this yet, but they do indeed appear to be .COMs).
"Ark v1.101 - COM archiver and EXE 2 COM converter" (45822 bytes) ftp://ftp.sac.sk/pub/sac/pack/ark101.zip On Tue, Sep 1, 2015 at 12:40 PM, Jerome E. Shidel Jr. <jer...@shidel.net> wrote: > > I know what you mean, but it is worse than you think. The command line > parsing routines > eat up nearly 1000 bytes in each tool. Some of the tools would only be 100 > bytes or so without > needing to interpret the command line. However, there are several reasons > that it is being made this way. > > 1) Jim asked for individual tools that be used in place of the normal things > like choice, echo and etc. > 2) Keep what you need and delete the rest. If all you ever want to use is > vecho, you can delete everything else. > 3) Easier to grasp, instead of one do-it all utility. > > That all being said, I think at some point I may add a v8power.com that does > do it all. > >> On Sep 1, 2015, at 11:32 AM, Mateusz Viste <mate...@viste.fr> wrote: >> >> Might be a dumb question - but why creating so many micro tools? Would >> it be possible to have all of them inside one binary, with behavior >> adapted with a switch? (a la busybox - like "V8POWER VCURSOR HIDE") ? >> >> It would certainly make the toolbox much more space-efficient on big >> (fat) clusters :) >> >> If I see right, the effective space of the toolbox would be around ~100 >> KiB now on 4K clusters. Having them all in a busybox-like package would >> probably take one tenth of that. ------------------------------------------------------------------------------ _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
