CD-Loader (included in the build, starting with version 2.4.4, also available on the exchanger - download
CD-Loader 2k10 v.1.3) for cutting to mikrobolvanku (e.g. "business card", or 210Mb MD) or for use in CD-section of the stick, 1,3Mb resolution. In particularly difficult cases (no CD-Rom, USB-port), you can even use a screw. Loader task - to run one way or another assembly on a flash drive (or HDD). You can also test the 'live' new build, for example STEA - unzipped folder of assembly to any section (you can on the screw section) in the root of the drive, download the loader and test, it does not need to put the assembly on a flash drive or to bother with connecting the newcomer to the other assembly. FDD-the Loader performs exactly the same task, only for a floppy drive or FDD-section of the stick. The distribution is not included, but is available for download from the exchanger - Download FDD-Loader 2k10 v.1.3
. Launch options for the assembly on a flash drive:
1. Plop manager (select bootable media). Unfortunately, it does not always work.
2. Integrate the GRLDR loader to connect the assembly menu (options for running assemblies are provided).
3. Find and run the GRLDR (or GRUBLDR) loader assembly (variants for different assemblies).
4. It is possible to find and immediately start the OS loader (NTLDR and BOOTMGR), or boot from the MBR (brute-force HDD).
5. In addition, low-level memory tests (Memtest86 +, VMTCE), Kon-Boot password reset and HDT iron test have been added. The latter, by the way, is remarkable in that it shows the VESA-resolutions that are set up by vidyahi (that is, in practice, only these permissions can be installed in an assembly without a video driver ... or for Linux-based applications).
The main bootloader is the bootloader from the XP installation CD, and it immediately loads Grub. If unsuccessful attempt will return to the menu loader. Plus of loading with Grub is that you can boot this way even if the partition is inactive / non-bootable, that is, if the assembly is simply unpacked to any partition (to the root of the disk).Loader use options:
1. "Iron" does not support booting from flash drives, but there is a USB port.
2. No USB (burned / missing), but it is possible to pour the unpacked assembly onto the screw (via the network, or by a connected screw). The carrier itself with the assembly may not be bootable (i.e., the assembly is simply unpacked into the root).
3. There is a desire to test the new assembly live, but I do not want to install it on a flash drive instead of the current one.Additional Information:
So you can:but)
Burn the loader image onto a CD (as is). b)
Use the loader image for uploading to a CD partition of a flash drive (if you can create one using special utilities). At the same time, the assembly is installed on a regular partition of the same flash drive. Read more about the CD section on a flash drive: http://www.flashboot.ru/index.php?name=New...icle&sid=29
. In short: Windows do not work with partitions on a flash drive (ie, on a flash drive to create two partitions is possible, but Windows will "see" only one of them). But flash drives controllers can be configured to emulate a hardware CD-section, on which "poured" image CD-ROM. After such an operation, the flash drive in the system is available as two devices: USB-CDRom (with the loaded manner) and normal partition. This option allows you to boot without a problem on the PC, where the boot from the usual stick impossible (to boot from USB-CDRom, as a rule, is everywhere). The operation to change the stick rather difficult and is only recommended for those who know what to do. In principle, a CD-section can immediately fill the image Multiboot 2k10 (or micro), and this has its advantages - for example, the assembly will be invulnerable to viruses and can be downloaded everywhere. But also significant downsides - when updating the assembly will have to rebuild from scratch each time sections. And anti-virus software on CD-section was not updated. So, I think it is more convenient to use the loader - can be used with different assemblies in the ordinary section of the stick (or on the screw, CD / DVD), simply by updating them as necessary, and without changing the CD-key. at)
Use the loader image on the primary boot partition of the screw, having previously prepared it for the Grub4Dos loader.
Along the way, he showed an interesting use case loader - with its help it is convenient to test the assembly, not tinkering with the boot flash. Just unpack the assembly to any section (you can screw on the section) to the root directory. If the assembly is a "classic" GRLDR menu.lst or radically - it can be run directly loader by selecting the appropriate menu item. To eliminate the load "wrong" assembly (already installed on a flash drive, for example), you need to choose the item that is not compatible with the installed and compatible with the test. For example, with the loader mounted Micra GRLDR radically. So, you need to select the option to boot from menu.lst to root (if you want - just copy the pre-test assembly to the root of the menu with the same name).Practical advice on the use of the loader
(versions 1.4 and up)
0. Media number / starts from 0, i.e. The first partition of the first HDD is (hd0,0) /.
The number of the current media (the one from which the loader is loaded or the assembly is currently) is indicated in the header of the Grub4Dos main menu, after the name of the assembly. This will allow you to navigate the transition between different carriers. Ie, it is possible to boot from the CD and go to the flash drive, then download the assembly from the HDD ... and again return to the CD. Normally loaded from a flash drive or screw assembly should be represented as hd0, x.
1. Start Boot-manager PLOP
Start the boot manager Plop, which allows you to select the device to boot. In addition, it accelerates booting from USB on some computers (which do not support booting in USB 2.0 mode). When running from FDD / CD, it can be used to initiate a USB boot (if the BIOS does not have this option). It works, unfortunately, not on all versions of Bios, can "hang" the PC. But at the moment this is the only way I can "turn on" USB 2.0 when booting (if Bios itself does not).
2. Start NTLDR from HDD (Windows XP / 2000/2003)
Designed to find and run the bootloader Windows XP / 2000/2003 from the hard disk. If the boot loader is found, the disk with it becomes the first / (hd0) in Linux numbering / and NTLDR is transferred to the control.
3. Start BOOTMGR from HDD (Windows 7 / Vista)
Designed to find and run the bootloader Windows 7 (Vista / 8) from the hard disk. If the boot loader is found, the disk with it becomes the first / (hd0) in Linux numbering / and control is transferred to BOOTMGR. If the launch of several OSes is registered in the BCD boot menu, then it will be possible to start them.
Note: 5 *
4. Load MultiBoot / SV-Micro 2k10
The Grub4Dos 2k10 bootloader (2k10 / Grub4Dos / Grldr file) will be searched for on all available drives (flash drives / HDD / CD / DVD). If the build loader is detected, it will be started. This option also allows you to start the assembly, simply unpacked to the root of any HDD partition, regardless of the partition activity and its main bootloader (i.e., you can, for example, unpack the assembly into the operating system partition and run the assembly from this partition under the loader).
Note: 1 *, 2 *, 3 *
5. Load MultiBoot / SV-Micro 2k10
The file /2k10/syslinux/syslinux.cfg (Syslinux builds 2k10 menu) will be searched on all available drives (flash drives / HDD / CD / DVD). After the menu is found, the main loader of this media will be launched (Syslinux, Isolinux or Grub4Dos, depending on the build version).
Note: 1 *, 2 *, 3 *, 4 *
6. Load main Grub4Dos loader
Search in the root of all Grub4Dos boot media (file / GRLDR) and its launch. Designed to run assemblies, in which the GRLDR loader is in the root of the disk. It should work with a large number of assemblies, for example: Azjio, Ieshua, LexLive, Sonya, SysTools5, VasAlex, 2k10 (only version with Grub4Dos loader).
Note: 1 *, 2 *, 3 *
7. Load second Grub4Dos loader
Sequential search on all available disks and launching Grub-loaders for assemblies STEA (file Stea / Boot / Stldr), Ruslive (/ Grubldr), Hiren's (boot in HBCD / Grldr) and some others (Boot / Grldr, Boot / Grub4Dos / Grldr ). The first found option will be launched. The search order corresponds to the description order.
Note: 1 *, 3 *
8. Start drive with Grub4Dos menu
Search in the root of the Grub4Dos menu media (file / menu.lst) and launch this disk. It will work with all assemblies whose menu is in the root of the disk. Unlike the variant with the configuration, GRLDR will launch the main disk loader. That is, if the menu.lst file is copied to a disk with the installed OS, the OS will be launched, not Grub4Dos !!!
Note: 1 *, 3 *, 4 *
9. Start Syslinux (search /ldlinux.sys include / Boot & / Syslinux)
Search for Syslinux loader (search order: /ldlinux.sys, Boot / ldlinux.sys, Syslinux / ldlinux.sys, Boot / syslinux / ldlinux.sys) and start from this media. CD / DVD are ignored. The main media loader will start. Used to load various Linux builds.
Note: 1 *, 4 *
10. Start Isolinux (search /isolinux.bin include / Boot & / Isolinux)
Search all Isolinux boot loaders (search order: /isolinux.bin, Boot / isolinux.bin, Isolinux / isolinux.bin, Boot / isolinux / isolinux.bin) and start the main media loader. If the main boot loader cannot be started (for example, Grub4Dos may not start the CD bootloader!), The found isolinux.bin is launched. It can be used to run various OS and Linux builds (on HDD, isolinux.bin is used only as a marker!, On CD / DVD, it will be launched).
Note: 1 *, 2 *, 3 *
10. Boot MBR of Hard Disk 1-2-3-4-5
An attempt will be made to boot from the active partition of the first HDD. If the disk is non-bootable, then from the second, third, fourth and fifth. Disk swapping is not performed, i.e., Windows XP will boot only if it is on the first HDD (to download it, it is better to use the option with direct disk indication). Vista / 7/8 / Linux OS should boot.
Note: 5 *
11. Boot MBR of Hard Disk 5-4-3-2-1
An attempt will be made to boot from the active partition of the fifth HDD. If the disk is non-bootable, then from the fourth, third, second and first. Disk swapping is not performed, i.e., Windows XP will boot only if it is on the first HDD (to download it, it is better to use the option with direct disk indication). Vista / 7/8 / Linux OS should boot.
Note: 5 *
12. Boot any HDD & Partition
To boot from the disc. Depending on the indication, the download is made from the master boot record (valid for all media), or only from the desired carrier section (of the PBR, only for the HDD and flash drives, translated in HDD mode). Unlike in the name: cd0 or hd0,1 (the last digit after the decimal point indicates the section used by Linux-numbering - ie, 0). Before loading is carried out "sharing" disk on hd0 (it does not work for floppik fd and compact cd) and the loading of the disc. If you specify a particular section - will then be booted from partition. If the disc is incorrect, there is a return to the menu. If it is true and is in the disc loader - loading the disc (for CD / DVD can not be guaranteed). Before starting the listing shows all available media to the system, if you press 'Enter' without entering or 'Esc' - exit back to the menu without loading.
Note: 1 *, 5 *[i]Notes:
1 * For HDD and Flash (in HDD mode) assembly options, the assembly disk will be installed first / (hd0) /. For CD / DVD and Fdd (or flash drives recognized by Bios as Fdd), the disc will remain the same. Since WinRE based on XP / 2003 cannot вЂњbootвЂќ from disks other than hd0 / cd (read error winnt.sif), loading PE assemblies based on XP from flash drives (aka floppik) is impossible. RE builds based on 7s should be launched (not tested!), And various DOS and Linux utilities should also work.
2 * For the loader version integrated into the assembly, the current disk (from which the assembly was actually loaded) will be skipped (ignored) during the search.
3 * Search priorities (descending): HDD, Flash, CD / DVD, Fdd.
4 * You can use the specified file as a marker. That is, place a dummy file (the contents do not matter), if necessary, at the specified path (for example, D: \ 2k10 \ syslinux \ syslinux.cfg). Then, when using the boot option with a marker, you can boot from the вЂњrequiredвЂќ disk (provided that the marker is no longer repeated on other disks or in the assembly вЂ” otherwise the first found disk with a marker will be loaded).
5 * It is possible that Windows 7 will start unactivated during such a boot (it depends on the activation method).