Printable Version of Topic

Click here to view this topic in its original format

Boot Land _ Grub4dos _ Grub4dos Guide/Tutorial

Posted by: diddy Jul 14 2008, 08:01 PM

After harassing Jaclaz and ilko countless times over the past few weeks I have finally, with their help, completed a grub4dos guide. Many thanks to Jaclaz and ilko for their input, suggestions and support thumbsup.gif .

Feel free to post any errors or feedback good or bad. The guide is available http://diddy.boot-land.net/grub4dos/Grub4dos.htm a downloadable version is also available.

diddy

Updated - 18th July 2008
Guide updated to version 1.1 following feedback from tinybit - see below.

Updated - 19th February 2009
Guide updated to version 1.2

Updated - 22nd April 2009
Guide updated to version 1.3

Updated - 17th May 2009
Guide updated to version 1.4

Posted by: tinybit Jul 15 2008, 02:55 AM

Good work thumbup.gif

I would like to add one point on the "mappings" page: http://diddy.boot-land.net/grub4dos/files/map.htm.

"Double-mapping" should perhaps (better) be called "nested mapping". The nest is no limit to the depth.

Another point about the "memory mapping":

QUOTE
The use of compressed images is therefore recommended, as it allows for less memory usage and faster loading.


The gz image does not save memory since it will be decompressed by the map command. It only save disk space where it occupies. It allows faster loading, yes.

QUOTE
Example use for Gzip'ed images -

* find --set-root /win98.ima.gz
* map /win98.ima.gz (fd0)
* map --hook
* root (fd0)
* chainloader +1
* boot


In map --mem /win98.ima.gz (fd0), the --mem should not be omitted.

Posted by: jaclaz Jul 15 2008, 07:59 AM

Hmmm, it seems that the proofing by jaclaz wink.gif wasn't so accurate, after all. happy22.gif

jaclaz

Posted by: tinybit Jul 15 2008, 10:08 AM

Oh, I think jaclaz's words are very accurate indeed, and even more accurate than the developer's documents in most cases.

Posted by: diddy Jul 15 2008, 12:41 PM

@Tinybit

Thanks for the quick response (and the eagle eyes - well spotted on the missing --mem switch). I'll edit the guide with the necessary changes and upload the new version within the next week - I want to see if any other errors are noticed first.

diddy

p.s. Jaclaz - you're sacked wink.gif

Posted by: mr_ Jul 26 2008, 02:11 PM

Great guide! Helps very much.

But why not post this guide into the grub4dos wiki?

Posted by: jaclaz Jul 27 2008, 10:18 AM

@diddy

A couple links that you may want to add to this page:
http://diddy.boot-land.net/grub4dos/files/links.htm

Grub4dos latest releases (sometimes more up-to-date than http://grub4dos.jot.com/ )
https://gna.org/projects/grub4dos/
http://download.gna.org/grub4dos/

jaclaz

Posted by: Xtremee Sep 21 2008, 08:12 PM

@ diddy,

Thank you a lot for your excellent Tutorial for Grub4Dos it is really interesting.

While I am reading you tut I find some typos that need to be fix.

QUOTE
Boot Options.htm
1st line: utilises --> utilizes

Map Command.htm
Nested Maopping section
2nd line: utilises --> utilizes

Booting Disk Image Files
section
this maps the image file (in this case PE.img --> sectionthis maps the image file (in this case PE.ima

I fix the .htm pages and http://rapidshare.com/files/146992787/Grub_Typos.rar.html them to you.

Posted by: ilko Sep 22 2008, 04:56 AM

@diddy- yet another link from Tynibit, the latest builds:
http://grub4dos.nufans.net/

@Xtremee- isn't utilise alternative spelling?
http://en.wiktionary.org/wiki/utilize
http://www.babylon.com/definition/utilise/

Posted by: Galapo Sep 22 2008, 06:01 AM

QUOTE (Xtremee @ Sep 22 2008, 06:12 AM) *
While I am reading you tut I find some typos that need to be fix.


[joking]
That depends on one nationality and the acceptance or non-acceptance of whether US English should be the standard. Apart from specialised (not a typo!) terms for a domain of study originating (or in part originating) from the US, I prefer to use -ise suffix myself and reject the use of -ize. Diddy's choice could be similarly intentional.[/joking]

Regards,
Galapo.

Posted by: jaclaz Sep 22 2008, 10:05 AM

With all due respect to our U.S. friends, the language is called English, and rather obviously the fact that you have to specify "U.S. English" or "American English", means that it is NOT the "real thing".
http://www.bartleby.com/68/36/3436.html

QUOTE
-ise, -ize (suffix)


is an extremely prolific word-forming suffix, and many conservatives balk at what appears to be unnecessary invention and overuse of the device to coin such originally nonce words as concretize, computerize, pauperize, and the like. Americans make more use of -ize; Britons use more of -ise, but there are many American spellings with -ise as well.


Both suffixes are commonly accepted, but the -ise one does look more "British".

By the way, there is even people that use the term "amlish" for the "american way" of using English wink.gif:
http://www.accomodata.co.uk/amlish.htm

Of course all the "English" we commonly write and talk has had some influences from American English, and it is very difficult to distinguish American terms that have become common use in English from "wrong" ones, but when we are talking about spelling, I guess that British English should always prevail.

Personally I find that calling a dinner jacket "tuxedo" (American) or "smoking" (Italian) is a crime against logics and semantics:
http://en.wikipedia.org/wiki/Black_tie
roll1.gif

jaclaz

Posted by: Xtremee Sep 22 2008, 10:28 AM

@ ilko & Galapo & jaclaz

Thanks for the info I really don't know that.

afro.gif blush.gif wub.gif

Posted by: Climbing Nov 13 2008, 06:57 AM

I suggest to add some contents to the guide as below:

1. grldr.mbr can also be used to load grldr under Windows NT. for example:

edit boot.ini just like below:

CODE
[boot loader]
timeout=3
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional" /fastdetect /NoExecute=OptIn /PAE /3GB
c:\boot\grldr.mbr="Grub4DOS by grldr.mbr"
c:\grldr="Grub4DOS by grldr"


2. grldr can also be loaded by PXE as PXE boot file. after boot through PXE, it will use (pd) as the TFTP Server device.
map --mem (pd)/someimg.img (fd0)
map --hook
...

3. about PXE, you can use pxelinux to switch to grub4dos just as syslinux does, but you can keep the pxe stack and let grub4dos can access the (pd) device.

pxelinux.cfg:
CODE
LABEL grub4dos.pxe
MENU LABEL GRUB4DOS with PXE
kernel /grub.exe
append keeppxe


ALSO in (pd)/menu.lst/default you can do this:
CODE
title Return to PXELinux
pxe keep
chainloader --force --raw (pd)/pxelinux.0

title Load grub.exe with PXE support
pxe keep
terminal console
kernel (pd)/grub.exe

title Load grldr with PXE support
pxe keep
terminal console
chainloader --force --raw (pd)/grldr


At last, please forgive my poor English.

Posted by: jaclaz Nov 13 2008, 01:34 PM

@Climbing

Thanks for the update smile.gif, I am sure that diddy will include them in next "revision" of the guide.

But two questions, one maybe worth something, the second pretty much noobish:
1) What are the advantages (if any) or drawbacks (if any) in using grldr.mbr instead of grldr in BOOT.INI? unsure.gif
I mean, if I am not mistaken, the "job" of grldr.mbr is simply that of starting grldr, so I cannot see the usefulness of this "added step".

2) About PXE booting I have a number of perplexities - mainly because I did some experiments with PXE booting only a long time ago and I am not at all "familiar" with the process.
Could you post (or PM me if you prefer) a single "from beginning to actual boot" example (I mean a real world example, with actual settings used and known to work), including the settings of the TFTP server, some details of the OS/image booted through PXE and the like?
Even if you do not trust your English (in which I can see no problems, BTW wink.gif) it would be useful, as I could try and "fill the blanks" and "pass" it to diddy so that he can edit it in "real English" and add to the guide a complete set of instructions.
I see bits and pieces of the process, here and there, on the board and on the grub4dos readme_grub4dos.txt but I am failing to catch the thing in its entirety.

cheers.gif

jaclaz

Posted by: Climbing Nov 14 2008, 03:38 AM

@jaclaz

Thanks. (BTW: The word "noobish" is hard to understand. I googled it for a long time. Finally got it.)

My answers to your questions:

1) about using grldr.mbr to load grub4dos. I think grldr.mbr just like a boot sector of grldr as well as bootsect.dos to IO.SYS(MS-DOS). and in some situation, user want grldr has customized name such as mygrldr, foo.ldr ... etc. then he can use grubinst to edit grldr.mbr to do this:

CODE
grubinst  -b=mygrldr -o grldr.mbr


also, you can use :
CODE
grubinst -e -b=mygrldr grldr
ren grldr mygrldr
copy mygrldr c:\
echo c:\mygrldr="grub4dos" >> c:\boot.ini

similar way to customized the grldr name.

grldr.mbr needn't have to put in drives root directory. Also, some one want to load grub4dos under NT and Vista in the same way. then using grldr.mbr is the only way.

2) I think you want me give the steps to setup a PXE server and use grldr as the boot file. ok, following:

PXE server = DHCP Server + TFTP Server.

How to setup DHCP Server and TFTP Server, there are many documents on the internet, just google it.

DHCP Server settings for PXE:
Option:066(boot server) = IP address of the TFTP Server.
Option:067(boot file) = grldr

TFTP Server settings for PXE:
suppose the TFTPServer root is: c:\tftproot, pxemenu.lst is the PXE boot menu for grub4dos.
CODE
copy grldr c:\tftproot
copy grub.exe c:\tftproot
md c:\tftproot\menu.lst
copy pxemenu.lst c:\tftproot\menu.lst\default
copy memdisk.gz c:\tftproot
copy pxelinux.0 c:\tftproot


then setup PXE Server done!

You can simply use TFTPD32(who include DHCP and TFTP Server in one program) in windows (NT) to setup a PXE Server for simple use or test.

you can downloads files above at: http://nufans.net/upload/pxe/tftpd32


TFTD32 Settings:


DHCP Server Settings of TFTD32:


When you setuped the PXE Server, you can try boot the computer from PXE(in a LAN with the PXE Server).

Hope this can help.

Climbing

Posted by: Twilight Cruiser Dec 2 2008, 01:23 PM

Hi diddy,

great piece of work!
Hard to get through because it's so comprehensive, but a great help in understanding and handling GRUB4DOS (which is a real great boot manager tool)! worship.gif

Greetings
Norbert

Posted by: JonF Jan 1 2009, 08:14 PM

Minor error at http://diddy.boot-land.net/grub4dos/files/map.htm, at the end of the first paragraph after the bulleted list: "Either of the following programs can be used to defragment a file that is contiguous" should be "Either of the following programs can be used to defragment a file that is not contiguous".

Posted by: mr_ Jan 3 2009, 08:06 PM

The tips from here http://www.boot-land.net/forums/index.php?showtopic=6614 could be potentially added to this guide if a pxe part will be introduced.

Posted by: Icecube Jan 3 2009, 09:29 PM

The Installing Grub4dos part doesn't mention, booting grub4dos via (legacy) grub for the linux folks rolleyes.gif .

Load via Grub
Copy grub.exe to /boot/.
Add the following section in your /boot/grub/menu.lst file.

CODE
title Grub4dos
root (hd1,0)
kernel /boot/grub.exe

Change the root (hd1,0) command to the right drive and partition for your PC.

Posted by: rasker Jan 15 2009, 06:05 PM

Really a great guide. Well done! Perhaps it should form the basis of the official documentation.

Cheers
R

Posted by: diddy Jan 19 2009, 10:24 PM

This is just a quick message to thank everyone for the positive feedback and useful comments. Unfortunately, due to other commitments I have had very limited time in which to update the guide. I'm hoping that things calm down within the next few weeks and will work on an updated version at that time - incorporating some of the suggestions (and corrections) made so far. I will definitely be adding a pxe boot section but confess to being an 'English English' speaker so will be sticking with the utilise spelling - sorry Xtremee wink.gif .

I might end up waiting for the release of grub4dos 0.4.4 Final to motivate me in updating the guide and eagerly look forward to the release - thanks for all of the hard work tinybit. Due to the explosion of grub4dos builds it's hard to keep track of all of the changes so it's likely to take a few weeks to make all of the additions - I've been using build 2008-5-14 for a while now and haven't been keeping up with any new releases so it's likely to take a week just to work through the changelog.

Thanks for the patience.

diddy

Posted by: caze Jan 29 2009, 09:22 AM

the tutorial is really great! thank you all a lot!
unless i am mistaken (which is very probable), it might be helpful to include under esp. method 6 the note that the grldr file should, in order to be found by grub4dos stage1 in mbr, not be placed on an ntfs partition but may e.g. reside in the root of any fat16/32 partition. but note that this might be wrong and only not work for me.

Posted by: jaclaz Jan 29 2009, 10:08 AM

QUOTE (caze @ Jan 29 2009, 11:22 AM) *
the tutorial is really great! thank you all a lot!
unless i am mistaken (which is very probable), it might be helpful to include under esp. method 6 the note that the grldr file should, in order to be found by grub4dos stage1 in mbr, not be placed on an ntfs partition but may e.g. reside in the root of any fat16/32 partition. but note that this might be wrong and only not work for me.


grldr placed in NTFS partition works perfectly, AFAIK.

You may want to start a new thread detailing the problem you are having.

jaclaz

Posted by: caze Jan 29 2009, 12:04 PM

hm. thank you for the advice. you are sure about that - in the situation where there is only grub4dos in mbr plus grldr on a ntfs (logical) partition, no grub4dos in bootsector, i assume? i will try and look into this. if it reproducably won't work, i'll open a new thread as you advice. thanks again!

Posted by: Icecube Feb 9 2009, 06:15 AM

Add some new commands to the tutorial:
http://www.boot-land.net/forums/index.php?showtopic=6880&st=0&gopid=58554&#

Posted by: diddy Feb 19 2009, 10:58 PM

Guide updated to version 1.2 (Grub4dos 0.4.4-2009-02-05).

Since downloading build 0.4.4-2009-02-05 two weeks ago there have been 8 new builds - great news for anyone not trying to maintain an up to date guide sporty98.gif .

I will try to keep the guide updated on a monthly basis but can't keep up with tinybit et al.

The .chm version has been temporarily removed - not sure when it will be updated due to lack of free time.

diddy

Posted by: Icecube Feb 21 2009, 05:45 AM

QUOTE
Menu colours can be set using the following command (default is white text on a black background, with current option being black text within a white highlight) -
CODE
color a/b c/d

Where a=text, b=background, c=selected option text, d=selected option highlight

Colours b and d must be one of the following - black, blue, green, cyan, red, magenta, brown, light-gray

Colours a and c must be one of the following - black, blue, green, cyan, red, magenta, brown, light-gray, dark-gray, light-blue, light-green, light-cyan, light-red, light-magenta, yellow and white.

The new color command:
CODE
color NORMAL [HIGHLIGHT] [HELPTEXT [HEADING]]]

CODE
color fg/bg fg/bg fg/bg fg/bg

All colors can be used as foreground and background color now: black, blue, green, cyan, red, magenta, brown, light-gray, dark-gray, light-blue, light-green, light-cyan, light-red, light-magenta, yellow and white.

Posted by: mr_ Mar 21 2009, 06:54 PM

In appendix commands I am missing:
- bootlace.com
- grubinst.exe
- grbins16.exe
- hmload.com

What are the commands install and setup currently doing? Installing the grub legacy way?

Posted by: Uofis Mar 21 2009, 10:33 PM

Great Tut.. thx..

Helped already experimenting the .iso booting .. greetZ

Posted by: jaclaz Mar 22 2009, 12:01 PM

QUOTE (mr_ @ Mar 21 2009, 08:54 PM) *
In appendix commands I am missing:
- bootlace.com
- grubinst.exe
- grbins16.exe
- hmload.com

What are the commands install and setup currently doing? Installing the grub legacy way?

You are not "missing" them, the appendix is about grub4dos commands.

The files you listed are not grub4dos commands, they are "external utilities".

The use of grubinst/bootlace/grbins16 is in the install chapter:
http://diddy.boot-land.net/grub4dos/files/install.htm
http://diddy.boot-land.net/grub4dos/files/install.htm#method08
http://diddy.boot-land.net/grub4dos/files/install.htm#method09
http://diddy.boot-land.net/grub4dos/files/install.htm#method13

Advanced info is in the README_GRUB4DOS.txt file.

As well in this last file there are details on the use of hmload.com and a link to the developer's page:
http://sysdocs.stu.qmul.ac.uk/sysdocs/Comment/GrubForDOS/

jaclaz

Posted by: mr_ Mar 26 2009, 01:39 PM

I am pleased to see instructions for creating the triple MBR (3x2), related topic, http://www.boot-land.net/forums/index.php?showtopic=7507.

QUOTE (jaclaz @ Mar 22 2009, 12:01 PM) *
You are not "missing" them, the appendix is about grub4dos commands.

The files you listed are not grub4dos commands, they are "external utilities".

Indeed, well I was seeing all this more as a package..

Still I would appreciate putting the syntax also for the external utilities also into the guide, in meanwhile I posted them into the grub4dos wiki.

QUOTE
As well in this last file there are details on the use of hmload.com and a link to the developer's page:
http://sysdocs.stu.qmul.ac.uk/sysdocs/Comment/GrubForDOS/

On this site I don't find the word 'hmload'.

Posted by: jaclaz Mar 26 2009, 10:58 PM

QUOTE (mr_ @ Mar 26 2009, 03:39 PM) *
On this site I don't find the word 'hmload'.


Sure smile.gif, there isn't any. wink.gif

For unknown reasons the program by John Cobb was renamed/changed into xsel (or viceversa unsure.gif), compare the grub4dos readme.txt with the site:

QUOTE
******************************************************************************
*** About the DOS utility `hmload' ***
******************************************************************************

This program was written by John Cobb (Queen Mary, University of London).

John Cobb's note:

To make use of the ram drive feature I wrote a program `hmload' to load
an arbitrary file to an arbitrary address in high memory. The program
is not very sophisticated and relies on XMS to turn on the A20 line.
(Also one must be very careful to steer clear of any areas of memory
already in use).

Under Linux we generated a disk image `dskimg' (with the kernel and
Initrd and a partition table).

Using this our boot procedure looked something like this:

hmload -fdskimg -a128
fixrb
<unload network drivers>
grub

map --ram-drive=0x81
map --rd-base=0x8000000
map --rd-size=0x400000
root (rd,0)
kernel /kernel root=/dev/ram0 rw ip=bootp ramdisk_size=32768 ...
initrd /initrd
boot

See http://sysdocs.stu.qmul.ac.uk/sysdocs/Comment/GrubForDOS/ for details.


and with info.htm:
http://sysdocs.stu.qmul.ac.uk/sysdocs/Comment/GrubForDOS/code/info.htm

jaclaz

Posted by: diddy Apr 22 2009, 06:47 PM

Guide updated to version 1.3

Changes -

* Updated guide for use with Grub4dos version 0.4.4 Final (build 2009-03-31).
* Significant changes made to Installing Grub4dos section - which has been renamed as Loading/Installing Grub4dos
* Added Embedded Menu section
* Added Bootlace Commands section
* Added Grubinst Commands section
* Edited Introduction - simplifying the grub4dos boot process
* Updated Display Options in Configuration File Entries section.
* Added Using && and ||Commands to Configuration File Entries section.
* Amended/updated color, dd, geometry and map commands in Commands section.
* Minor edits and spelling corrections throughout the guide.

The .chm version is still missing for now. I'm going on holiday with family from 24/4/09 and will update the .chm version on my return home (honest).

I'm without internet access whilst away (much to my wifes pleasure) and will check for feedback on the updated guide on my return.

diddy

p.s. Sorry linkmaster (jaclaz) but the updated Loading/Installing Grub4dos section will probably result in some broken links in some of your posts. The original was getting a little too big (and messy) so I have taken an executive decision in breaking it up into smaller OS/device specific sections.

Posted by: jaclaz Apr 22 2009, 07:21 PM

QUOTE (diddy @ Apr 22 2009, 08:47 PM) *
Guide updated to version 1.2

Like in "please read 1.3":
QUOTE
Welcome to Grub4dos guide Version 1.3 (22nd April 2009).


tongue.gif

QUOTE (diddy @ Apr 22 2009, 08:47 PM) *
I'm going on holiday with family from 24/4/09 and will update the .chm version on my return home (honest).


Have fun smile.gif

QUOTE (diddy @ Apr 22 2009, 08:47 PM) *
I'm without internet access whilst away (much to my wifes pleasure) and will check for feedback on the updated guide on my return.



I wonder why women are so motivated against the Internet....happy22.gif

QUOTE (diddy @ Apr 22 2009, 08:47 PM) *
p.s. Sorry linkmaster (jaclaz) but the updated Loading/Installing Grub4dos section will probably result in some broken links in some of your posts. The original was getting a little too big (and messy) so I have taken an executive decision in breaking it up into smaller OS/device specific sections.

"Linkmaster" in his simplicity wink.gif usually gives three links, like:
http://www.boot-land.net/forums/index.php?showtopic=5187
http://diddy.boot-land.net/grub4dos/Grub4dos.htm
http://diddy.boot-land.net/grub4dos/files/install_windows.htm#windows5

Should intended audience fail to find last item, it's their problem. cool.gif

cheers.gif

jaclaz

Posted by: diddy Apr 22 2009, 07:47 PM

QUOTE (jaclaz @ Apr 22 2009, 08:21 PM) *
Like in "please read 1.3":


Oops

I've just edited by last post - cheers jaclaz

Posted by: Icecube Apr 22 2009, 08:28 PM

The page at http://diddy.boot-land.net/grub4dos/files/syntax.htm isn't very clear:
- missing (rd) as valid device
- missing (hd32) (and higher bios drive numbers) as virtual CDROM/DVDROM drive
- not that clear distinction between the numbering of primary and logical partitions.

Maybe something like the following, will be more structured:

CODE
Drives/devices are numbered using the following syntax in Grub4dos:

The numbering of the hard disks starts with zero.
    * (hd0) - first hard disk
    * (hd1) - second hard disk
    * (hd2) - third hard disk
    * ....

Virtual CD drives start at (hd32):
    * (hd32) - first virtual CDROM/DVDROM drive (equal to (0xA0))
    * (hd33) - second virtual CDROM/DVDROM drive
    * ...
    * (0xFF) - last virtual CDROM/DVDROM drive (use this if (hd32) doesn't work for you)

(hd32) is a grub drive number equivalent to (0xA0). If a virtual drive is specified with a drive number greater than or equal to 0xA0, then it will be treated as a cdrom (i.e., with 2048-byte big sectors).

Floppy disks:
    * (fd0) - first floppy disk
    * (fd1) - second floppy disk

CD/DVD drives:
    * (cd0) - first (real) CDROM/DVDROM drive
    * (cd1) - second (real) CDROM/DVDROM drive
    * ...

PXE drive:
    * (pd) - virtual device used to designate the root director of PXE boot server

Ramdisk drive:
    * (rd) - ramdisk


Partition numbering for hard disks:
- Primary partitions (numbering from 0 to 3):
    * (hd#,0) - first primary partition
    * (hd#,1) - second primary partition
    * (hd#,2) - third primary partition
    * (hd#,3) - fourth primary partition (usually an extended partition)

   Examples:
    * (hd0,0) - first primary partition on first hard disk
    * (hd2,1) - second primary partition on third hard disk
    * (hd5,3) - fourth primary partition on sixth hard disk

- Logical partitions (numbering starts from 4):
    * (hd#,4)  - first logical partition
    * (hd#,5)  - second logical partition
    * (hd#,6)  - third logical partition
    * (hd#,7)  - fourth logical partition
    * (hd#,8)  - fifth logical partition
    * (hd#,9)  - sixth logical partition
    * (hd#,10) - seventh logical partition
    * (hd#,11) - eight logical partition
    * (hd#,12) - ninth logical partition
    * (hd#,13) - tenth logical partition
    * (hd#,14) - eleventh logical partition
    * (hd#,15) - twelfth logical partition
    * (hd#,16) - thirteenth logical partition
    * (hd#,17) - fourteenth logical partition
    * ...

   Examples:
    * (hd0,7) - fourth logical partition on first hard disk
    * (hd3,10) - seventh logical partition on fourth hard disk
    * (hd1,14) - eleventh logical partition on second hard disk


To get a list of all devices that grub4dos can see, press 'c' to go the command line mode and type:
  root (
and press <TAB>.



Also repeat at the http://diddy.boot-land.net/grub4dos/files/map.htm#hd32 part of the tutorial:
QUOTE
The "map" process is implemented using INT 13 - any disk emulation will remain accessible from an OS that uses compatible mode disk access, e.g. DOS and Windows 9x. The emulation can't however, be accessed from an OS which uses protected mode drivers (Windows NT/2000/XP/Vista, Linux, FreeBSD) once the protected mode kernel file(s) take control.

and add that Windows based boot disks can't be booted with grub4dos iso emulation, unless they are ramdisk based (link to tutorials would be nice).
This will hopefully solve the problem of newbies that try to use grub4dos iso emulation for booting windows based boot CDs (iso's), but that didn't read or didn't understand the INT 13 access problem with protected mode drivers, which is now only explained at the beginning of the map page.

Also explain that most linux based iso's won't work with grub4dos iso emulation, unless they only need a kernel and an initrd for their working.

It would also be nice when the guide is available from: http://diddy.boot-land.net/grub4dos/index.htm (which seems more logical to me than http://diddy.boot-land.net/grub4dos/Grub4dos.htm)


Upload also the original README_GRUB4DOS.txt and link to it.
It will be useful for people that are searching for some more advanced examples that aren't covered in the tutorial (yet).

Also update your first post.

Posted by: diddy Apr 23 2009, 01:03 AM

@Icecube
I've had a quick scan through your suggestions, which all seem worth adding to the next revision.

Will work on it after my holiday.

Thanks for the suggestions and advice.

diddy

Posted by: Icecube May 9 2009, 08:21 PM

Update: http://diddy.boot-land.net/grub4dos/files/links.htm

The text isn't actually wrong, but grub4dos 0.4.4 is the last official version, so maybe it is appropriate to update the number 0.4.3 to 0.4.4.

Posted by: river~~ May 11 2009, 07:37 PM

hi Diddy,

I am putting together a floppy disk for use in rescuing windows systems that have been broken by a clumsy Linux install, and also to allow usb cds to boot when the BIOS does not support it.

I'm using Grub4DOS and FreeDOS on the floppy.

I'd like to include some text files on the disk to be used as help files from within FreeDOS. May I take a lot of the material from your tutorial? What acknowledgements would you like? I was planning to include the url of the download, and this forum, any other urls you' like me to include?

Also, I don't think I saw any licence / copyright notice at all in the tutorial (I downloaded the zip with all the pages, and have read through them all). Apols if it is in there and I missed it, but if there is no such info at present, may I suggest you add it to the next edition. It is useful to know if it is GPL or Public Domain or whatever.

Thanks for the work you put into the tutorial - it was a real time saver for me getting started.
best regards,

River~~

Posted by: jaclaz May 11 2009, 07:45 PM

QUOTE (river~~ @ May 11 2009, 09:37 PM) *
It is useful to know if it is GPL or Public Domain or whatever.


At least for my small contribution to it, it follows CAREWARE License:
http://home.graffiti.net/jaclaz:graffiti.net/careware.html

Of course diddy is the real Author worship.gif , so he may well apply a more restrictive one.

cheers.gif

jaclaz

Posted by: diddy May 12 2009, 09:48 PM

@river~~

The guide is a community project and is public domain as far as I am concerned, having been compiled with help from other boot-land members and numerous posts both here and on the 911cd forum.

jaclaz's CAREWARE License (see previous post) should however be applied due to the help he gave me with the guide + for pointing me in the right direction whenever I've posted with a Grub4dos related problem worship.gif .

I'd appreciate anyone copying the guide to include the url's for the guide (see first post) + this thread.

Cheers,

diddy


Posted by: river~~ May 13 2009, 04:23 PM

For your info here are my cut down pages of Diddy's guide, intended to be read in DOS from a floppy with no browser, no graphics, etc

Please feel free to copy/use/amend as per jaclaz's CAREWARE licence. In these files I have only covered things relevant to my 'rbrokwin' project (no grub.exe, no PXE, etc) so if you apopt these for anything else you may want to add those back in.

The attachment is a zip file containing MS-DOS text files (\r\n line separators)


River~~

EDIT by jaclaz
Discussion/ideas about the rbrokwin project continues here:
http://www.boot-land.net/forums/index.php?showtopic=7995&hl=

edit by R~~
thanks jaclaz smile.gif
added brief comment about "missing" topics in my files.

 grubhelp.zip ( 10.13K ) : 161
 

Posted by: diddy May 17 2009, 04:40 PM

Guide updated to version 1.4

Changes -

* Added Gfxmenu section following some subtle prompting from jaclaz.
* Added Acknowledgements section.
* Included README_GRUB4DOS.txt (as requested by Icecube).
* Edited Device Allocation/Numbering (as suggested by Icecube).
* Edited Booting from .ISO Images in Map Command section (as suggested by Icecube).
* Edited Display Options in Configuration File Entries section - adding information about gfxmenu.
* Edited Fundamentals section, adding instructions for using spaces in file/folder paths.
* Edited Contents.

The .chm version has finally been updated.

diddy

Posted by: Alberich May 18 2009, 06:13 AM

Thanks a lot to all the people contributed to this Guide. Excellent work. One of the best tutorials I've read.

It was planned for month to change my project for all booting purposes to grub. I expect a horrible piece of work, especially reading all the manuals, examples, tips n tricks available on the net.

It took me only some hours to implement the new booting concept with Grub, thanks to this Guide. A must to read for all beginners and very usefull for experienced users. Handy, well structured, focussing on things you really need to know.
Brilliant.

Juergen smart.gif


Posted by: jaclaz May 18 2009, 06:53 AM

@diddy
An alltogether new meaning to the world subtle! worship.gif

Good work, once again. thumbsup.gif

@Alberich
Actually, grub4dos. happy22.gif

cheers.gif

jaclaz

Posted by: diddy May 18 2009, 07:19 PM

QUOTE (jaclaz @ May 18 2009, 07:53 AM) *
@diddy
An alltogether new meaning to the world subtle! worship.gif


I decided not to publish the (underhand) tatics used by jaclaz as I did not want to upset any of the more sensitive members of the forum tongue.gif

@everyone
Work now begins on version 1.5. I will not be updating the guide from 0.4.4 final to one of the newer builds for now as I don't have time at present to update/check the whole guide and want to add a couple of new topics in the coming weeks. It's nice to see that development continues in tinybit's absence.

diddy

Posted by: river~~ May 20 2009, 06:42 AM

Minor suggestion for http://diddy.boot-land.net/grub4dos/files/map.htm, soon after the bulleted list.

"Either of the following programs can be used to defragment a file" - suggest you also add winimage. Some people frown on it as non-free software, but many others use it and happily pay for it as an easy way to extract/insert file to/from an image.

In winimage, with the image already open, click image->defrag current image. Works in v6.1, not tested it with later/earlier versions. Of course this only works to defrag an image that winimage recognises, as you have to open the image before defragging it.

Tip: insertion of new files into the disk image can fragment the image on disk, and so does reading a new image from a real disk - so I have got into the habit of forcing a defrag before every close.

@Diddy: How much of this detail you include in the manual is up to you of course

River~~

Posted by: jaclaz May 20 2009, 09:32 AM

QUOTE (river~~ @ May 20 2009, 08:42 AM) *
"Either of the following programs can be used to defragment a file" - suggest you also add winimage. Some people frown on it as non-free software, but many others use it and happily pay for it as an easy way to extract/insert file to/from an image.

In winimage, with the image already open, click image->defrag current image. Works in v6.1, not tested it with later/earlier versions. Of course this only works to defrag an image that winimage recognises, as you have to open the image before defragging it.


Well, NO. (i.e. it is NOT recommended as it is NOT a "general" solution)

For TWO reasons:
1)
Winimage will work properly ONLY on a Floppy or Super-Floppy image (one that has NOT a MBR).

Since it "understands" only partitions, it connects to one of them and then you can save the image as a "Full HD" image by adding a MBR and hidden sectors to it.

The management of this feature is NOT always accurate, i.e. the resulting MBR (and partition DATA) may not reflect anymore original one.

2) While Winimage defrags the image "internally" there is no actual "foolproof" guarantee that the file containing the image will be contiguous on the "external" filesystem.

You may be interested (as an alternative) to the good ol' poor man's way that we used in the times of NT4.00:
http://www.msfn.org/board/index.php?showtopic=131017

jaclaz



Posted by: river~~ May 20 2009, 11:14 AM

QUOTE (jaclaz @ May 20 2009, 10:32 AM) *
Well, NO. (i.e. it is NOT recommended as it is NOT a "general" solution)

For TWO reasons:
1) Winimage will work properly ONLY on a Floppy or Super-Floppy image...

fair comment

QUOTE
2) While Winimage defrags the image "internally" there is no actual "foolproof" guarantee that the file containing the image will be contiguous on the "external" filesystem.

my experience (with floppy images only) is that it always seems to do an external defrag (I must have just been lucky so far - and I've done it so often that perhaps I am now thinking of buying a lotto ticket...)

QUOTE
You may be interested (as an alternative) to the good ol' poor man's way that we used in the times of NT4.00:

basically copy it to a recently initialised disk? - yes, done that before(*) - hoping for something a bit friendlier - or were you referring to another post in that thread?

I recently discovered this does not work on ext3 - even writing to a newly formatted ext3 partition a dvd image is not contiguous (my guess is that some journal entries get interleaved with the dvd).

What is the best/recommended linux tool to defrag a single file?

River~~
(*)
[nostalgia]
first did a copy to defrag and compress in 1980 on an interdata 8/16e which had a 5Mb removable disk (in a cartridge about 400mm across and 40mmthick). Used to sort & copy onto 1/2" mag tape and then initialise the disk and copy back. The tape then got filed as backup - the only time in my life I've regularly done backups wink.gif. Including disk and tape drives, the machine took a whole standard rack from bottom to top. And it took long enough to process that we'd have lunch while it was rolling, even though it only had to process max 10Mb (5 to tape, 5 back)
[/nostalgia]

Posted by: jaclaz May 20 2009, 11:57 AM

QUOTE (river~~ @ May 20 2009, 01:14 PM) *
basically copy it to a recently initialised disk? - yes, done that before(*) - hoping for something a bit friendlier - or were you referring to another post in that thread?

Yep, to that one, plain and simple, as I see it, I find it trivial if we are talking of relatively small devices (USB sticks).
What I normally do with them is "building" an image from scratch, copy to the image the files (including "inner" images, then "dd" the whole thingy.
Once you get familiar with the process, possibly using a script to mount/partition/format, see here:
http://www.boot-land.net/forums/index.php?showtopic=5000
http://www.boot-land.net/forums/?showtopic=3191
it is better in my view then actually fiddling with the "real" USB stick. (and besides you already have an image of it should it become coirrupted for any reason).

The friendly way is already Contig/Wincontig.

About EXT3FS I guess you are right, there is no practical way to have on it a (large) contiguous file on it. (or I may too miss something).
What you may want to have a look at is Shake:
http://vleu.net/shake/
AFAIK it works better than Defrag:
http://ck.kolivas.org/apps/defrag/
or PYTHON Defrag:
http://bazaar.launchpad.net/~jdong/pyfragtools/trunk/files

Unless of course you convert it "back" to EXT2FS and than re-convert it "forward" to EXT3FS, which it doesn't seem to me really "handy". unsure.gif

jaclaz

Posted by: Icecube May 20 2009, 10:45 PM

We (read linux users) need to wait for the online defragmentation tool for ext4 (e4defrag). It can completely defragment a single file on an ext4 partition, but it is still in development.
http://polishlinux.org/apps/cli/ext4-defragmentation-with-e4defrag/

Posted by: Icecube Jul 19 2009, 07:39 PM

The "Load via SysLinux" section needs an update:

Old syslinux syntax for loading grub.exe from Syslinux:

QUOTE
LABEL grud4dosexe
MENU LABEL Grub4dos (grub.exe)
KERNEL grub.exe

New syslinux syntax for loading grub.exe from Syslinux:
CODE
LABEL grud4dos
MENU LABEL Grub4dos (grub.exe)
LINUX grub.exe


grldr can also be loaded with the chain.c32 com32 module of the Syslinux package. (Version 3.82 currently needs a small patch, see http://www.boot-land.net/forums/index.php?showtopic=8457&pid=72127&st=10&#entry72127 for the patched version.
Update:
chain.c32 is fixed in syslinux-3.83-pre1, so you not need to download the version attached to that post, but you can download syslinux-3.83-pre1 from:
http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/

Old Syslinux syntax:
QUOTE
LABEL grub4doschain
MENU LABEL GRUB4DOS menu (chain.c32)
KERNEL chain.c32
APPEND ntldr=grldr

New Sylinux syntax:
CODE
LABEL grub4doschain
MENU LABEL GRUB4DOS menu (chain.c32)
COM32 chain.c32
APPEND ntldr=grldr


You also can boot grub4dos from Syslinux/Isolinux by using:
New Syslinux syntax:
CODE
LABEL grub4dosboot
MENU LABEL GRUB4DOS menu (BOOT command)
BOOT grldr

Old Syslinux syntax for usage with SYSLINUX (you need to rename grldr to grldr.bs:
QUOTE
LABEL grub4dosboot
MENU LABEL GRUB4DOS menu (BOOT command)
KERNEL grldr.bs

Old Syslinux syntax for usage with ISOLINUX (you need to rename grldr to grldr.bin for ISOLINUX)
QUOTE
LABEL grub4dosboot
MENU LABEL GRUB4DOS menu (BOOT command)
KERNEL grldr.bin

So you see that you better can use the new Syslinux syntax.

Posted by: jaclaz Jul 20 2009, 09:45 AM

@Icecube
Very GOOD report! smile.gif clap.gif

I edited your post to better show which was the "old" and which is the "new" at first glance.

cheers.gif

jaclaz

Posted by: Icecube Jul 20 2009, 10:51 PM

@ jaclaz: Thanks

The "Load via SysLinux" section needs an update (part 2 rolleyes.gif ).

Loading it as regular boot file will work too. (You need the patched chain.c32, if you want to use it from ISOLINUX).

CODE
LABEL -
MENU LABEL GRUB4DOS menu (chain.c32 file=)
TEXT HELP
This entry will bring you to the GRUB4DOS menu.
ENDTEXT
COM32 chain.c32
APPEND file=grldr

Posted by: risolutore Jul 29 2009, 07:24 PM

if you want to test UFD with Grub4dos put this cmd file in the root of qemu dir alongside with qemu-win.bat

qemu-ufd.bat

CODE
REM Start qemu on windows UFD Boot.
@ECHO OFF
qemu.exe -L . -M pc -boot c -hda \\\\.\\physicaldrive1 -localtime

with this batch you can make a very portable test env for grub4dos ufd

Posted by: Icecube Jul 29 2009, 08:32 PM

QUOTE
\\\\.\\physicaldrive1

doesn't sound very portable to me. It will work when you have only one internal HDD, but if you have more than one, it won't work.

Posted by: risolutore Jul 29 2009, 08:59 PM

QUOTE (Icecube @ Jul 29 2009, 10:32 PM) *
doesn't sound very portable to me. It will work when you have only one internal HDD, but if you have more than one, it won't work.

Oh yes. I assumed only one fixed hd and one only external UFD, I have to admit it. We should use a sytem of variables, one related to the number of internal fixed disk and another with the number of UFD

Posted by: jaclaz Jul 30 2009, 07:27 AM

Additionally the number of back slashes needs to be checked:
http://www.boot-land.net/forums/index.php?showtopic=7650

http://www.boot-land.net/forums/index.php?showtopic=7650&st=2

jaclaz

Posted by: risolutore Jul 31 2009, 09:01 AM

I have read the posts regarding the number of backslashes, on 0.91 seems to be different from previus qemu ver

Posted by: tsetya Aug 4 2009, 04:20 PM

after a few experiment with vista boot manager, i've found an altenative (easy) way to add grub4dos entry to vista boot manager (and perhaps 2008/7). instead of adding entry to bcd directly, we can use boot.ini to add entry to vista boot manager.
to load grub4dos via vista boot manger:
methode 1. bootmgr>grldr.mbr>grldr
> create new file using text editor and save as boot.ini in vista partition and add
following entry. (or use boot.ini file from windows xp)

CODE
[boot loader]
[operating systems]
c:\grldr.mbr="grub4dos"

> copy grldr.mbr to vista partition and grldr/menu.lst to any supported partition

methode 2. bootmgr>ntldr>grldr
> create boot.ini file and add following entry
CODE
[boot loader]
timeout=10
default=c:\grldr
[operating systems]
c:\ntldr="ntldr"
c:\grldr="grub4dos"

> copy file grldr and ntldr from any windows xp to vista partition
> from vista boot manager choose "ntldr" to load ntldr
> from xp boot manager choose "grub4dos" to load grldr (or set timeout=0 to load grub4dos directly)

if vista not installed, also possible to use this methode. use vista formatted partition (partition boot sector calling bootmgr), copy file bootmgr and \boot\bcd from any windows vista (or dvd), then add boot.ini as above.
this methode will also work for others boot loader that are "not well known" by vista like plop boot manager and tboot if supported by bootmgr/ntldr.

hope this methode can be add to tutorial

Posted by: ktp Aug 4 2009, 04:32 PM

@tsetya
The grldr.mbr in step 1 is not necessary. As far as I know, when bootmgr finds the files ntldr and boot.ini on the same disk, it automatically adds an entry for ntldr (kind of dynamic entry to BCD). So you simply add entries to boot.ini (grub4dos, PLoP....) without even needing the lines "c:\ntldr="ntldr"").

Posted by: tsetya Aug 4 2009, 04:41 PM

that's not step 1, but two different way.
1. bootmgr>grldr.mbr>grldr
2. bootmgr>ntldr>grldr

bootmgr will read entry from boot.ini file even if there is no ntldr as loang as there are two line in boot.ini

CODE
[boot loader]
[operating systems]


all entry will be kept in boot.ini, so add/remove/edit entry just like in win xp. (no need bcdedit.exe to add/remove/edit entry, so you can edit vista boot manager entry from any os/live cd using text editor)

Posted by: Twilight Cruiser Oct 31 2009, 03:43 PM

Hi Diddy,

I like your guide very much, and it helped me a lot anytime I needed to set up my system from scratch!

Anyway, there are some issues I'ld like to read about: wink.gif

(1) It would be nice if there would be an explaining "walk through" for the existing example settings in the default menu.lst. Not all, but many of the things done there are a little miracle to me. Would be a nice help.

(2) Unfortunately, there's nothing mentioned about the possibility of using the UUID for identifying a partition. Using the UUID for selecting a boot partition helped me a lot when making boot entries for Ubuntu.

Hope I haven't overlooked any of these issues in the guide... - like the "booting from CD", where I was totally blind... biggrin.gif

Greetz & have a nice weekend + Halloween! smile.gif

Posted by: ireneuszp Feb 15 2010, 06:56 PM

grubinst-1.2-bin-w32-2008-12-30
http://bbs.wuyou.com/viewthread.php?tid=160226&extra=page%3D1

download:
http://www.uushare.com/user/marksu2006/file/2583098

http://grub4dos-ireneuszp.googlecode.com/files/grubinst-1.2-bin-w32-2008-12-30.zip

http://code.google.com/p/grub4dos-ireneuszp/downloads/list

wink.gif

Posted by: gbrao Feb 16 2010, 03:06 AM

My Chinese isn't too good, where exactly is the download link for 1.2 ?

Posted by: woebetide Feb 16 2010, 09:18 AM

QUOTE (gbrao @ Feb 16 2010, 03:06 AM) *
My Chinese isn't too good, where exactly is the download link for 1.2 ?



Download:
http://rapidshare.com/files/351291005/grubinst-1.2-bin-w32-2008-12-30.rar.html

Posted by: ireneuszp Feb 16 2010, 02:29 PM

GRUB4DOS SplashImage Creator



download:

splashimage.rar
http://docs.google.com/uc?id=0B6rhKRgmLefCNmRiNmY3MDYtNDRmMC00MTA0LWIzNDctYTc4YTdmNDhjN2Nk&export=download&hl=en
or
http://www.megaupload.com/?d=016WN2WQ

splashimage.zip
http://docs.google.com/uc?id=0B6rhKRgmLefCMGQ4NDZjZmEtMzg0NC00YjEyLWJhOTItODA1Y2JkOWQ1MmEy&export=download&hl=en
or
http://www.megaupload.com/?d=B4273BR3

wink.gif

Posted by: ireneuszp Feb 16 2010, 07:56 PM

GNU GRUB MD5 Encrypt Password Tool Ver0.0406



download:
http://docs.google.com/uc?id=0B6rhKRgmLefCYWFkMmU4YTYtMDlmMS00MTBlLTg1Y2YtZWJlM2Q5NWYzNzJl&export=download&hl=en
or
grubmd5p.zip
http://www.megaupload.com/?d=QA4WOR03

wink.gif

Posted by: maanu Feb 16 2010, 07:56 PM

QUOTE (ireneuszp @ Feb 16 2010, 02:29 PM) *
GRUB4DOS SplashImage Creator



download:
https://docs.google.com/uc?id=0B6rhKRgmLefCYTc5MTM3MTYtODYwNS00ZjE1LWJhNGYtNzYzMjY3MDhjM2E2&export=download&hl=en

wink.gif


link is broken i guess . file corrupt every i downloaded .

Posted by: ireneuszp Feb 17 2010, 11:37 AM

QUOTE (maanu @ Feb 16 2010, 08:56 PM) *
link is broken i guess . file corrupt every i downloaded .


new download links

splashimage.rar
http://docs.google.com/uc?id=0B6rhKRgmLefCNmRiNmY3MDYtNDRmMC00MTA0LWIzNDctYTc4YTdmNDhjN2Nk&export=download&hl=en
or
http://www.megaupload.com/?d=016WN2WQ

splashimage.zip
http://docs.google.com/uc?id=0B6rhKRgmLefCMGQ4NDZjZmEtMzg0NC00YjEyLWJhOTItODA1Y2JkOWQ1MmEy&export=download&hl=en
or
http://www.megaupload.com/?d=B4273BR3

wink.gif

Posted by: ireneuszp Feb 18 2010, 12:08 PM

grldr editer

download link:
http://www.megaupload.com/?d=9J84TRCI
or
http://docs.google.com/uc?id=0B6rhKRgmLefCNDY0NjYxMWMtMzRiNC00MTAzLTgxYjQtOThhM2Q1YTMyZjVh&export=download&hl=en

wink.gif

Posted by: Wonko the Sane Feb 18 2010, 12:23 PM

@ireneuszp
Have any of these files a homepage?

Or we just have to click on a link and get a file?

As an example, last one, contains a single .exe GRLDR.EXE.

Are people supposed to just double click on it?

Or can you post also a link to where it came from, or, a short description/howto?

This way less experienced people might be able to actually use it.

Again, for the last link:
GRLDR Editer is an editor for the embedded menu in grldr.
Start it, you will see two buttons with question marks (it is probably a Chinese originated app).
The top one is "Open".
The bottom one is "Save".
Click on the "Open" button, and choose a copy of grldr.
You will see the embedded menu in it.
Modify it as you wish.
Click on the "Save" button.


cheers.gif

Wonko

Posted by: maanu Feb 18 2010, 04:03 PM

the best Grldr editor is fbinst Tool . the one linked in above post has a bug , it changes the date of grldr to a specific old one . by the way it is from the author of fbinst tool too .


Posted by: mlt Apr 12 2010, 05:51 AM

It would be nice if grldr tried (hd0) in search for menu.lst as a last resort.

I followed alternative method 2 installing Grub4dos into my flash drive by renaming it to ntldr. I was surprised when I saw default menu instead of my menu.lst upon reboot. Flash was formatted as a single NTFS partition starting as sector 0 without MBR as it appeared to be.I was lazy to reformat it since it already had a lot of stuff. So I slightly modified grldr with editor for default menu to include root(hd0) as a first line instead of 'errorcheck off'. Default menu can be found at the very end of the grldr 0.4.4 Use overwrite mode of editor instead of default insert one. This workaround works fine for me though with some flickering in the beginning.

Posted by: www Apr 13 2010, 07:10 PM

Thank you to the creators and documenters of this very nice tool. I found it useful for setting up an XP/Fedora linux dual boot. For loading linux I did something that seemed easier and more maintainable to me than the documented process. When I installed Linux I asked that the boot information be written to the /boot partition and not the MBR. I was then able to boot linux using the chainloader as follows:

timeout 10

title Windows at (hd0,0)
root (hd0,0)
chainloader +1

title Linux at (hd0,2)
root (hd0,2)
chainloader +1

This way I can let XP own the MBR and not have to know what files linux needs or change them if the kernel gets updated. I don't know how many linuces this would work for, but it seems simpler for Fedora and if others agree, might be worth adding to the documentation. I could even make some suggested changes to the docs for submission to whoever is responsible if wanted. I'll check back in a few days and see if that is desired.

Keith I. (logged in generically)

Posted by: Wonko the Sane May 10 2010, 07:43 AM

QUOTE (www @ Apr 13 2010, 08:10 PM) *
This way I can let XP own the MBR and not have to know what files linux needs or change them if the kernel gets updated. I don't know how many linuces this would work for, but it seems simpler for Fedora and if others agree, might be worth adding to the documentation. I could even make some suggested changes to the docs for submission to whoever is responsible if wanted. I'll check back in a few days and see if that is desired.


Well, NO.
You have two separate partitions, each with it's own bootsector (or PBR) code, which you alternatively load through "something".
There are only three places where you can normally have boot code:
  1. the MBR
  2. the PBR (or boot record) of first partition (hd0,1)
  3. the PBR (or boot record) of second partition (hd0,2)


From what you report, the PBR on (hd0,1) is the XP PBR (invoking NTLDR) and the PBR on (hd0,2) is the "whatever" Linux installed (typically a GRUB - not grub4dos bootsector).

The "something" can then be residing ONLY in the MBR.

The default XP MBR can ONLY directly boot - without any choice possible - the PBR of the partition marked active in the partition table (also inside the MBR), no more, no less.

So, what you reported is either (no offence intended smile.gif) inaccurate or missing some steps/details.

The only "possible" explanation I can see right now is that you have three partitions and have grub or grub4dos in the third one. unsure.gif

Please try detailing the steps you took, which version of grub4dos you used (if any) or what version of GRUB (coming form Fedora) you are using, how you did the partitioning, etc., etc. smile.gif
FYI the normal booting process of a linux distro (most use GRUB) is:
BIOS->GRUB MBR->menu.lst->whatever
BIOS->Standard MBR->GRUB PBR of active partition->menu.lst->whatever
(things are slightly different if GRUB2 is used, but substantially the same)

The normal booting process of a XP is:
BIOS->Standard XP MBR->Standard XP PBR of active partition->NTLDR->BOOT.INI->whatever

cheers.gif
Wonko

Posted by: Lama May 23 2010, 03:45 AM

Hi! Quick question!

I installed 3 OSes on my system.
01. OSX
02. 7
03. XP
04. (X.IMG tongue.gif )

Now, once I'm done with installations, I want to save OS changed MBR to file and then boot it from Grub4Dos. Bootice allowed me to save huh.gif Can I boot those MBRs with this?

CODE
title find and load MBR01.SAV
fallback 1
find --set-root --ignore-floppies --ignore-cd /MBR01.SAV
map () (hd0)
map (hd0) ()
map --rehook
find --set-root --ignore-floppies --ignore-cd /MBR01.SAV
chainloader /MBR01.SAV
savedefault --wait=2

Posted by: Wonko the Sane May 23 2010, 09:00 AM

@Lama
Why don't you simply try it? unsure.gif

Usually this kind of things either:



From a pure syntax standpoint, you can use hook instead of rehook, and you may save some time by not re-searching for the file and directly establishing root on (hd0,0).

I am not at all sure that the () that you get is mappable to a whole (hd0). dubbio.gif

cheers.gif
Wonko

Powered by Invision Power Board (http://www.invisionboard.com)
© Invision Power Services (http://www.invisionpower.com)