George King

@Dave-H I’m not going to help or support personal issues with Turkish spammer. Its always same. Spamming me over various forums and requesting prebuild ISO. Because he was banned on MDL and never receive activation e-mail again. This drive me to be crazy. My tools are not for rookies / noobs and spammers. They are build to help with various serious things. And even beginner can use them If really reads first post. If someone started spamming and was deleted and do same spamming again and want to use XP2ESD, its sad. Also quoting whole first post is riddiculous. And I really cant post current XP2ESD on MSFN. New version probably yes, Because I want to have it for MSFN rules. But this takes time. PS. He really don’t know what he write or maybe its caused by his translator.. I’m not going to react again. This topic and probably others he found will be spammed again.

@archlinuxuser You are 100% dumbass. As you don’t understand anything. Stop spamming my topic with your personal issues. I don’t care. @Dave-H Can you please clean every post in this topic begining from first post of this user?

I have set it in Visual Studio, do you have test environment to try it? It will be still dynamic build with VC++ Repack installed.

@genieautravail Output is directly one that gives system API

Thats probably file from SMXDIY according to mentioned password. I will build ported drivers for Vista or 7 too, same as I did for XP/2003. But not sure when. I still need to finish new POWIS which covers any deployment scenario. Then add into XP2ESD same image rebuilded with all updates for Vista and 7 and when I have this done then will come to porting drivers. Of course signed drivers with my custom certificate.

@ED_Sln Thanks for Benchmark tip! Installer doesn’t work on XP, But app works just fine. I just UniExtracted it under Windows 10 and then run under XP EDIT: I got really similar results on my testing machine with brand new SZMZ GTX 960

@genieautravail I have not reproduced your issue on Windows 10 x64 with connected USB2 CardReader to motherboard.. New improved version should be released in few days.

No you don’t need to have it installed. I builded updated 2007 setup with all updates from Windows 10. We can build FINAL 2007/2010 setup for XP x86/x64 and it doesn’t grow at all! So If Enterprise had 570Mb setup you receive like 600Mb setup! And installation time is same like without any updates Its really perfect

@Cixert Why not to use already created downloader of all needed updates from Office 2007 UpSourcer? https://forums.mydigitallife.net/threads/upsourcer-slipstream-patches-for-office-2007-2010-2013-2016-and-rebuild-setup-source-files.87111/#post-1794847 From Readme:

Yes, GenAHCI should work on Windows 7, just remove MSHDC driver before integration in Components -> Drivers -> IDE ATA/ATAPI controllers. Then integrate it on Drivers page.

It's another tool done with ChatGPT4..

ResolutionChanger Hello everyone! I'm excited to introduce ResolutionChanger, a command-line utility designed to help you manage and modify display settings on Windows systems efficiently. Whether you're a power user looking to automate display settings or someone who needs to frequently switch between different resolutions, this tool has you covered. Features ResolutionChanger offers a variety of features to make managing your display settings straightforward and hassle-free: List Monitors and Settings: Quickly display all connected monitors along with their current resolution, color depth, and refresh rate. Set Resolution, Color Depth, and Refresh Rate: Adjust the display settings of any connected monitor, including resolution, color depth (bits per pixel), and refresh rate. List Available Display Modes: See all possible display modes (combinations of resolution, color depth, and refresh rate) for a selected monitor. Error Handling: Provides detailed error messages to help you troubleshoot any issues during the execution of commands. Efficient Checks: Automatically skips redundant settings changes, saving time and avoiding unnecessary operations. Usage Examples Here are some examples of how to use ResolutionChanger: List Current Settings for All Monitors: ResolutionChanger.exe /list Set Monitor 1 to 1920x1080 Resolution: ResolutionChanger.exe /set 1 1920 1080 Set Monitor 2 to 1280x720 Resolution with 32-bit Color Depth: ResolutionChanger.exe /set 2 1280 720 32 Set Monitor 2 to 1280x720 Resolution, 32-bit Color Depth, and 60 Hz Refresh Rate: ResolutionChanger.exe /set 2 1280 720 32 60 List All Available Display Modes for Monitor 1: ResolutionChanger.exe /modes 1 How It Works ResolutionChanger leverages the Windows API to interact with connected displays, allowing you to query and set display settings programmatically. It offers a simple command-line interface, making it perfect for use in scripts or batch files for automating display configuration tasks. System Requirements ResolutionChanger is compatible with: Windows 2000 and later versions 32-bit and 64-bit architectures Requires no external dependencies – fully self-contained. Download and Installation You can download the latest version of ResolutionChanger from the link below: https://github.com/GeorgeK1ng/ResolutionChanger/releases To install, simply extract the archive and run the appropriate executable (x86 for 32-bit systems or x64 for 64-bit systems). For easier access from any command prompt, consider copying the executable to the C:\Windows\System32 directory. This allows you to run ResolutionChanger.exe from any location without specifying the full path.

So then just grab my silent SFX repack https://www.mediafire.com/file/2uydf8pk2i82zr5/ChromeXP115-all.exe/file

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"