Can the Hyper-V BIOS be modded?

Can someone please post the sum32 and the ChecksumApp apps. I checked all the links in this thread and they're all dead.

TIA

 

You need to login to view this posts content.

 

Thanks alot nexus76 . Now time to do some modding and testing.

 

Files are deleted. It is possible upload it again ?
Thank you

 

17334 vmwp , xp sp3 (dell) can not work. Need to activate.

17334 vmwp , xp sp3 (dell) can not work. Need to activate.

 

I have not added any SLP1 string to the 1b module. Just use the GENUINE C&C [8B2EBECB] OEM set to activate XP.

 

Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Virtualization]
"BiosLockString"="AcerSystem FSC SYSTEMDell System"

or whatever you like to activate ...

 

You need to login to view this posts content.

 

Does anyone happen to have a tutorial on how to mod the HyperV vmwp.exe? I have done other SLIC mods and have used hex editor before but HyperV stumped me.

After going back and forth through this thread it seems I have to find the start of the 1b module, extract it, mod it, use the ChecksumApp.jar to fix the checksum on the 1b module and then resinsert it into the vmwp.exe. Is that correct?

My question is how do I find the start of the 1b module and how long is it?

Thanks

Edit: I figured it out by looking over a few mods that others have posted.

 

Inge, the vmwp.exe in your link appears to be the original exe. When I look at it in hex editor I am still seeing the Microsoft virtual SLIC. I also am seeing the virtual slic in my VM using RWEverything.

 

Correct, it is only for SLP1

 

Thanks, updated.

 

You need to login to view this posts content.

 

sebus,

Thanks for the reply. None of the posts you linked to tell specifically where the 1B module starts (unless I am missing something). The first linked post states: "You know (by comparison of the known module from previous version) that the end of 1B module is 01 80 06 80 06 01 80 FF FF FF. You also know (again by comparison) that somewhere towards the beginning of the 1B module would be FF FF 1B 80 00 00 00 00 14" which is correct for the end of the 1B but it doesn't tell exactly where the start is. Knowing the length, you could back calculate the exact beginning since this tells where the end is.

I found the 1B starts with "D4 41 03 00". Your included screenshot actually tells the whole story. I am new to this so if I am mistaken please correct me.

 

You need to login to view this posts content.

 

Inge,

The module header information you linked to helped to understand the structure of the header.

I successfully modded my own exe last night. The only missing piece I needed was the start and stop of the 1B which I figured out. Thanks for your help guys.

 

You need to login to view this posts content.

 

Just a question, does this work

1. Activate Physical Hyper V Host via KMS
2. Activate VM's on the Physical Hyper V Host via AVMA

 

As Tito said, but it can be also OEM or Retail activation, as long as the host is activated.
And if KMS then KMS server can even be the VM (of course fully activated from MS or otherwise...) like a loop: you are activated, as I am activated, cause you activated me... surreal