Jump to content

reboot12

Member
  • Posts

    168
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Poland

Everything posted by reboot12

  1. Which version exactly, mod for WinXP or official? Please give me the link.
  2. @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.
  3. 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.
  4. 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
  5. @George King https://win-torrent.net/windowsxp_torrent/807-windows-xp-professional-sp2-x64-english-mui-rus-soft-updated-261014.html
  6. @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:
  7. 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.
  8. 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?
  9. @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/
  10. 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.
  11. @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.
  12. 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
  13. 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 ................
  14. 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.
  15. 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.
  16. 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.
  17. https://www.betaarchive.com/forum/viewtopic.php?p=445485#p445485 Have you installed VMware Tools?
  18. 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 ?
  19. @roytam1 Can you add OAuth2 support over POP in the MailNews client?
  20. OE6 has stopped working. Has anyone checked if it works with two-step verification?
  21. Try Smart Defrag 4.1 or 4.2
  22. 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
  23. 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
  24. 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?


×
×
  • Create New...