Well, I just tried the Toast 10 Titanium method, and the same thing happened. I was met with the dreaded 1. 2. Select CD-ROM Boot Type:_ error. I guess I'll install the 32-bit edition if no one has a way to fix this. It seems to be particular to non-aluminum macbooks. I wish that I could get it to recognize all of my RAM...
It happened to me once with a copy of Windows. It has to do with the way the ISO was saved. Find another copy of Windows 7 or I was able to fix this by extracting the boot sector information from a Windows disc that boots ok and re burning the contents of the problem disk on to a new disk with the new boot sector info. I aslo found this quote: "Actually, this is a problem brought on by Microsoft using a slightly modified boot record on the SP1 (and apparently W7) CD. It has two boot sectors where most would just have one. The disc image itself is burned (or pressed in the case of a genuine disc) in a way that isn't exactly compliant with standard El Torito boot protocol. I can only surmise that this was done so that EFI-based PCs would not require a "GPT utility disk" as they did in the past. It's rather unfortunate that Apple seems to have only put a workaround in the 2008 Mac lines. Whatever the cause, it's treatable by extracting the "standard" boot sector onto a Windows machine (which can be a Mac with Windows on it somehow), copying the new Windows sources into a work folder, and finally re-burning your Windows disc using the boot image plus your sources. An unnecessarily complicated task, to be sure, but there are many walkthroughs on the Net for it ."
Thank you both very much, for sending me in the right direction! I think I have a grasp on the situation now. About those tutorials, though... It seems Microsoft has changed the location of the ETFSBOOT.COM program on the RTM version of W7 from its location on the disc during Beta status. Could anyone please tell me how to apply the same MS-DOS command-prompt logic on the current RTM version of W7, as is circulating in the Repository thread?
Thank you very much for this walkthrough. The DOS command worked, and I'm trying it now! (I guess I'll reformat my Boot Camp partition and start over again )
oscdimg created an windows7dvd.iso (3GB i think) in c:\efi-iso\ and it's impossible that it's 6 GB in size, so i quess you did something wrong.
As it turns out, the c:\efi-dvd\ directory not only included all of the files on the W7 ISO, but also a copy of the ISO itself I'm attempting the process again as we speak. I'm even more anxious to get this to work as I have installed 4GB of RAM in my computer today. Seeing that "(2.98 Usable)" message just kills me!
can someone reup grldr from zsmin b8...the previous link does not valid anymore...whats the different from b6 anyway?? if i use daz loader than it will overwrite my hazard loader...i prefer just overwriting the grldr only...please re up thx
And, it works! My question now, is... How do I get drivers working? W7 Update seemed to do a lot of the trouble for me, but I'm still having sound issues [no sound whatsoever] and Device Manager says my iSight isn't working yet. My keyboard shortcuts also don't work. I inserting my 10.6 CD, but I keep getting the message that "Boot Camp x64 is unsupported for this computer model", when clearly it isn't! Please advise!
No I meant any non-pro line model, meaning all MacBooks, iMacs and the MacBook Air are officially not supported, yet all MacBook Pros and Mac Pros are supported. I myself own a MacBookPro and the installation of the BC drivers worked even without applying the method I described above. Though on my iMac I had to use the method described to get the drivers installed.
I just recently received a brand new Mac Mini with Snow Leopard for use at my office. My previous machine died and had boot camp with Windows XP. Worked great. Now this machine I decided to boot camp with Windows 7 Ultimate 32. The install including the boot camp drivers went without a hitch. Working, IMHO, better than XP. Long story short, I tried using the most recent loaders from Hazar and Daz. Both ended up at the exact result.. the blinking cursor. I removed the loader and 7 worked fine again, of course, not activated/genuine. Is anyone else having this issue and have a resolution? Thanks!
After receiving the "Windows not genuine" error I decided to wipe the boot camp partition clean and start over. Unfortunately it was the same result of the dreaded cursor. Guess for now until someone knows how to fix is to sick with rearming