Acronis UltraPack 2k10 v.7.26
Acronis UltraPack 2k10 v.7.26
[Misafirler Kayıt Olmadan Link Göremezler Lütfen Kayıt İçin Tıklayın ! ]
Acronis UltraPack 2k10 v.7.26
Language: Russian / English | File Size: 692.53 MB
The boot disk is based on the bootloaders BOOTMGR (Windows 8.1), Isolinux / Syslinux v.4.06 and Grub4Dos v.0.4.6a. The disk consists of a large number of Acronis, Paragon products, etc., with the ability to boot from a CD, USB Flash Drive, USB-HDD and regular HDD. The main purpose is to prepare the HDD for OS installation, create / deploy system images, restore / copy data.
This disk is a set of DOS and Linux-versions of the products of the assembly "Multiboot 2k10", adapted to the size of the CD-ROM.
The list of programs in the assembly:
� USB-driver PLOP v.5.0.11
� Linux version of Acronis DDS v.10.2169 (rus)
� 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 B&R Advanced v.11.5.39029 (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 Free Edition v.9.0 (eng)
� Linux version of TeraByte Image for Linux v.3.17 (eng)
� DOS version of Acronis DDS v.10.2169 (rus)
� DOS version of Acronis TIES v.9.7.8398 (rus)
� DOS version of Paragon HDM 15 v.10.1.25.813 (rus)
� DOS version of Hiren's Boot CD 15.2 (rus)
� A large set of various DOS utilities.
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 file with image, make sure that "Finalize disk" and recording method "Disc-At-Once (DAO)" are marked. A disc with other recording settings will not load! For Nero, it is also recommended that "Allow the generation of a short lead-out" (File -> Options -> Expert Properties), this allows you to reduce the recording time, speed up the recognition time of the compact and slightly increase the "capacity" of the disc. The recording speed is the minimum within reasonable limits. I recommend 8-16x for CDs or 4x for DVDs. The principle is this: write slower -> read faster (more reliable).
You can also use other programs that allow you to record images (for example, UltraISO, Alcohol 120, ...).
2. Installing the assembly on a USB flash drive:
Attention!!! Many utilities (for example, the standard windows format) do not completely format the USB flash drive, they look at what is on it and do not touch portions that seem correct to them. Therefore, it is advisable to first clear the USB flash drive, for example using the RMPrepUSB, HDD Low Level Format Tool or run a write test on any of the utilities FlashNull, Check Flash, HD Tune Pro, Flash Memory Toolkit Pro, this will kill the markup and force the formatting program to do everything from scratch . After cleaning, be sure to "flip" the USB flash drive, and after formatting, check it using CheckDisk (2k10 \ Programs-2k10 \ HDD-Utilites \). If errors are found, repeat flash drive cleaning and formatting. If formatting using BootICE -> Parts Manage -> ReFormat USB disk is used, then this is an unnecessary operation.
2.1The flash drive must first be formatted (Warning! All data on the flash drive will be destroyed). This is necessary so that the flash drive is perceived by Bios as a USB-HDD, from which the operating system can be loaded. If the flash drive / screw has already been used as boot, you can skip this item. It is recommended to format the USB flash drive for FAT32 (it works longer and more stable in this file system), but, if necessary, NTFS can also be used (it "kills" the USB flash drive faster, requires "safe extraction", but it supports files larger than 4GB). This is best done using RMPrepUSB (available in the assembly along the path 2k10 \ Programs-2k10 \ Flash-Utilites \ RMPrepUSB \ or from the P2Start.exe menu "2k10 Programs \ USB-Flash Utilities"). This utility creates the geometry closest to the screw on the USB flash drive. If you mark Boot as HDD (C: 2PTNS), two partitions will be created on the USB flash drive (the second is the minimum size, for maximum screw simulation). But I do not recommend using this option, such a flash drive will "hang up" household appliances (TVs with a flash player, players, etc.). It is quite enough to do, as in the figure.
Alternative flash drive formatting methods (instead of 2.1)
2.1.1 Format the USB flash drive using the HP USB Disk Storage Format Tool (available in the assembly along the path 2k10 \ Programs-2k10 \ Flash-Utilites \ HPUSBFW \ or in the menu, in the USB-Flash utilities section), you can use fast formatting. On some PCs, it may not work (the bootloader does not connect correctly on the USB flash drive). If it works, it can be used for both FAT32 and NTFS.
2.1.2 Format the USB flash drive using BootICE (2k10 \ Programs-2k10 \ Flash-Utilites \ BootICE \) ... It is recommended to format it like this: BootICE (select the USB flash drive) -> Parts Manage -> ReFormat USB disk -> USB-HDD mode ( Single Partition) - Align to sectors: 2048 -> Next -> FAT32 (NTFS) -> OK. It also does not always work, for me - the bootloader connects correctly only under NTFS.
2.1.3 We use FBInstTool (2k10 \ Programs-2k10 \ Flash-Utilites \ FBInstTool \). Utility for custom formatting flash drives, creates a structure of a special kind (USB-ZIP or USB-HDD). Select a USB flash drive (focus on size!), Check formatting options: -raw -force, format.
2.1.4 We use the script FlashFormat_2k10_FBinst (2k10 \ Programs-2k10 \ Flash-Utilites \ FlashFormat_2k10_FBinst \). Utility for custom formatting flash drives, creates a special kind of structure (USB-ZIP + USB-HDD). Select a flash drive (focus on size!), Use method 7. RAW FORMAT, format.
The script automatically reconnects the USB flash drive so you do not need to "juggle" it after formatting.
2.1.5 To format a flash drive with automatic connection of the XORBOOT bootloader, it is recommended to use the scripts:
a) FlashFormat_2k10_FBinst - method 1 (flash drives up to 2GB for FAT16) or method 2 (flash drives 4-32GB for FAT32). Support USB-ZIP. On older systems, only WinXP-PE will boot.
b) FlashFormat_2k10_FBinst - method 5 (flash drives up to 2GB for FAT16) or method 6 (flash drives 4-32GB for FAT32). Support USB-ZIP + USB-HDD. On older systems, only Win7-PE will boot.
c) FlashFormat_2k10_RMprep - use if NTFS support is required, use method 5 (flash drives of any size). Support only USB-HDD.
Scripts automatically reconnect the USB flash drive, so you don't need to "juggle" it after formatting.
Scripts can be used both under the OS and under the assembly (any), they will automatically connect XORBOOT to MBR (63 sectors, PBR is ignored). Immediately after formatting, the USB flash drive can be checked for loadability (starting XORBOOT) under any virtual machine (for example, MobaLive).
2.2 After formatting, remove the USB flash drive and reconnect.
2.3 You need to add assembly files to the USB flash drive - the 2k10 folder and the bootmgr.efi and P2Start.exe files. The bootmgr file on the flash drive / HDD is not used, so it is not copied. They can be unpacked from the image using 7-zip, WinRar, Total Commander, FAR, UltraISO or copied from a virtual disk mounted by any virtual machine for CD / DVD to the root of the flash drive. If the flash drive was formatted using scripts, the bootable media is ready (the XORBOOT bootloader is connected).
It will be faster at first to unzip the contents of the image into a temporary folder on the screw, and only then copy everything from it to a USB flash drive - it has been repeatedly tested by experience. You can also mount the image as a virtual CD-ROM and copy from it - the effect is the same. If the flash drive is created under a loaded assembly, it is convenient to mount the image using ImDisk (RMB on the image, "Mount ...").
The main bootloader, if desired, can be installed / changed at any time both in a regular OS and under any PE-assembly (MakeBoot_XXX.bat batch files in the 2k10 folder are responsible for connecting bootloaders, where ??? is the bootloader).
2.4 Using the Syslinux bootloader for flash drives:
You need to make the flash drive bootable. We go into the 2k10 \ folder on the flash drive and run MakeBoot_SYSLINUX.bat. This batch file will make the drive bootable. Please note that MakeBoot_SYSLINUX.bat needs to be launched from the flash drive (it determines the device by this letter). After practicing your batch file, your flash drive is ready to go.
Under Windows Vista / 7/8, if UAC is enabled, you must first set attrib.exe (2k10 \ Syslinux \ attrib.exe) as administrator in the properties of the file! After working out the batch file, your flash drive became bootable (a boot file ldlinux.sys was created in the 2k10 \ Syslinux folder (attributes: hidden / system).
Possible mistakes:
"syslinux.exe" is not an internal or external command, executable program or batch file - appears when you try to run a batch file under x64 version of Windows. For proper development, you need a 32-bit version (Windows 2000 / XP / 2003 / Vista / W7). The solution is to make it on another computer or burn the image to a disc, boot from it and do everything from under LiveXP.
2.5 Using the Grub4Dos bootloader for flash drives:
You need to make the flash drive bootable. We go into the 2k10 \ folder on the flash drive and run MakeBoot_GRLDR.bat. This batch file will make the drive bootable. Please note that MakeBoot_GRLDR.bat needs to be launched from the flash drive (it determines the device by this letter itself). After practicing your batch file, your flash drive is ready to go.
Under Windows Vista / 7/8, if UAC is enabled, you must first set up the properties of the BSmod.exe file (2k10 \ GRUB4DOS \ OTHER \ BSmod.exe) as administrator!
This is not the only way the Grub4Dos bootloader installs, but one of the most "bootable" compatible ones. Downloading is identical to how it was done for BOOTMGR (Vista / 7/8), the same registration is used in the boot area (only adjusted under the name GRUBMGR to exclude intersections with other assemblies / installers / ...).
2.6 Using the BOOTMGR bootloader for flash drives:
You need to make the flash drive bootable. We go into the 2k10 \ folder on the flash drive and run MakeBoot_BOOTMGR.bat. This batch file will make the drive bootable. Please note that MakeBoot_BOOTMGR.bat needs to be launched from a flash drive (it determines the device by this letter). After practicing your batch file, your flash drive is ready to go.
Under Windows Vista / 7/8, if UAC is enabled, you must first set BootSect.exe (2k10 \ GRUB4DOS \ OTHER \ BootSect.exe) in the properties of the file as administrator!
This is the standard way to connect the bootloader from MicroSoft using BootSect. However, if desired, the bootloader can also be connected using BootICE.
2.7 Using the XORBOOT bootloader for flash drives:
You need to make the flash drive bootable. We go into the 2k10 \ folder on the flash drive and run MakeBoot_XORBOOT.bat. This batch file will make the drive bootable. Please note that MakeBoot_BOOTMGR.bat needs to be launched from a flash drive (it determines the device by this letter). After practicing your batch file, your flash drive is ready to go. After working out the batch file, the XORBOOT bootloader will be registered in the MBR, in the menu of which there will be all the assembly loaders (BOOTMGR, Grub4Dos and Syslinux) and several "bonuses". Installing the bootloader exclusively in the MBR allows you to provide better bootability on new PCs and allows quick access to any bootloader.
3. Installation on USB-HDD / HDD:
3.1 The screw must be formatted with any HDD partitioning program, create a primary active / boot partition of a suitable size (at least 2 GB). We select the FAT32 file system, but, if necessary, you can use NTFS.
If the HDD is used in parallel for data transfer, it is convenient to break it up like this: we make two primary partitions (if necessary, we can have more partitions, but be sure the first and last, for the assembly, are primary, in the middle there may be logical). The first section is formatted to fit your needs in FAT32 / NTFS / ..., the size of the screw capacity minus 3-5 GB. The second (or last section, for the assembly) - be sure to make active / boot, under FAT32. We install the assembly on this section. Why so? The most convenient way is if you need to delete the partition with the assembly, or, conversely, increase the space for this partition, the operation will be QUICKLY done using almost any disk manager without losing data on the first partitions.
3.2 We copy the assembly to the active partition of the HDD (similarly to clause 2.3) and connect the bootloader (clauses 2.4-2.7).
The Syslinux bootloader for the HDD is connected in the second run of MakeBoot_SYSLINUX.bat (in the first - only flash drives), read the hint!
Under Windows Vista / 7/8, you must run the batch file with administrator rights!
Alternative methods of using the Grub4Dos bootloader using BootICE (2012) for flash drives / HDDs:
1. WEE bootloader . It is placed completely in the MBR (PBR is ignored), occupies 63 sectors (non-standard!). There is a built-in menu (you can edit it during installation) that allows you to find and load NTLDR, BOOTMGR, GRLDR, ... Due to its non-standard nature it is not recommended for a universal flash drive, but it is very convenient, for example, as a boot manager on a system disk.
2. GRUB4DOS in MBR (PBR is ignored), occupies 18 sectors (non-standard!). Immediately launches GRLDR. Due to the non-standard, it is not recommended for a universal flash drive.
3A. USB-HDD + in MBR, GRUB4DOS registration in PBR. A good option, it is installed and works on most flash drives, especially suitable for FAT32.
3B. USB-HDD + in MBR, NTLDR registration in PBR. When installing, either rename the boot loader in the root of the disk to NTLDR, or specify the name GRLDR when registering in PBR (see the picture). A good option, similar to 3A.
3C. USB-HDD + in MBR, BOOTMGR registration in PBR. When installing, either rename the rough bootloader in the root of the drive to BOOTMGR, or specify the name GRLDR (or GRUBMGR for assembly) when registering in PBR. A good option, similar to 3A.
4B. Windows NT 5.x MBR in MBR, NTLDR registration in PBR. When installing, either rename the boot loader in the root of the disk to NTLDR, or specify the name GRLDR when registering in PBR (see the picture). A good option for bootability on different hardware, but rarely works on flash drives (depends on the flash drive chip?), Especially under FAT32.
5C. Windows NT 6.x MBR in MBR, BOOTMGR registration in PBR. When installing, either rename the rough bootloader in the root of the drive to BOOTMGR, or specify the name GRLDR (or GRUBMGR for assembly) when registering in PBR. An excellent option for bootability on different hardware, on some flash drives it may not work under FAT32 (depends on the flash drive chip?). Implemented by batch file in assemblies 2.6.0 / 2.6.1.
My recommendations: for flash drives, if you do not need to transfer files larger than 4GB try installing a batch file, check the download in MobaLive. If it does not work, use NTFS + batch file or the installation option using BootICE - 3C (3A, 3B - they practically do not differ) for FAT32.
How to create a 2k10 bootable USB flash drive using Rufus:
To create a bootable USB flash drive, you must first format the USB flash drive correctly (so that it is perceived in Bios as a USB-HDD device from which you can boot.
SEE 1st screenshot
The easiest and fastest way to create a bootable USB flash drive is to use the Rufus utility. We select the USB flash drive (1), the partition scheme (2), the file system (3, FAT32 or NTFS, FAT32 is recommended - as preserving the resource of flash cells), if necessary, change the flash drive label (4). In the formatting parameters according to (5), expand the additional parameters and mark (6.7 - optional, but recommended for older PCs). We mark (8.9), select the build image (10) and remove the bird (11 - so that autorun.inf is not created in the root of the flash drive). Once again, we check the correctness of the choice of the flash drive (1) and the image (12), press Start (13). To speed up the process, you can temporarily disable the antivirus.
After creating the flash drive, it is completely ready for use. But to speed up the boot, it is recommended to connect the desired bootloader using the SetLDR-2k10 utility.
To install the desired bootloader from the 2k10 assembly, after preparing the flash drive, run the SetLDR-2k10 utility from the 2k10 folder.
Some antiviruses / OSs may block installation with the Grub4Dos or BOOTMGR bootloader. If this happens, boot from the assembly to the CD and install the desired one, or perform this operation on another PC (where the antivirus is not so aggressive)!
If the assembly of the previous version is already on the USB flash drive, just delete the 2k10 folder from the USB flash drive and add a new one from the distribution, and then connect the bootloader with SetLDR-2k10 utility.
Changes of May 13, 2020 Version 7.26:
� Updated Dos versions: HDDaRTs, HDAT2, BWP, terabytes.
� Fixed other minor bugs and errors.
System requirements:
� A computer with 128 Mb RAM and higher,
� CD / DVD drive or USB interface.
Checksums:
File: UltraPack 2k10 7.26.iso
CRC32: 427E1ED3
MD4: D2622188ECD63905A9B04857F60BCD75
MD5: EA113BDA2C5A61D301A93320C2F72093
SHA-1: 2B3804296606DF797C92644700EF4A62F57F2CA6
DOWNLOAD LINKS :
Kod:
https://nitroflare.com/view/49E6C26D9682901/BaDshaH.UltraPack_2k10_7.26.iso
https://rapidgator.net/file/14451ceedc42b2989bb8b7646f9e596a/BaDshaH.UltraPack_2k10_7.26.iso.html
