cdob

Read the Pro version index, extract the pro part and create a new ISO file. Data are read and written at the disk: this uses almost no CPU usage dism.exe /Get-WimInfo /WimFile:sources\install.esd dism.exe /Export-Image /SourceImageFile:sources\install.esd /SourceIndex:6 /DestinationImageFile:sources\install_pro.esd del sources\install.esd ren sources\install_pro.esd install.esd oscdimg.exe -m -o -u2 -udfver102 -bootdata:2#p0,e,b.\boot\etfsboot.com#pEF,e,b.\efi\microsoft\boot\efisys.bin . ..\Win10_20H2_x64.iso I get a 4.32 GB image and matches a DVD RW. Dism is included by default nowadays. Oscdimg https://msfn.org/board/topic/156869-get-waik-tools-wo-downloading-the-huge-isos/

Boot XP. Run regedit. Load the 2000 registry file <windows_2000>\system32\config\system to loaded_hive Navigate to <loaded_hive>\SYSTEM\Select. Read the Current value. If the value reads one, goto <loaded_hive>\ControlSet001 If the value reads two, goto <loaded_hive>\ControlSet002 If the value reads three, goto <loaded_hive>\ControlSet003 And so on. Add the BigLBA setting. Unload the hive loaded_hive. Without 48bit LBA : There was data corruption attempting to write after 128 GiB address location. Writings occured below 128 GiB instead, this resulted to the data corruption.

No, I didn't test this drivers. I' don't pocess a 300 series chipset hardware.

Try modded drivers https://www.win-raid.com/t4883f52-Solution-Win-drivers-for-USB-Controllers-of-new-Intel-chipset-systems.html View the post #4 and #205

Can you clarify? Do you use BIOS or UEFI boot at the ProLiant DL380 Gen 5? Do you use BIOS or UEFI boot at the ProLiant DL380 Gen 10? Do you use MBR or GPT layout at the ProLiant DL380 Gen 5? Do you use MBR or GPT layout at the ProLiant DL380 Gen 10? https://docs.microsoft.com/en-gb/windows-hardware/manufacture/desktop/bcdboot-command-line-options-techref-di A example: If yoo boot WinPE at BIOS mode, but wan't to write UEFI boot files to the disk, then use bcdboot /f UEFI

Use different bcd files. How do you like to use the big ISO image? Do you like to boot from a virtual CDROM drive at VMware? Do you like to write to a USB disk at boot from a USB disk? This are different cases. A Eltorito floppy boot image is used at a DVD, master is the file efisys.bin. 1809 ISO x32 \efi\boot\bootia32.efi 1.210.168 bytes x32 \efi\microsoft\boot\efisys.bin\EFI\BOOT\BOOTIA32.EFI 959.584 bytes x32 \bootmgr.efi 1.199.416 bytes x64 \efi\boot\bootx64.efi 1.469.240 bytes x64 \efi\microsoft\boot\efisys.bin\EFI\BOOT\BOOTX64.EFI 1.121.792 bytes x64 \bootmgr.efi 1.452.865 bytes efisys.bin - BOOTIA32.EFI does chainload \bootmgr.efi at a DVD. \efi\boot\bootia32.efi is used directly at USB disk. Win10PESE used \Programs at x86 and x64, this causes conflicts at a multi boot. I assume RAM load feature next, \Programs is inside of each boot.wim. (Idea: There is a ISO mount feature at running PESE in addition. Add a Programs_x86.iso and a Programs_x64.iso, mount the iso file at boot.wim\windows\system32\pecmd.ini file. Maybe used at a second step.) Within OS default boot loader, use single files at DVD: Expand a x64 ISO file to a folder. Create a floppy image 7200 sectors at imdisk, mount at letter b: format b: /fs:fat Copy \efi\boot\bootia32.efi to b:\efi\boot\ Copy \efi\microsoft\boot\efisys.bin[EFI\BOOT\BOOTX64.EFI] to b:\efi\boot\ (This will launch the x64 \bootmgr.efi) Hexedit b:\efi\boot\bootia32.efi, change unicode string \BCD to \B32 This breaks UEFI secure boot at x86, secure boot works at x64 still. Save this floppy image to \efi\microsoft\boot\efisys3264.bin Copy b:\efi\boot\bootia32.efi to \efi\boot\ (to boot from USB stick in future) copy \efi\microsoft\boot\bcd to b32 copy a x86 boot.wim to \sources\boot_x32.wim bcdedit.exe /store (extracted files)\efi\microsoft\boot\b32 /set {default} device ramdisk=[boot]\sources\boot_x32.wim,{7619dcc8-fafe-11d9-b411-000476eba25f} bcdedit.exe /store (extracted files)\efi\microsoft\boot\b32 /set {default} osdevice ramdisk=[boot]\sources\boot_x32.wim,{7619dcc8-fafe-11d9-b411-000476eba25f} replace (extracted files) with the full path to single files for the DVD. oscdimg.exe -m -o -u2 -udfver102 -bootdata:2#p0,e,b(extracted files)\boot\etfsboot.com#pEF,e,b(extracted files)\efi\microsoft\boot\efisys3264.bin (extracted files) win10_3264.iso BTW. There is a MakeWinPE3264.cmd from 2015. This uses one bcd file, no hexediting, secure boot works. Maybe this shows some hints as a starting point anyway. http://reboot.pro/topic/20471-windows-pe-5x-boot-problem/page-2#entry192722

It depends on used storage controller driver. It's a setting to atapi.sys, part of the default IDE driver stack. USBstor.sys is another case. A default Win 2000 SP4 access first 128 GiB at atapi.sys only. Yes the parition size, in addition the location does matter too. https://web.archive.org/web/20100128222202/http://support.microsoft.com/kb/305098

Do you use 48 bit LBA at Windows 2000? https://msfn.org/board/topic/75713-48-bit-lba-on-win2k-setup/

That's a good catch. Isn't this a cloned system? Did the source system used a AGP bus? Are there agp440.sys loaded still, obolete at a PCI express system, causing the BSOD at ati2dvag.dll? ati2dvag.dll is the main dll, next to driver ati2mtag.sys.

There are no official XP Radeon HD 8180 drivers according unofficial driver site. https://www.amd-drivers.com/amd-ati-mobility-drivers.html Radeon HD 8180 is Kabini architecture. There are Vista drivers https://www.amd-drivers.com/download-RadeonHD8180-mobility-driver-for-WindowsVista-32bit.html https://www.amd-drivers.com/inffile-366.html [ATI.Mfg.NTx86.6.3] "%AMD9839.1%" = ati2mtag_Kabini_Mobile, PCI\VEN_1002&DEV_9839 There are Version 14.4 / 9.000.300.300 Radeon HD 8210 XP drivers https://www.amd-drivers.com/download-RadeonHD8210-mobility-driver-for-WindowsXP-32bit.html https://www.amd-drivers.com/inffile-390.html [ATI.Mfg.NTx86] "%AMD9830.1%" = ati2mtag_Kabini_Mobile, PCI\VEN_1002&DEV_9830 "%AMD9831.1%" = ati2mtag_Kabini_Mobile, PCI\VEN_1002&DEV_9831 "%AMD9832.1%" = ati2mtag_Kabini_Mobile, PCI\VEN_1002&DEV_9832 "%AMD9833.1%" = ati2mtag_Kabini_Mobile, PCI\VEN_1002&DEV_9833 "%AMD9834.1%" = ati2mtag_Kabini_Mobile, PCI\VEN_1002&DEV_9834 "%AMD9835.1%" = ati2mtag_Kabini_Mobile, PCI\VEN_1002&DEV_9835 "%AMD9836.1%" = ati2mtag_Kabini_Mobile, PCI\VEN_1002&DEV_9836 "%AMD9837.1%" = ati2mtag_Kabini_Mobile, PCI\VEN_1002&DEV_9837 "%AMD9838.1%" = ati2mtag_Kabini_Mobile, PCI\VEN_1002&DEV_9838 PCI\VEN_1002&DEV_9839 is missing at official inf file. I wonder about a modded Radeon HD 8180 inf file: [ATI.Mfg.NTx86] "%AMD9830.1%" = ati2mtag_Kabini_Mobile, PCI\VEN_1002&DEV_9839 Does the 14.4 / 9.000.300.300 graphic card driver works at a Asus X102B? Or is there a yellow mark at device manager?

No need to add tPCI\VEN_1022&DEV_7801&CC_0106 to the registry file. The setting should work as it is. There is a HardwareID PCI\VEN_1022&DEV_7801&CC_0106 And there are GenericID to the same hardware. Compare this at device manager. PCI\VEN_1022&DEV_7801 PCI\VEN_1022&CC_0106 Hence PCI\VEN_1022&CC_0106 matches PCI\VEN_1022&DEV_7801&CC_0106.

The setting from 2009 is old. AMD added VEN_1022, e.g. PCI\VEN_1022&DEV_7801&CC_0106 Add VEN_1022 too. VEN_*&CC_0106 refers to AHCI mode. REGEDIT4 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1002&cc_0106] "Service"="ahcix86" "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1022&cc_0106] "Service"="ahcix86" "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ahcix86] "Type"=dword:00000001 "Start"=dword:00000000 "ErrorControl"=dword:00000001 "Tag"=dword:00000021 "ImagePath"="system32\\drivers\\ahcix86.sys" "Group"="SCSI Miniport" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ahcix86\Parameters\PnpInterface] "5"=dword:00000001

Boot drivers are marked as CriticalDeviceDatabase. Boot at IDE mode and add AMD AHCI registry settings at CriticalDeviceDatabase. Is there a file system32\drivers\ahcix86.sys in the meantime? If not, copy this file manually.

The ID PCI\CC_0101 refers to IDE mode. The BSOD 0x7b dosn't refer to the SATA disk, more likely to the USB boot.

The ID PCI\CC_0101 refers to IDE mode. The BSOD 0x7b dosn't refer to the SATA disk, more likely to the USB boot.