On 12.04.12 20:38, dmccunney wrote:
> I just made a post amending my statement.
Ok, but still it has nothing common with DOS itself. Because:
> I amend my statement: they'll boot DOS if you jump through an
> assortment of hoops to get them to do so. I got FreeDOS to boot
> alongside Win2K and two flavors of Linux on an old notebook, but it
> took lots of fiddling (and I'm not sure just *which* fiddle did the
> trick. I was multi-booting from Grub2.
It's clearly not a DOS problem. Multiboot setup *must* be carefully
planned and deployed, and on every step you *must* clearly understand
what you are about to do. Or else you'll end up with "lots of fiddling",
being "not sure just *which* fiddle did the trick". Also worth
mentioning that GRUB2 is a way more complex to configure than GRUB-legacy.
> A subsequent clean re-install of Win2K to solve other problems broke
> it. I could get grub and my grub config back, but FreeDOS won't boot,
> claiming it can't find KERNEL.SYS. (And yes, I'm using a current
> kernel, SYSed to the correct place from a FreeDOS boot floppy.) I can
> successfully run DOS apps in a Win2K console window, so fixing it
> isn't exactly urgent.
It is well-known behaviour of Windows, to destroy any other single or
multi-OS boot schemes, replacing it with it's own bootloader. Also GRUB2
is related in your particular case. But it's even less related to DOS
than previous statement, as *any* OS can be victim in such scenario.
> But if you are going to boot DOS on current hardware, you are likely
> to be multi-booting, with other things like Windows and Linux in the
> mix. That may require plain and fancy fiddling: what's your
> boot-loader? How do you successfully add DOS to the list of things it
> can boot?
I'm using GRUB-legacy. And for GRUB-legacy adding FreeDOS is as easy as
adding 3 lines to /boot/grub/menu.lst:
title FreeDOS 1.0
rootnoverify (hd0,0)
chainloader /freedos.bss
> One question to ask is what you are doing, and whether you actually
> need to boot into DOS from the BIOS level at all. Epending upon your
> use case, it may make more sense to use an emulator or VM.
There is no silver bullet. And while using an emulator or VM can be
sufficient for many of the cases, they have their own downsides.
Regards
--
------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
