[EMAIL PROTECTED] schreef:
I don't recall off hand what is new with the kernel, for stable only bugfixes I
think, and for dev I can't say off hand. The cvs logs (or cvs mailing list
archives) are the best place to look, but the history file within the kernel
source docs should give a good indication of the changes. Most recently I've
been playing with sys, so I can easily make an alternate DOS kernel boot,
allowing me to more easily test various programs and how the FreeDOS kernel
compares (working or not, not speed).
As for FreeCom, again I don't recall offhand, but if you look in the readme
I've included there is a detailed all the changes and which files the fix or
enhancement was for; also included is a diff file. As best I can recall, there
is a bug fix for errorlevel when loading high, a few language file
updates/compile fixes, support for dir showing 4DOS descriptions, added support
to SET so it will set a user response to uppercase and I think I added the code
so you can do an IF ignoring case, a couple other bugfixes, and some build
fixes (valid mini-suppl library based on an prerelease version I had access to
and implemention for a missing but referenced file). The size difference, I
believe is due to compression, I'd have to check to be sure, but I do not
believe the FreeCom builds on my site are compressed, whereas the released one
is. To check for yourself just run upx --8086 --best command.com and if it
does not give already compressed error, then the size should be com
parable. Not a change I did, but cvs FreeCom (at least I don't think the release has them, but maybe it does) can display LFNs with dir if the LFN api is available; I think the switch to dir /lfn. And for seeing error codes, it supports the /z option, I believe command.com /z. Check the docs for them though, I could be mistaken on the proper switch.
Please note that I don't maintain FreeCom, I just maintain a small patch set that my builds use until they are committed to cvs by a FreeCom maintainer.
Send me another note this weekend (Fri/Sat) and when I am back at my computer and give a better answer if needed. And if I get to it, I will see about updating my FreeCom builds to include loadfix and one that has less features but works with an 8086+. (Almost forget, my FreeCom builds are compiled with 186+ due to size increases mostly unrelated to any changes I made, just the set of features I wanted enabled).
Jeremy
Jeremy, I can read your email correctly but responding to it creates 4
long sentences (paragraphs) divided by 3 ">" each.
This is Mozilla Thunderbird v1.0.x win32.
Most notable difference between stable development kernel and the
unstable/experimental development kernel would be (for an end-user)
support for NLS codepages. (COUNTRY=xx,yy ; DISPLAY ; MODE)
FreeCOM is now available in a few more languages, but I'm absolutely not
sure if the binary can be created without any errors, as build procedure
is kind of obscure, and many language files are outdated or result in
errors.
SYS program has been made more flexible to work with anything based on
MS-DOS. It's not perfect yet, but getting close. One fine example is
that SYS can now create a bootsector for the windows98 kernel files.
It even works with WindowsME. However, currently limited to diskettes only.
I too have been working a bit on FreeDOS again, based on the need for a
new FreeDOS cdrom as there have been many updated components now with
added possibilities (kernel, emm386, udma, shsucdx), and a few new
programs, of which mainly the ramdisk and diskette image mounting
programs worked on by Jason Hood are interesting.
Installation process for the bootable cdrom has hardly changes, but for
next FreeDOS distribution I have a few goals:
*provide translated interface for batchfile messages/menus (done)
*accelerate bootdisk by using ramdrives
*store only a minimum of temporary files on the installed distribution.
again, a ramdisk might be usefull.
*integrate user-provided drivers in the freedos distribution, for
example cdrom drivers or USB drivers (not yet possible to implement).
*allow uninstallation of FreeDOS (not yet possible to implement)
*create a diskette that can boot both FreeDOS and MSDOS (done)
*use build scripts to create ODIN, FreeDOS installation diskette and the
FreeDOS cdrom (slowly being worked on)
Implementing these features still requires a few changes to several
components. Examples are getting a fat16 and fat32 bootsector working
for MSDOS (to allow restoring bootsector for Win98 when FreeDOS is
uninstalled), and allow CDD to accept filenames (and switch to directory
in which this file is located).
CDD A:\KERNEL.SYS for example would switch to A:\ then.
ofcourse packages will be updated also, but people will have to remind
me what to update, as I somehow always forget things like improved HELP
html-files and such.
Bernd
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
