How to create a bootable DVD or USB-Flash/USB-HDD:

1. For CD/DVD: you will need a program to burn images - for example, Nero Burning ROM. Run the program, the Recorder -> Record the image, specify the image file, make sure that it is marked "Finalize the disk" and the recording method "Disc-At-Once (DAO)". The disk with other recording settings will not load! For Nero, it is also recommended to "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 blank. The recording speed is minimal within reasonable limits. I recommend 8-16x for CDs or 4x for DVDs. The principle is as follows: we write slower - we read faster (more reliably).
You can also use other programs that allow you to record images (for example, UltraISO, Alcohol 120, ...).
. To create a bootable USB flash drive: use the Rufus utility from the distribution (or a newer version, if available). Select the flash drive (1), the partition scheme (2), the file system (3, FAT32 or NTFS, FAT32 is recommended - as a sparing resource of flash cells), if desired, change the label of the flash drive (4). In the formatting parameters of the software (5), expand the add.parameters and note (6,7 - optional, but recommended for older PCs). Note (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), click Start (13). To speed up the process, you can temporarily disable antivir.
You can also create a flash drive using UltraISO, but this option is worse.
After creating the flash drive, it is completely ready for use. But to speed up the download, it is recommended to remove files from the root of the flash drive ldlinux.sys and syslinux.cfg and connect the desired loader with a script.
Notes:
* If you want to use Grub4Dos as a bootloader, after preparing the flash drive, run the MakeBoot_GRLDR script.bat from folder 2k10. MakeBoot_BOOTMGR script.bat will allow you to install bootmgr as a loader. MakeBoot_SYSLINUX.bat - will install Syslinux as a loader, but this loader will immediately launch Grub4DOS. The latter option is one of the best in terms of load capacity on various (especially old!) iron. For more or less new PCs, you can use bootmgr.
** Run scripts under Windows Vista/7/8 (makeboot_grldr.bat and MakeBoot_BOOTMGR.bat) necessarily with administrator rights!
*** Some antiviruses/OS may block the installation by Bootmgr or Grub4Dos loader. If this happens, boot from the build to CD and install the desired one, or perform this operation on another PC (where antivir is not so aggressive)!
**** If the build of the previous version is already available on a flash drive, it is enough to delete the 2k10 folder from the flash drive and add a new one from the distribution, and then connect the loader with a script. If there is a desire to add an assembly to a ready-made multi-boot flash drive based on Grub4Dos, copy the 2k10 folder and the P2Start file to the root of the flash drive, and add the 2k10 call to the grub menu (menu.lst):
title C9PE MultiMedia 2k10 Plus Pack
chainloader /2K10/GRUB4DOS/GRLDR
3. Installation on USB-HDD/HDD:
3.1 The screw needs to be formatted with any HDD partitioning program, create a primary active/boot partition of a suitable size (at least 1GB). Choose the file system FAT32 / NTFS (optional).
If the HDD is used in parallel for data transfer, it is convenient to split it like this: we make two primary partitions (if necessary, as many partitions as possible, but necessarily the first and last, for assembly, are primary, there may be logical ones in the middle). The first section is formatted to fit your needs in FAT32 / NTFS / ..., the size of the screw capacity minus 1-32GB (the planned size for assembly). The second (or last) section, under the assembly, we must make active / bootable. Why is this the case? The most convenient thing is that if you need to delete a partition with an assembly, or, conversely, increase the space for this partition, the operation will be QUICKLY done using almost any disk manager without data loss on the first partitions.
3.2 Copying the assembly to the active HDD partition (unpacking the contents of the image using WinRAR/7zip/UltraISO/TC/FAR)
3.3 Connect the desired bootloader (BOOTMGR or Grub4Dos) using a script (see notes from paragraph 2), or using BootIce.

How to boot from this disk:

To boot from CD/DVD or USB-Flash/USB-HDD, select the appropriate media in the boot menu when booting the computer. This can be done either in the BiOS or in the Quick Boot menu /called at the time of BiOS initialization, usually by pressing Esc, F11, F12, F8 - see the hint or instruction/. USB-Flash is often hidden in the HDD submenu in Quick Boot (a bootable USB flash drive is perceived as a boot screw). If there are several options for booting from a USB stick (USB-FDD, USB-Zipdrive, USB-HDD) - select USB-HDD.
In new versions of the assembly, after downloading from a USB flash drive in USB-FDD/USB-ZIPDRIVE mode, AFTER switching to the Grub4Dos menu, the assembly media is FORCIBLY installed as hd0, which makes it possible to download RE-assemblies (made specifically for older Bios versions that load the flash drive as fd0). Similarly, if after loading, for example, using a CD-Loader, the USB flash drive/screw with the assembly is not hd0, AFTER switching to the Grub4Dos menu, the assembly media is set as hd0. The media display is available in the header of the Grub4Dos main menu.

Some notes on working with the assembly:

1. The WinPE kernel can be loaded in one of three ways:
1.1 Normal boot (RAM). In this mode, the kernel is fully loaded into memory and runs as fast as possible. An extensive set of SATA/SCSI/RAID/USB 3.0 controller drivers is integrated into the core, but the RAM requirements are at least 192Mb. The mode is recommended for more or less modern PCs (if booting in USB 2.0 mode and memory from 384Mb or more is supported).
1.2 Normal Boot (RAM) with external MassStorage (SRS). This is a normal (RAM) boot mode in combination with an external SRS (MassStorage package). Allows you to slightly improve the loading of the assembly (for example, if the drive controller driver is not in the kernel, but is in the external driverpack). When loading, an intermediate script is executed that analyzes the controller and connects the FDD with the necessary driver. *** Added in v.3.0.
1.3 Primitive mode of operation. In this mode, a microkernel is loaded into memory, and the main one is connected (mounted) directly from the media (CD/DVD/USB/HDD). The speed of the kernel depends directly on the speed of the media, and is always lower than with a normal boot. When disconnecting/removing the media, the assembly freezes. The microkernel contains only standard drivers for IDE controllers of drives and drivers for SATA controller chips from Intel/AMD, there is also no support for USB 3.0. The mode is recommended to be used for the oldest PCs with limited RAM (128-384MB) and/or for PCs that do not support booting via USB 2.0 (on such PCs, the download is much faster).
1.4 Primitive mode with external MassStorage (SRS). It is completely identical to the usual setup, but when loading, an intermediate script is executed (under Grub4Dos), analyzing the HDD controller and connecting the FDD with the necessary driver. This driver is picked up (F6) at the kernel startup stage, which allows you to connect drives that are "invisible" for normal charging. The driver package is small, but there are drivers for running SATA HDD controllers.
Note:
In the positive modes (1.3 / 1.4), Runscanner does not work correctly, so all utilities "targeted" with it do not work with the target OS, but with the WinPE registry.

Installing Windows from the build:

It is possible to install Windows 2000/XP/2003/Vista/7 under any build. Installation packages are not included in the assembly, they are supposed to be added independently, based on user preferences.