The FreeDOS 1.4-RC3, release candidate build (aka T2503) is now available at:

https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/

I will not be updating the FreeDOS 1.4 “download/update repositories” with the 
updated versions of the packages that are available in RC3. 

Updating those files in the various repositories is a very cumbersome, tedious 
and time consuming process.  

I will update those packages immediately before the 1.4 Final release.

Changes since 1.4-RC2:

2025-03-01 09:50:52 doszip (Shidel): added extra copy of DOSZIP.TXT to BIN dir 
so menu item to view file will work
2025-03-01 09:43:53 project_FD-NLS (Shidel): from W.Spiegl
2025-03-01 03:57:29 project_FDI [candidate] (Shidel): Release Candidate 3
2025-02-28 20:41:46 7zip (Shidel): Merge branch 'master' into 'master'
2025-02-28 13:43:19 7zip (Darik Horn): Retro7zip 24.09+5 release
2025-02-25 12:07:39 perl (Shidel): Merge branch 'master' into 'master'
2025-02-25 07:03:04 zerofill (Shidel): updated to v2.05
2025-02-21 15:51:07 freecom [candidate] (Bernd Boeckmann): fix INDEX.md
2025-02-21 15:35:31 freecom [candidate] (Bernd Boeckmann): fix MZ headers and 
icon file
2025-02-17 02:33:51 project_FDI [candidate] (Shidel): Exclude FDTUI package 
from install media
2025-02-05 15:00:47 perl (David VANTYGHEM): Remplacer PERL.TR
2025-02-05 15:00:29 perl (David VANTYGHEM): Remplacer PERL.SV
2025-02-05 15:00:14 perl (David VANTYGHEM): Remplacer PERL.LSM
2025-02-05 14:59:55 perl (David VANTYGHEM): Remplacer PERL.FR
2025-02-02 18:08:30 7zip (Shidel): Merge branch 'master' into 'master'
2025-02-02 11:03:10 7zip (Darik Horn): Retro7zip 24.09+4 release

I also removed MINIBOX from the BonusCD (part of the RC3 commit).

I also ran a script to verify any NLS updates at FD-NLS have been incorporated 
into the packages. (Those messages are filtered out).

I do not think the “out of memory” issue on VMware has had a resolution 
provided. I do not have a recent version of that Emulator available for 
testing. I think the simplest solution would be for someone who has it to 
create a CONFIG.VMW file for inclusion in FDI. Then the installers can simply 
install a custom under VMware. This is not really any different than the custom 
config that is used under VirtualBox. [1] Just note, that if the number of 
options in the boot menu are reduced, a custom AUTOEXEC.VMW may be required.

:-)

Jerome

[1] https://github.com/shidel/FDI/blob/master/FDISETUP/SETUP/CONFIG.VBX

_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Reply via email to