Hi Eric,
> On Mar 1, 2026, at 8:03 AM, Eric Auer via Freedos-devel > <[email protected]> wrote: > > > Hi :-) > >> The FreeDOS Interim Test Build T2603 for March is now available for download >> at: >> https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/ > > Ibiblio seems to be a bit slow at the moment? As I mentioned before, anyone can fetch the releases from my server at: https://fd.lod.bz/releases/ But also as I said, I do not want it listed as “Official mirror". > >> Changes since T2602: > > Which (languages) of the translations of project_FD-NLS, > diskcopy, assign, append, and possibly other packages are > made by AI and could use some proof-reading now? First let me say, nearly all of the translation updates over the last couple months have been done using AI and sent to me for inclusion. This particular month that would be everything except the ones from cardpuncher which are done by a human and the translation update by al-hor which was provided to correct some mistakes made by an AI during translation. The others this month are done by AI and sen to me. Generally, you do not need to be concerned with the changes that occur with “project_FD-NLS” that is just where all of the translations for packages are managed. It is also where anyone who want to contribute or make corrections to translations should visit. You can Also, one can go there to review both human and AI translations. It is not difficult to figure out what ones were performed by AI on that site just by browsing the directories for the different program translations. https://github.com/shidel/fd-nls Now, in the Changes Log for the monthly build you will see messages for a program regarding translation updates. This is from when I integrated translations into that package. Those can be reviewed for errors on the Interim build itself. I will try and remember to always use “AI” somewhere in the commit message during that step to make it easier to identify when a package has received new or updated AI translations. > > Actual SOFTWARE updates in this build are: > >> 2026-02-26 09:44:31 fdnpkg16 [unstable] (Shidel): updated to 0.99.8253c > >> 2026-02-26 09:26:58 kernel [unstable] (Shidel): updated COUNTRY.SYS to 2.0 You did not mention Label moving to v1.6. > > As Jeremy said: > > > In order to get some more reviews, please have a look at > > https://www.fdos.org/country/ > > Feedback can be submitted at https://github.com/FDOS/country > >> 2026-02-18 16:12:26 ldebug (Shidel): updated to release 10 > >> 2026-02-16 03:31:22 listpci (Shidel): metadata URL update > >> 2026-02-16 03:14:17 fdnpkg16 [unstable] (Shidel): updated to 0.99.8253b > > The country.sys update reminds me that: > > https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/unstable/html/en/base/kernel/20260226.3/index.html > > Hooray! :-) Small updates for kernel 2044 "2026-02-26.3" (?) > including country.sys, setver.sys (?) and sys.com, the SECOND > monthly build with our new kernel, see Jeremy's 2026-01-25 mail: > > Updated boot/init paths, env handling, filesystem/partition > handling, improved compiling, better FCB compatibility and > (network) redirector code, I/O and file size 4GB boundary > handling, WINDOWS 3.x ENHANCED MODE COMPATIBILITY, truename, > device and memory management handling and much more :-) :-) > > See also: https://github.com/FDOS/kernel/releases/tag/ke2044 > > As this is the second release with the new kernel, I assume > people have been happy with it? Do you know download counts? I believe that Jim mentioned in a previous message that those tools to get information regarding download counts are no longer available since IBIBLIO switched its hosting over to the new machine. (That switch over was also when connection and download speeds starting having issues.) > > However, as described in my 2026-01-23 mail, it is almost > IMPOSSIBLE to 1. find and 2. test the interim builds on real > hardware :-( Jim, can you work on 1.? Thank you :-) > > Jerome, how complex would it be to make the ISOs suitable for > use as USB boot images? Or to build a LiveUSB from the LiveCD? As I mentioned before, there are issues do either of those. And either may or may not be possible. There is Zero chance that I will even look into doing either until I resume working on the RBE4. To me, the RBE3 has reached end of life and will only receive critical bug fixes at this point. I cannot afford to invest time into the RBE3. I do not know when I will be returning to work on the RBE4. The RBE4 is a huge time commitment and other projects of greater immediate importance are taking precedence. Right now, I am working on the final required pieces of a DOS adjacent program for its 1.0 release. While this program does not run under DOS, it is for doing work for DOS. Even not being complete at present, testers have found it saves a lot of time and effort. That’s all I will say about it for now. Hopefully, I will get this one wrapped up soon and back to the next thing on my TODO list called “TheList”. Then there are other things needing done before the RBE4. So, I can kind-of see the RBE4 out there on the horizon. But, it is just a shadowy vague figure at this time. I just hope that not to many more things pop up in between to push my return to that project further away. > > Thank you :-) > > Regards, Eric :-) Jerome _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
