Jump to content

reboot12

Member
  • Posts

    833
  • Joined

  • Last visited

  • Days Won

    2
  • Donations

    0.00 USD 
  • Country

    Poland

Posts posted by reboot12

  1. 11 hours ago, Dietmar said:

    PS: But result is the same. I cant install any driver because of

    "The parameter is not correct"

    So, no unsigned driver possible via 9560.inf .

    Tomorrow I make a try to add them by hand to registry and to system32\drivers .

    Impossible :huh:<_<-_- !!!!!!!!!!!!!

    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:
    how-make-USB.png

  2. 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

  3. @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);
      }
  4. 43 minutes ago, nicolaasjan said:

    What can you suggest as a more lightweight compiler for Windows?

    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 :)
    flashrom-OK.png

    Other my tool UefiMenu + Windows driver I compile in WDK 7600.16385.1 and UEFI loader in same Ubuntu 16:
    Save-Rt.png Dell.png Uefi-Menu.png

    Another one tool setcsum - I compiled in Visual Studio 2005

  5. 9 minutes ago, nicolaasjan said:

    It has all features you can think of.

    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

  6. 1 hour ago, nicolaasjan said:

    There are numerous people who use FFmpeg for other things than yt-dlp. :yes:

    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 ?
×
×
  • Create New...