reboot12

That's not true. vga and VgaSave services must be disabled otherwise it will be the error 50 that caused the vga.sys file: Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Opened \\.\com3 Waiting to reconnect... Connected to Windows Server 2003 3790 x64 target at (Thu Aug 11 07:39:01.106 2022 (GMT+2)), ptr64 TRUE Kernel Debugger connection established. Symbol search path is: *** Invalid *** **************************************************************************** * Symbol loading may be unreliable without a symbol search path. * * Use .symfix to have the debugger choose a symbol path. * * After setting your symbol path, use .reload to refresh symbol locations. * **************************************************************************** Executable search path is: ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe - Windows Server 2003 Kernel Version 3790 MP (1 procs) Free x64 Built by: 3790.srv03_sp2_rtm.070216-1710 Machine Name: Kernel base = 0xfffff800`01800000 PsLoadedModuleList = 0xfffff800`019d5100 System Uptime: not available Intel Storage Driver Ver: 11.2.0.1006 *** Fatal System Error: 0x00000050 (0xFFFFF800000C0200,0x0000000000000000,0xFFFFF80001CA664D,0x0000000000000000) Break instruction exception - code 80000003 (first chance) A fatal system error has occurred. Debugger entered on first try; Bugcheck callbacks have not been invoked. A fatal system error has occurred. ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe - ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff800000c0200, 0, fffff80001ca664d, 0} *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll - ***** Kernel symbols are WRONG. Please fix symbols to do analysis. *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* *** ERROR: Symbol file could not be found. Defaulted to export symbols for hal.dll - *** ERROR: Symbol file could not be found. Defaulted to export symbols for VIDEOPRT.SYS - *** ERROR: Module load completed but symbols could not be loaded for vga.sys *** ERROR: Symbol file could not be found. Defaulted to export symbols for win32k.sys - *** ERROR: Module load completed but symbols could not be loaded for vga.dll ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Probably caused by : vga.sys ( vga+56d9 ) Followup: MachineOwner --------- nt!DbgBreakPointWithStatus: fffff800`01826db0 cc int 3

I have to check it again. Virtual machines operate differently from a real computer with pure UEFI and a graphics card that has a GOP. Virtual machines are not suitable for pure UEFI testing. UEFI in VirtualBox is not pure UEFI because legacy graphic bios is used in this mode: Legacy VGA ROM in memory C0000: 55 AA 40 (40h*200=8000h=32768 bytes=32KB) c0000.zip Qemu with OVMF pure UEFI bios use VGA emulator similar to UefiSeven: 000C0000 56 45 53 41 00 03 22 00 00 C0 01 00 00 00 27 00 VESA..".......'. 000C0010 00 C0 30 00 00 00 2B 00 00 C0 30 00 00 C0 3D 00 ..0...+...0...=. 000C0020 00 C0 51 45 4D 55 00 F1 00 FF FF 4F 56 4D 46 00 ..QEMU.....OVMF. 000C0030 51 45 4D 55 20 51 58 4C 20 56 47 41 00 4F 56 4D QEMU QXL VGA.OVM 000C0040 46 20 49 6E 74 31 30 68 20 28 66 61 6B 65 29 00 F Int10h (fake). 000C0050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 000C0060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Signed drivers AHCI, graphics etc. must be for sysprep.exe: Note If the OEM-supplied drivers are not digitally signed, the mini-setup wizard postpones the installation of the device until an administrator logs on to the computer. This is referred to as client-side versus server-side installation, which occurs during mini-setup.

Necessary things: graphics card with GOP firmware and drivers for WinXP 64-bit - I tested only one AMD HD7450 en_win_xp_pro_x64_with_sp2_vl_x13-41611.iso Win7, 8 or 10 ISO image for disk partition by diskpart SATA-USB case/adapter signed Intel SATA controller drivers for WinXP 64-bit signed AMD HD7450 drivers for WinXP 64-bit UefiSeven 1.3.0 64-bit loader efi files from beta 64-bit Windows Server 2008 Longhorn 6001.16497 (patched winload.efi) BOOTICE v1.3.3 x64 Debian Live 6 x86 VMware Workstation 8 Target PC spec: MB ASUS P8H61-M LE R2 (CSM disbaled, AHCI enabled) CPU Sandy Bridge i3 HDD 2.5" SATA (tested with 60GB) Graphics Card AMD HD7450 with GOP Reference PC with VMware Workstation 8 installed (I use ThinkPad X61 with WinXP 64-bit :-) ) spec: Virtual Machine WinXP Pro 64-bit HW 5.x CPU amount 2 RAM 1024MB HDD IDE 3GB CD/DVD IDE Step-by-step instruction: in VMware, create a WinXP Pro 64-bit machine: start the machine from ISO e.g. Win7 and partition the disk with diskpart: diskpart sel disk 0 clean create par pri size=100 create par pri active exit install WinXP SP2 64-bit on partition 2 C: (format NTFS) after installation, disable page file, system restore and automatic restart in System Properties add an account with administrator privileges and restart the system to work with this account format the D: partition (100MB) as FAT32 shut down the machine, close VMware, make a copy of the .vmdk file with WinXP installed (so as not to reinstall if something goes wrong) start the machine and copy the necessary files to the appropriate locations - I have these files in the sysprep_V2.iso image, which I made with the UltraISO program: EFI directory with UefiSeven loader and BCD copy to FAT32 partition Sysprep dir with the appropriate sysprep.inf file copy to C: Drivers dir copy to C: winload.efi file copy to C:\WINDOWS\system32 BOOTICEx64.exe copy to C: run BOOTICE, click BCD tab, open file D:\EFI\Microsoft\Boot\BCD (Professional mode) and edit the values ApplicationDevice and OSDevice by setting the C: partition: enable hidden files, remove display.inf from C:\WINDOWS\Inf run regedit and delete services vga and VgaSave from HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services run sysprep.exe from C:\Sysprep, select Quit and click Reseal and OK: shutdown machine and close VMware using a SATA-USB adapter, connect the target SATA 2.5 drive to the computer where you have VMware installed start VMware and add this disk to the WinXP configuration as PhysicalDrive1 (Use entire disk): mount the Debian ISO image and boot the WinXP machine from it - just don't let the machine boot from the hard drive where you have sealed WinXP - hit Esc quickly and select CDROM from the Boot Menu: now clone sda WinXP machine drive to connected real sdb drive (this will take a few minutes): fdisk -l (read Units bytes from sda drive and last cylinder sda2 partition - should be 8225280 & 392) dd if=/dev/sda of=/dev/sdb bs=8225280 count=392 poweroff Debian, close VMware, Safe remove USB connected SATA HDD and disconnect the drive from the SATA-USB adapter boot target computer (my ASUS) to bios and set disk controller operation mode to AHCI, disable CSM and disable integrated iGPU connect the SATA drive with sealed WinXP to your target computer (me ASUS) and boot the computer from it Aurora green wallpaper will appear, after about 1 minute the computer should restart and we have a working WinXP 64-bit on pure UEFI P.S. Who wants the sysprep_V2.iso image please write a private message.

But I don't want to download 4GB XP2ESD to create an ISO ~700MB. You could write in short points how to make an ISO based on WIM.

https://www.betaarchive.com/forum/viewtopic.php?p=445485#p445485 Have you installed VMware Tools?

XP2ESD is interesting but contains a lot of updates and additions. You could write a tutorial on how to make a clean ISO WinXP image based on .wim ?

@roytam1 Can you add OAuth2 support over POP in the MailNews client?

OE6 has stopped working. Has anyone checked if it works with two-step verification?

Try Smart Defrag 4.1 or 4.2

You need to disable Intel 3000 card in bios instead in WinXP.

It's not true. UefiSeven is stable but cannot unlock C0000 memory on some computers: UefiSeven test I have a PC in which I have CSM turned off (UEFI class 3) and I run WinXP SP2 x64 on it without any problems using UefiSeven WinXP x64 + UefiSeven

Qemu (virt-manager) is best run on Linux host e.g. Debian 9. I tested WinXP 64-bit and it works very efficient especially with a second host PCIe graphics card: PCI passthrough karty graficznej na Debian 9 64-bit

The link in my post works! This is a link to the Polish Intel website. Maybe the link to the Polish version does not work in your country. This is a link to the US English version of the Intel website: https://www.intel.com/content/www/us/en/download/16545/22644/intel-hd-graphics-driver-for-windows-xp-64-exe.html?

OK, already found out, you need to delete the %appdata%/OpenSource folder

I tested several email clients on WinXP that support OAuth2 (IMAP is required). Read this: Yahoo mail and OAuth2 I tested with Google Chrome 49.0.2623.112m set as the default browser on the system Two programs are best: MailNews - tested version mailnews.win32-20200815-b8025053-uxp-d3383327a-xpmod.7z POP Peeper Pro - tested version 5.1.1

How to delete an account from Outgoing Server (SMTP) in MailNews? The Remove button is unavailable. Where is the MailNews data stored in WinXP?

I use the Arduino IDE 1.8.9 in my ThinkPad X61s in WinXP SP2 64-bit, C2D 1.6GHz, and CPU usage is also very low. I have Java8 (1.8.0) installed in my system this way: Java8 on WinXP Arduino IDE installed with the installer from the file arduino-1.8.9-windows.exe I also tested other older IDE versions - 1.8.2, 1.8.3 and they also work. There are compilation errors in newer versions of the IDE.

use nLite 1.4.9.3 to integrate 64-bit SATA/AHCI your disk controller and WinVBlock drivers to WinXP 64-bit ISO image (if in the bios there is an option of the disk mode in PATA, IDE, Compatibility then turn it on and you can not integrate the SATA driver) rename the ISO image to xp.iso connect a USB flash drive (1-2GB USB 2.0) format it to FAT32 with USB Disk Storage Format install GRUB4DOS on this USB flash drive copy the files to the flash drive: grldr, menu.lst, to subfolder images: dummy.ima, xp.iso boot from this USB and select: TXT-Setup WinXP - phase 1 when the message to restart the computer appears, restart it from USB but this time select: GUI-Setup WinXP - phase 2 when phase 2 of the installation is complete and the computer restarts, boot it from the hard disk (remove the USB flash drive) Note1: You must have at least 1GB RAM for the xp.iso image to fit in the memory Note2: If the flash drive is detected by the BIOS as USB-FDD and not USB-HDD, then you have to remove this lines from the menu.lst file: map (hd0) (hd1) map (hd1) (hd0) winvblock.zip usb_disk_storage_format.zip g4d_install.zip grldr menu.lst

Is it about IOBit Smart Defrag? Which version?

Officially, it does not support, but I would try the drivers for individual devices from the manufacturers websites e.g. for Intel HD Graphics 3000/4000 driver is winxp64_145111.exe

I noticed a strange thing. If I run a ThinkPad X61s computer with WinXP SP2 x64 while a Samsung smartphone is connected to it via USB, there is no volume icon in the tray. The sound in the system works, I can also manually run the sndvol32 volume control. Re-enabling the icon in the control panel does not help:

In WinXP 64-bit you can use hibernation but it depends on the hardware. All you need to do is switch in boot.ini: maxmem=4096 ThinkPad X61 C2D, 4GB RAM - hibernation OK ThinkPad X220 i5, 8GB RAM - hibernation FAIL WinXP 64-bit hibernation

Still using WinXP SP2 64-bit on two PC's - the best system in the world PC1 ThinkPad X61 C2D 4GB RAM, docking station with LPT and COM ports. I mainly use for browsing the Internet. Page file disabled. PC2 Sandy Bridge platform ASUS P8H61-M LE R2, Intel i3, AMD HD7450 + 2K LCD monitor (2560x1440) connected over DP-DP cable, M-Audio Audiophile 2496 PCI sound card. This PC is not connected to the Internet and I only use it for audio/video FullHD/720p production with Sony Vegas 9 64-bit at 2560x1440. My favorite games also work: CueClub2 at 2560x1440 Worms World Party Remastered 2015 at 2560x1440 - you can see the entire island, not just part of it, as in the old version NFS3 modern patch at FullHD 1920x1080

@wimb I was able to build WinPE10 64-bit with Win10PE_SE_2016-04-08.zip (Host OS and source DVD the same - Win10 enterprise LTSB 2015) but I don't like it - building the ISO - including solving the problems took me about 3 hours : builder stops with an error: Wimgapi was not found after searching for help on the internet for a long time, I found a solution: the file wimgapi.dll 64-bit is missing in Projects\Tools\Win10PESE\x64 very long build time - I don't know why it processes install.wim - wouldn't boot.wim alone be enough? VMware UEFI64 test: WinPE starts with error pecmd.exe Firefox not start: there are no interesting tools and the ISO image is 650MB ??? I know a simpler way to build a WinPEx64 ISO: download boot.wim x64 from ADK extract .cab file, rename filad61... to boot.wim open source Win10 DVD x64 ISO in UltraISO delete support folder and all files and subfolders in sources directory copy downloaded boot.wim to sources directory change label to win10pe_x64 and save ISO as new file e.g. win10pe_x64.iso ->> ISO image is ready in few minutes (instead of a few hours) and only has 246MB Of course, you can edit the boot.wim with gimagex.exe or ISO with UltraISO file before and add your applications, e.g. Total Commander, BootICE etc. It's best to convert the WinPE.ISO to a bootable USB stick (e.g. using Rufus) and copy the portable applications to USB - as much as we want, fast and comfortably. There is no desktop, but you can easily run a GUI application using CMD or Total Commander: Sorry, but WinPE is supposed to do the make job, not for look like candy