Search results

You might want to avoid the Sandisk Cruzer Glide 2.0's which are still being sold on Amazon and at one time didn't work with UniBeast due to their "looks like a fixed drive" issue. https://forums.sandisk.com/t/new-sandisk-glide-appears-as-fixed-instead-of-removable-disk-useless/32900

I'd like to add to the chorus of thanks. After many years of thinking I was somehow messing configuration items up when occasionally getting my ASRock H77M to work but more often than not would fail to boot properly. I usually just gave and moved the same disk to my Gigabyte where it worked...

Thanks for the pointer. That will teach me a lesson not to mess around with my lone memory stick location just so it might be a bit cooler.

I am having the same "the recovery server could not be contacted" issue with a 8.3 generated installer. I note that the screen would previously display "Install macOS" instead of "Reinstall macOS" as it does now.

Just trying to let bomboly know they were not alone. I'll just stick with 12.6 and wait for the support of 13 to mature.

I too am trying to use a long time functional i3-3225 iGPU (also tried testing with a GT 610) with the same GA-Z68X-UD3H-B3 and it also hangs at the logo. Disabling Super I/O and -f no cache did not help.

I am also getting stuck at the logo just like with the MultiBeast 9.2.1 attempts. This is getting tiresome. Edit: Installed a GT 610 just to see if that works better than just the integrated but it still hangs at the logo.

I'm thinking it might be time for a front page update regarding the status and various roadblocks you are hitting with MultiBeast 10. Searching for these random hints within various threads is not the best use of everyone's time. Thanks for the work.

I got the error during the initial installation process but downloaded Yosemite again and it worked. I'm thinking I may have used the wrong Unibeast on the first attempt.

'An Update to Kingston SSDNow V300: A Switch to Slower Micron NAND' http://www.anandtech.com/show/7763/an-update-to-kingston-ssdnow-v300-a-switch-to-slower-micron-nand

Thanks for posting this. I was going crazy with formats, diskpart, etc. on a Sandisk 16gb 2.0 Cruzer Glide before reading this. It is indeed a very strange problem.

It is not a "great ssd" and if you Google 'Kingston V300 asynchronous NAND' you will find the numerous discussions regarding the dodgy business practices of Kingston. As an alternative check out the PNY XLR8 Pro which is selling for the same $59.99 after rebate today on Egg. The standard XLR8...

I am and used the same BIOS settings as the original op ecmcube did. It is running very well with no unresolved issues. Here are my installation notes: 1. Run Parted Secure Erase on target SSD 2. Follow these instructions...