reboot12

I don't believe. Record a video of how you install the system from a pendrive prepared using my method.

Impossible !!!!!!!!!!!!! Everything works in my XP and I can install all drivers without any problems, including yours - all the ones you have provided me with so far, i.e. i219 on AIMB, 9560 on Dell. You're probably still making ISO/Flashdrive your way - that's wrong !!!!!! You need to make a pendrive using diskpart in newer Windows because the one in XP does not support USB. Use diskpart on e.g. Win7. If you do not have another computer with Win7 installed, you can use the Win7 ISO/Pendrive installer (WinPE) in which you prepare the pendrive. Of course instead Win7 you can use other newer Windows e.g. 8, 10 or 11 P.S. When you tested my ISO in 2024, you probably also wrong made pendrive because you wrote about problems with unsigned drivers: https://forums.mydigitallife.net/threads/winxp-64-bit-on-a-modern-pc-iso-boot-wim-install-wim.88435/#post-1845263 I repeat again - my modern WinXP has no problems with unsigned drivers !!!!!! I my tutorial I wrote step-by-step how prepare USB stick:

OK, but today I will help you only make USB on webchat.

@Dietmar Please go to https://webchat.quakenet.org/?channels=xp64modern because we won't be able to communicate quickly on the forum

Noooooooooo. F...........k Make USB like this: For test on real machine you need build USB from ISO in Win7 or newer - do not use Rufus or other USB making tools !!! : connect USB stick (max 32GB because FAT32 only supports that) run CMD and: diskpart list disk sel disk x (x is USB drive) clean create par pri format fs=fat32 quick label="xp64_pe31" active exit mount ISO in virtual CD-ROM drive or open in 7z then copy (extract) all files and folders from ISO to USB drive

F..k, refresh browser to see previous edited posts I hate forum for this. I prefer webchat because no possible miss the message NOOOO!!! Never use Rufus for me modded ISO - it damages the UEFI loader.

@Dietmar I don't know if you don't see the previous posts on the forum??? I've been writing several times today whether you want my ISO and to use my ISO - check e-mail Search B66VY... Make USB like this: https://forums.mydigitallife.net/threads/winxp-64-bit-on-a-modern-pc-iso-boot-wim-install-wim.88435/

Apart from the fact that the .inf file is in Linux format, everything is OK - for WinXP it does not matter, but Notepad displays it incorrectly - you need to use WordPad or another editor, e.g. Notepad2 or Notepad++ Your WinXP installation is bad. Use my ISO, link on old e-mail or will send you one more time.

@Dietmar Your drivers are bad location .sys file. To auto install .sys need in same directory as .inf or you need edit .inf like this: [SourceDisksNames] 1=%DISKNAME%,,,WDM\objfre_wnet_amd64\amd64

Which exactly driver you use? Upload me for test.

@Dietmar Do you have an old email with a link? Want a link to the ISO? P.S. DebugView 4.90 work OK on WinXP 64-bit - both 32 and 64-bit versions https://web.archive.org/web/20220315163343/https://download.sysinternals.com/files/DebugView.zip

@Dietmar Eh, with my ISO (USB) you will install WinXP 64-bit in about 5-10 minutes

You're not reading previous posts again: https://msfn.org/board/topic/183464-updated-drivers-for-windows-xp-sp3-and-windows-2003-sp2-x32x64-for-modern-hardware/page/194/#findComment-1287248

Yea, antena connected.

@Dietmar AI suggest: full hardware reset // Przed wczytaniem Firmware if (Adapter->MmioBase != NULL) { // Wykonaj Soft Reset WifiWriteRegister32(Adapter, WIFI_CSR_GP_CNTRL, 0x04000010); ExfreesystemThreadResource(); // Czekaj 10ms LARGE_INTEGER delay; delay.QuadPart = -10000000LL * 10; // 10ms KeDelayExecutionThread(KernelMode, FALSE, &delay); // Sprawdź czy karta odpisała ULONG val = WifiReadRegister32(Adapter, WIFI_CSR_GP_CNTRL); DbgPrint("9560nn56: After Reset Check = %08lx\n", val); }

@Dietmar https://pastebin.com/3zqscvth

@Dietmar Same error code 10: 9560m8c: WifiInitialize fail status=c0000001 hwpresent=1 hwready=1 awake=1 alive=0 alive_status=00000000 mmio=00000000:bfffc000 len=16384 AI suggests: use DMA addressing MmMapIoSpace(..., MmNonCached) or test MmWriteCombined increase firmware loading timeout

@Dietmar https://pastebin.com/vavKv5ZU

OK, send me diagnostic driver 137 DbgView 4.90 not work on XP but 4.81 yes: https://web.archive.org/web/20180926162235/https://download.sysinternals.com/files/DebugView.zip

Simply use my modern ISO - make USB from ISO (how make USB is in my tutorial). I sended you link about year ago to e-mail

Unfortunatelly on WinXP 64-bit is error This device cannot start. (Code 10) in Device Manager Please compile for me version IRQ or write me how fix code to compile IRQ version - I have WDK 7600 installed, compilation time ~3 seconds

Fantastic !!! Respect

One environment will not be universal for everything - it depends on many things: what are you compiling and what is your source code - c, c+, c++, rust, etc. whether the code is old or new on what system the application is to be used - old XP or only new Vista and newer As I wrote, I compile all tools to work under WinXP 64-bit because they are simply missing. Recently I tried compiling flashrom 1.2 - first attempt MinGW+MSYS on Windows - failed, next attempt MinGW on Ubuntu 24 - failed. All I had to do was change Ubuntu to an older version, e.g. 16, and I could compile the application normally Other my tool UefiMenu + Windows driver I compile in WDK 7600.16385.1 and UEFI loader in same Ubuntu 16: Another one tool setcsum - I compiled in Visual Studio 2005

I'm sorry, but I'm a minimalist and I'm irritated by such oversized applications, unnecessary code in scripts or source code. Recently, I have been compiling a lot tools in various environments: Linux with edk2, UEFI, MinGW, Windows with WinDDK, Visual Studio and I try to make the code as readable as possible without unnecessary lines, so that the compiled tool does only what it is supposed to do. My latest tools - all for WinXP 64-bit: ffmpeg, flashrom, UefiMenu

I understand, but ~100 MB is not a normal CMD application size. I chose this tactic: I built an absolutely minimal ffmpeg.exe 2.20 MB to combine and split YT streams I added some functions for which I use ffmpeg e.g. convert framebuffer device dump.bin (from Linux) to PNG image or convert video file to GIF (I had to compile an external zlib library to support PNG): ./configure \ --enable-cross-compile \ --arch=x86_64 \ --target-os=win32 \ --cross-prefix=x86_64-w64-mingw32- \ --extra-cflags="-D_WIN32_WINNT=0x0502 -O2 -I/opt/ffmpeg-xp64/include" \ --extra-ldflags="-L/opt/ffmpeg-xp64/lib -static" \ --disable-everything \ --disable-autodetect \ --enable-demuxer=avi,mov,matroska,ogg,rawvideo \ --enable-muxer=gif,mp4,matroska,webm,adts,ogg,image2 \ --enable-decoder=h264,mpeg4,msmpeg4v3,tscc,rawvideo \ --enable-encoder=gif,bmp,png \ --enable-filter=fps,palettegen,paletteuse,split,scale,format \ --enable-parser=aac,h264,vp9,av1 \ --enable-bsf=aac_adtstoasc,vp9_superframe \ --enable-protocol=file,pipe \ --enable-zlib Now my ffmpeg.exe has 3.81 MB - I don't need a million other features that I will never use. And if you need something, you can always add it and compile Compilation time: version minimum + my functions (3.81 MB) - 5 minutes version no external lib (17.2 MB) - 25 minutes ffmpeg with full possibilities (~100 MB) - I don't know - probably couple hours ?