Jump to content

reboot12

Member
 View Profile  See their activity

  • Posts

    440

  • Joined

  • Last visited

  • Donations

    0.00 USD 

  • Country

    Poland

 Content Type 

Posts posted by reboot12

    XP Pro X64 On Dell Optiplex 9020?

    in Windows XP 64 Bit Edition

    Posted

    On 1/6/2025 at 5:23 AM, Klemper said:

    Though I'm not sure how, since XP drivers for Haswell are very problematic or non existent at ll.

    Eh, everything is described in this forum - learn to look for before you write senseless posts :boring:

    https://msfn.org/board/topic/183956-asus-b85m-e-with-core-i5-4590-code-10-in-device-manager/

    https://msfn.org/board/topic/176356-simple-xp-32bit-64gb-ram-true-pae-guide/page/10/#findComment-1280987

    xp64-b85.png

    1

    WinXP SP2 64-bit on Asus J1800I-C BayTrail

    in Windows XP 64 Bit Edition

    Posted · Edited by reboot12

    1 hour ago, j7n said:

    I'm getting old. How is there a sound card inside an Intel processor? Where does it output the audio? Only on HDMI?

    Normally the same as in the PCIe HD graphics card, e.g. AMD HD7450:
    AMD-HD-Audio.png

    Audio output from Intel CPU is over HDMI, DP or DVI (DVI only if in bios is function Audio over DVI and you need DVI > DP or DVI > HDMI cable:
    i-GPU-Audio-DVI.png

    1

    [Research] Windows 7 and eMMC drives

    in Windows 7

    Posted · Edited by reboot12

    On 4/30/2024 at 12:30 AM, User1732 said:

    I've actually gotten this to work, here's what I did:

    I tried this on my Dell Wyse 5070 GeminiLake but Win7 installer still not see eMMC disk. My disk ID: PCI\VEN_8086&DEV_31CC

    I tried also replace some Vendor Device e.g. TED PCI\VEN_1679&DEV_3000 to PCI\VEN_8086&DEV_31CC in sdbus.inf but still not help: 

    dism /mount-wim /wimfile:boot.wim /index:2 /mountdir:mount
dism /image:mount /add-driver /forceunsigned /driver:eMMC
dism /image:mount /add-package /packagepath:Windows6.1-KB2732471-v2-x64.msu
dism /unmount-wim /mountdir:mount /commit

    I run installer pressing F8 then select Disable Driver Signature Enforcement

    0

    WinXP SP2 64-bit on Asus J1800I-C BayTrail

    in Windows XP 64 Bit Edition

    Posted · Edited by reboot12

    @Dietmar

    Yea, I found solution:

    • extract devcon.exe tool from XP ISO > SUPPORT\TOOLS\SUPPORT.CAB to %windir%
      devcon.png
    • press Win+R and run gpedit.msc
    • in Device Manager check Device ID MS UAA device - mine has DEV_0F04
    • go to Local Computer Policy > Computer Configuration > Windows Settings > Scripts (Startup/Shutdown) and open Startup
    • click Show Files and using Windows notepad make script re_UAA.cmd (use yours MS UAA Device ID) 
      @echo off
devcon disable *DEV_0F04
devcon enable *DEV_0F04
      gpedit.png
    • click Add... > Browse... - select created script and click OK then close gpedit window
    • restart WinXP
    • after the restart, the system's starting sound is not heard and no speaker icon in tray but when the system starts fully, in device manager is OK and Realtek sound card works

    P.S. devcon.exe version must be same architecture - best from same ISO as installed OS because 32-bit version cannot disable/enable device in the 64-bit OS !!!

    0

    WinXP SP2 64-bit on Asus J1800I-C BayTrail

    in Windows XP 64 Bit Edition

    Posted · Edited by reboot12

    @Dietmar

    Yeeeeeeeeaaaaaaaaaa - it works :thumbup:worship:

    After disabling and enabling Microsoft UAA Bus Driver for High Definition Audio, WinXP finds 2 new sound devices - Realtek and Intel. I have drivers for Realtek so I can install them now and the sound works :cheerleader:

    UAA-re-enbled.png Realtek-OK.png

    Thanks a lot Dietmar, I would never think of disabling then enabling UAA can help detect audio devices :dubbio:

    I need to add a script to the autostart which restarts the MS UAA driver and should be ok.

    0

    WinXP SP2 64-bit on Asus J1800I-C BayTrail

    in Windows XP 64 Bit Edition

    Posted

    9 minutes ago, Karla Sleutel said:

    When one has a dedicated card, the onboard needs to be disabled in BIOS.

    Can you read with understanding? I do not have a dedicated card, both are integrated - one of the Realtek motherboard and the other with the Intel processor and both work OK in Win7, Win10. The point is that in WinXP they are not visible in the device manager so I can't install the drivers. And no, in the bios it is impossible to disable the Intel card integrated with the processor, you can only disable the Realtek card integrated with the motherboard but I do not want to disable because I have drivers to it and I would like to use it in WinXP:

     

    0

    Simple XP 32BIT 64Gb RAM (true Pae) Guide

    in Windows XP

    Posted · Edited by reboot12

    On 7/1/2025 at 6:47 AM, reboot12 said:

    I have to use the system for some time to make sure 100% that there is no problem.

    Unfortunately, after a few days of testing, there is still a problem with the lag on Haswell machine. I changed OS to my favorite - WinXP 64-bit - everything works ok and I have full access to RAM  :thumbup
    xp64-b85.png

    P.S. I wanted to add a RAM patch to my project on MDL - WinXP 32-bit on a modern PC (ISO boot.wim + install.wim) but since it works unstable, I will probably give up :dubbio: Maybe I will add as an alternative in the boot.ini and BCD file but not as default.

    0

    CSMwrap - boot CSM on UEFI only systems.

    in Windows XP

    Posted · Edited by reboot12

    @Dietmar

    A CSMWrap version has been released, which allows you to use the BIOS video from the disk from EFI\Boot\vgabios.bin
    https://github.com/FlyGoat/CSMWrap/issues/37#issuecomment-3030297746

    Compiled bins: https://github.com/FlyGoat/CSMWrap/actions/runs/16040013218

    Thanks to this, WinXP boot OK on iGPU using ntldr as on a normal Legacy machine :cheerleader: - I tested CoffeeLake, Haswell, SandyBridge: CSM Disabled, iGPU VBIOS extracted from motherboard bios.

    Now - I don't have to use SeaVGABIOS and Longhorn bootmgr 5472 loader.

    2

    Simple XP 32BIT 64Gb RAM (true Pae) Guide

    in Windows XP

    Posted · Edited by reboot12

     

    53 minutes ago, Dave-H said:

    So, do you think the two patches I've tried are actually doing exactly the same thing, so there's no advantage of one over the other?

    I don't know, but if you compare patched kernel files 5.1.2600.6368 in a hex editor and are changed exactly the same bytes in the same offsets, it means that they work the same. You must first patch using a patcher v3.5 kernel file 5.1.2600.6368

    ntkrnlpa.exe 5.1.2600.6368 > https://catalog.update.microsoft.com/Search.aspx?q=2813170

    WinXPPAE.bat script default patch all RAM: 

    WinXPPAE.exe /M:ALL /NOBACKUP

    so, put ntkrnlpa.exe (GDR version) and WinXPPAE.exe in same folder then patch as above: 

    winxppae /M:ALL
Windows XP PAE Patcher 3.0 by daniel_k | HAL patches by <Mov AX, 0xDEAD>
PAE will be enabled using all available RAM.
Patching ntkrnlpa.exe (Uniprocessor PAE Kernel)... OK!
File ntkrpamp.exe (Multiprocessor PAE Kernel) was not found.
File hal.dll (Standard PC/Standard PC w/ C-Step i486 HAL) was not found.
File halaacpi.dll (ACPI Uniprocessor PC HAL) was not found.
File halacpi.dll (ACPI PC HAL) was not found.
File halapic.dll (MPS Uniprocessor PC HAL) was not found.
File halmacpi.dll (ACPI Multiprocessor PC HAL) was not found.
File halmps.dll (MPS Multiprocessor PC HAL) was not found.

    No, this is not simple to compare - too big differences :-( Probably ntkl64g.exe is compiled from source code.

    org vs v35 differ only in 11 bytes: 

    Search for differences
1. org_ntkrnlpa.exe: 2 070 016 bytes
2. 35_ntkrnlpa.exe: 2 070 016 bytes
Offsets: hexadec.

   138:    C2    04
   139:    FF    03
   13A:    1F    20
16B632:    07    00
16B637:    01    02
1703C2:    74    EB
1BE554:    10    00
1BE555:    00    02
1BE56A:    1B    00
1BE572:    FC    F8
1BE576:    01    02

11 difference(s) found.
    0

    Simple XP 32BIT 64Gb RAM (true Pae) Guide

    in Windows XP

    Posted · Edited by reboot12

    21 minutes ago, Dave-H said:

    How the other patch does it without having that specified is impressive!

    This is not impressive - simply this is patched ntkrpamp.exe for multi CPU/multi core use:
    kernel.png

    Modern computers have multi-core processors and the use of RAM patch on old PC does not make sense because old computers with a single-core processor do not support a large amount of RAM and a patch is not needed.

    Therefore, the 64G patch does not contain other kernal and hal files.

    0

    Simple XP 32BIT 64Gb RAM (true Pae) Guide

    in Windows XP

    Posted · Edited by reboot12

    @Ascii2

    I make big tests:

    • using Macrium Reflect clone OS to other HDD - still problem
    • replace RAM modules - still problem
    • use only 2GB RAM 1+1 - still problem
    • using Macrium Reflect make disk image, then restore on other PC - Haswell 8GB RAM (4+4 Dual Channel), OS boot, find new devices, I install drivers. I test and it looks like there is no problem and WinXPPAE 3.5 works well :-)
      I use exactly same patched files and settings: ntkrnl2.exe SP2 5.1.2600.2180 + hal2.dll SP3 5.1.2600.5512, noexecute=optin
      I have to use the system for some time to make sure 100% that there is no problem.

    It seems that the problem is only on SandyBridge machines.

    0

    Simple XP 32BIT 64Gb RAM (true Pae) Guide

    in Windows XP

    Posted

    2 hours ago, Ascii2 said:

    With regards to not having to use the /PAE switch because "noexecute=optin is enough".  That is not correct.

    No. /PAE switch load Ntkrnlpa.exe I use only like this and PAE works:

    /noexecute=optin /fastdetect /kernel=ntkrnl2.exe /hal=hal2.dll


    optin-PAE.png

    Enabling PAE

    Windows automatically enables PAE if DEP is enabled on a computer that supports hardware-enabled DEP

    The PAE kernel can be enabled automatically without the /PAE switch present in the boot entry if the system has DEP enabled (/NOEXECUTE switch is present) or the system processor supports hardware-enforced DEP. Presence of the /NOEXECUTE switch on a system with a processor that supports hardware-enforced DEP implies the /PAE switch. If the system processor is capable of hardware-enforced DEP and the /NOEXECUTE switch is not present in the boot entry, Windows assumes /NOEXECUTE=optin by default and enables PAE mode.

    You need use /NOPAE because default (optin) is enabled:
    https://web.archive.org/web/20060313135704/http://support.microsoft.com/kb/900524/

    0

    Simple XP 32BIT 64Gb RAM (true Pae) Guide

    in Windows XP

    Posted · Edited by reboot12

    1 hour ago, Ascii2 said:

    reboot12 has not indicated which kernel and HAL file versions

    Yea, I use SP2:

    • ntkrnl2.exe SP2 5.1.2600.2180 (patched by WinXPPAE 3.5 on SP2 OS) + hal2.dll SP3 5.1.2600.5512 (patched by WinXPPAE 3.5 on SP3 OS because the patcher cannot patches the hal.dll SP2 version)
    • ntkrnl3.exe SP3 5.1.2600.5512 + hal3.dll SP3 5.1.2600.5512 - both patched by WinXPPAE 3.5 on SP3 OS
    • ntkl64g.exe SP3 5.1.2600.6368 + hal64g.dll SP3 5.1.2600.5512 - files from @Dave-H 64 GB of RAM patch.zip

    I test (for a short time) my XP SP2 on other machines and probably no lag issue but this is fresh installed OS - no any drivers, apps.

    • maybe lag issue is only on my SandyBridge machine
    • recently I changed 2x4GB RAM - maybe they cause the problem?
    • my OS has all drivers and many applications installed - maybe some application or driver works badly with a RAM patcher?

    I have to test the patch for a long time on other computers + all drivers installed.

    boot.ini 

    [boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="RAM v3.5" /noexecute=optin /fastdetect /kernel=ntkrnl2.exe /hal=hal2.dll
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="WinXP" /noexecute=optin /fastdetect

    This is my table when DEP/PAE works on WinXP SP2 depending on the setting of the noexecute option in boot.ini
    noexecute-boot-ini.png

    So, I do not have to use boot.ini switch /PAE because noexecute=optin is enough.

    0

    Simple XP 32BIT 64Gb RAM (true Pae) Guide

    in Windows XP

    Posted · Edited by reboot12

    22 hours ago, Dave-H said:

    I wasn't very confident, expecting a BSOD at worst, and other issues even if that didn't happen.
    To my amazement, at least on my system, it seems to have worked perfectly!

    @Dietmar @Mov AX, 0xDEAD

    I use the WinXPPAE 3.5 patch for a week and I noticed a problem with disk operations - the same is for the 64G version:
    Video when ram patch is used - lags: https://files.catbox.moe/ericzb.zip
    Video when no ram patch: https://www.sendspace.com/file/17e170

    Testing config:

    • Asus P8H61-M LE R2.0
    • RAM 2x4GB DDR3-1600 Dual-Channel
    • CPU Intel Core i3-2120
    • WinXP SP2 Pro
    • HDD: SATA in AHCI mode

     

    0

    CSMwrap - boot CSM on UEFI only systems.

    in Windows XP

    Posted · Edited by reboot12

    @Dietmar

    I spent a bigger half day today testing XP32 with iGPU and I have good news. XP runs best with iGPU (Haswell) on vbemp.sys (PNP) 2015 driver in co-op with my UefiSeven (u7nwbm.efi + UefiSeven.ini with set native resolution of monitor) and Longhorn 5472 bootmgr+BCD+winload.exe loader - iGPU need be set as Primary Display in bios

    • XP can be run in the native resolution of the monitor - it depends on the monitor connected and the cable used (probably also on the EDID), the aurora boot screen is badly displayed when the resolution is native but the XP desktop works fine :P
    • you can change the available resolutions - if the resolution is lower than the native one, the desktop is displayed from the top right corner without cleaning the screen - the previous content remains on the screen
    • original XP vga.sys driver works badly with UefiSeven, there are some resolutions to choose from display settings but trying to change it restarts XP

    I boot XP in this way: in bios CSM Disabled (pure UEFI) > PC boot UEFI Shell from FAT32 100MB from EFI\Boot\bootx64.efi > startup.nsh starts UefiSeven and CSMWrap 1.2.1 (in UefiSeven.ini file native resolution monitor is set)

    NOTE: During installation of the vbemp driver, the system reboots but after the reboot it already starts on the vbemp driver at 640x480 and you can change the resolution to another e.g. native (if UefiSeven was previously running at this resolution)

    My monitor native resolution is 1360x768 but I test also other monitors native 1920x1080 and native 2560x1440 - see screenshots at bottom.

    UefiSeven.ini 

    ; UefiSeven configuration file
; 0 = false, 1 = true

[config]
skiperrors=0      ; skip warnings and prompts
force_fakevesa=0  ; overwrite Int10h handler with fakevesa even when the native handler is present
verbose=1         ; enable verbose mode
logfile=0         ; log to UefiSeven.log file
resheight=1360    ; preferred height
reswidth=768    ; preferred width

    EFI\Boot\startup.nsh 

    @echo -off

if exist fs0:\121.efi then
set base "fs0:"
endif
if exist fs1:\121.efi then
set base "fs1:"
endif
if exist fs2:\121.efi then
set base "fs2:"
endif
if exist fs3:\121.efi then
set base "fs3:"
endif
if exist fs4:\121.efi then
set base "fs4:"
endif
if exist fs5:\121.efi then
set base "fs5:"
endif
if exist fs6:\121.efi then
set base "fs6:"
endif
if exist fs7:\121.efi then
set base "fs7:"
endif
if exist fs8:\121.efi then
set base "fs8:"
endif
if exist fs9:\121.efi then
set base "fs9:"
endif
if exist fsa:\121.efi then
set base "fsa:"
endif
if exist fsb:\121.efi then
set base "fsb:"
endif

%base%
u7nwbm.efi
121.efi

    u7-csmwrap121-vbemp-monitor-1360x768.png u7-csmwrap121-vbemp-monitor-1920x1080.pn u7-csmwrap121-vbemp-monitor-2560x1440.pn

    If we run the XP without UefiSeven then OS boot in 1024x768 and there are only 3 resolutions available (no native):
    no-Uefi-Seven.png

    0

    CSMwrap - boot CSM on UEFI only systems.

    in Windows XP

    Posted · Edited by reboot12

    I compile CSMWrap replacing SeaVGABIOS to ValleyView Legacy video BIOS extracted from Jetway HPC070SC industrial computer:
    https://github.com/FlyGoat/CSMWrap/issues/37#issuecomment-2921265627
    Risky to use on other Laptops but this is Mobile/Desktop version so should work on desktop computers:
    Bay-Trail-Mobile-Desktop.png
    https://files.catbox.moe/6xj4hm.zip

    User win98se on github test this version, "But the graphics are glitched, and after spinning for a while" but not damaged:
    https://github.com/FlyGoat/CSMWrap/issues/39#issuecomment-2977152878

    bt.png

    0

    CSMwrap - boot CSM on UEFI only systems.

    in Windows XP

    Posted

    4 minutes ago, Dietmar said:

    I still do not understand,

    why now you get the latest Source files from csmwrap.efi .

    Is it, because you connect now to another server via

    No, they probably already corrected the repository and now git clones the latest version :-)

    0

    CSMwrap - boot CSM on UEFI only systems.

    in Windows XP

    Posted · Edited by reboot12

    OK, git corrected and now downloads the current version :D

    This is full tutorial how compile CSMWrap:

    Download and install Ubuntu: https://releases.ubuntu.com/noble/ubuntu-24.04.2-live-server-amd64.iso
    During installation, select Install OpenSSH server - this makes it easy to copy files from Ubuntu to Windows using WinSCP and use Ubuntu over SSH e.g. in Putty
    SSH-server.png

    sudo passwd root (enter password for user)
    sudo passwd root (make new password for root)
    sudo login root or reboot and login using root
    nano /etc/ssh/sshd_config

        PermitRootLogin yes
        PasswordAuthentication yes

    Ctrl+o to save and Ctrl+x to exit
    service ssh restart
    ssh.png

    apt update
    apt install -y build-essential nasm curl xxd net-tools

    git clone https://github.com/FlyGoat/CSMWrap.git --recursive
    cd CSMWrap
    make seabios
    make

    ifconfig - to check IP
    using WinSCP make connection and connect to Ubuntu:

    New Site, File protocol: SCP, Host name: IP, root User name and Password, Save
    ssh-win.png WinSCP.png works-121.png

    0
×
×
  • Create New...