well paradox first loader was blacklisted but it was not done in MBR so files were in the system, i think thay use some driver to emulate bios ACPI ... also bunch of time stopers and rest of the crap were detected by M$ update...
Arn't vista loaders easily detected by M$ now?? (loaders for sp2 and sp1) so won't win7 loaders be detected as well?
There are so many different legitimate boot-up methods in the world amongst all the different BIOS's, multi-boot managers, etc. as well as a multitude of legitimate ways that ACPI/SLIC tables get built, that it would be very difficult to detect and neutralize just those that are cheating Vista/Win7 and not break a ton of legitimate systems in doing so.
could enybody help me?? I wrote a post on 16 page, and I still don't get an answear. please tell me, what does men that error, which pop up me when I try active windows 7 no matter what activator....
mac boot camp virtualization? I know this is a retarted question but is this possible using mac bootcamp? or virtualizations like parallels?
after trying all the activators and other options.the last option would to do a fresh install and try again.(cause you used the other ones first)
Opa, I think it only fair we let Mac users know that after applying either loader by hazar or Orbit your Mac will take approximately 40 seconds to boot Windows. Granted it will be activated but the 40 second boot time is a real pain. So we still need a fix on the Mac side of things.
As i said before, i doubt about it if there'll be ever a solution for the 40 seconds delay problem. With Vista it was the same. It's such a shame that nobody takes the effort to solve this. If i was no noob in that area then this problem was already fixed.