Jump to content

Updated drivers for Windows XP SP3 and Windows 2003 SP2 (x32/x64) for modern hardware


Recommended Posts

Posted

@reboot12

I find the Mac in first 6 Byte in the very beginning of the GbE-Region,

at 00001000 (Hex) with Windbg. On your Bios from seller stands there

88 88 88 88 87 88 (00 08)

and for me

C4 00 AD 65 E8 90 (01 08)  interesting, why there stands a 01 and from seller 00. All other Bit around are identic

Dietmar

 


Posted

@reboot12

I use only Winhex and NOT UEFITOOL for this operation, because only in GbE-Region MAC should be set.

And I set the checksum at 0x107E–0x107F to 1E 3D via Winhex.

 

Now I look for settings of NVram and the "Default" values in Bios

Dietmar

Posted (edited)

@reboot12

I think, the NVram block starts from

NVRAM-FV: 0x1800000 - 0x182FFEF (both Bios)

Then comes a single line from 0x182FFF0 - 0x182FFFF  with

6F D2 99 45 11 1A B8 49 B9 1F 85 87 45 CF F8 24

This line belongs also to NVram, as you can see from the lenghts written in first bytes of NVram.

It is the last line of NVram.

0x1800020: 00 00 03 00 00 00 00 00 means a length of all together form NVram of 0x30000 Bytes.

on both Bios

Dietmar

Edited by Dietmar
Posted

@reboot12

"Do your motherboards with i219 cards have the ME region and did you have to disable it for the i219.sys driver to work?"

The AIMB-786 is the only board, where I have to kill ME explicit. All have ME, because i219 is introduced in 2015 and there

was NO motherboard from Intel from those days without ME. Crazy spy tool ME, like Terminator:cool:.

On all the other boards with the i219 lan device, it was enough to kill ME influence only in the driver.

I tried yesterday evening this hack also in the i219.sys driver for the AIMB-786 but fail.

I wrote here, that I can see LIVE the changing back of registries only because of ME

Dietmar

Posted (edited)
14 minutes ago, Dietmar said:

I think, the NVram block starts from

NVRAM-FV: 0x1800000 - 0x182FFFF (both Bios)

In bios dumped from mobo NVRAM data present also after 0x182FFFF:
after-182FFFF.png

I found last string "NVAR" in offset 0x1FB8D9E:
last-NVAR.png

Edited by reboot12
Posted

@reboot12

Yes, we need to be careful as much as possible.

I edit my post before. Because in this region, also some data are written in the NEW Bios

Dietmar

Posted
10 minutes ago, Dietmar said:

Yes, we need to be careful as much as possible.

Make current bios full backup:

fpt -d backup.bin

Then flash another one. If something be wrong then you always back flash backup.bin

Posted (edited)

@reboot12

This Hex values

6F D2 99 45 11 1A B8 49 B9 1F 85 87 45 CF F8 24

appear 6 times in the Old Bios from motherboard extract,

and 5 times in the NEW Bios

Dietmar

Edited by Dietmar
Posted

@reboot12

I make 3 different extract of my motherboard Bios!

And after this, I compare each with each other, if they are the same.

Because in past I have to learn painful,

that even 2 copies can be not enough,

because when 1 Bios extract fail, which is the correct one

Dietmar

Posted

@reboot12

I just identified this bytes

6F D2 99 45 11 1A B8 49 B9 1F 85 87 45 CF F8 24

as a GUIDE

4599D26F-1A11-49B8-B91F-858745CFF824

StdDefaults in AMI/UEFI variable listings.

Strange, how this Little Endian is here mixed in this Guide via pure Hex

Dietmar

Posted (edited)

@reboot12

Now begins the hard part

I want 

Setup Item Hidden=disableME=disable, CSM=enable , Fast Boot=disable, HII=enable

in "Default" Bios settings

Dietmar

Edited by Dietmar

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...