Jessica Alba, thanks for that. I assume that you can reactivate again with your previous crack right? Did you right click and run this as admin? basically its having trouble finding "C:\bootmgr". That is really wierd. C:\ is is derived from the drive that SYSTEM32 is on. I'll have to do more testing... Really appreciate your help.
i have my bios modded all i have to do is reinstall my key and cert i was just testing for fun and i did run as administer
@Mr Jinje haha. Took me about 30mins to upload that to rapidshare (56k) Nah dont worry its fine, Share away @Jessica Alba Good good
I have tried two slics so far and it seems to be working, I wounder if this will help the Mac folks with boot times. this also might be a good option for the people that cant activate with a grub bootloader. . also will be easer to sneek into a Windows 7 install DVD
I flex new bootmgr into PCAT and WinSXS folders to replace the original in both places. Worked fine in VMware. MountedWIM:\Windows\Boot\PCAT Folders were protected by TrustedInstaller, so I had to first take ownership of the folder with right click > take ownership reg tweak, then once I had ownership of the folder, I could get replace the bootmgr.
I think this is cleaner method versus hacking the bootsector. If microsoft can push a new bootmgr via Windows Update (never happen except during Service Pack), I see no reason why they cannot run Bootsect.exe and close out GRLDR when installing a Service Pack. This is a moot point.
I know I won't be adding it to my tool because I don't want to be held responsible for what happens when MS patch it and the user can't get back into their system so format and lose everything. You have to think from a users standpoint, not everyone knows how to restore/fix the bootmgr without being online to read how. Now when will it be patched, a week after retail release, a month, 2 months who knows... but pretty much any kind of tool thats ever modified Windows system files (in a piracy type way) has always got patched. It's a shame because I would like for this to work, it would/should work for just about everyone and props to Karsten for trying but like with Vista this method didn't take off for a reason. You shouldn't jump the gun and get excited here guys... if you are going to use this method you should really warn the user they risk MS putting out an update that could change their bootmgr and cause the system to fail to boot. It's all cool and working now just as the Vista one was, but think about later. At least with GRLDR even if MS done anything the users system would still work is the point.
I learned a long time ago that inserting the absolute path to a file or directory saves me alot of trouble in the long run, and makes the sript able to run without error anywhere on the system.
But Daz, they would patch it to the default, so it wouldm't render it unbootable. They could just check the file modification dates or some other value and just put it back again.
You think they would care to put it back? On Vista they just changed it and left everyone unbootable lol.
Wow. Really? That sounds bloody crazy. I didn't think this got patched? The first ever activator I made (Wrote it in jan 08) Used the modded bootmgr files, but I switched to a loader to make my Vista and Server 2008 activator at antiwpa. Crypto will tel ya all bout that
If microsoft caught this, they would just replace it with a clean copy, and or nag you about non geniune OS this would look more like you had a rootkit pach your bootmgr, microsoft probably wouldnt just f**k someone over like that.