RyanThaDude29 contact zsmin, send him PM. he is the developer of the loader and he will be able to fix your problem.
Did you try to hold the R (or C) key during startup to display the loader menu? it allows you to try an alternative method, and also to display a debug output (take a picture and post it in the forum to give zsmin the opportunity to fix it!)
Finally figured out how to get to the grub menu. I've attached the picutres of the menu and the log. Basically everything I've tried except "Windows without loader" resulted in the same cursor. by the way, I'm currently using Daz's loader. Thanks
Hi Ryan. That's an unusual place for the loader to stop. There are quite a few things that happen between there and the next debug message so it's not clear exactly what happened. I'll fix what I think is causing it, and add extra debugging information for the next version so it will be easier to identify if something else is the problem. I'll send you a PM later with the new version to try.
2008 Mac Pro I just stumbled across this forum after running into a dead-end in my Win7 activation "holy grail" quest. I have tried the various internet full-packaged Win7+loader combo iso's and then Daz Windows 7 Loader v1.7 on a fresh Win7 unactivated install, all to no avail. I then tried the older Daz 1.5.9 loader after reading this particular threads' success with virplay, but it also did not work (I assumed from the quote above that "1.5.9" was in reference to the older Windows 7 Loader v.1.5.9). In either case, after the blinking cursor in the upper left corner flashes for a few seconds, I get the following error message: <begin quote> find --set-root /bootmgr Error 15: File not found Press any key to continue..._ <end quote> After pressing a key, I get into the SLIC menu, of which no method to boot Windows (even without the loader option) works. I have to enter command line and 'reboot" the computer. If I understood the files that should be at the root level of the Win7 partition, they are indeed there as seen in the attached screen shot. I have not tried Hazor's nor Zsmin's loaders as of yet, nor have I tried Hazor's alternate method utilizing basic cmd lines. I am using Windows x64 Ultimate OEM RTM (unmodified), which works just fine (wiped partition prior to install) before attempting to use a loader. My system is a 2008 (late) Mac Pro 8-core 2.8 Ghz/12 GB RAM. I have a 2TB WD Caviar in Bay 1, partitioned with 1.72TB (SL calc'd) to HFS+ (10.6.1) and 276GB (SL calc'd) to NTFS (Win7) (I actually have 3 2TB drives and 1 1TB drive but I unplugged Bays 2-4 throughout my exercise in futility). I have been able to successfully run Vista w/SP1 (both 32 and 64bit) via Vista Loader 2.1.2 on this same system, both on a partition as well as on a separate, full NTFS 1TB hard drive. I have been able to install the same Win7 DVDs (both 32 and 64bit) via Windows 7 Loader v1.7 successfully on my 2007 MacBook Pro. Thus, it has to be an issue with my Mac Pro and Win7+Loaders. The steps I take are: 1) Boot into Win7 x64 installation DVD (I've tried thru Boot Camp Assistant, through booting directly off the CD via "c" key as well as selecting the DVD via "option" key) 2) Format target partition 3) Install Win7 with no key and don't activate over internet 4) After successful install/working Win7 unactivated, load boot camp 3 drivers & restart (I've also tried NOT installing any BC drivers before installing loader) 5) Run Windows 7 Loader (tried 1.7 then 1.5.9) & restart 6) Dump into error message The only thing I did not try on the Mac Pro was x86 (32bit), but I've reached the conclusion that that would be unsuccessful as well as the same x86 DVD with 7 Loader works on my MacBook Pro. Thus, I turn to this forum in hopes of finding answers from the valued experts... Help?
What is the solution? I've read the thread throughout. There have been only a handful of users out there with Mac Pro's (not to be confused with MacBOOK Pro's, which the majority of here are users of, and which I, too, have, and which all the loaders work fine with). I have determined no obvious change of strategy (loader's versus Hazar's CMD line suppression methodology). If you are being flamingly cryptic with your very simple reply that contains no direction whatsoever, please, I'm no n00b to the online world. I've done my research here in this thread and the solutions used by other Mac Pro users are not working for me.
Loader: Unknown boot device detected! Hey guys I get this error on my MacBook as well as my Dell Vostro 1000, anyone know how I can fix this issue. Cause what happens on both is that it request that I run "Repair Computer or Startup Repair" but it fails to repair. Thanks in advanced for you answers, really appreciate it.
Sorry, didn't realise the modified loader doesn't work for everyone. It works for me though on my Intel iMac, so I automatically assumed that the problem is solved.
For everyone with MAC/DELL/etc. that has boot problems/errors with Zsmin v0.97 loader (by using Daz v1.7.2) PLEASE post your debug output. (boot up your coputer, hold R or ESC key to get into the grldr options, choose the full Debug option, and take a picture of the debug log with your phone/camera and upload it and post the picture here).
Win7 loader Bootcamp & Fusion VM Not sure if this has been mentioned, I have searched and not found a specific reference to the problem I have encountered...go's like this successfully installed and activated win7 x64 on a imac 24 with bootcamp partition using daz'z loader all is sweet and works a charm...The problem arrises when running the bootcamp partition from vmware fusion 3 it seems to bypass the loader and windows complains that it is not genuine. Has any one else a setup similar to mine? or has any one got any idea of a way around this problem. Respect edit on pressing c and viewing debug output the loader is complaining about there being no memory left in the ACPI tables, will try to investigate further.
Have you tried installing Daz'z loader again while running the bootcamp partition from Vmware Fusion 3?
Hi. For anyone having grub errors (file not found or similar), it will be helpful if you could try this: Reinstall Daz's loader (latest version) and reboot. As soon as the screen goes black and the flashing cursor appears in the top right corner, press and hold R or ESC until the red recovery menu appears. It's important to catch the recovery menu BEFORE you see any grub error. If an error flashes up, reboot and try again (try holding R or ESC slightly earlier/later). When you reach the recovery menu without error, select the "without loader" option and let me know what happens. This will tell me if it's a grub problem or a loader problem. If there are no errors without loader, and Windows boots fine, you should post the debug output as tuvi said earlier so I can try and fix the problem. @gazzaleano Pressing C should no longer work for accessing the menu. Can you try a later loader version? I have no problems with Fusion 3 loading my bootcamp partition.
Hi zsmin, I have tried Daz'z loader 1.7.2 on both my Desktop Mac Pro's 2007 and Early 2008 and it works fine. Thanks again for your support, your grub loader is the ONLY reason I am activated.
Why would anyone run Windows 7 on a mac? You buy macs to use Apple's Crappy MAC OS X. If you plan to run Windows then just do not buy a mac..
Me personally the only reason I use Windows 7 is to run games. What else is it good for? I would not trust my important work like web browsing, online banking, passwords or personal correspondence with Windows 7 because it is not secure enough. The number of virus's and spyware that can infect Windows 7 is frightening. Mac Snow Leopard is based on Unix which is a much more secure platform.
To be honest, online banking isn't safe on either windows 7 or mac os even with encryption it can still be broken into, its a matter of time. To put down windows 7 as not secure enough isn't a good enough reason, whos to say snow leopard is as secure as you think it is. If I recall, at a recent hacking conference, mac os applications and mac os was fairly easy to break into. I'm not here to start a flame war, but back up your info with facts, not your opinions.