Search results

Tried installing Logic today, but a weird thing happened - the actual install went fine, I figured out how to do a custom install and move a lot of the extra content onto my HDD so it wasn't taking up unnecessary space on the SSD and all was good... until I tried to run it. After restarting...

I haven't actually tried it out but from what I've read, the Wifi definitely won't work, but the bluetooth will, but it might not have great performance - a few people have reported jumpy mouse movement and occasional full dropouts and things like that so I would suggest getting a separate...

Forgot to mention: I'll be installing Logic Pro 9 and Reason 5 very soon too. Does anyone know of a way to install Logic so that the key program files are on the SSD but all the Apple Loops and other 40ish GB of data is on the HDD? And is there a way to do a similar thing with Reason - have the...

Here's the latest update: I sent the faulty Motherboard back and my replacement arrived 2 days ago. I connected everything back up, including the GTX670 in the PCIe x16 slot, made sure Windows was running properly (it actually seems slightly faster and more stable before, there was probably...

Good news and bad news: Good news is that my GTX670 is actually functioning normally and that means that it's not through fault of my own that things haven't been working. Bad news is that the Motherboard appears to have a dead PCIe slot, and that's why I couldn't get the graphics card working...

That's normal - you're meant to boot back from the Unibeast USB drive and then select your hard drive at the boot screen. I think this is because there's no bootloader on the hard drive install yet. Multibeast will add one (Chimera) when you run it. The Unibeast drive also runs chimera I think...

So does anyone see any issues I might come up against with my currently selected Multibeast settings from my previous post? Is there anything missing? Is there anything there that I wont need? And my other question from before that hasn't been answered: If I want to change just one thing in...

Yeah the GTX670 will go in later, but for now I'm not including it. Thanks, I had forgotten about PCIRootUID=0 - it worked and I am able to boot into normal mode (not safe mode) using PCIRootUID=0. Do my selections within Multibeast from my previous post look OK?

dart=0 makes no difference. VT-d option not available

Not initially, but trying it just then gave me exactly the same result as the previous -v photo stuck on [IOBluetoothController] My understanding is that you only need GraphicsEnabler=No when using a discrete graphics card

So I'm now booted into safe mode and have run the remainder of the Mac installation and setup. I need to run Multibeast, but before I do I want to check that I've got all the options correct. Using Multibeast 5.3, for the record. Here's what I've selected: A quick rundown of choices...

Nope, DVI

I've been trying to get this thing to work properly for over 3 weeks now to no avail. I've followed countless guide and hundreds of tonymacx86 forum pages trying to get answers, but the solutions rarely work, and when they do, another problem pops up again straight away. More than just solutions...

I'm actually starting to think its a faulty graphics card again because my Windows stopped recognising it overnight and now I can't even see the BIOS page anymore on it. I'm going to remove it and get everything working properly, then try and install it and see what happens.

Just a quick question for Dawsman: When you first ran Unibeast to install ML and then booted into ML to run Multibeast, were you running from your HD4000 graphics or your GTX670? I get a black screen when I try to boot into ML or Unibeast going out of my 670 although I can view the BIOS and...

I have almost the same build: Gigabyte Z77X-UP5-TH Core i7 3770K Gigabyte Geforce 670 4GB 4x8GB Corsair Vengeance DDR3 1600 RAM 2x Samsung 840 Series 120GB SSDs Seagate Barracuda 3TB Seagate Barracuda 1TB Samsung CD/DVD Optical Drive TP Link TL-WDN4800 Wifi Adapter Corsair HX750 80Plus Gold...

Switched my display to a TV with HDMI which seems to have solved the problem of the BIOS reverting the Init Display First setting to Auto, but with all of PCIRootUID=0 GraphicsEnabler=No -v ; PCIRootUID=1 GraphicsEnabler=No -v ; and PCIRootUID=1 GraphicsEnabler=Yes -v it finishes loading in...

I switched Init Display First to PEG, left Internal Graphics on Auto, Save and Exit. Shut down, move DVI cable from HD4000 to 670, power on, boot ML from Chimera with pcirootuid=0 and graphicsenabler=No hangs at grey spinning wheel screen. pcirootuid=1 graphicsenabler=no hangs as well...

This is probably a dumb question with an obvious answer, but do I have to change my Init Display in the BIOS from IGFX to either PEG or PCI when I do boot with pcirootuid=0, and at what point should I move the DVI cable from the motherboard out to the 670 out?

Ok so clearing the CMOS worked, restored BIOS setting to defaults, restart, restore settings I had before. Init Display set to Auto. ML boot hangs on grey spinning wheel screen. Restart, try again in ML, works. Try to boot to Windows 8, tells me the drive is corrupted and I can attempt a repair...