How to add Minix to Windows Boot Manager
Roshan Bharath Das
Evgeniy Ivanov
On Wed, Dec 14, 2011 at 12:42 PM, Roshan Bharath Das
<roshanbh...@gmail.com> wrote:
> Hello,
>
> I installed minix 3.2.0 successfully in my netbook and I want to add minix
> in to the windows 7 boot loader.
> How can I do that?.
I'm not sure if Windows boot loader supports chain loading. Check its
documentation.
There are some instructions how to boot grub using windows, e.g.:
http://goo.gl/OCnid
You can try it for MINIX boot loader instead.
> I am not able to boot minix after installation, as every time windows is
> booted.
>
> Disk Partion:
> Windows is in Disk 0 - Partition 0.
> Minix is in Disk 0 - Partiton 1.
When you boot BIOS, choose partition 1 to boot from, this should bring
you into MINIX 3 world.
--
Evgeniy Ivanov
Antoine LECA
> I installed minix 3.2.0 successfully in my netbook and I want to add minix
> in to the windows 7 boot loader.
> How can I do that?.
Save the installed (patched) MINIX boot sector
dd count=1 if=/dev/c0d0p1s0 of=BOOTMNX
and move the 512-byte BOOTMNX file to the starting ("system") Windows
partition, the one where BOOTMGR resides.
Then use BCDedit; something along the lines of
bcdedit /create /d �MINIX320� /application BOOTSECTOR
Note the GUID created, and use it in below commands
bcdedit /set {GUID} device boot
bcdedit /set {GUID} path \BOOTMNX
Please read Microsoft's (and others') documentation about bcdedit, there
are a lot more options, some may be interesting to you (like to reduce
the default 30-second time out.)
IMPORTANT NOTICE: Keep in mind that every time you reinstall the boot
monitor running `installboot -d ...` (it should *not* be very often),
you will need to move the newly patched MINIX boot sector again to the
starting ("system") Windows partition.
Antoine
Donald Allen
> Roshan Bharath Das wrote:
>> I installed minix 3.2.0 successfully in my netbook and I want to add minix
>> in to the windows 7 boot loader.
>> How can I do that?.
>
> Save the installed (patched) MINIX boot sector
> dd count=1 if=/dev/c0d0p1s0 of=BOOTMNX
> and move the 512-byte BOOTMNX file to the starting ("system") Windows
> partition, the one where BOOTMGR resides.
>
> Then use BCDedit; something along the lines of
> Note the GUID created, and use it in below commands
> bcdedit /set {GUID} device boot
> bcdedit /set {GUID} path \BOOTMNX
>
> Please read Microsoft's (and others') documentation about bcdedit, there
> are a lot more options, some may be interesting to you (like to reduce
> the default 30-second time out.)
>
>
> IMPORTANT NOTICE: Keep in mind that every time you reinstall the boot
> monitor running `installboot -d ...` (it should *not* be very often),
> you will need to move the newly patched MINIX boot sector again to the
> starting ("system") Windows partition.
This all seems unnecessarily complicated. I've had a lot of success
with GAG, though I haven't tested it with minix:
If all minix requires is a boot manager that does chain-loading, as is
apparently the case, this will work and is extremely simple to set up.
/Don
>
>
> Antoine
>
> --
> You received this message because you are subscribed to the Google Groups "minix3" group.
> To post to this group, send email to min...@googlegroups.com.
> To unsubscribe from this group, send email to minix3+un...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/minix3?hl=en.
>
Antoine LECA
> This all seems unnecessarily complicated. I've had a lot of success
> with GAG, though I haven't tested it with minix:
>
> http://gag.sourceforge.net/
It is a long time since I looked at GAG; does it now allows being
launched from the Windows Boot Manager?
Antoine
Donald Allen
I'm not sure what you mean. GAG becomes the primary boot manager,
installed in the MBR. It then invokes the selected partition
boot-loader; in other words, chain-loading. I have used it with
systems on which I dual-boot Windows and one of the BSDs and it works
very well. On my dual-boot Windows/Linux systems, because I use
Slackware Linux, I just let Patrick Volkerding's clever use of Lilo do
its thing (he detects the presence of the Windows system and generates
a lilo.conf that will boot either Windows or Linux), which gives me
the same thing GAG does on the Windows/BSD systems -- easy boot-time
choice of Windows or the Unix/Linux system.
Antoine LECA
> On Wed, Dec 14, 2011 at 9:07 AM, Antoine LECA wrote:
>> Donald Allen wrote:
>>> This all seems unnecessarily complicated. I've had a lot of success
>>> with GAG, though I haven't tested it with minix:
>>
>> launched from the Windows Boot Manager?
>
> I'm not sure what you mean.
The question I was answering was about the ways to boot MINIX away from
Windows Boot Manager.
> GAG becomes the primary boot manager, installed in the MBR.
If we are to install a new "primary" boot manager _instead_ of Windows,
MINIX is an obvious candidate (perhaps with the help of jumpboot if
Windows Bootmgr has the nefast idea to fiddle the active boot indicator)
I agree there are lots of other solutions, and yes GAG is a fine one (as
GRUB, as LILO are). Just that I was not answering about that.
Antoine
Donald Allen
Yes, I understand the original question was about the Windows boot
manager and you were responding to that. What I did not understand was
your question about GAG being launched by the Windows boot manager,
since GAG *replaces* the Windows boot manager in the MBR.
The point I'm trying to make to the original poster is that there are
better options, simpler options, than trying to wrestle with
Microsoft's junk.