On 07/04/2025 18:50, Jerome Shidel via Freedos-devel wrote:
The primary installer used on the CD-ROMs and USB images requires a 386 or
better processor. It was originally the only installer for FreeDOS 1.2. It is
simply called FDI (for the FreeDOS Installer). There was no floppy disk version
to install FreeDOS at the time.
Later, I then created a floppy disk based version for us to include as a part
of the OS release. It uses a different installer than FDI. The installer used
for the Floppy Edition is completely different. It also supports all x86 based
processors and that is where it gets its name… FreeDOS Installer for all x86
based computers (with a legacy BIOS).
OK, I get it. I feel that you are missing my point though: saying:
"This version is for x86" (which is correct)
_Implies_
"The other versions are not for x86"
Which implies "they are for things that are not x86."
Do you see what I mean
This is an issue with VirtualBox not the LiveCD or FreeDOS.
Yes, I know.
The LiveCD still boots to a prompt and is usable.
Yes, I know.
However with 32Mb, not all of the Live Packages can be loaded into a RAM disk.
Those packages are still Live on the CD itself. This means that the CD must
remain mounted. Otherwise, trying to use a program that is on the CD (and not
on the RAM disk) will result in DOS errors messages.
Yes, I know that, too. I tried it.
The last time I checked, the minimum amount of RAM to expand all of the
packages that are live by default is 48Mb. Then, the OS will switch over
completely to the RAM disk and the CD can be removed without any worries.
OK, thanks, that is the info I wanted.
I personally recommend having 128mb or more. That permits the LiveCD to
completely switch over to the RAM disk. Plus, it leaves a lot of extra room to
use FDIMPLES to install other packages into the RAM drive. The User can also
insert and use other CD-ROMs.
OK, also noted. Thanks.
There is a change.log file included with the release. Most of that file is
created based on commit messages to the various projects in the FreeDOS Archive
at GitLab and not from a developers website or VCS. That means most of the
messages will be something like “upgraded to v2.3.4” and not contain details.
You will need to visit the developer’s site to view the changes they made for
the new version.
I found that since last night, yes. But as you say, it's not very
informative.
Projects like, FDI, FDI-x86, FD-NLS, FDISK and a few others are either
maintained in the FreeDOS Archive or directly mirrored there. Those projects
have much more detailed commit messages which are included in the change.log.
This is not likely to change anytime soon. Pulling all of the change log
messages from projects developed elsewhere cannot practically be automated.
While manually updating that information on a single project does not take a
very long time, doing it on mass is very time consuming. Time better spent on
other aspects of the project.
When I was writing docs for JBoss FUSE, SUSE SLE, SUSE CaaSP and other
projects, we had a saying:
"Docs or it didn't happen."
The point being: writing the software is the fun bit... But the product
is not ready for release until the docs are ready.
--
Liam Proven ~ Profile: https://about.me/liamproven
<https://about.me/liamproven>
Email: lpro...@cix.co.uk <mailto:lpro...@cix.co.uk> ~ gMail/gTalk/FB:
lpro...@gmail.com <mailto:lpro...@gmail.com>
Twitter/LinkedIn: lproven ~ Skype: liamproven
IoM: (+44) 7624 227612: UK: (+44) 7939-087884
Czech [+ WhatsApp/Telegram/Signal]: (+420) 702-829-053
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
