If it's activated I can learn to live with the extra boot time however I need to fix my issue of getting it to boot to begin with.
Where did you get this info from? It could be informative for other forum users. I believe it was stated in other threads that the win 7 partition should be active for grub to do it's thing. Well, all we Mac users need now is a real slic 2.1 bios emulator wita an oem identifier
I get the same as on the first page from this thread. Warning: Unrecognized partition table for drive 80. Please rebuild it using a Microsoft-compatable FDISK tool(err=4). Current C/H/S=266305/255/63 Starting cmain() ... Warning: Unrecognized partition table for drive 80. Please rebuild it using a Microsoft-compatable FDISK tool(err=4). Current C/H/S=266305/255/63 Waiting 40 sec............ Permanently Activated! The Hazar loader works, so i can live with that
The Hazar loader definetly works on Mac's using Bootcamp. Now if we could only get rid of the annoying 40 sec. timeout...
Ok Great! My issue is fixed and it seems like everyone else has no issues to begin with except for the 40 seconds of extra bootup.
It was information I knew about from modifying the Tri-Boot system on my Mac. I just took 2 different things I learned and put them together to make my solution work. In order to access Windows XP tho I did have to delete "GRLDR" from the Windows XP drive and leave it on the Windows 7 drive. Now all I have to do is use rEFIt to select Partition 2 for Mac OS X, Partition 3 for Windows 7, or Partition 4 for Windows XP or Windows 7 (without Activation).
Hmmm, maybe the problem relates to the legacy bootloader all together. When Vista came out (same bootloader as Win 7) there where problems with dual boot XP and Vista configurations. It could well be the case in your configuration... Well, I do have an activated Win 7 using Hazar's method at the moment. I will look in the Grub options to find out if the 40 or so seconds delay can be omitted by appoiting just one boot good boot point for grub. Glad it finally works for you by the way
Does not work I still cannot get the activator to work on my Macbook Pro. I have a triple boot setup like pilot(leopard/7/XP). After i install the activator i get a blinking cursor for about a minute then it starts windows XP which is Partition 4. Anyone know how to fix this? I did a clean install and i get same result.
Oh believe me you'll start to get aggravated at some point with the long boot time if you start using 7 alot! I've noticed certain programs seem to run somewhat faster in 7 then OSX (email, browser)etc.... However, I don't know how long that will last since Snow will be seeing the light of day soon. All we need is a Mac hacker to take a look at this since I believe it is going to be an easy fix.
Would love to add to this thread but its beyond my technical skills. However I will give my input about problems I'm experiencing. I have an early 2009 Unibody MBP and have Win 7 build 7068 installed using bootcamp. Stupidly I ran one of the older cr**ks (I dont remember which exactly but I know it was v1.5). The cr**k removed the watermark and seemed to have removed the timebomb. However, over the last few days I have experienced the whole "Windows is not genuine" thing. I have tried running both the Hazar and Orbit30 (v4) lo*ders but neither works. I'm guessing this could be in part due to the fact I had one of the older cr**ks installed beforehand. The one thing I did notice though is that after running the Orbit30 (v4) lo*der I began to get the whole 'black screen/blinking cursor" scenario at bootup. It would boot after the 40 or so seconds but Win 7 is still flagged as "victim of counterfit" :S Can I get any idea about what I should do now? Should I wait for a new cr**k or just do a reinstall. I've got the 1635 build ready to go but am loathed to do the reinstall as I have a lot of apps/data/fonts etc on the Win7 partition. Any ideas would be greatfully received.
Download the bittorrent for Windows 7 OEM (7600.16385.090713-1255 64bit), then apply hazar's lo*der to it. Granted you'll still get the black screen with blinking cursor for 40 seconds at bootup, but Windows will be fully activated etc...and you'll have the real final version. It'll definitely be worth your time and effort!
Nope, it will still activate you just won't be able to get Windows updates until a new OEM master key is leaked. That shouldn't be too far down the path.