reboot12

Put files to another server (https://www.zippyshare.com , https://www.sendspace.com) because on ufile.io it shows me Premium Access Only. I don't understand what PLOP is for legacy NVMe boot? I do not want to remove Realtek PXE from the bios. Isn't it better to insert it as PCI OptionRom with PCI DEV/VEN adapter NVMe PCIe or another PCI device? Or maybe it can be inserted as ISA OptionRom? I used to do tests with BIOS AMI in MS VPC 2007 and I put PLOP in OptionRom for the PCI device Host Bridge: Intel Corporation 440BX/ZX/DX and works: plpbtrom -compress -vendorid 0x8086 -deviceid 0x7192 plpbt.bin plop80867192.rom I can also try to build an ISA or PCI OptionRom: Building a "Kernel" in PCI Expansion ROM P.S. If I want to boot WinXP 64-bit in UEFI mode, it is enough to integrate in the BIOS NVME DXE Driver in this way? : [HowTo] Get full NVMe support for all Systems with an AMI UEFI BIOS

I also prefer the dummy driver, especially since I also have an integrated Realtek sound card on this motherboard. In addition, I can also have a sound from a PCIe graphics card or a sound card on PCIe and even on PCI.

Use drivers from Fernando: Universal 64bit Intel RST AHCI+RAID driver v11.2.0.1006 mod+signed by Fernando.rar

I have ASUS B85M-E motherboard with two PCIe x16 slots (second work at x4). In the first slot x16 I have a graphics card AMD. I would like to buy the NVMe M.2 PCIe adapter (x4) and M.2 drive, e.g. Samsung 9xx Pro and install WinXP SP2 64-bit What adapter to buy and will it work? P.S. Information about PCIe/PCI slots from the user manual of the motherboard:

Read carefully the beginning of my previous post: Install dummy (null) driver for unsupported device

Why don't you use the WinXP SP2 64-bit version? There is already a hdaudbus.sys file 5.10.1.5013

I have not found a working driver but for the order in the Device Manager you can make a dummy driver. I did it by editing the IntcDAud.inf file from the XP64_14.51.7_5421_Dell_setup_ZPE.exe package. I changed 2806 to 2807 in two places in the [Intel.NTAMD64.5.1] section. I did the similarly with the ACPI\PNP0A0A device - I made a dummy driver: ; ** COPYRIGHT (C) 2007-2012 ASUSTeK Computer Inc. ; ; ASMBSW.inf ; [Version] Signature="$WINDOWS NT$" Class=System ClassGuid={4D36E97D-E325-11CE-BFC1-08002BE10318} Provider=%ManufacturerName% DriverVer=11/08/2012,12.14.17.909 [SourceDisksNames] [SourceDisksFiles] [Manufacturer] %ManufacturerName%=ASUS,NTamd64 [ASUS.NTamd64] %DeviceName%=dummy, ACPI\PNP0A0A [dummy] [dummy.Services] AddService = ,2 [Strings] ManufacturerName="ASUSTeK Computer Inc." DeviceName="AMDA00 Interface" Now I have all the drivers in the Device Manager

@liquidLD Does the Intel Audio HDMI: VEN_8086&DEV_2807 sound driver work for you?

I installed the Intel Haswell HD Graphics - GT2 graphics driver using the setup.exe file from Intel_Graphics_WinXP_V614105449.zip After the restart, the Audio Device on High Definition Bus driver did not install, so I tried manually by forcing from the 64bit\HDMI\Intchdmi.inf file but have error Code 10 and yellow exclamation mark. Device ID is: VEN_8086&DEV_2807 but there is no such string in the .inf file - they are only DEV_2802 and DEV_2803 I tried to edit the .inf file changing to DEV_2807 but it doesn't help.

@UsefulAGKHelper I have already checked it all in this topic: https://www.betaarchive.com/forum/viewtopic.php?p=434653#p434653 vbemp driver work in UEFI+CSM with Intel iGPU (I didn't test under pure UEFI with Intel iGPU) but I tested the vbemp driver under pure UEFI with the AMD 7450 PCIe card and unfortunately it doesn't work but then a normal AMD 7450 PCIe card driver for WinXP 64-bit works on pure UEFI I also tested a few NVIDIA graphics cards in UEFI+CSM mode (without GOP) and probably work with vbemp - I don't remember exactly but WinXP 64-bit on UEFI+CSM is not interesting and graphics cards without GOP will not work under pure UEFI. The screen from WinXP 64-bit in UEFI+CSM from vbemp or pure UEFI mode from amd7450 driver is displayed only from the moment of welcome: However, the Aurora boot screen is displayed using the graphics card firmware and winload.efi loader:

Thanks a lot - it works!

After clicking the three dots icon, the context menu is not shown. Only a circle is just spinning: WinXP, Firefox 52.9.0 ESR, Mypal 68.12.2b, Serpent 52.9.0. Interestingly, if I'm not logged in, the Copy Link menu appears: I can't log out either (I have to remove cookies): There is also a problem on the home page:

Serpent 52.9.0 (2022-08-24) 64-bit work OK on WinXP 64-bit. I am writing this post from this browser.

I tried different versions of MX 5.x but none works on WinXP 64-bit

Which version exactly, mod for WinXP or official? Please give me the link.

@Dietmar Thanks for the information. I already thought I was missing something in the system. I checked Firefox 52.9.0 ESR on 3 Windows: WinXP SP2 64-bit, WinXP SP2 32-bit, Win7 SP1 64-bit and there is the same problem everywhere.

I can't write posts on the forum. After clicking Submit Replay message appears: This field is required: and there are no pictures in the post. I write this post using Mypal 68.12.2b browser. The same problem is when I start Firefox in Safe Mode. A few days ago I restored the WinXP 64bit system from the image and before that there was no problem. P.S. Exactly the same problem is on the wincert.net forum. Both forums are Powered by Invision Community.

Why do you need an installer? Files are enough to put on the disk into the appropriate folders. This can be done, for example, with WinPE KB935551 seems to be an update 32-bit (SysWOW64 folder), so probably the file cewmdm.dll is the same for WinXP x86 and WinXP x64 https://web.archive.org/web/20160528151407if_/http://download.microsoft.com/download/e/1/f/e1fc9a52-a01a-40f1-938a-93f3fc85fa71/windowsmedia11-kb935551-x86-intl.exe https://web.archive.org/web/20071027024815/http://support.microsoft.com/kb/935551

@George King https://win-torrent.net/windowsxp_torrent/807-windows-xp-professional-sp2-x64-english-mui-rus-soft-updated-261014.html

@JFX WinPE works in 1024x768 32-bit and it cannot be changed. The 8-bit image (256 colors) looks completely different: And once again, for comparison, the screen with a defect looks:

I use the default settings. I tested the same WinPE also in legacy BIOS mode and there is no problem. The problem is only with pure UEFI.

I built ISO image Win7 PE SP1 64-bit from this builder: Win7PE_SE_2021-05-04.zip With Rufus I made a 16GB FAT32 pendrive in MBR partition scheme for UEFI (with GPT it is the same) I replaced loader UEFI on UefiSeven in the efi\boot folder - I deleted all files and copied these 3: bootx64.efi bootx64.original.efi (renamed bootmgfw.efi from Win7 SP1 64-bit Ultimate) UefiSeven.ini I boot a PC from this pendrive in pure UEFI mode (CSM disabled) and I have such a screen defect - photos taken with a digital camera: And this is what the screen shot looks like with the Print Screen key and pasted to the Paint and saved to .png file: And now an interesting thing! If I replace the sources\boot.wim file with KB3AIK_PL.iso\WinPE.cab\F3_WINPE.WIM and rename to boot.wim, there is no screen defect : The boot.wim file from KBAIK is based on Win7 SP0 but I also built Win7 PE SP0 and there is the same problem. The same graphic driver is used in both boot.wim files: vga.sys 5.2.3790.1830 (VgaSave service) boot.wim from Win7 PE - screen defect boot.wim from KBAIK - screen OK Why? What could be the reason?

@UsefulAGKHelper To see BSOD just run debug mode in BCD, connect RS232 cable to other PC and run WinDbg. I've figured it out a some time ago, both in laptops with an RS232 ExpressCard and in desktops with an RS232 PCIe card (old Win-Raid forum): and also on wincert.net: https://www.wincert.net/forum/topic/18477-i-am-looking-for-a-pcie-card-for-winxp-debugging/

I'm only interested in WinXP SP2 64-bit in pure UEFI mode. If the UEFI BIOS of the motherboard has CSM mode (Legacy), you do not need to use other loaders. Then NTLDR and NTDETECT.COM operates normally. Please do not post in this topic on legacy WinXP and create your own topic on the forum. I can help with legacy but not on this topic.

@UsefulAGKHelper First of all, GOP is not a Windows driver, but the UEFI firmware of the graphics card. Second - not every graphics card and its driver for WinXP 64-bit works in pure UEFI with UefiSeven + winload.efi loader from beta Longhorn 2008 Third - WinXP can run under pure UEFI with UefiSeven and installed graphics driver and running vga and VgaSave services, but for Sysprep it is necessary to disable these services because at this point there is no graphics driver installed yet. Sysprep installs the graphics card driver and only after restart WinXP works under pure UEFI. At this point it doesn't matter if vga and VgaSave services are started or not. It doesn't matter anymore. Sysprep is necessary because you will not normally install WinXP from a CD/USB in UEFI mode.