Multiboot System Administrator disc is based on bootloaders 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 vozmozhnost download c CD / DVD, USB Flash Drive, USB-HDD and conventional HDD. The main purpose - HDD preparation, OS installation (with vozmozhnostyu install Win 2000 / XP / 2003 / Vista / 7 - WinNTSetup utility installation packages in the assembly are not included!), Creation / deployment system images, restore / copy data, operating system, resuscitation and recovery boot OS clean from viruses / trojans and blockers / pornobannerov, testing the basic components of MS, and more. There is a support network vozmozhnost access 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 build package 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 -> Burn image, specify the image file, make sure that it was noted "Finalize CD" and the method of recording "Disc-At-Once (DAO)". The disc with other recording settings will not boot! For Nero also recommended "Enable generation of short Lead-Out" (File -> Options -> Expert Features), it can reduce the recording time, speed up the recognition of the compact and a bit of time to increase the "capacity" blanks. Writing Speed ??- the minimum reasonable. I recommend 8-16h for the CD-ROM drive or 4 - for the DVD. The principle is: slower write -> faster (more reliable) reads. You can also use other programs, allows you to record images (for example, UltraISO, Alcohol 120, ...). 2. Installation of the assembly on the stick: pic
Attention!!! Many utilities (such as a standard windows format) are not completely format the flash drive, they see that it is, and do not touch the areas that they seem 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 FlashNull utilities, Check Flash, HD Tune Pro, Flash Memory Toolkit Pro, it is guaranteed to kill your markup and make formatting program to make everything from scratch . After cleaning, be sure to "distort" the stick, and then formatting it perform a check using CheckDisk (2k10 \ Programs-2k10 \ HDD-Utilites \). When bugs stick repeat cleaning and formatting. If you use formatting with BootICE -> Parts Manage -> ReFormat USB disk, it is an extra step. BootICE when formatting automatically makes cleaning.
2.1 USB flash drive, you must first format (Warning: All data on the flash drive will be destroyed). This is to ensure that the 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. USB flash drive, it 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" a 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 or P2Start.exe 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 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 below. Alternative methods of 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 loader is connected properly). If the work 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 (choose 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 - 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 the formatting options: -raw -force, format.
2.1.4 Using a script 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 the method 7. RAW FORMAT, to format. The script automatically reconnects the stick so "distorting" her after the formatting is not needed. 2.1.5 To format a USB drive with automatic connection XORBOOT loader is recommended to use the scripts:
a) FlashFormat_2k10_FBinst - Method 1 (flash cards up to 2GB for FAT16) or Method 2 (flash 4-32Gb under FAT32). Support USB-ZIP. On older systems, will only boot WinXP-PE. b) FlashFormat_2k10_FBinst - way to 5 (up to 2GB flash drive for FAT16) or a method of 6 (stick 4-32Gb under FAT32). Support USB-ZIP + USB-HDD. On older systems, will only boot Win7-PE. in) FlashFormat_2k10_RMprep - use if required NTFS support, use method 5 (flash drives of any size). Support only USB-HDD.
Scripts automatically reconnect the USB flash drive so the "distorting" her after the formatting is not needed.
Scripts can be used by the OS, and under assembly (any), they will automatically be connected XORBOOT in the MBR (sector 63, the PBR is ignored). Immediately after formatting the USB flash drive, you can check for bootable (startup XORBOOT) under any Dev (eg, MobaLive).
2.2 After formatting, remove the USB flash drive and connect again. 2.3 It is necessary to add to the stick assembly files - a folder 2k10, EFI and P2Start.exe file. bootmgr file on a flash drive / HDD is not in use, so it is not copied. They can be unpacked from an image by using 7-zip, WinRar, Total Commander, FAR, UltraISO or copy from any Dev mounted the CD / DVD drive to the virtual root of the stick. If reformatting the stick produced scripts - bootable media ready (XORBOOT attached loader).
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 verified by 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, as in a conventional OS, and under any PE-assembly (using SetLDR-2k10 2k10 utility in the folder). 2.4 Using a bootloader Syslinux / Grub4Dos / BOOTMGR / XORBOOT using SetLDR-2k10 for flash drives / HDD:
It is necessary to make a bootable USB flash drive. Go to the folder 2k10 \ on the flash drive, run the utility SetLDR-2k10 and set the correct assembly of the loader 2k10. Checkbox (right inscriptions Xorboot) - allows you to optionally install the boot loader for intermediate XORBOOT BOOTMGR / GRLDR (it will immediately download the latest). Also, the utility checks the right start-up (if the UAC is active), the presence of downloaders, and allows you to make active (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 the file system FAT32, but, if necessary, can be used and NTFS. If the HDD is used for parallel data transfer, it is convenient to break it down like this: make two primary partitions (if necessary - can be more partitions, but be sure the first and last, under the assembly, - primary, in the middle can be logical). The first format the partition to fit their 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 make 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, on the contrary, 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. If you are using an NTFS boot loader Syslinux there may be problems with downloading, it is recommended to do a breakdown / repartition USB / HDD using Paragon HDM. 3.2 We carry out assembly up to the active HDD partition (similar to 2.3) and the loader connection (paragraph 2.4). Alternative methods use Grub4Dos bootloader via BootICE (2012) for flash drives / HDD: pic
1. loader WEE. Is put completely in the MBR (PBR ignored), it covers 63 sectors (outside the box!). There are built-in menu (you can edit the installation) that allows to find and it is not recommended to load NTLDR, BOOTMGR, GRLDR, ... In connection with the non-standard for a universal stick, but it is very convenient, for example, as a Boot-Manager on the system drive. 2. GRUB4DOS in the MBR (PBR ignored), covers 18 sectors (outside the box!). Immediately starts GRLDR. In this regard, it is not recommended for non-standard universal flash. 3A. USB-HDD + in an MBR, registration GRUB4DOS in PBR. Not a bad option, and placed works on most flash drives, particularly suited for FAT32. 3B. USB-HDD + in an MBR, NTLDR registration in the PBR. When installing or rename rough bootloader in the root directory on the NTLDR, or specify GRLDR name when registration in the PBR (see. In the picture). Not a bad option, similar to 3A. 3C. USB-HDD + in an MBR, registration BOOTMGR in PBR. When installing or rename rough bootloader in the root directory on BOOTMGR, or specify the name of GRLDR (or GRUBMGR for assembling) for registration in the PBR. Not a bad option, similar to 3A. 4B. Windows NT 5.x MBR in an MBR, NTLDR registration in the PBR. When installing or rename rough bootloader in the root directory on the NTLDR, or specify GRLDR name when registration in the PBR (see. In the picture). A good option for bootability on different hardware, but the stick works rarely (depending on the flash chip?), Especially under FAT32. 5C. Windows NT 6.x MBR in an MBR, registration BOOTMGR in PBR. When installing or rename rough bootloader in the root directory on BOOTMGR, or specify the name of GRLDR (or GRUBMGR for assembling) for registration in the PBR. A great option for bootability on different hardware, some flash drives may not work under the FAT32 (dependent on flash chip?). Implemented utility SetLDR-2k10. My recommendation: for flash drives, if you do not need to transfer files larger than 4GB to try to establish the utility SetLDR-2k10, check the load 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 WinPE 10x64 Live ( Xemom1) Multilingual Edition 2k10 Parted Magic 2016.04.26 / 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 the 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.10.1.21.471 (rus) Linux-version of Paragon HDM 15 v.10.1.25.813 (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.99 (eng) DOS-version Acronis TIES v.9.7.8398 (rus) DOS-version Paragon HDM 15 v.10.1.25.813 (rus) DOS-version Hiren's Boot CD 15.2 (rus) Big set of different DOS-utilities, and much more.
Installing Windows XP / 7/8/10 of the assembly In the assembly, there are different ways to install Windows. Some installation methods, including by means of add-ons, 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 from the stick of _WIN folder \ Download and unzip the addon ~ 2k10-WIN7-10 ~ on a USB flash drive / HDD. Folder _WIN \ have to be at the root of flash / HDD. Copy of your image with Windows 7/8/10 folder Sources file install.wim / install.esd / install.swm in the appropriate subdirectory under the Windows 7/8/10 addon edition: 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 using 78Setup utility. The number of additional distribution is not limited. Throw, if any folder - $ OEM $ and unattend.xml file (relevant for Windows assemblies). The menu / submenu Grub4Dos "DOS-install Windows" add-on will automatically appear. The BCD-menu and the EFI BCD-menu it is already registered. _WIN Folder with installation files / images of Windows may be at the root of any drive / partition your HDD / USB-HDD.
You can also set the install.wim / esd / swm files by selecting 78Setup utility screen by pressing the "Select file manually" (file install.wim / esd / swm) for installation. Add your own images of the installation disks in Windows 7/8/10 _WIN folder, _ISO, 2k10 \ User.Image. The first image in the list will be displayed in the utility window 78Setup. The remaining images can be selected and run by pressing the "Select an image manually" button. Note:
C using x86 boot set any bit Windows. Not supported EFI / UEFI. C using x64 boot loader installed only x64-bit Windows, and only on a disk with a GPT layout. Supported by EFI / UEFI. If you do not need the installation of EFI / UEFI, you can use only one x86 boot for all installations. Detailed instructions for the addon itself neofitsialki ~ 2k10_Unofficial-WIN7-10 ~ can be found here.
Differences from the author's assembly 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 /), left linux utility is slightly different set of dos utilities gopher menu is present in the assemblies WinPE by Acronis DDH. Also, usually in an informal version includes all copyrights updates (at the time of assembly neofitsialki).
Thanks Conty9 author for kindly providing assistance in updating its assembly Multiboot 2k10 DVD / USB / HDD to the current version.
Year: 2016 Program Version: 6.4 Unofficial Developer: conty9 / Viktor Kisel Language: English + Russian Medicine: Disinfected System requirements:
A computer with 128Mb RAM or higher, CD / DVD drive or a USB interface.
Uploader.zone не содержит никакой нелегальной информации, только хеш-суммы файлов свободно доступных в сети.
Владельцы сайта не могут нести ответственности за действия пользователей. Этот ресурс полностью анонимный - IP адреса и действия пользователей не сохраняются. Сайт не предоставляет электронные версии произведений, а занимается индексированием файлов, находящихся в файлообменных сетях, Все права на произведения принадлежат правообладателям. Если вы являетесь правообладателем произведения, проиндексированного нашей поисковой машиной и не желаете чтобы ссылка на него находилась в нашем каталоге, свяжитесь с нами через форму обратной связи и мы незамедлительно удалим её. Публикация материалов сайта возможна только с разрешения администрации.