Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won

  • Donations

    0.00 USD 
  • Country


Everything posted by cdob

  1. 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/
  2. 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.
  3. No, I didn't test this drivers. I' don't pocess a 300 series chipset hardware.
  4. 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
  5. 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
  6. 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
  7. 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
  8. Do you use 48 bit LBA at Windows 2000? https://msfn.org/board/topic/75713-48-bit-lba-on-win2k-setup/
  9. 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.
  10. 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?
  11. 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.
  12. 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
  13. 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.
  14. 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.
  15. 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.
  16. Thanks for the testings and the report. I wasn't aware of this 2048 bytes sector feature in real world. What about the future? The mainboard may fail in some years. Swap the disk to another system? Swap the disk to a USB case? How to mount the partition then? Choose a choice depending on your situation. different data importance: data loss is acceptable or data loss is not acceptable. What to do with the 5 TB disk finally? Rely on a specific driver version? And use 2048 bytes sectors? Any chance to read the disk at another approach? Does a default Win10 DVD mount the disk? Does ntfs-3g support 2048 bytes sectors? Is there a parameter? The Asus M5A88-M provides a PCI slot still. A Promise PCI controller can be attached. This may be another chance. But: are there mainbords with PCI slot in future? Are there drivers? Or try another driver with 512 bytes per sector. This should be readable now and in future. Two partitons at MBR should provide each 2 TiB, sums to 4 TiB. About a CD data is missing from the 5 TB disk. No idea, if this is possible with default XP IDE drivers. Given average importand data: I would choose the 2048 bytes per sector. And create a 32 bit PE with the AMD drivers integrated. Second booting with data access is possible. I would igore a mainborad failure.
  17. What happens at IDE mode? Does device manger list a hard disk? Does disk manager list the hard disk? The Asus M5A88-M manual describes a SATA Block (Multi-Sector Trasfer) mode. Long shot, guessed: This leads to a assumption: may this creates the 2048 sectors at a 5 TiB disk at BIOS level? The Windows IDE driver fails at this? The AMD AHCI dirver support this? The default is [Auto]. Multi sectors are transferred. Do you use Auto mode? What happens at [Disabled] mode?
  18. There are new partitons at the new disk. The old \boot\bcd dosn't match the new disk. Booting fails. Another approach: use locate http://mistyprojects.co.uk/documents/BCDEdit/files/device_locate.htm Set locate at the source system. Clone the disk next.
  19. MBRview shows one partition with Num LBA: 2441879937 http://reboot.pro/topic/8734-tiny-hexer-scripts/ 2441879937*2048/1024^2 ~ 4769297 Stange, yes there are 2048 bytes per sector. If it's not the hot swap case, then there has to be another reason. This can be a driver, e.g. the previous referenced DiscWizard Extended Capacity Manager. If no one ist installed, then there are the ahci driver still. Does ahcix86.sys creates virtual 2048 bytes per sector, given a hard disk greater 4 TiB? Try, write the full disk. Be aware, if you swap this hard disk to another system, reading files may fail. Backup the data.
  20. Use 'Intel SSD Toolbox' to TRIM the SSD manually. Try a old version at Vista too. https://downloadcenter.intel.com/download/29205/Intel-Solid-State-Drive-Toolbox https://drivers.softpedia.com/get/HDD-SSD-NAS-USB-Flash/Intel/Intel-SSD-Toolbox-335.shtml
  21. Thanks for the confirmation. I got curious and asked myself about a challenge: Windows 10 1507 x64 and a Xperia Z3. Xperia Manufacturer offers Emma to flash a device. Emma dosn't use fastboot mode, flashmode is used instead. Emma does use a Gordons Gate driver ggsomc.sys, signed by 'Sony Mobile Communications AB'. https://developer.sony.com/develop/open-devices/get-started/flash-tool/download-flash-tool/ Sony dosn't offer a fastboot driver themself. https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/how-to-unlock-bootloader/ Sony recommends android.com USB drivers, android.com recommends Sony OEM dirvers. Loop closed, no signed fastboot drivers. There is a custom build FlashTool Xperia Driver Pack, the hash catalog file dosn't match the .inf file, it's not signed. USB\VID_0FCE&PID_0DDE is a generic Xperia fastboot HardwareID. https://forum.xda-developers.com/showthread.php?t=2635830 https://github.com/johnantoni/fastboot-adb/blob/master/Win32/Drivers/ADB%2BFastboot/android_winusb.inf Back to Windows 10 1507. There is winusb.sys driver integrated. But neither ADB nor fastboot inf file. Xperia Z3: Both ADB and fastboot does work, by selecting winusb manually at device manager. To summarize this: Windows 10 1511 and later supports ADB out of the box. A signed driver is integrated. As for fastboot, select winusb manually at device manager.
  22. Just to confirm, there are XP and later manufaturer drivers. Most likely you used this one in the past. https://developer.sony.com/file/download/xperia-e3-xperia-e3-dual-driver/ The manufacuter so0109adb.inf file uses the same driver and settings for ADB and fastboot mode. winusb.sys is used in both cases. https://en.wikipedia.org/wiki/Android_software_development ADB and fastboot is a generic Android feature. Back to Windows 10 default files. No drivers added. ADB is installed out of the box. At fastboot select winusb.sys manually. Install Xperia "S1Boot Fastboot" device: Run device manager, goto "Other devices". Is there a "S1Boot Fastboot" device with a yellow question mark? Verify the Compatible Id "USB\Class_ff&SubClass_42&Prot_03" Select 'Update Driver', 'Browse my computer for driver software', 'Let me pick from a list of available drivers on my computer', 'Universal Serial Bus devices', Manufacturer: WinUsb Device / Model: ADB Device Confirm the 'Update Driver Warning' Is there a "S1Boot Fastboot" device at 'Universal Serial Bus devices'? It is used the driver winusb.sys?
  23. Which HardwareID do you use? Which Windows Build number do you use? Windows 10 default winusb.inf supports the ADB interface out of the box nowadays. If I recall correctly, ADB was missing in Win 10 1507, but was added later. Fastboot mode USB\Class_ff&SubClass_42&Prot_03 is not supported in winusb.inf.
  24. No idea about a linux host. Yes, should be at home folder. Or download the tools files yourself https://packages.vmware.com/tools/esx/latest/windows/index.html It's 10.3 tools currently at ESX. Use the Workstation Tools CD: http://softwareupdate.vmware.com/cds/vmw-desktop/ws/15.5.0/14665864/windows/packages/ There is .tar image, expand the file. And connect the ISO file to a virtual CD drive.
  25. Did you install the VMware SVGA drivers, included in the VMware Tools? Which graphic card is listed at device manager?
  • Create New...