Hi,
[EMAIL PROTECTED] escribió:
What does /M do? I think SHSUCDX is quite sufficient for FD 1.0
Put by me, copied from MSCDEX: I suppose MSCDEX does some disk catching,
if this is already configurable in LBACACHE for CD-ROMs, then I could
just edit the list, make a note that it should be configured in
LBACACHE, and mark SHSUCDX as ready (provided it has no pending bugs in
bugzilla).
So Eric will confirm if /M is already implemented, and if it doesn't
perhaps it's not too important and could be moved to the post-list.
cannot test this myself, even though I want to. About LFNs: Some
think that LFN support should be mandatory in all FreeDOS programs for
a 1.0 release. I personally do not feel that way, but how hard would
For a 1.0 release I think the only LFN requirement would be that
they do not interfere with each other. eg DIR/TREE/etc should not
show junk values because of LFN entries (which I believe is already
true for all utilities) and the program should not trash LFN entries,
ie a degrag/chkdsk/etc shouldn't destroy them or unlink LFN entries
from the corresponding SFN entry.
Correct, I entirely agree.
LFN support is great for semi to modern computers (386+), but
for old or embedded type where filesize is still an issue, this
support may bloat the binary unnecessary (no LFN API TSR ever used)
and/or cause unneeded memory usage (leading to out of memory
errors). Thus LFN support should not be mandatory, in fact we
may want to offer support for it as a second binary (eg tree v3.x
is intended for older systems or spaced limited ones, whereas
pdtree (tree v4.x) supports LFNs (and additional items on NT systems
such as indicating SPARSE files or displaying alternate streams).
I agree entirely too.
(Well, personally I would not be happy with LFN being mandatory, it'd
force me to entirely write LFN for Pascal, or see how FPC's LFN can be
compiled for TP, as the KEYB non-resident code is, for the moment,
written in Pascal, the only inheritance remaining from the xkeyb days).
support? Should the number of programs which use kitten become
expanded (which isn't really all that hard)? What about NLS support
in programs coded in assembler? Should there be a version of kitten
NLS support would be nice, but I leave the decision to add it to
the various utility maintainers. The hard part is getting the actual
translated content, and NLS support with no translations seems pointless.
Correct. I just want to emphasize here that the NLS settings (date/time,
numeric, etc) is mandatory, whereas translations isn't.
At some point I'd like to create some info page to collect available
translations/file to be translated.
Aitor
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Freedos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-devel
