Dietmar
Content Type
Profiles
Forums
Events
Posts posted by Dietmar
-
-
I found this
https://github.com/jeremitu/PatchPae2
and
Has somebody tested it, if it is stable
Dietmar
0 -
Hi,
I just test win7 SP1, win8.1 on the Gigabyte z690 UD DDR4 board, both bit32 versions.
In win7 SP1 I have to change the acpi.sys against my modded version, because it shows Acpi A5 BSOD during install.
The for XP modded USB3 driver works there.
But compi is slow. A check shows, that only 790 MB ram are free, the same for win8.1.
Any idea, for to get more ram
Dietmar
1 -
You can take your original XP CD, name it to the *.iso from Ramsey in the folder
and integrate all the needed driver.
This is a fantastic possibility of the Ramsey XP Patch Integrator
Dietmar
PS: Later you update it with all the Posready Updates using this:
0 -
I also cant find the DSDT table in this Bios from ASRock QC6000M .
May be, that you can extract it on running compi via RWEverything or acpidump -b
Dietmar
PS: Do you find a speed compare of the cpu?
Interesting board.
0 -
In win98 you can disable any acpi with the setup /P i switch.
Interesting board, for all its devices there are XP SP3 driver, sound, lan ..
And Bios is from 2020. I just check, if there are Acpi2.0 orders in their DSDT
Dietmar
0 -
And here is the same tested Bios Mod for XP for to show processors in Device Manager and bring power consumption down as max as possible and no more "1000" unknown devices there,
for the MSI z690-A Pro board.
Procedure is the same:
Copy only
MSI.ROM (BIG letters)
to an fresh with Fat32 formatted USB stick and put it into the MSI board,
very left down, and press the Flash botton, left direct next
Dietmar
Biosflash is always a risk. So no garantie. For me it works.
You can easy go back to original Bios from webside, copy for this the original Bios to the USB stick and rename the original Bios there to MSI.ROM .
0 -
Hi,
look for Ramsey XP
Dietmar
0 -
You can easy go back to your original Bios:
Just copy the Original Bios from Webside on the with Fat32 formatted USB stick, rename it and repeat the procedure.
The name of the Bios file on this USB stick depends on manufacturer:
It is
creative.rom for Asrock
GIGABYTE.bin for Gigabyte (letters big size and small for bin)
MSI.ROM for MSI .
I just check this with reading out its new build DSDT, works
Dietmar
0 -
I found the reason for the Dxdiag.exe crash on z690 boards under XP.
It is the LED device under Hid conforme devices in Device Manager.
Just disable this (not the USB Hid),
and crash is gone
Dietmar
0 -
I did the same Bios Mod (last version F20b from Gigabyte Webside) for the
Gigabyte Z690 UD DDR4
board, for to enable the old processor definition thanks to @Damnation , which shows normal Processor in Device Manager and brings power consumption under XP down as much as possible. All the "Unknown Devices" are gone.
You have only to copy the Biosfile
GIGABYTE.bin
to an fresh with Fat32 formatted USB stick.
Put this stick in USB port left side, most up with name Bios written on this port.
Compi is shut down, but power is connected.
Press Qflash_Plus botton (on board).
The orange LED on the board begins to blink, and on your USB stick also.
Whole process laasts about 5 min. Dont shut power off as long as the LED is blinking!!!
At the end, all LEDs are out.
Restart compi, voila you see Bios version F20b, which also works for 13900k etc.
Dietmar
EDIT: Now no crash because of USB on this board
Gigabyte Z690 UD DDR4
when running dxdiag.exe .
Before, this Bios even do not recognice a CD-Rom device. Now it does.
Gigabyte repairs a lot in their faulty Bios.
Now this is also a nice z690 board for XP.
The Asrock z690 Extreme board still crashes with dxdiag.exe .
Biosflash is always a risk. So no garantie. For me it works.
BiosMod for Gigabyte Z690 UD DDR4
0 -
The methode does not work so easy on every compi, when you modd DSDT and SSDT1.
But this nice methode from you seems to work everywhere, to modd only DSDT.
You can see, what I did when you compare with Beyond Compare both *.dsl files.
The numbers of processors is here in DSDT always 64, this I check before
Dietmar
PS: I dont need to do any other with the Asrock z690 Extreme board for to flash this modded Bios.
Dont use this Bios on any other board!
As told on Website, disable before EVERYTHING about Security in BIOS Setup.
On Asus boards you have to put back its crazy cap, here no cap.
0 -
Yesssa, I did it
!
Was crazy much afraid, that I kill my Asrock Z690 Extreme board with this action.
I download the newest Bios 9.04 for this board from Asrock Webside, supports also 13900k cpu.
With UEFITOOL I extract its DSDT and modd it via the Methode from @Damnation and delete in DSDT also all the 64 "007" devices for "new" cpu definition.
Only DSDT is modded.
With iasl I make new dsdt.aml from it, all under XP SP3.
This I put DSDT back via UEFITOOL into the Bios 9.04 file from Webside.
This board has Bios Flashback. So no need for EEpromer.
But this Bios Flashback Methode has a bad side effect:
On my Asus Apex z370 I "succeed" to kill its Bios chip with wrong Biosfile and "Flashback".
There I can repair this with desoldering Bios chip and using EEpromer and new Bios chip.
On the Asrock Extreme z690 it is mechanical nearly impossible with Clip to go direct to the Bioschip, you have to solder it also.
But this time everything was ok.
I put the modded Biosfile named creative.rom on a fresh with Fat32 formatted USB Stick, put this USB Stick into the special slot down next to sound connector, 3 sec press Bios Flashback. And then programming laaasts about 2 min. Blinking red LED on USB stick and green from board.
Lightning on stick and LED from board went off and then crossing fingers: board starts, shows Bios 9.04.
This methode from @Damnation works on z690 boards
for to go away from "1000" unknown devices in Device Manager under XP.
The power consumption of the cpu goes down after this methode to nearly zero.
And the processor is now shown correct,
nice
Dietmar
PS: This are the files.
Very easy to use:
As told on Website, disable before EVERYTHING about Security in BIOS Setup.
Copy only
creative.rom
to an with Fat32 formatted USB stick, put it in Flashback port of the Asrock Z690 Extreme board and press "Flashback".
No garantie, for me it works.
0 -
Yeppp,
for to understand, if I am right,
I make a complete new readout of the DSDT file with acpidump - b under Win10 on the Asrock z690 Extreme board.
And then I compare the DSDT from just now and from 2 months ago.
ONLY the time stamp is different.
Ok, then I integrate with asl.exe the new modded DSDT into the registry of this board.
And voila, works.
Crazy, that time can make the difference for XP SP3 boot between a working DSDT and Bsod
Dietmar
From just now
0 -
I succeed to build an XP SP3,
which can boot via freeldr or ntldr on any compi,
meaning from IDE, any Sata, any USB any nvme device.
I build this XP on my Asrock z370 k6 board.
Then I test it for nvme boot on the Asrock z690 Extreme board.
Boots, everything works as wished.
But now comes a crazy thing: When I apply the DSDT patch (thanks to @Damnation) for to use the old processor definition on the Asrock z690 board, suddently compi showes BSOD.
Hm, I check the DSDT patch, everything is ok with this patch.
This can only mean one thing: After now about 2 months, the compi rejected the same static DSDT patch in registry,
which works before. Now I understand, why @Mov AX, 0xDEAD asks for to upload always the modded DSDT fresh to ram,
because there must be something crazy like a clock, which compares timestamp in loaded DSDT with actual time
Dietmar
0 -
It is not enough to do the same copy methode with whole folder "config" in system32.
Still the message "Hive not found" appears in this case.
And the Win Defrag, contig.exe and Wincontig make a very bad job:
When you later make a test with for example contig.exe you see, that a lot of files are still fragmented(!).
But via my copy method of system32, you see only one block and ALL
files there in are contigous.
On the Reactos side they mentioned, that they also noticed this problem with "Hive not found" as a very strange thing, that happens also in Reactos Setup.
They think, that the entries in freeldr.ini are not exact the same as in Hive system.
This I thought before also. But you can set in freeldr.ini what ever you want, still the message "Hive not found" remains.
Newer versions of freeldr.sys cant boot via NTFS. It was very funny, how I come to this special Debug version of freeldr.sys.
On Twitter a guy from Reactos team told, that he makes a try with NTFS. I think, that he can do this only because of the leaked SP1 Source files.
And then I look in nightly builds for this Author. Not on any other places is noticed, that this freeldr.sys can boot XP.
I tested also freeldr.sys around this special build. No NTFS boot
Dietmar
0 -
What helps for working freeldr boot is, to copy the whole folder system32 to another harddisk with enough free space.
Than delete the folder system32 on that XP, FROM where it is taken.
Run "Defrag" on this xp, which has now no folder system32.
Copy the folder system32 back to its original place.
So, it has to do something with, how the files in system32 are sitting to each other or
that one of the bootfiles is fragmented but until now, we do not found out, which file this is.
With a lot of work, you can make an XP with only the bootfiles, one by one, for to understand this problem.
freeldr has this problem, ntldr not
Dietmar
0 -
I make a try with contig.exe.
Before there where 6 fragments and after contig only 1.
But it is not enough to defrag the HIVE "system". Still the message "Hive cant be find" happens
Dietmar
0 -
Hi @jaclaz, nice to see you!
I just prepare a very easy XP SP3, only with the Sata1006 driver and acpi.sys 7777 integrated.
This I build with the nice Ramsey Integrator, because the error "Hive not found" happens not, when you take an original XP SP3 CD.
Here is the output of extents, waaaoh what a nice tool!
The question is, if the message from freeldr is correct for Hive "system" or if another bootfile is not found
Dietmar
PS: And soon I paste here also from the same XP install an output with working freeldr.
***************************
Bytes Per Sector:512
Sectors per Cluster:8
Cluster size :4096
Filesystem :NTFS
***************************
Filename:L:\WINDOWS\system32\config\system
File Cluster count :576 -> in bytes: 2359296
File size in bytes :2359296
File cluster first :363856
Extents count :6extents_[0] - VCN : 0 LCN : 363856 Lba : 2912896 Sectors : 2048
extents_[1] - VCN : 256 LCN : 342773 Lba : 2744232 Sectors : 512
extents_[2] - VCN : 320 LCN : 340357 Lba : 2724904 Sectors : 512
extents_[3] - VCN : 384 LCN : 340053 Lba : 2722472 Sectors : 512
extents_[4] - VCN : 448 LCN : 279942 Lba : 2241584 Sectors : 512
extents_[5] - VCN : 512 LCN : 332216 Lba : 2659776 Sectors : 512And here is the working one, yepp, there are differences.
This is the XP from the same installation, only copy files by hand
***************************
Bytes Per Sector:512
Sectors per Cluster:8
Cluster size :4096
Filesystem :NTFS
***************************
Filename:L:\WINDOWS\system32\config\system
File Cluster count :576 -> in bytes: 2359296
File size in bytes :2359296
File cluster first :216893
Extents count :1extents_[0] - VCN : 0 LCN : 216893 Lba : 1737192 Sectors : 4608
0 -
Now I think, that the problem is at another place.It seems, that the bootfiles for freeldr need to be at the very first bytes of the harddisk.
I come to this idea, because I succeed to boot an XP from Ramsey, which showed before the "Hive" error.
The only thing I changed is, that I copy those files again by hand on the with Winhex to 00 00 00 everywhere wiped out harddisk.
From XP SP1 I know this behavior, that it does not boot, when the bootfiles are too far away from the MBR
Dietmar
PS: In this case, the only thing what the original XP CD is doing better, is to put the bootfiles nearer to MBR.
EDIT: I just test my idea. Fresh installed XP, via freeldr booted XP shows install "Hive" error,
I copy all the files and folder of the installation to an extra Folder under another XP.
Then I copy the files in this order from that XP folder after deleting all files on the harddisk with faulty XP.
freeldr.sys
freeldr.ini
ntldr
ntdetect.com
menu.lst
grldr
The folder with whole Windows
then Documents and Settings
then programs
then all the rest together.
Pagefile I do not copy.
And voila, now this XP boots via freeldr and ntldr
Dietmar
0 -
Please write exact, what you did for the success in the last try "The 2nd SSD drive I used to install the XP ISO.."
Dietmar
0 -
Crazy Nlite,
needs some doing by hands,
but now it works. I integrated acpi.sys 7777 also in SP3.cab
and the Kai Schtrom Sata driver with storport.sys 4173.
Just now I am installing
Dietmar
PS: 40 years ago I learned Italian language
..
EDIT: Booting this XP SP3 via ntldr and freeldr both work
.
0 -
0
-
Do you have an original XP CD, this Italian one?
You can upload the *.iso of this CD and I try
Dietmar
0 -
No need to compress those files or to put into sp3.cab,
because XP knows nothing about them.
After opening folder for Nlite, just use integrate driver and then choose Textmode driver, showing to Nlite the TXTSETUP.OEM from Kai Schtrom
Dietmar
PS: The message "missing storahci.sys at the beginning of txt-mode"
can also mean, that you forget to mention storport.sys at all its places as @daniel_k told.
And you have to copy by hand storport.sys into i386 folder for Nlite.
0
Windows XP in hardware H110M-K Asus 2017 :Blue Screen
in Windows XP
Posted
@we3fan
Yepp, I tested a lot of different xp.iso CDs,
all work
Dietmar