Sunday, September 14, 2008

Virtual Machine - Problem #1 PXe

Currently, I am attempting to get past the PXe boot program which is reinstalling their access to my computer.

The PXe program is executing before the computer gets to my hard disk to run any protection software.

The PXe program seems to be stored in the BIOS memory.

Reloaoding the BIOS is not effective as there is some sort of BIOS Memory Manager Program which is blocking any change or update to the BIOS.

If I reset the system by pulling batteries, erasing CMOS etc, the Memory Manager seems to pull the Windows Validation with it as it is deleted.  

So it is necessary to reinstall Windows, BUT you will not be able to run Windows without connecting to Microsoft to validate.  

When you try to connect to Microsoft, you will reinstall the surveillance program.

If you try to connect and get the validation code via phone support you will get the run-around of your life.   I was disconnected multiple times after holding for hours, being transferred around from one level to the next, and then being told that the database was down and there was no way to provide validation.  I should call back the next day.   (This happened several times - months apart.)

Imagine the frustration of spending entire days on the phone with support only to be told it was for nothing and you could start again the next day - only to get the same script on subsequent calls.  When the situation arose last week again, it became very clear that this was a defense method of the program and not just a random file loss on the pc.

It is necessary to get around the PXe, and there doesn't appear to be a way to get around one which has defense mechanisms which will only require you to connect to the web.

Trying to find a solution for this.

No comments: