Hey HK, I made a gun and I am shooting at you, but wait a few days for bullets to become lethal. The same or what?
At the indicated time stamp in my machine, the eventlog says: The Windows Activation Technologies Service service entered the running state. The Software Protection service entered the running state.
My OEM Activation 2.0 Data is different:- OEM Activation 2.0 Data--> BIOS valid for OA 2.0: yes Windows marker version: 0x20001 OEMID and OEMTableID Consistent: yes BIOS Information:
You should know that MS is investing billions of USD in hardware, and if they can't accept 65 mil. connections in 24 hours, than something is wrong there or they are talking about rupees not USD>
Anyway, I've a little idea for when it reads directly from the chip. Doesn't that goes with a biosdriver? (you can find itin divecemanager => system devices. Can't we make a virtual bios then? Just like virtual cd drives used by alcohol/daemon tools/ultraiso etc. Those drives are nothing more than a driver which emulates a drive, and as far as I know windows can't see the difference between a real and a virtual drive. So maybe it's possible to make a driver which emulates a bios (a backup of a real 100% valid bios), and when you replace the existing bios driver with the emulatordriver windows still only sees 1 bios, but that's the virtual one. If WAT then reads bios data it will read the virtual bios and if the slic from the loader is the exact same slic as in the emulated bios then WAT won't see anything I think.