Well, I tried a Win 7 OEM 64 bits with hazar's beta 2 loader, and the same thing.... black screen with blinking cursor _ _ _ _ 1 min, 2 min 3min _ _ 4min _ not working Any idea? Thx for ur help
I tried the USB thing before and didn't have any luck. What is boggling my mind is that my OEM copy of Windows XP (with legit key) works perfectly through boot camp, and Windows 7 boots up every time up until the point I try to activate it with a loader or whatever.
I have tried everything, the problem comes with the loaders! Cause when I reboot to my win 7 partition not using the loader, it works perfect. When I use the loader, I have the black screen with the f*** blinking cursor I will gi it another try, will unplugg all my usb and fireware conexions... but I ampretty sure the problems comes with the loader and the mac intel EDIT: I tryed everything again (no usb attached no fireware...etc..), and the same problem..black screen blinking cursor Maybe someone can work on a working loader for mac user and this issue on bootcamp and win 7
Be careful about Chew WGA guys. It modifies important windows files and kind of breaks some things accidentally. You will need to reinstall your OS if you want full abilities such as windows updates (it crashes out with error messages right now).
It appears none of the folks who created these loaders know enough about the inner workings of it to successfully modify it to work on Macs. I would have thought it by now it would have been rectified, but I guess it is trickier then I first thought.
lol excuse me? I am working on it. AFAIK the problem arises in this chain of events: Normal boot Emulated BIOS --> bootmgr --> winload.exe Loader boot Emulated BIOS --> grldr -- SEARCH FOR BOOTMGR (hangs on HFS partitions) --> finally finds grldr on the windows partition. THE SOLUTION I THINK: Open grldr in a hex editor. Find this line: find --set -root /bootmgr with rootnoverify (hd0,3) that might do it.
Hazar, Hopefully you're right. We'll anxiously await you next experiment and obviously if you need testers just give us a shout.
I have a simpler solution. Don't buy MACs and use Modded BIOS like us and save some cash in the process . Whoever said BIOS was a bad idea If you want EFI at least try to emulate a BIOS chip. On a serious note I would save the effort of BIOS emulation if I am using a Mac because BIOS emulation activation is designed for system that has a BIOS chip and Mac don't fall into that category. You will meet with a lot of problems I am sure if you could afford a Mac you can afford a Win7 License.
Yeah but if it's a problem with the licensing itself, why would I buy Windows 7? I actually fully intend on buying a Windows 7 upgrade package when it's made commercially available, but I want to make sure that it's going to work on my system. I'm assuming it's the loaders at fault, but all other variables haven't been ruled out thus far, so what if this is just what happens when Windows 7 is activated on my particular Mac?
If you buy a license Win7 it will be activated without using SLIC because it will be validated via Microsoft Activation Server. The retail activation method. I explain how it works. Win7 will take the serial data of certain components:MAC (Media Access Control) address, RAM, Motherboard data to calulate a hash with the CD-Key. When you activate on a server it will return a hash that that decrypts the hash hence validating it. The validation will not be running at boot time like SLICs You won't need to bother about loaders.
Because the problem is at root level. SLIC need some kind of BIOS to at least get the address to throw in the SLIC but Mac don't have BIOS? Looking into other methods of activation is more fruitful.