> On Apr 18, 2021, at 3:01 PM, Eric Auer <e.a...@jpberlin.de> wrote: > [..] > I am looking forward to Jerome's next update with a tuned > driver strategy. FDISK would not help with that.
RC4 is coming very very soon. The new RBE is done. Currently, testing and fixing minor issues with release media builds that were caused by me changing stuff. Things like—Oh, since it builds the boot disk image from a package list and not based on tweaking some other disk image. I needed to add the HIMEM package to the list and rebuild the release. Just a bunch of little fiddly bits. :-) > I agree that there should be documentation about how the > install process works which can help you to push it a bit > when it gets stuck at some point. Of course the documents > should be available online, also outside the install disk. Better documentation would be nice. But, I’ve only got so much spare time. :-) On the bright side… It says “packages not found.” Instead of those wonderful modern error messages like “iTunes Store Error (-232342)” or those good old DOS errors like “runtime error 204 at 31fa:1100” I always found those so very informative. not. :-) > [..] > You are of course right that creating a dual boot system > is tricky. In particular, it is not something the FreeDOS > installer can do for you. So depending on how much you want > it, we could write some howto about how to create a dual > boot system with Linux (or Windows) or even a triple boot, > using tools for Linux or Windows. DOS tools are not enough > to do dual boot with anything without the help of the Linux > or Windows system itself. So you have to use their tools. Like when installing Windows... By default, the installer configures the system to boot FreeDOS. Leaving other operating systems not very accessible. It does make backup copies of the MBR. So, a knowledgeable user could possibly use those to restore booting to the previous OS. However, that is still risky, complicated and I don’t really recommend doing that. If a user intends to install on real hardware, has a prior OS they want to keep and intends on multi-boot, they should not run the installer in default mode. They should run it in advanced mode. (quit, and restart the installer with “setup adv”) Or, switch from default to advanced mode by pressing CTRL+C when the installer is waiting for user input. In advanced mode, things like selecting the target drive and install path, overwriting the boot loader, transferring system files and other options are available. In advanced mode, the installer pre-selects the settings it would make for you. However, you can change them if needed. :-) Jerome _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
