Bernd Blaauw wrote:

Kenneth J. Davis schreef:

I have updated my daily FreeCom builds so there are now two sets.
The cmdxms* files are same as before, 186+ xms-swap nearly all features.
Added cmd8086* files, 8086+ kernel-swap some features disabled.


Jeremy, can you reduce the number of files which are downloadable?
I guess the non-XMS build is most universal, despite the high memory consumption then.

Well, I don't know what people want, so I have included a variety of options. They are:

cmdxms* refer to the 186+ xms-swap builds
cmd8086* refer to the 8086+ kernel-swap builds

(XX=xms or 8086)
cmdXX.HEAD.zip is the file I expect most people to use, it is English, ready to run and just contains command.com (UPX'd) and the build log.

(YY is language, i.e. dutch, ENGLISH, french, german, italian, pt_br, russian, serbian, spanish, swedish, or yu437) cmdXX.HEAD.YY.zip is a translation pack for indicated language, it contains a precompiled portion COMMAND.BIN, precompiled critical error handler, and the general strings in a form for easy updating/building.

cmdXX.HEAD.NLS.zip includes the COMMAND.BIN portion and prebuilt strings.dat for all the supported languages; just combine the two and you have your translated command.com for use. This is the archive I expect those who do not wish to use the English command.com to use.

freecom.HEAD[.8086].zip is the complete source treee (minus config.mak which is particular to my setup); the difference is in CONFIG.H only.


Some translations are missing, I can not help that, but I will update cvs with any new translations.


Thank you for the implemented features and renewed 8086 compatibility for XMSswap versions.

see my reply to Eric. If you really want an xms-swap 8086 one, I can either change the 8086 build to use it or add yet another variant; but this way the cmd8086* set should be the most compatible and useful for testing. Just let me know, its easy to change now, either way.


*fixstrs.exe is available, but where is critstrs.exe ?

I don't include it, as I do not provide a way to update the critical error handlers outside of a complete FreeCom build.

*readme.cmd might be changed to readme.bat so also opens on Win9x?
 and it contains a typo: COMMMAND instead of COMMAND

see my note to Eric.  Thanks will fix.


you build 3 command.bin files
(8086, 80286+ full featured, 8086-disabled).
Might be an idea to store them in cmd%LANGUAGE%.HEAD.ZIP:
[language dependent] command.bin (+logfile?)
[language dependent] xmsswap.bin (+logfile?)
[language dependent] xms8086.bin (+logfile?)
[language dependent] criters.bin
[language dependent] %language%.err/lng
[independent       ] default.err/lng (has to be english?)
                       yes, used when lacking and determines order
[independent       ] fixstrs.exe/critstrs.exe

Note: I switched it so the cmdxms builds have loadfix & loadhi, and these are disabled in the cmd8086 builds. WARNING: loadfix is completely untested by me! If you can test it, please let me know if it works correctly or not.


old HTMLHELP binary required it somehow.

I think this is everything I said I would do, so let me know if I forgot anything.


Only SYS remains. Is it safe to combine development version of SYS with a stable kernel? I don't think SYS and KERNEL depend on each other very much.

perfectly safe. The only difference combining sys from other kernel is in the sys CONFIG usage, but this hasn't changed between the two branches. SYS is bootsector dependant, but these are embedded within it, so a mismatch there can not happen.


Jeremy


Bernd

Jeremy





-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Freedos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Reply via email to