Hello all, I'm attempting to use this tutorial to build a bootable flash drive, and usually it works, but we just ordered a bunch of 4GB mini flash drives and not so much. It is the Corsair voyager mini. Well, when I try to run the Grub4DOS installer (the GUI, not command line) on it I get a 'Invalid partition table, if you still want to install, use the -skip-mbr-test'. I'm unsure how to continue from here. I apologize if I missed an older topic on the same thing. I'm using Grub4DOS Installer 1.1 2008-01-01 and Grub4DOS 0.4.4 2008-11-19, Windows XP Professional SP3. Thanks for any help, sco.
Try using another method to format the stick, before using grub4dos, such as the HP utility, or fuwi's batch It may work or it may not. On some sticks it is necessary to wipe first few sectors. A similar thread with some attempts to be made is here: If you cannot succeed, attach a HDhacker made copy of your MBR (compressed in a.zip or.7z arrchive) and I'll try have a look at it. November 2008 is a bit oldish release (nothing related to your problem, but you should get latest.
Jaclazjaclaz, fuwi's solution worked for me, thank you for the help.
I installed Windows XP on a VMware virtual disk with NTFS. From NT bootloader (boot.ini) I could start a well working grub4dos. So I made another virtuel Windows XP and this time I used FAT32 (fast) format for the XP installer. This time I am getting missing MBR-helper?
![]()
(With grubinst-1.1-bin-w32-2008-01-01.zip and grub4dos directly in MBR it`s also working, but I want to start from NT bootloader.) What`s the problem? How can I solve it? You did not have a clear description on the line used in BOOT.INI, but I am guessing you might have employed the GRLDR.MBR. The usage of GRLDR.MBR in BOOT.INI is undocumented and only some GRLDR.MBR versions could be used in this way. Only those GRLDR.MBR files that have exactly 8192 bytes in size can be successfully used in BOOT.INI. You should use GRLDR instead, as mentioned in the readme, just like this: C: GRLDR=.
GRLDR.MBR is intended to work with BOOTMGR of VISTA. You may also try installing by hand the GRLDR.MBR onto the MBR track, that is, the first track on the hard drive. But BE CAREFUL not to mess up your hard drive partition table!!!! See readme for details. The line in boot.ini is always C: grldr.mbr='Start GRUB4DOS' like the grub4dos wiki (English dokumentation) wants it.
(1) Filesystem NTFS / FAT32: grub4dos in MBR - grub4dos - working (I done that just for testing.) - (2) Filesystem NTFS: NT Bootloader in MBR - boot.ini - gldr.mbr - grub4dos - working! - (3) Filesystem FAT32: NT Bootloader in MBR - boot.ini - gldr.mbr - grub4dos - not working! When does the 'missing MBR helper' message appear? When booting the MBR or after GRLDR has been chainloaded by NTLDR/BOOT.INI?
It happens only in case of (3). Gldr.mbr chainloaded by NT bootloader. PS: The GRLDR only seams to work.
This was undocumented. The method with grldr.mbr was in the grub4dos wiki. Antamedia hotspot enterprise full version crack download.
![]()
PS: The GRLDR only seams to work. This was undocumented. Absolutely NOT. Read the file grub4dosreadme.txt: Since version 0.2.0 the recommended way to boot: Update 1: Version 0.2.0 also brings out a new thing, GRUB for NTLDR, which could be used to boot into GRUB from the boot menu of Windows NT/2000/XP. Copy GRLDR to the root directory of drive C: of Windows NT/2000/XP and append to C: BOOT.INI this line: C: GRLDR='Start GRUB' That will be done. The GRLDR should be in the same directory as BOOT.INI and NTLDR. Note that BOOT.INI is usually hidden and you must unhide it before you can see it.
The filename GRLDR shouldn't be changed. If GRLDR is in a NTFS partition, it should be copied to the root directory of another non-NTFS partition(and likewise should the menu.lst file be).
If GRLDR is compressed, e.g., in a NTFS partition, it will not work. Even if the drive letter of this disk has been changed to other than C by the Windows device manager, it seems you still have to use the letter C here in BOOT.INI, otherwise, NTLDR will fail to locate the GRLDR file.
And what's more, if you are booting NTLDR from a floppy, you will have to write the GRLDR line in A: BOOT.INI like this: C: GRLDR='Start GRUB' and shouldn't use the letter A like this: A: GRLDR='Start GRUB' (Note that in the case when BOOT.INI is on floppy A, the notation 'C: GRLDR' actually refer to the file A: GRLDR). Please find (apart the wiki) a single post on this or on 911cd board the uses C: grldr.mbr I don't know who wrote the article on the wiki, but maybe (having been 'last modified 06:30, 23 July 2007') it refers to an old version of grub4dos (0.4.2?) where both ways worked. I had a problem of my own with FreeDOS where NTLDR tried to boot FreeDOS directly even though I was an idiot and decided to install GRUB. So, the FREEDOS.BSS file NTLDR tried to load couldn't find KERNEL.SYS because (I guess) FREEDOS.BSS and KERNEL.SYS were not in the MBR. So I changed the line in BOOT.INI to: C: GRLDR='FreeDOS' Which corrected the problem.
Grub4dos Multiboot
However, I tried to boot the FreeDOS GRUB from my main GRUB (my computer's boot sequence is a clusterf. of Ubuntu, Windows 2000 Advanced Server, FreeDOS with Windows 3.1, and Damn Small Linux that I can't find to boot from any of the three or four bootloaders on my computer) via the command line. I first set the root partition (the one with Windows 2000 and FreeDOS): root (hd0,0) Then, I figured 'okay so I'm booting into another GRUB. That's a multiboot.'
, thus giving me this line: multiboot /grldr (I don't remember the exact syntax) Finally, I issued the boot command. The result: FreeDOS' GRUB complained about a 'missing MBR-helper'. Wierd that I have the OPPOSITE issue. I'm gonna take a look at the FreeDOS menu.lst and figure out if its different. That way I can just bypass NTLDR when loading FreeDOS by booting it from the main GRUB (right now it has a 'FreeDOS' menu item that loads NTLDR).
Grub4DOS is a boot manager that can be easily installed to a flashdrive or hard drive (internal or external). It allows booting multiple operating systems directly as well as booting into bootable partitions. For the purpose of this guide, Grub4DOS will be used to setup a flashdrive to boot the Acronis Resuce Media. This can be done by booting to the partition on the flashdrive (as setup by the Acronis Media Builder program) or by directly booting the Acronis ISO file.
When you use the ISO method, you can put as many Acronis ISO images as required on the same flashdrive. This allows you to easily be able to boot into True Image Home 9, 10, 11, 2009, Echo Workstation, etc. By just selecting the desired menu entry. Either of these methods work equally well on flashdrives.
However, if using a USB hard drive or internal drive, the ISO method is strongly recommended. This is because you can’t use the Acronis Media Builder program to properly create a bootable partition on a non-flashdrive device (it must be prepared manually). If you are not setting up a flashdrive, use any references to flashdrives in the instructions as references to your destination drive.
For example: You can setup Grub4DOS on a secondary internal drive and then boot into it by using your BIOS’s boot menu and selecting to boot that drive. This allows easy access to your recovery media without needing to plug in another drive or insert a CD. While it is always recommended to have backups of any important data before making any changes to your drives, installing Grub4DOS is not a destructive procedure. Existing partitions and data on the destination drive should not be erased or corrupted in any way. This method will not work properly with devices other than flashdrives unless special steps are done to create a bootable partition on the device. If you are trying to create a bootable USB hard drive or an internal drive for your Acronis Media, the ISO method (Section 3) is strongly recommended.
Grub4dos Installer 1.1 Zip![]()
Using this method, Grub4DOS just boots to the boot sector of the partition on the flashdrive to start the Acronis Media. This is very similar to using a standard bootable flashdrive. You can only have one version/build of your Acronis Media on the flashdrive. Please note that if the flashdrive’s partition table or structure is non-standard, the Acronis Media may have a problem booting using this method just as it would using a non-Grub4DOS MBR. There are only two steps needed to use your Grub4DOS flashdrive in this fashion. First, run the Acronis Media Builder on the flashdrive as you normally would. This will install the proper boot sector code to the partition and copy all necessary files to the flashdrive.
Second, create the Grub4DOS menu.lst file with the entry to start the Acronis Media. The menu.lst file is a plain text file created using the Windows Notepad program.
(Please note that the filename is MENU.LST. In the extension, it’s a lower-case L, not a one.) This file must be located in the root folder of the flashdrive. Start the Notepad program and type (or copy and paste) in the following text. The ability to boot ISO files directly is one of the newer features of Grub4DOS.
Grub4dos Win 10
It is still a work in progress and has problems with some types of ISO files. However, in my use and testing, it hasn’t had any problems with the Acronis ISO files. The flexibility allowed by being able to boot the ISO file directly makes keeping multiple versions and/or different builds on the same flashdrive an easy task.
Adding them is as simple as putting the ISO file on the flashdrive and adding the menu entry to boot it. As with the partition method, there are only two steps needed to use your Grub4DOS flashdrive in this fashion. First, run the Acronis Media Builder. However, instead of specifying the flashdrive as the destination device, select to create an ISO file. You can save the ISO file directly to the flashdrive if you wish. Second, create the Grub4DOS menu.lst file with the entry to start the Acronis Media. The menu.lst file is a plain text file created using the Windows Notepad program.
(Please note that the filename is MENU.LST. In the extension, it’s a lower-case L, not a one.) This file must be located in the root folder of the flashdrive. Start the Notepad program and type (or copy and paste) in the following text. Download To update this flashdrive to a different version or build of the Acronis Media, just rerun the Media Builder program and save the new ISO file to the flashdrive. If you are replacing an existing ISO file, no other changes are needed. If you are adding an ISO file, edit the menu.lst file and add the new menu entry. For example: If you want to add your True Image Home 10 build 4,942 ISO (ti-10-4942.iso) to the flashdrive, you would put the ISO file on the flashdrive and add the following menu entry.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |