reboot12
Content Type
Profiles
Forums
Events
Posts posted by reboot12
-
-
On 10/4/2022 at 3:57 PM, Tripredacus said:
Yeah but does HDMI audio work?
Read carefully the beginning of my previous post:
On 10/3/2022 at 11:34 AM, reboot12 said:I have not found a working driver but for the order in the Device Manager you can make a dummy driver.
Install dummy (null) driver for unsupported device
QuoteA null device is recognized but not used and will not be started.
0 -
Why don't you use the WinXP SP2 64-bit version? There is already a hdaudbus.sys file 5.10.1.5013
0 -
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
0 -
Does the Intel Audio HDMI: VEN_8086&DEV_2807 sound driver work for you?
0 -
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.
0 -
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:
0 -
Thanks a lot - it works!
0 -
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:
0 -
Serpent 52.9.0 (2022-08-24) 64-bit work OK on WinXP 64-bit. I am writing this post from this browser.
0 -
I tried different versions of MX 5.x but none works on WinXP 64-bit
0 -
On 8/20/2022 at 12:28 PM, Dietmar said:
and also the Maxthone 5 browser
Which version exactly, mod for WinXP or official? Please give me the link.
0 -
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.
0 -
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.
0 -
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/20071027024815/http://support.microsoft.com/kb/935551
0 -
-
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:
0 -
3 minutes ago, jaclaz said:
But which settings do you have for the video driver (resolution, number of colours, frequency, etc.)?
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.
0 -
- 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 OKWhy? What could be the reason?
0 -
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/
0 -
21 minutes ago, UsefulAGKHelper said:
The mistake with the code is that vga drivers will be removed even on legacy mode so there will be added an "if" command to ensure that the code works on uefi mode only.
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.
1 -
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.
0 -
15 hours ago, UsefulAGKHelper said:
VGA-only drivers should be disabled only when VGA emulator is absent.
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 31 -
6 hours ago, UsefulAGKHelper said:
If you use VGA emulator like FlashBootPro/UefiSeven, then it's no longer required to disable VGA. In fact, windows won't even display the screen if vga.sys/vgapnp.sys are disabled even if VGA emulator is used.
VGA-only drivers should be disabled only when VGA emulator is absent.
I have to check it again.
6 hours ago, UsefulAGKHelper said:I can boot xp x64 from VirtualBox EFI using FlashBootPro bootmgfw.efi and xp vga.sys with GUI boot disabled as long as the VGA emulator inside bootmgfw.efi (generated by FlashbootPro or UefiSeven) is present.
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)
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 ................
0 -
9 hours ago, George King said:
Is signed driver requirement only for winload.efi Driver signature enforcement problem?
Signed drivers AHCI, graphics etc. must be for sysprep.exe:
0
XP Pro x64 OS Boot NVMe
in Windows XP 64 Bit Edition
Posted · Edited by reboot12
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: