On 3/4/2021 12:36 PM, Jerome Shidel wrote:

On Mar 4, 2021, at 2:56 PM, Ralf Quint <freedos...@gmail.com <mailto:freedos...@gmail.com>> wrote:

[..]
Yes, I can fix this problem myself, that is not the issue. It is that this all seems to trip potential new users right at the start.

From what I recall (and I could be wrong), the vast majority of “new” users are not running on bare metal. Mostly it get’s installed into a virtual machine. That isn’t to say it is not a problem. Just saying it isn’t how most users run FreeDOS.
Well, could you consider that this is likely an observation of a symptom rather than the cause?

I would also wondering why the C: drive, though offered to be formatted, is at the same time not "SYStemized", including a baseline config.sys and autoexec.bat as well as a base FREEDOS folder before starting FDIMPLES to install further packages. To me, this seems to be the next logical step (and what I just did manually to move on on this system)...

Not sure what you mean.

If you are referring to why the kernel and the shell are not transferred automatically to drive C: when the disk is formatted, there are several reasons. Mostly, those are:

— some systems won’t boot into FreeDOS after a simple SYS. Sometimes more work is required to make that happen. All of it is consolidated into a single par of the installer to aid in simplifying the code some.

— the installer can run in advanced mode. when it does, that step is optional. A user could for example in advanced mode, install just the FreeDOS binaries onto PC/MS-DOS.

— most systems are (including VMs) are configured to boot the HD before the CD. The installer wants to be sure the install process has completed before committing the system to boot from the internal HD.

I don't see how this would prevent the transfer of boot record, kernel, command.com and a basic config.sys&autoexec,bat (and a basic FREEDOS\BIN folder). If someone at this point chose to format the C: drive, I doubt that there is any reason NOT to make this drive bootable (and at least baseline workable, in case of an unexpected abortion of the install process). That doesn't mean that the installer has to reboot at that point, so the boot order of the system for example should not be an issue...

Ralf



--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Reply via email to