I've tested the Yume Yao Add On updated by Rick, I can't find the adric version. All of them are in the same situation. Can anyone test the real Hardware please report me. The 5th test I will use the program.
You can check my files right now in addon, good luck with your creations. for wes2009 My phone in testing is a Wiko Y62.
If anyone is going to test my addon, go to the thread I created. Thanks, I don't want to bother George.
@381Tech I will PM you testing ISO soon EDIT: Are you sure that message about Media Center was for you?
oh sorry, i thought you were replying to my post.. I just wanted to reply you.. I just read that you said Media Center mb, sorry. Also i used Windows 10 1903 x64 ISO EDIT: I meant 1903
Read first post again to find out supported Windows 10 versions. P.S. H1 means first 6 months in year. H2 second 6 months. H = Half, So no H3 should exist
Yea a typo... It's 1903 sorry. I'm rly tired so please ignore some mistakes i might make.. Edit: Same thing happens with Windows 10 2004 ISO
@George King I am gonna try to modify setup.cmd so I can make the installation to install both Legacy and EFI loaders on MBR. The scope is to have an installation that can boot from both modes. I shall try to find an application that converts GPT to MBR on command-line in and then re-configures the active partition, MBR, reconfiguring the path in the 2 BCD files available, from setup.cmd in order to allow UEFI-MBR installation. XP2ESD only provides CSM-MBR or UEFI-GPT installation depending on the mode it's booting from. On settings.ini, to avoid bugs, MBR after EFI installation should only work when this option is added in settings.ini: "UEFI-MBR-Support=Yes" If it's set to no (as default), XP installation from XP2ESD on UEFI mode should theoretically remain on GPT as usual. The side effects of this is that Windows setup on UEFI mode won't allow the installation to work on MBR, so the partition has to be converted manually on from MBR to GPT (on the first installation before proceeding reinstallation) without erasure using other software or command-line apps. If there are issues or complications with setup.cmd that prevent from implementing this suggestion easily, please let me know, I'd love to dive deeper into the batch code so I can try to come up with solutions.
@UsefulAGKHelper I already implemented this for next version. But it's not ready to release yet. But I promise it will be soon Code: - v1.6.3 - Updated Windows Media Player 11 updates collection to final (complete) version for both architectures - Improved UEFI disk partitioning, EFI + MSR partitions are correctly created - Fixed Win-Raid certificate injection into boot.wim - Fixed "Logical Disk Manager" driver installation error on Home editions - Added Win-Raid certificate injection into captured systems, NOTE: Win-Raid drivers are still marked as unsigned due badly created signing certificate - Added ported Generic Disk v5.2.3790.4171 driver for x86 systems, this brings GPT support into Windows XP(5.1) same as 2003 (5.2) have - Added UefiSeven and FlashBoot integration into boot.wim - Removed GPT support addon, it caused additional disk installation prompt and "Logical Disk Manager" error on XP Home - Updated ported drivers with XP2ESD digital signature - Updated Generic USB2 and Generic USB MassStorage with multilanguage strings - Updated ported drivers DriverPack to v24, Generic USB2 + Generic USB MassStorage are now merged into one archive with all ported drivers
Btw I also know how to fix the "There's no disk in the drive" popup error in XP during XP2ESD myfactory. I found out that taking the A and B letters out of the list of searching of drive letters in setup.cmd will get rid of the "There's no disk in the drive" pop-up errors, it worked for me. These two drive letters (A and B) are typically only used on floppy drives. EDIT: I realized that these pop-up errors only appear when floppy drive is available on real hardware or virtual machine.