On the issue of what to do with a preexisting MBR on installation target, my
installation target would be a USB stick, or I could possibly use an old 1.2 GB
IDE hard drive in a Sabrent enclosure with USB 2.0.
So then I would not worry about overwriting the MBR, though I would want to be
sure it
> On Feb 23, 2016, at 3:47 PM, Eric Auer wrote:
>
>
> Hi Jerome,
>
>>> - user has another OS and DOS must not kill the boot menu without asking
>>>
>>> - user made a virtual computer for DOS, the disk contains nothing at all
>>
>> - user has some old hardware they want to install and play wi
Hi Jerome,
>> - user has another OS and DOS must not kill the boot menu without asking
>>
>> - user made a virtual computer for DOS, the disk contains nothing at all
>
> - user has some old hardware they want to install and play with a newer DOS.
>
>> In the second case, it is good to automatic
> On Feb 23, 2016, at 3:05 PM, Eric Auer wrote:
>
>
> Hi!
>
>> Matuesz, I actually went and tested this. MS-DOS 6.22 [0]
>> handles the MBR that same way as FDI [1] does. :/ Both leave a broken
>> MBR, one that cannot boot into the newly installed DOS.
>
> Ouch. Note that MS DOS is from the
Hi!
> Matuesz, I actually went and tested this. MS-DOS 6.22 [0]
> handles the MBR that same way as FDI [1] does. :/ Both leave a broken
> MBR, one that cannot boot into the newly installed DOS.
Ouch. Note that MS DOS is from the time where nobody had any
other operating system previously insta
Preview 14, Is going to zap the MBR by default in normal mode.
In advanced mode, this can be overridden.
I may push Preview 14 out the door sometime today. Mostly, because I made a dumb
mistake in FDIMPLES with search and replace. Completely breaking the detailed
package selection in advanced mo
Old knoppix distro live-cd has the option to boot knoppix linux or freedos,
On the isolinux prompt type "dos"
Sadly last time I tested they old pre1.0 freedos distro. I asked editor
to use an updated freedos image but they take everything from
debian repositories, and this is the Freedos image
On Tue, Feb 23, 2016 at 12:28 AM, Mateusz Viste wrote:
> I'm going with Louis on this one. When installing FreeDOS, I'd expect
> the installer to overwrite my MBR with clean boot code, so I don't have
> any troubles booting FreeDOS post install. That's what MS-DOS did, and
> that's what I expect f
> On Feb 23, 2016, at 8:54 AM, Corbin Davenport
> wrote:
>
> Is there a possibility FreeDOS could install the GRUB manager by default on
> PCs with multiple partitions? Or even go a step further and try to detect an
> existing GRUB installation, and adding it's own menu item to it?
I don’t t
Is there a possibility FreeDOS could install the GRUB manager by default on
PCs with multiple partitions? Or even go a step further and try to detect
an existing GRUB installation, and adding it's own menu item to it?
Corbin
On Tue, Feb 23, 2016 at 7:05 AM, Don Flowers wrote:
> OK - I have seve
OK - I have several PC's with varying modern installs (WIN7, WIN10,
Xubuntu)
residing along with various versions of MS-DOS and FreeDOS (even a custom
FAT16 version of FreeDOS). I have created several rescue disks and yet
there is
always at least one install that either messes up my boot code (usua
Mateusz Viste composed on 2016-02-23 09:28 (UTC+0100):
> I'm going with Louis on this one. When installing FreeDOS, I'd expect
> the installer to overwrite my MBR with clean boot code, so I don't have
> any troubles booting FreeDOS post install. That's what MS-DOS did, and
> that's what I expec
I'm going with Louis on this one. When installing FreeDOS, I'd expect
the installer to overwrite my MBR with clean boot code, so I don't have
any troubles booting FreeDOS post install. That's what MS-DOS did, and
that's what I expect from any OS in fact.
Naturally, an appropriately big warning
13 matches
Mail list logo
