Some facts are strange: The Hwdirect dump shows OEMX table. Length 176h (shown at table length byte) at BFF80470h physical address. The table contains no pubkey (RSA data) and no marker data. The maker data is found at 1b module at offset 1AEE9h to 1AF84h. There are also exactly B6h zero bytes as space remaining for the marker field, but no marker data at 1b module. There is absolute no marker data found neither at any module nor at the biosfile itself, activation without any maker data? Is the marker found data somewhere, but encrypted? Why contains the 1b module the public key data (RSA field) but it's not mapped to OEMX tables' physical address??? Anyway the 1b module contains a SLIC entry at offset 50EE5h, but AcpiScope doesn't show a SLIC table......also Acpiscope doesn't dump the whole OEMX table, why? Hmmmm.......... I'm curious about that OEMX table. Would be that empty table alone be able to activate Vista??? I don't think so. There must be another mechanism to activate....... To play with it would be nice. I need to know what will happen if the RSA data will be removed from the 1b module.......also I would like to know if that OEMX table alone is able to activate. Edit: What's that OEMB table? Hmm.... 71h bytes are too less to hold the marker......
Yen - pretty much what I found. Mustang Sally - just to confirm: 1) You have no bootloaders and nothing resembling the remnents of bootloaders. 2) Windows definitely shows the genuine icon. 3) What certificate and key did you use (ie ASUS.XRM-MS and 6F2D7 key)?? 4) What SLIC method did your previous BIOS use?? Andy
1) this notebook came with vista hp preinstalled 2)yes it's genuine 3)I had installed Ultimate with ASUS.XRM-MS and 6F2D7 key, no problems 4)Previous bios showed the factory asus slic in everest, no slic in everest with new bios. Just tried an install on a new hard drive and got the 30 day to activate. tried the asus restore disk and got Cannot load imagex 0 from src WIM file error. (somethings have definately changed) contacted asus and now they want me to rma. will keep everyone posted when i recieve it back. The drive i took out is still activated and genuine. thank you everone for your input
These points aren’t clear to me, need brain storming: The original bios 207 has a SLIC table, it activates Vista, right? The original bios 209 has no SLIC, but OEMX table, it activates Vista, right? Why your Notebook became unactivated? Which bios version was modded to install OSX? It came with HP preinstalled NOT Asus??? How do you know it is HP? The bios 207 has a ASUS SLIC right? How was it activated? Against HP cert.???? Probably it uses the Asus certificate, but HP OEM logo???? The RSA data at bios 209 matches to the _ASUS_Notebook. Please clarify, thanks… this is really exciting……
yes yes, h/p only not ultimate loaded ultimate on another drive (worked with 207) both sorry thats home premium. Thanks Yen
QUOTE The original bios 209 has no SLIC, but OEMX table, it activates Vista yes, h/p only not ultimate UNQUOTE I wonder if there are coming with a more powerful and intelligent way of stopping us........ SLIC sounds like a "generic" OEM systems that allows ANY version provided that certs and key match. OEMX is that stands for a "new OEM extended approach"? Looks like only allows the particular OEM disc and version and that is it ?
New version v1.02 FIX: Overflow bug in unlinked module scan code FIX: Handle module 1B checksum errors Andy
Andy, just for my ignorance........If OEM's use DYNAMIC only, what are the risks after mod,successful OS running, etc,etc, and then a few months down the track you want to put more memory in the machine or use other slots by adding hardware. I am thinking in memory conflicts with a fixed method, or SLIC tables would never touch other modules in a BIOS when expanding a system ? Thanks
This sounds to me that some data (public marker) is stored somewhere additionally. Usual SLIC activation works.(207) OEMX activation works only with home premium AND only at the drive that comes with the Notebook? It's probably stored at the bootsector, or the preinstalled home premium uses a special bootloader. Have you tried to activate a HP home premium install on 'the other' drive using 209?