Author: huayting on 1-02-2016, 01:35
MultiBoot 2k10 5.20 Unofficial
MultiBoot 2k10 5.20 Unofficial | 4.01 GB

Multiboot disk system administrator, based on the loaders BOOTMGR (Windows 8.1.1), Isolinux / Syslinux v.4.06 and Grub4Dos v.0.4.5c. The disc consists of a large number of products, obedinёnnyh shell with vozmozhnostyu download c CD / DVD, USB Flash Drive, USB-HDD and a conventional HDD.
The main purpose - preparation of HDD, OS installation (with vozmozhnostyu install Win 2000 / XP / 2003 / Vista / 7 - Utility WinNTSetup, installation packages in the assembly are not included!), Creation / deployment system images, restore / copy data, resuscitation operating system recovery download, clearing the OS from viruses / trojans and blockers / pornobannerov, testing the basic components of MS, and more. There is a support network vozmozhnostyu to the Internet and multimedia support. There vozmozhnostyu use most of the program from the assembly as a "portable" (fully portable they are not, it's just a self-extracting in TEMP-Marketing directory with autoenrollment) and convenient way to connect software package assembly for use in a conventional OS or other PE-assemblies.
How to create a bootable DVD or USB-Flash / USB-HDD

1. For CD / DVD:
You will need a program for recording images - for example, Nero Burning ROM. Run the program, Recorder -> Save image, specify the image file, make sure that it was noted "Finalize disc" and write method "Disc-At-Once (DAO)". The disc recording with the other settings will not boot! For Nero also recommended "Enable generation of short Lead-Out" (File -> Options -> Expert Features), it can reduce the recording time to speed up the recognition time of the compact and slightly increase the "capacity" blanks. Writing Speed ​​- the minimum reasonable. I recommend 8-16h for CD-ROM drive or 4 - for the DVD. The principle is: slower write -> faster (reliable) reads.
You can also use other programs, allows you to record images (for example, UltraISO, Alcohol 120, ...).
2. Installation of the assembly to the stick:

Attention!!! Many utilities (such as the standard windows format) are not completely format the flash drive, they see that it is, and do not touch the areas that they appear to be correct. Therefore, it is advisable to clean the stick, eg by RMPrepUSB, HDD Low Level Format Tool or run a test to record any of the utilities FlashNull, Check Flash, HD Tune Pro, Flash Memory Toolkit Pro, it is guaranteed to kill the layout and make the program format to make everything from scratch . After cleaning, be sure to "distort" the stick, and then format it to perform a test with the CheckDisk (2k10 \ Programs-2k10 \ HDD-Utilites \). When bugs repeat cleaning stick and formatting. If you use formatting with BootICE -> Parts Manage -> ReFormat USB disk, it is unnecessary operations. BootICE when formatting automatically makes cleaning.
2.1 USB flash drive, you must first format (Note: All data on a flash drive will be destroyed). It is necessary to flash drive was seen as the Bios USB-HDD, from which you can boot the operating system. If the flash drive / propeller is already used as a boot, you can skip this item. Stick is recommended to format a FAT32 (in the file system it works longer and more stable), but if necessary, you can use NTFS (faster than "kills" USB flash drive requires a "safe removal", but supports files larger than 4GB). This is best done with the help of RMPrepUSB (is in the assembly by way of 2k10 \ Programs-2k10 \ Flash-Utilites \ RMPrepUSB P2Start.exe or from the menu "Programs 2k10 \ USB-Flash Utility"). This utility creates as close as possible to the screw geometry on a flash drive. If you check Boot as HDD (C: 2PTNS), on a flash drive will be created two partitions (half the minimum size for maximum imitation screws). But I do not recommend using this option, this flash drive will "hang" appliances (TVs with flash player, players, etc.). It is enough to do, as shown.
Alternative methods for formatting the stick (instead of 2.1)

2.1.1 Format the USB flash drive using the HP USB Disk Storage Format Tool (is in the assembly by way of 2k10 \ Programs-2k10 \ Flash-Utilites \ HPUSBFW \ or in the menu under USB-Flash utility), you can use the quick format. On some PCs may not work (on a flash drive is connected properly boot). If it works, it can be used for FAT32, and for NTFS.
2.1.2 Format the flash drive using BootICE (2k10 \ Programs-2k10 \ Flash-Utilites \ BootICE \) ... so recommended format: BootICE (select the USB flash drive) -> Parts Manage -> ReFormat USB disk -> USB-HDD mode ( Single Partition) - Align to sectors: 2048 -> Next -> FAT32 (NTFS) -> OK. The same does not always work, I - the loader is connected correctly only on NTFS.

2.1.3 Using FBInstTool (2k10 \ Programs-2k10 \ Flash-Utilites \ FBInstTool \). Utility to format the custom flash drives, creates a structure of a special type (USB-ZIP or USB-HDD). Select the USB flash drive (focus on the size!), Choose formatting options: -raw -force, format.
2.1.4 Using scripts FlashFormat_2k10_FBinst (2k10 \ Programs-2k10 \ Flash-Utilites \ FBinst-FF \). Utility to format the custom flash drives, creates a structure of a special type (USB-ZIP + USB-HDD). Select the USB flash drive (focus on the size!), Use a method 7. RAW FORMAT, to format.
The script automatically reconnects the stick so the "distorting" her after formatting is not necessary.
2.1.5 To format a USB drive with automatic loader XORBOOT connection is recommended to use the scripts:
a) FlashFormat_2k10_FBinst - Method 1 (flash card up to 2GB for FAT16) or Mode 2 (stick 4-32Gb under FAT32). Support USB-ZIP. On older systems will be loaded only WinXP-PE.
b) FlashFormat_2k10_FBinst - way to 5 (up to 2GB flash drive for FAT16) or a method 6 (stick 4-32Gb under FAT32). Support USB-ZIP + USB-HDD. On older systems will be loaded only Win7-PE.
in) FlashFormat_2k10_RMprep - apply if necessary support NTFS, use method 5 (flash drives of any size). Support only USB-HDD.
Scripts automatically reconnect the USB flash drive so the "distorting" her after formatting is not necessary.
Scripts can be used under the operating system and under the assembly (either), they will automatically be connected XORBOOT in the MBR (sector 63, PBR is ignored). Immediately after formatting the USB flash drive can be checked for bootable (startup XORBOOT) under any Dev (eg, MobaLive).
2.2 Formatting to remove the flash drive and re-connect.
2.3 It is necessary to add to the stick assembly files - a folder 2k10, EFI and file P2Start.exe. Bootmgr file on a flash drive / HDD is not used, so it is not copied. They can be unpacked from an image using 7-zip, WinRar, Total Commander, FAR, UltraISO or copy any of the installed Dev for CD / DVD drive in the virtual root of the stick. If reformatting the stick produced scripts - bootable media ready (boot XORBOOT connected).
Faster will first extract the contents of the image to a temporary location on the screw, and then copy all of it on a flash drive - repeatedly checked experience. You can also mount an image as a virtual CD-ROM and copy from it - the effect is the same. If the creation of the stick is made under the loaded assembly, convenient to mount the image using ImDisk (RMB on the way, "mount ...").
The primary boot loader, if desired, you can set / change at any time in the normal operating and under any PE-assembly (using a utility SetLDR-2k10 folder 2k10).
2.4 Using a bootloader Syslinux / Grub4Dos / BOOTMGR / XORBOOT using SetLDR-2k10 for flash drives / HDD:
It is necessary to make the flash drive bootable. Go to the folder 2k10 \ on the flash drive, run the utility SetLDR-2k10 and set the desired boot from the assembly 2k10. Checkbox (right inscriptions Xorboot) - allows you to install additional XORBOOT intermediate loader for BOOTMGR / GRLDR (it will immediately download the latest). Also, the utility checks the startup (if enabled UAC), the presence of downloaders and allows you to set an active partition (if necessary).
3. Installation on USB / USB-HDD / HDD:
3.1 Screw you want to format any program on the breakdown of HDD, create a primary active / boot partition is the right size (at least 2GB). Select FAT32 file system, but, if necessary, can be used and NTFS.
If the HDD is used for parallel data transfer it is convenient to break it this way: make two primary partitions (if necessary - can be more partitions, but always the first and last, under the assembly - primary, in the middle can be logical). The first format the partition to fit your needs in FAT32 / NTFS / ..., the size of the capacity of the screw minus 3-5Gb. The second (and the last section, for assembly) - be sure to do the active / boot, under FAT32. This section establishes the assembly. Why so? The most convenient way - if you want to delete the partition with the assembly, or, conversely, increase the place under this section, the operation will be quickly made using virtually any manager disks without data loss in the first sections.
P.S. When used to NTFS boot loader Syslinux may be problems with downloading, it is recommended to do a breakdown / repartition USB / HDD using Paragon HDM.
3.2 is copying the assembly to the active partition HDD (similar to 2.3), and connect the loader (item 2.4).
Alternative methods use boot Grub4Dos using BootICE (2012) for flash drives / HDD:

1. The loader WEE. Is placed entirely in the MBR (PBR ignored), covers 63 sectors (non-standard!). There are built-in menu (you can edit during installation), allows you to find and load the NTLDR, BOOTMGR, GRLDR, ... Due to the originality is not recommended for universal stick, but very useful, for example, as a Boot-manager on the system drive.
2. GRUB4DOS in the MBR (PBR ignored), covers 18 sectors (non-standard!). Immediately starts GRLDR. In connection with the non-standard is not recommended for universal stick.
3A. USB-HDD + in an MBR, GRUB4DOS residence in the PBR. Not a bad option, and placed works on most flash drives, particularly suited for FAT32.
3B. USB-HDD + in an MBR, NTLDR residence in the PBR. When installing or rename boot rough in the root directory on the NTLDR, or specify the name of GRLDR at registration in PBR (see. In the picture). Not a bad option, similar to 3A.
3C. USB-HDD + in an MBR, BOOTMGR residence in the PBR. When installing or rename boot rough in the root directory on BOOTMGR, or specify the name of GRLDR (or GRUBMGR for assembling) for registration in PBR. Not a bad option, similar to 3A.
4B. Windows NT 5.x MBR in an MBR, NTLDR residence in the PBR. When installing or rename boot rough in the root directory on the NTLDR, or specify the name of GRLDR at registration in PBR (see. In the picture). A good option for bootability on different hardware, but the stick works rarely (depending on the chip stick?), Especially under FAT32.
5C. Windows NT 6.x MBR in an MBR, BOOTMGR residence in the PBR. When installing or rename boot rough in the root directory on BOOTMGR, or specify the name of GRLDR (or GRUBMGR for assembling) for registration in PBR. A great option for bootability on different hardware, some USB flash drives may not work under the FAT32 (depends on chip flash drive?). Implemented utility SetLDR-2k10.
My advice: for flash drives, if you do not need to transfer files larger than 4GB to try to install the utility SetLDR-2k10, check the download in MobaLive. If you do not work - use NTFS + SetLDR-2k10 or installation option using BootICE - 3C (3A, 3B - they are virtually identical) to FAT32.

List programs in assembly
USB-driver PLOP v.5.0.11
C9PE Plus Pack (@ conty9) 2k10
WinPE 7x86 Live (@ Xemom1) Special Edition 2k10
WinPE 7x64 Live (@ Xemom1) Special Edition 2k10
WinPE 8x86 Live (@ Xemom1) Special Edition 2k10
WinPE 8x64 Live (@ Xemom1) Special Edition 2k10
Parted Magic 2016.01.06 / Linux Live-CD /
Linux-version of Acronis DDH v.12.0.3270 (rus)
Linux-version of Acronis TIES v.9.7.8398 (rus)
Linux-version of Acronis TI Premium 2014 v.17.0.6673 (rus)
Linux-version of Acronis Universal Restore v.11.5.38938 (rus)
Linux-version of Acronis B & R Advanced v.11.5.39029 (rus)
Linux-version of Acronis Snap Deploy v.5.0.1416 (rus)
Linux-version of Acronis Align Tool for WD / Hitachi v.2.0.154 (eng)
Linux-version of Paragon HDM 12 v. (rus)
Linux-version of Paragon HDM 15 v. (rus)
Linux-version of MiniTool Partition Wizard Server Edition v.9.1 (eng)
Linux-version of R-Studio Emergency v.7.1.555 (eng / rus)
Linux-version of R-Drive Image v.6.0.6003 (eng / rus)
Linux-version of TeraByte Image for Linux v.2.98 (eng)
DOS-version of Acronis TIES v.9.7.8398 (rus)
DOS-version of Paragon HDM 15 v. (rus)
DOS-version of Hiren's Boot CD 15.2 (rus)
Big set of different DOS-utilities, and much more.

Install Windows XP / 7/8/10 of the assembly
In the assembly, there are different ways to install Windows.
Some installation methods, including using addons, painted in the file 2k10 \ GRUB4DOS \ WINXP.txt, as well as in 2k10 \ Programs-2k10 \ -Help- \ 2k10-FAQ.chm. Consider one of them.
Installing Windows 7/8/10 with the stick from my _WIN \
Download and unzip the addon ~ 2k10-WIN7-10 ~ to stick / HDD. Folder _WIN \ have to be at the root of the stick / HDD. Copy out of its way to Windows 7/8/10 Sources folder of the file install.wim / install.esd / install.swm the appropriate subfolder according to the wording of add Windows 7/8/10:
for Windows 7 x86 ---> folder _WIN \ 7x32
for Windows 7 x64 ---> folder _WIN \ 7x64
for Windows 7 x86-x64 ---> folder _WIN \ 7AIO
for Windows 8 x86 ---> folder _WIN \ 8132
for Windows 8 x64 ---> folder _WIN \ 8164
for Windows 8 x86-x64 ---> folder _WIN \ 8AIO
for Windows 10 x86 ---> folder _WIN \ 1032
for Windows 10 x64 ---> folder _WIN \ 1064
10 for Windows x86-x64 ---> folder _WIN \ 10AIO
These subfolders are registered in the startup script installations boot8x86.wim and boot8x64.wim.
If you do not have enough of these sub-folders, then by their example can create their own and rename them as you prefer, and then have to run additional installation utility 78Setup.
The number of additional distribution is unlimited.
Throw, if any folder - $ OEM $ and the file unattend.xml (important for assembly Windows).
The menu / submenu Grub4Dos "DOS-install Windows" add-on will appear automatically.
The BCD-menus and menu EFI BCD-he was registered.
_WIN Folder with the installation files / Windows images can be in the root of any drive / partition your HDD / USB-HDD.
You can also set file install.wim / esd / swm by 78Setup in the window by pressing the "Select archive manually" (file install.wim / esd / swm) for installation.
Add your installation image folder in Windows 7/8/10 _WIN, _ISO, 2k10 \ User.Image.
The first image in the list will be displayed in the window 78Setup.
The remaining images can be selected and run by pressing the "Select an image by hand."
C using x86 boot loader install Windows every bit. Not supported EFI / UEFI.
C using x64 boot loader is installed only x64-bit Windows, and only to the disk layout GPT. Supported by EFI / UEFI.
If you do not need the installation of EFI / UEFI, it can be used for all installations is only one x86 boot.
Detailed instructions for the addon itself neofitsialki ~ 2k10_Unofficial-WIN7-10 ~ can be found here.

Differences from author build
The unofficial version is different from the original design and the content (added some utilities, which the author considers excessive for assembly / removed in the author's version or it did not include /), leaving the Linux utility is slightly different set of dos utilities present menu gopher, in assemblies WinPE by Acronis DDH. It is also common in the informal version of the update includes all copyright (at the time of assembly neofitsialki).

Author conty9 for kindly providing assistance in updating its assembly Multiboot 2k10 DVD / USB / HDD to the current version.


Dear visitor, you are browsing our website as Guest.
We strongly recommend you to register and login to view hidden contents.

Would you like to leave your comment? Please Login to your account to leave comments. Don't have an account? You can create a free account now.

Register | Forgot Password
Link 1
Designed by
Go Daddy Web Hosting! A completely unique experience - only  $1.99 / mo from Go Daddy! - 468x60