Siginet, on Dec 14 2009, 11:00 PM, said:
I'm curious... is it manditory that grldr be on the root of the hard drive? I tried to put it in boot.ini to launch from C:\WINDOWS\GRUB\grldr... but it did not work. I just figured if it was something to leave on the hard drive it would be nice to have it inside the Windows dir... so that most users would not notice it as clutter on the drive. If it possibly could be launched from within a subfolder it would be great.
Also... I could not figure out how to edit the embedded config inside of grldr so I can get rid of the need for menu.lst.
There may be some problems in accessing files in that stage, but the problem is that AFAIK grldr initial part tries to "find itself" and it looks in ROOT of any partition, even a hidden one, but not in folders.
Some releases may behave differently.
About the embedded menu.lst read here:
http://diddy.boot-la...es/embedded.htm
http://www.boot-land.net/forums/index.php?...c=6775&st=5
http://www.boot-land.net/forums/index.php?...=8634&st=13
But since we are into the realm of experimentation, you can also edit it to point to BOOT.INI itself

.
Try a BOOT.INI like this:
title PLoP Boot Manager
find --set-root /plpbt.bin
kernel /plpbt.bin
boot
[boot loader]
Timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect
C:\grldr=grub4dos
Before changing the "menu.lst" in the embedded to "boot.ini", simply go to command line in grub4dos and issue command:
configfile /boot.ini
What happens?
The NTLDR parses BOOT.INI starting from the first "[", so you can add something before it:
http://www.msfn.org/board/win-98-and-win-x...604-page-8.html
Of course I am COMPLETELY in disagreement to the approach you chose.
Both grub4dos and PLoP are in continuous development, and hard-coding them inside the .exe means putting on the HD a "static" version, unless you continuously update the app.
BTW, your approach is an infringement of the GPL license of GRUB/grub4dos, you should add the COPYING license file and at least a minimal text explaining that your app contains GPL code.
You do NOT actually "need" grub4dos to load PLoP:
http://www.plop.at/e...ger.html#runwin
Quote
Run from the Windows boot menu (2K, XP and VISTA)
Download the file plpgenbtldr-0.7.zip and extract it.
Create a directory like c:\plop. You can use any directory you want.
Copy plpbt.bin and plpgenbtldr.exe to your c:\plop directory.
As administrator/with administrator rights open a command shell and change to c:\plop
Then start plpgenbtldr
This program searches for the file plpbt.bin in the currrent directory.
plpgenbtldr generates the file plpbtldr.bin.
Adding to the boot menu. Windows 2K and XP is different to Windows VISTA
Windows 2K, XP
add the line below to your c:\boot.ini
c:\plop\plpbtldr.bin="PLoP Boot Manager"
Windows VISTA
open notepad as administrator and create a file c:\boot.ini
add those lines
[boot loader]
[operating systems]
c:\plop\plpbtldr.bin="PLoP Boot Manager"
Thanks to tri_zet for this info
Now you should be able to start the PLoP Boot Manager from your Windows boot menu.
You can configure the file plpbt.bin with plpcfgbt.
Problems/Errors
plpbt.bin must not be fragmeted! Use contig to take care, that plpbt.bin is not fragmented.
jaclaz
This post has been edited by jaclaz: 15 December 2009 - 04:37 AM