Ich kann dir nur empfehlen mal in das Handbuch von grub zu schauen:
Diese Dateien sind im Verzeichnis /boot/grub gespeichert und hier wird deren Funktion erklärt. Der grub kann nicht jeden Betriebsystemkern direkt starten.
/boot/grub$ dir -l
insgesamt 196
-rw-r--r-- 1 root root 197 2007-09-22 22:35 default
-rw-r--r-- 1 root root 15 2007-09-22 22:35 device.map
-rw-r--r-- 1 root root 7584 2007-09-22 22:35 e2fs_stage1_5
-rw-r--r-- 1 root root 7424 2007-09-22 22:35 fat_stage1_5
-rw-r--r-- 1 root root 8192 2007-09-22 22:35 jfs_stage1_5
-rw-r--r-- 1 root root 4258 2008-02-11 22:03 menu.lst
-rw-r--r-- 1 root root 4238 2008-02-11 21:59 menu.lst~
-rw-r--r-- 1 root root 6848 2007-09-22 22:35 minix_stage1_5
-rw-r--r-- 1 root root 9280 2007-09-22 22:35 reiserfs_stage1_5
-rw-r--r-- 1 root root 512 2007-09-22 22:35 stage1
-rw-r--r-- 1 root root 108360 2007-09-22 22:35 stage2
-rw-r--r-- 1 root root 8904 2007-09-22 22:35 xfs_stage1_5
http://www.gnu.org/software/grub/manual/grub.html#Images
10 GRUB image files
GRUB consists of several images: two essential stages, optional stages called Stage 1.5, one image for bootable CD-ROM, and two network boot images. Here is a short overview of them. See Internals, for more details.
stage1
This is an essential image used for booting up GRUB. Usually, this is embedded in an MBR or the boot sector of a partition. Because a PC boot sector is 512 bytes, the size of this image is exactly 512 bytes.
All stage1 must do is to load Stage 2 or Stage 1.5 from a local disk. Because of the size restriction, stage1 encodes the location of Stage 2 (or Stage 1.5) in a block list format, so it never understand any filesystem structure.
stage2
This is the core image of GRUB. It does everything but booting up itself. Usually, this is put in a filesystem, but that is not required.
e2fs_stage1_5
fat_stage1_5
ffs_stage1_5
jfs_stage1_5
minix_stage1_5
reiserfs_stage1_5
vstafs_stage1_5
xfs_stage1_5
These are called Stage 1.5, because they serve as a bridge between stage1 and stage2, that is to say, Stage 1.5 is loaded by Stage 1 and Stage 1.5 loads Stage 2. The difference between stage1 and *_stage1_5 is that the former doesn't understand any filesystem while the latter understands one filesystem (e.g. e2fs_stage1_5 understands ext2fs). So you can move the Stage 2 image to another location safely, even after GRUB has been installed.
While Stage 2 cannot generally be embedded in a fixed area as the size is so large, Stage 1.5 can be installed into the area right after an MBR, or the boot loader area of a ReiserFS or a FFS.
stage2_eltorito
This is a boot image for CD-ROMs using the no emulation mode in El Torito specification. This is identical to Stage 2, except that this boots up without Stage 1 and sets up a special drive `(cd)'.
nbgrub
This is a network boot image for the Network Image Proposal used by some network boot loaders, such as Etherboot. This is mostly the same as Stage 2, but it also sets up a network and loads a configuration file from the network.
pxegrub
This is another network boot image for the Preboot Execution Environment used by several Netboot ROMs. This is identical to nbgrub, except for the format.
Der Acronis kann wahrscheinlich den Windowskernel nicht direkt starten und startet wie grub (Chain-loader) nur den ersten Sektor der Windowspartition.
Deswegen wirst du auch den Umweg über den Vista Bootmanager nicht umgeben können.
Das Wichtigste für einen Anfänger wäre die Konfigurationsdatei /boot/grub/menu.lst genauer kennenzulernen, weil da das Startmenü von grub konfiguriert wird.
PS: Hier ist nochmal erklärt welche Betriebsysteme der grub direkt starten kann
http://www.gnu.org/software/grub/manual/grub.html#Loading-an-operating-system-directly
Alle anderen Betriebsysteme wie Windows können nur indirekt gestartet werden, in dem mit Hilfe des Chain-loaders der erste Sektor der jeweiligen Betriebsystempartition (Laufwerk C: bei Windows) gestartet wird. Ich nehme mal an, weil das Binärformat von Windows und Linux total verschieden ist, kann der grub (und auch der Acronis Bootmanager) den Windwskernel (oder der Bootmanager von Acronis den Linuxkernel ) nicht direkt starten. Im Handbuch wird aber auch der Hinweis gegeben das man nicht unbedingt den Betriebsystemkernel direkt starten soll und lieber mit Hilfe des Chain-loaders den Betriebsystemkern indirekt starten soll.
KarstenW
Manfredtiel
