George King

I don't remember, I just scanned how is update installed on live system and grabbed registry changes to be able to integrate it into Vista PE. In past I have also figured aout how to enable servicing again on boot.wim, but it's useless to do something with that crappy PE.

Well, thats my file exactly and Mydigital Life is legit forum Just repost everything. Files without registry keys wont allow you to run USB3 in Vista PE. And yes, USB3 driver is one of older ones ported by @daniel_k before he dropped support for Vista from his Windows 8 USB3 driver port for 7. UpgradePE.cmd @echo off cls if "%~1" == "" ( echo. echo Drag and Drop path to mounted image: echo. SET /P IMAGE= echo. ) Else ( SET IMAGE=%~1 ) IF EXIST "%IMAGE%\Windows\SysWOW64" ( SET ARCH=x64 SET ARCH2=amd64 ) ElSE ( SET ARCH=x86 SET ARCH2=x86 ) xcopy /s /y /e "%~dp0updates\extracted\WinPE6.0-KB2864202-%ARCH%" "%IMAGE%\Windows\system32" >nul reg load HKLM\TEMPSYSTEM "%image%\windows\system32\config\SYSTEM" >nul reg add "HKLM\TEMPSYSTEM\ControlSet001\Control\Wdf\Kmdf\1" /v "Version" /t REG_SZ /d "1.11" /f >nul reg add "HKLM\TEMPSYSTEM\ControlSet001\Control\Wdf\Schema\KmdfService" /v "Type" /t REG_DWORD /d "0" /f >nul reg add "HKLM\TEMPSYSTEM\ControlSet001\Control\Wdf\Schema\KmdfService\Object" /v "KeyPath" /t REG_SZ /d "CurrentControlSet\Services" /f >nul reg add "HKLM\TEMPSYSTEM\ControlSet001\Control\Wdf\Schema\KmdfService\Object" /v "KeyRoot" /t REG_SZ /d "SYSTEM" /f >nul reg add "HKLM\TEMPSYSTEM\ControlSet001\Control\WMI\Autologger\SQMLogger\{1a3c3605-aa85-4b19-aa24-bb74bc365059}" /v "EnableLevel" /t REG_DWORD /d "4" /f >nul reg add "HKLM\TEMPSYSTEM\ControlSet001\Control\WMI\Autologger\SQMLogger\{1a3c3605-aa85-4b19-aa24-bb74bc365059}" /v "Enabled" /t REG_DWORD /d "1" /f >nul reg add "HKLM\TEMPSYSTEM\ControlSet001\Control\WMI\Autologger\SQMLogger\{1a3c3605-aa85-4b19-aa24-bb74bc365059}" /v "LoggerName" /t REG_SZ /d "SQMLogger" /f >nul reg add "HKLM\TEMPSYSTEM\ControlSet001\Control\WMI\Autologger\SQMLogger\{1a3c3605-aa85-4b19-aa24-bb74bc365059}" /v "EnableProperty" /t REG_DWORD /d "2" /f >nul reg add "HKLM\TEMPSYSTEM\ControlSet001\Control\WMI\Autologger\SQMLogger\{1a3c3605-aa85-4b19-aa24-bb74bc365059}" /v "MatchAnyKeyword" /t REG_QWORD /d "0x0000000000000800" /f >nul reg add "HKLM\TEMPSYSTEM\ControlSet001\Services\Eventlog\System\wdf01000" /v "EventMessageFile" /t REG_SZ /d "@%%SystemRoot%%\Windows\System32\drivers\Wdf01000.sys" /f >nul reg add "HKLM\TEMPSYSTEM\ControlSet001\Services\Wdf01000" /v "DisplayName" /t REG_SZ /d "@%%SystemRoot%%\system32\drivers\Wdf01000.sys,-1000" /f >nul reg unload HKLM\TEMPSYSTEM >nul "%~dp0apps\waik\x86\peimg.exe" /inf="%~dp0updates\extracted\GenericXHCIDriver-%ARCH%\XHCI\USBXHCI.inf" /image="%image%" "%~dp0apps\waik\x86\peimg.exe" /inf="%~dp0updates\extracted\GenericXHCIDriver-%ARCH%\UASPSTOR\uaspstor.inf" /image="%image%" And here you can get needed files https://www.mediafire.com/file/fgpxbkt9ly6i4py/WinPE_KB2864202++USB3x.7z/file

Link is dead, but you probably mean this archive? https://www.mediafire.com/file/g4cqr1jlt9di1iy/通用NVMe和USB3驱动.7z/file

@Mov AX, 0xDEAD Hi, any chance to reproduce XBOX 16TB HDD hack into XP? https://fatxplorer.eaton-works.com/2022/08/09/fatxplorer-3-0-beta-22-16-tb-xbox-360-internal-hdd-support-updated-usb-patches/ How this was done A more technical deep-dive will be published another time, along with the source code to the patches. Here is a general overview in the meantime: When the Xbox 360 kernel loads the disk size, it maxes out at 2 TB because of the 32-bit sector count field in the DISK_GEOMETRY structure. The 512-byte sector size multiplied by the maximum 32-bit value (4294967295) equals 2 TB. This field cannot be extended beyond 32-bits, so the alternative is to increase the sector size. The sector size was increased to 4096, and as a result, that 32-bit sector count field can now represent a maximum of 16 TB. Since the HDD itself still uses 512-byte sectors and the 4096-byte sector size is essentially a spoof, a conversion method had to be created so the read/write operation, based on the 4K sector size, would apply to the correct sectors on the HDD. Additionally, the lowest-level SATA code had to be upgraded to write sector values to the cylinder ports that go beyond 32 bits. The final problem to solve was non-buffered IO operations. Some files, like xexs, are opened with FILE_FLAG_NO_BUFFERING and reads are done that are 512-byte sector aligned, but not 4K sector aligned. With the sector size change, games failed to launch. A 512-byte-to-4K “emulation layer” had to be created, which is basically a kernel-mode function that translates 512-byte-aligned reads & writes into 4K-aligned reads & writes. The trick done on the XL USB patches with forcing off FILE_FLAG_NO_BUFFERING was insufficient (some games needed it), and was replaced with this emulation layer. This was the most difficult part of the project – the actual SATA patches were easy compared to this! The source code to this emulation layer will be published another time. For reference, all of the internal HDD patches combined are larger than all of the default xeBuild patches combined!

I will update POWIS when time commes. You can see progress in XP2ESD thread on MDL. Stop Offtopic, nothing you posted in this thread is related to first post. I’m not going to waste my time with upcoming Windows right now. Will probably work same as 11. And I mentioned, POWIS will be updated probably later this year. @Dave-H Please clean trash in this thread

Just debomb it. https://github.com/weolar/xpchrome/issues/11#issuecomment-1822125826 Or better to use Supermium https://github.com/win32ss/supermium

Do you think changing username and spamming me with your personal issues fix a problem on your side with Mydigital Life? All links works fine. Stop contacting me everywhere to request personal help where I really cant help you. PS. If you think about Windows ME then you really don't know anything about operating systems you wanna to play with.

All Office 2010 updates are compatible with XP. In latest updates there is “bug” in mso.dll and it has missing imports under XP. So we just added patched mso.dll to solve this issue Best to use UpSourcer as it simply create fully updated Office installation without growing its size drastically! And when you use Unlocked package it contains patched mso.dll so no hangs, just fully updated and working after installation. And I have also patched OS restrictions in osetup.dll so can be installed on 2003 or x64 too without any additional tricks

@AstroSkipper Just check this out - Office 2007 UpSourcer. Real problem solver There is also 2010 ones which is realy builded to works with XP and 2003 too! https://forums.mydigitallife.net/threads/upsourcer-slipstream-patches-for-office-2007-2010-2013-2016-and-rebuild-setup-source-files.87111/#post-1794847

@Dietmar Looks great! Can you mod x64 aswell please?

Are you sure you really need that driver integrated into setup? Try x86 version first. These both XPs are different kernel level 5.1 vs 5.2 I think I’m using in XP2ESD only syssetup.dll patches on 5.2. (I’m out of my machine, cant check it today) https://www.wincert.net/forum/topic/17689-xpw2k3-x64-on-modern-hardware/?do=findComment&comment=138860

setupapi.dll patch should do that job. I mean use any unsigned driver, including modified INFs during setup. Use patched dll just for setup, replace with original one later. REM Patch SETUPAPI REM 8B FF 55 8B EC 8B 45 2C 33 C9 3B REM 33 C0 C2 30 00 8B 45 2C 33 C9 3B expand "%~dp0_output\i386\SETUPAPI.DL_" "%~dp0_output\i386\SETUPAPI.DLL" >nul del /q /s "%~dp0_output\i386\SETUPAPI.DL_" >nul "%~dp0apps\bbe\%ARCH%\bbe.exe" -b "/\x8B\xFF\x55\x8B\xEC\x8B\x45\x2C\x33\xC9\x3B/:11" -e "s/\x8B\xFF\x55\x8B\xEC\x8B\x45\x2C\x33\xC9\x3B/\x33\xC0\xC2\x30\x00\x8B\x45\x2C\x33\xC9\x3B/" "%~dp0_output\i386\SETUPAPI.DLL" -o "%~dp0_output\i386\SETUPAPI2.DLL" del "%~dp0_output\i386\SETUPAPI.DLL" ren "%~dp0_output\i386\SETUPAPI2.DLL" "SETUPAPI.DLL"

@win32 I just noticed your repo return 404. Hope this issue is temporary. But I quess progwrp.dll should looks like virus container without published source (I understand why you have not published source) Btw, I have noticed various issues on my machine when upgraded to latest progwrp.dll and R6 Supermium. I need to check what caused it, But I think using 5002 on XP x64 was fine with R3 without freezing on basic search on Google. My XP machine is powerful enough and nothing else was changed.

I installed it normaly and it works, have not tried anything related to portable.

I have saved Partition Assistant 10.1.0.0 which I know works fine under XP and installer was obtained under XP before the dropped support. https://www.mediafire.com/file/w4s3a5eynl4nsu5/PartitionAssistant-all.exe/file Can be installed silently with /silent switch P.S. Full version require just correct cfg.ini in installation directory.

Fixed links in first post, I'm not sure if it's same, but I grabbed it from my other repository - it should be from my latest builds.

Use UpdatePack instead. https://msfn.org/board/topic/183839-5eraph-updatepacks-x64-v2019/

Great, I'm going to find my USB Floppy and SD Cards reader, then I should probably reproduce it my main machine. I will probably just suppress that error, because issue is caused by something else - Not used drives are mounted, but doesnt contains real disk physically connected IOCTL_DISK_GET_DRIVE_LAYOUT_EX, thats probably due that mechanism, because they are another part of HW where you connect another one too. Will see what can I do. I will check also mentioned SSE if it's possible.

@genieautravail Please add screenshots from Disk Management

@genieautravail Can you tell me more about your error 21? I need to know details about that disk which is not listed using ListDisk. Currently it means your disk is unsupported, but I don't know where should I dig, when I don't know nothing about it and can't reproduce it.

I think we should investigate how is done 16TB HDD support in XBOX 360. Maybe we can do something similar. https://fatxplorer.eaton-works.com/2022/08/09/fatxplorer-3-0-beta-22-16-tb-xbox-360-internal-hdd-support-updated-usb-patches/ https://fatxplorer.eaton-works.com/2024/01/03/combined-xbox-360-xl-patches-now-available/

Hi @Dietmar, Have you tried ChatGPT 4? Or just stick with free model? This whole app was designed by me with exact “prompts”. These models are really not comparable. I can tell you this. If you think its blind, I don’t really believe. I have spend amount of time to work with free version, Yes, its crap. ChatGPT 4 works much better, 90% of code is compile-able and working code. Depends just on prompt.

Just apply these registry settings into default and Administrator profile.

Exactly, ChatGPT is powerful for coding, but you need to know what you want. Be specific, have knowledge. I have succeed only when using ChatGPT 4, If you use free model 3.5 then its full of crap - no working code after many tries. These model are not comparable. Even I ask for solution, I have not faced mentioned issue - that mean I can reproduce and test. And this tool was not done in simple prompt. I really know what I want. Like give me working code for Visual Studio 2019 in C++ for command line application which will list all connected physical disks with partition details based on XXX structure which will use own structure to store data etc.. And each function was designed using that way.. For example I have fully rewritten POWIS from scratch to get Professional look and usability. Currently I have like 6000 lines of code in HTA, CSS, VBS and JS. Everything based on ChatGPT 4 code. But it takes time of course, but really duable

No idea, as you can see Disk 1 is missing in list. If exist on your machine, it will be probably something with that. Another important thing, I’m not programmer, just enthusiast. I needed tool like this so I managed it in a week with ChatGPT 4… Of course without programing knowledge it wont be possible. If you detect issue I can try to fix it, like I did with special characters replacement to display them correctly in CMD in systems older than 8.0. Source code is released, so you can always try to investigate. Feel free to fork, improve or fix and push request into main tree. Thats why we have source in public repository