Jump to content


  • Content count

  • Joined

  • Last visited

About duey101

  • Rank
    InsanelyMac Protégé
  1. Hmm... almost solved. Although I have an error free working DSDT, whenever I restart and then open up the default DSDT in MaciASL (which has already been patched/error free) I get the same error in the patched DSDT that has been loaded and then opened as default in MaciAsl. { If (IGDS) { Store (^^^PEG0.PEGP.LCD._BQC (Local0, ^^^PEG0.PEGP.LCD._BCM (Local0))) } Else { I thought I already fixed that before, well... I know I did, how did it come back again? "When editing DSDT and trying to understand compiler warnings, basic computer programming skills is a prerequisite." Or just plain old stubborn determination and knowledge that anything can be done if the desire to do it is strong enough.
  2. I have a working JMicron SD Card Reader (J38X) in Mavericks 10.9. I used these three kexts (attached here). HSSDBlockStorage.kext sourcxe VoodooSDHC.kext JMB38X.kext I had to use all three, the card reader works perfectly. My specs are in my signature, but this is for a Toshiba Satellite P755. It was a pretty straight forward process, used Kext Wizard, repaired permissions/cache/reboot. Card reader works and doesn't have to be plugged in on boot, works/ejects/ properly. Hope this helps others. JMicron.zip
  3. Nvidia GT 540M not recognized as GPU accelerator

    Nope, not a lot of options in my BIOS (AMI v, 2.10 / 07/13/2011). I have never updated the BIOS because I don't like fixing things that aren't broken, but there is an upgrade history 2.10 - 2.80. After reading some forums it seems people are having problems after updating to the latest 2.80. I don't want to break all the work I've done up to this point. Even the Toshiba tech support Moderators say right in the forum... "That BIOS (V 2.60) is available for download HERE. The prevailing wisdom on this Forum is do not update BIOS unless you are having a problem that it is supposed to cure. Don't fix what ain't broke!!! You will see the BIOS change history at the link I gave you. C.B." But now after checking the BIOS update history I see in 2.50 there was this... Updated: NVIDIA N12P-GS VBIOS to V70.08.4A.00.22. And in 2.60 there is this... Updated: ME Firmware to V7.1.52.1176. As of now there is no disable feature so it looks like I can't use the GT 540M for GPU acceleration on this mac partition unless those BIOS upgrades will make some new functions available in my BIOS options. The rest works fine.
  4. Nvidia GT 540M not recognized as GPU accelerator

    Thanks. Isn't it always this way? The ONE THING that I really only cared about won't work. Fortunately everything else does.
  5. New/Virgin DSDT causes system halt (KP) and can't boot.

    Thanks RHM, I figured it out for myself... Method (COKE, 0, NotSerialized) { Name (T_0, Zero) Store (ToInteger (PJID), T_0) If (LEqual (T_0, 0xBE)) { If (LEqual (^GFX0.DVID, 0x0126)) { Return (BE01) } If (LEqual (^GFX0.DVID, 0x0116)) { Return (BE00) } } Else { If (LEqual (T_0, 0xC2)) { If (LEqual (^GFX0.DVID, 0x0126)) {} If (LEqual (^GFX0.DVID, 0x0116)) {} } Else { If (LEqual (T_0, 0xC4)) { If (LEqual (^GFX0.DVID, 0x0126)) {} If (LEqual (^GFX0.DVID, 0x0116)) {} } Else { If (LEqual (T_0, 0xC5)) { If (LEqual (^GFX0.DVID, 0x0126)) {} If (LEqual (^GFX0.DVID, 0x0116)) {} } Else { If (LEqual (T_0, 0xC6)) { If (LEqual (^GFX0.DVID, 0x0126)) {} If (LEqual (^GFX0.DVID, 0x0116)) {} } Else { If (LEqual (T_0, 0xC8)) { If (LEqual (^GFX0.DVID, 0x0126)) {} If (LEqual (^GFX0.DVID, 0x0116)) {} } Else { If (LEqual (T_0, 0xC9)) { If (LEqual (^GFX0.DVID, 0x0126)) {} If (LEqual (^GFX0.DVID, 0x0116)) {} } Else { } } } } } } } Return (Zero) <--- Needed to add this } } } Everything is going well so far. Just have my one real problem the rest is minor. But I guess the Optimus won't work in OS X. So that shoots that down. I'll have to do without it.
  6. I have my successful Hackintosh install dual boot Win7/Mavericks 10.9 up and running with a patched custom DSDT (I just figured out how to implement). It is working well except for one issue that I really need a solution for. There is one very important missing function I need from my Hackintosh, the ability to use the integrated nVidia GeForce GT 540M as the GPU accelerator in Adobe Premiere Pro CC to take advantage of the Mercury Playback Engine Technology. My Hackintosh recognizes both the HD3000 and GT 540 M in System Information, but Adobe Premiere Pro CC doesn't find the GT 540M. In Windows 7, I can manually add the name "GeForce GT 540M" into the cuda_supported_cards.txt file and that tricks PPro CC into thinking I have a CUDA card (which it actually is) and then it uses my GT 540M for the Mercury playback Engine rendering which is a massive speed improvement! However, on my Hackintosh it does not work although I have added the GT 540M in the same way to the cuda_supported_cards.txt file in the package contents folder for PPro CC, where that file resides. This is the output of the Mac version of PPro CC GPUSniffer app that detects CUDA cards in PPro CC/CS5/CS6... <<<GPUSnffer Application>>> Last login: Sat Mar 8 09:32:46 on ttys000 UserName-Mac-Pro:~ username$ /Applications/Adobe\ Premiere\ Pro\ CC/Adobe\ Premiere\ Pro\ CC.app/Contents/GPUSniffer.app/Contents/MacOS/GPUSniffer ; exit; --- OpenGL Info --- Vendor: Intel Inc. Renderer: Intel HD Graphics 3000 OpenGL Engine OpenGL Version: 2.1 INTEL-8.18.27 GLSL Version: 1.20 Monitors: 1 Monitor 0 properties - Size: (0, 0, 1366, 768) Max texture size: 8192 Supports non-power of two: 1 Shaders 444: 1 Shaders 422: 1 Shaders 420: 1 --- GPU Computation Info --- Did not find any devices that support GPU computation. This is the problem! logout [Process completed] GPUSniffer didn't find the GT 540M, but it is there. This is the modified contents of the cuda_supported_cards.txt file... GeForce GT 540M <--- added my card here GeForce GTX 285 GeForce GTX 675MX GeForce GTX 680 GeForce GTX 680MX GeForce GT 650M GeForce GT 750M Quadro CX Quadro FX 4800 Quadro 4000 Quadro K5000 Quadro 540M In Windows 7 I only need to add the name of my nVidia card as above into the cuda_supported_cards.txt file and it works and the Mercury Playback Engine option can be selected when starting a new project and it works perfectly for rendering. In PPro CC on my Hackintosh, this option is greyed out as shown here... I need to find a way to get PPro CC on my Mavericks Hackintosh to recognize my GT 540M as it does in Windows 7. It finds the HD3000 for Open GL but not the GPU for the GeFore GT 540M, which is what I need. Does anyone have any idea what is missing?
  7. New/Virgin DSDT causes system halt (KP) and can't boot.

    Okay I am happy to report success, thank you. I think it was the DSDT Editor as in MaciASL there were several errors that were not detected in DSDT. I patched the DSDT with all the things you suggested iFire, looks like it works! I gained... Working WiFi Atheros 9285 (with no kext) Realtek Lan (with no kext) Character viewer in the taskbar Other things I probably have no idea of as yet. However when I booted I got to that common system halt IOBluetooth error and black screen... **** [iOBluetoothHCIController][searchForTransportEventTimeOutHandler] -- Missing Bluetooth Controller Transport! rebooted, then got another system halt at stoppage NTFS volume name Drive D, version 3.1.... Mar 8 17:47:07 Dueys-Mac-Pro kernel[0]: NTFS driver 3.11 [Flags: R/W]. Mar 8 17:47:08 Dueys-Mac-Pro kernel[0]: NTFS volume name Drive C, version 3.1. Mar 8 17:47:08 Dueys-Mac-Pro.local ReportCrash[119]: Metadata.framework [Error]: couldn't get the client port Had to reboot a couple of times but it works. If it hangs up I just have to reboot a couple of times, no other errors halt the system. From reading threads I think this has to do with graphics. One thing I noticed on boot is that in the boot log (reported in DPCIManager) it says... ERROR: dcbtable_version is 0x10 ERROR: nVidia ROM Patching Failed! Toshiba GeForce GT 540M 1024MB NVc1 [10de:0df4]-[1179:fc31] :: PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0) device number: 1 and in the system -v boot log I see GeForce Sensors waiting to start... a couple of different times during the boot up process. In the system report from my Win7 and AIDA 64 EE reports my nVidia GT 540M as a 2 GB card... NVIDIA GeForce GT 540M (2 GB) Graphics Processor Properties: Video Adapter nVIDIA GeForce GT 540M (Toshiba) GPU Code Name GF108M (PCI Express 2.0 x16 10DE / 0DF4, Rev A1) GPU Clock (Geometric Domain) 50 MHz GPU Clock (Shader Domain) 101 MHz Memory Clock 135 MHz But... System report in Mavericks reports it as a 1 GB card... Toshiba GeForce GT 540M: Chipset Model: Toshiba GeForce GT 540M Type: GPU Bus: PCIe Slot: Slot-1 PCIe Lane Width: x16 VRAM (Total): 1024 MB Vendor: NVIDIA (0x10de) Device ID: 0x0df4 Revision ID: 0x00a1 ROM Revision: 0x00 This is causing me a problem I think, just to let you know the whole reason I tried this Hackintosh thing was so I could dual boot and use Adobe Premiere Pro CC and the Mercury Playback Engine technology for video editing in Mac. I started another thread about this because I really need some advice on this as I have tried to figure this one out for a while now. Again, thank you for your help and suggestions. Overall I noticed a perfomance improvement from before the DSDT was loaded Now that I have a working DSDT I have more things to study/try/fail/adjust/try/fail/adjust/try/succeed. WindowServerError.txt DPCIManager_boot.txt system_boot.txt
  8. New/Virgin DSDT causes system halt (KP) and can't boot.

    Well iFire, remember way, way, way, back... how many years? When you knew nothing about DSDT's KP's, Binaries, and XCode? Well... that is where I am right now, but I'm reading, learning, trying, succeeding. I am grateful someone like you and RHM took the time to look and help, thanks. I only discovered Hackintosh a month ago. I just DL'd RehabMan's DSDT patches (he suggested) and MaciASL and I am patching my DSDT now. Found a bunch of errors DSDT Editor missed... thanks for your post and advice RHM, helped with this error, had many. # rehabman: # _PLD is supposed to return a variable length Package of Buffers into_all all code_regex (Name\s*\(_PLD,\s*)Buffer(\s\(0x10\)[^\)]*) replaceall_matched begin %1Package() { Buffer%2} end; RIght now I'm patching and will try again and report back. Thank you iFire and RHM for your help and suggestions. I'll get this all figured out, I enjoy learning, and having a dual boot Mac/PC is something I am really enjoying, just need to learn more. I spent weeks just getting it to install correctly but now it works, except for a few little things. My goal is to learn as much as I can so when I get new machines I know what to do. All patched, no errors, just this warning. I have been trying to figure it out since yesterday... 10266, 1088, Not all control paths return a value (COKE) }) Method (COKE, 0, NotSerialized) { I'll try the newly compiled DSDT tomorrow and report back.
  9. Thanks rals2007. But now I'm stuck on this warning... 9451 Warning Not all control paths return a value (COKE) }) Method (COKE, 0, NotSerialized) { Which is in the tag... } Scope (\_SB.PCI0) { 3.5 hours and still can't figure it out, there are no other references to COKE anywhere else in the DSDT. But I'll keep trying. It's always fun to try things you don't know. The DSDT is error free though. But now I have this problem. LOL!!!
  10. I prefer to try and figure things out for myself but this has me totally stumped. If I try to use a DSDT file in Chameleon I get a KP/system halt and can't boot up my otherwise working Mav's install (except SD Card reader/WiFI - Ordered supported WiFi card). But a few things need tweaking so I wanted to use a DSDT option and besides that I just want to learn how to use it for future reference and my own education. I already spent a week learning what/how to use DSDT but now when I try, no go. This is what I did... Open DSDT Editor Extract DSDT Clicked complie Installed DGTP patch Fixed errors (DGTP/Expecting "("/_REG/_T_0) Compiled again (without any errors) one warning)---> 9451 Warning - Not all control paths return a value (COKE) Method (COKE, 0, NotSerialized) (After 3.5 hours I gave up on trying to figure this warning out) Saved as DSDT.aml (no errors) Copied DSDT.aml to Extra folder In Chameleon Wizard checked box dsdt.aml and set path /Extra/DSDT.aml Clicked save Used DPCIManager to repair permissions, rebuld kernel cache Reboot... Crash/Kernel Panic/System halt... I searched the forums for this issue (First use of DSDT causes crash/kernel panic) but didn't find an answer. I followed instructions exactly and tried over and over again but the same thing happens. If I go to my Win7 boot (dual boot setup) and delete DSDT.aml from the Extra folder (MacDrive) and restore the backup org.chameleon.Boot.plist to it's pre-DSDT form and reboot all is fine. What am I missing? The DSDT is error free and the only patch I used was for DGTP (to fix some errors). After 15 or so attempts I haven't figured it out yet. Any ideas?
  11. 9904 Error syntax error, unexpected ')', expecting ',' <---(you get this somewhere in your DSDT) If anyone experiences this error when compiling your DSDT for the first time here is the fix. I know nothing about code but just figured it out with common sense and trial and error. I searched and searched all over Google and couldn't find a fix so I just kept working on it until I got it right. Here is how it got fixed... Looks like this... { If (IGDS) { Store (^^^GFX0.DD02._BQC (), Local0) ^^^GFX0.DD02._BCM (Local0) } Else { Store (^^^PEG0.PEGP.LCD._BQC (Local0, ^^^PEG0.PEGP.LCD._BCM (Local0))) } } Should be like this... { If (IGDS) { Store (^^^GFX0.DD02._BQC (), Local0) ^^^GFX0.DD02._BCM (Local0) } Else { Store (^^^PEG0.PEGP.LCD._BQC (), Local0) ^^^PEG0.PEGP.LCD._BCM (Local0) } } I hope this helps anyone else who may run across this error as it will save you many hours of searching if you are not proficient at code like me (but I'm learning ) Of course programmers would have fixed this in less than 30 seconds, took me an hour and a half! LOL!!!
  12. Hi Everyone, this is my 1st post! First off, thanks to Niresh and the crew for making awesome installs that work! I tried all the other install options available in the scene but this is the only one that worked for me and nearly everything worked out of the box except, WiFi (fixed with these) and SD card reader (fixed with this), so they do now. I AM NOT A TECHNICAL EXPERT - If you ask me how to fix this or that, I don't know. I read every forum, and researched all the Hackintosh info I could and spent countless hours learning. I just now what I did works and wanted to share it here. You can do things in another way (format/make bootable USB) but I put in this article up documenting what I did and how I did it, and it works. My specs are... Toshiba Satellite P755 1004XT (Model - PSAY3L-0PX055) Purchased in Thailand. Mobile QuadCore Intel Core i7-2670QM, 2200 MHz HM65, Intel Sandy Bridge 8 Gigs (DDR3-1333 DDR3 SDRAM) NVIDIA GeForce GT 540M (2 GB) Intel HD Graphics 3000 LG Philips LP156WH4-TLA1 (Monitor)[15.6" LCD] Intel Cougar Point HDMI @ Intel Cougar Point PCH - High Definition Audio Controller [b-2] Realtek ALC269 High Definition Audio Controller Standard AHCI 1.0 Serial ATA Controller TOSHIBA MK7575GSX ATA Device (750 GB, 5400 RPM, SATA-II) HL-DT-ST BDDVDRW CT31F ATA Device (DVD) HID Keyboard Device Standard PS/2 Keyboard HID-compliant mouse Synaptics PS/2 Port TouchPad Atheros AR9002WB-1NG Wireless Network (WiFi) Adapter Realtek PCIe GBE Family Controller (Ethernet) Your system may vary but if you have the same system I have or a Toshiba with specs close to these ou may be in luck. My laptop worked nearly out of the box with the Niresh installer, except for a few adjustments, but right now it works flawlessly with all components, sound, both graphics (Intel/nVidia) WiFi, Ethernet, all of it works, with no issues. Here is what I did to get it up and running. I'm using one 750 GB hard disk with two partitions, one for Win 7 x64 and one for MacOSX (this Hackintosh) for dual boot. I will assume you already know how to create partitions. If not you need to learn how. You need two partitions, one for Win 7 x64 and one for Mac. I named mine WIN7X64(C:/) and MacOSX(D:/). The WIN7X64 (C:/) partition already had an existing installation of Windows 7 x64 on it and the other partition (D:/) I used for file storage. I just moved all the files from the storage drive (D:/) to a Passport drive and made that partition (D:/) my MacOSX drive for this Hackintosh install. Pre Install: a. Download Niresh for Mavericks here... http://kickass.to/niresh-mac-os-x-mavericks-10-9-0-for-amd-and-intel-for-apple-and-non-apple-computers-t8406620.html b. Download RehabMan's FakeSMC kext here... http://bitbucket.org/RehabMan/os-x-fakesmc-kozlek/downloads c. Download NullCPUPowerManagement kext here... http://olarila.com/files/10.6/PM/NullCPUPowerManagement.kext.zip d. Download the Atheros WiFi kext here... http://www.osx86.net/files/file/372-atheroswifiinjector-kext/ (See below) e. Download WinDiskImager here... http://sourceforge.net/projects/win32diskimager/ f. Download BootIce here... http://www.softpedia.com/get/System/Boot-Manager-Disk/Bootice.shtml g. Download TransMac here... http://www.acutesystems.com/tmac/tmsetup.zip (15 day Trial/Used for viewing Mac volumes in Win 7 x64) Edit: Added VoodooTSCSync.kext > Resolved the cpus=1 issue. Now HWMonitor reads all 4 Cores boot flag no longer needed. Be sure to read the directions and change the file to fit your CPU i3, i5, i7 etc. I removed the AtherosWifiInjector and usedthe above WiFi solution while I wait for my new fully supported WiFi card to arrive. Edit: Added RehabMan's DSDT patch bundle (most of them) and created a custom DSDT, this made a lot of things work and improved stability. I'd like to thank RehabMan for all the great work he has done and has been very helpful to me. The DSDT part can be done later after your initial install. h. Use BootIce to format your USB stick. Open the program, Select your USB stick, Click on Parts Manage, then click Repartition. It will format the drive, done. Ignore any Windows popup that asks you to format it again, just close that window. Continue... i. Use WinDiskImager to create your boot disk with Niresh (OSX-Mavericks.dmg) you downloaded. Open WinDiskImager, select your USB drive you just formatted with BootIce, and then click on the little blue folder icon to navigate to where where the Niresh OSX-Mavericks.dmg is. Click/Open that and then click "write" and WinDiskImager will start writing the Niresh DMG file to the USB. If you get an error while writing to the USB drive just repeat the process and write again. Done. Here we go! 1. Installing: MAKE SURE NO OTHER DRIVES OR DEVICES ARE PLUGGED INTO USB PORTS (mouse okay). Put the Niresh USB stick you made into your computer, power on, and then hit f12 (or whatever key it is that allows you to select the boot device in your BIOS and select boot from the USB drive. 2. The Niresh menu will pop up. IMPORTANT: Select the USB drive OSX and then hit the space bar and use these boot flags... cpus=1 -f -v (<<<--- If you don't use those flags the installer will hang up and not work correctly) 3. Hit the <Enter> key. You will see the program loading in verbose mode going through all the stuff and then it will get to [AGPM] something... and appear to halt, it doesn't. It just takes a couple of minutes to get past this part (3-5 minutes in my case). You will now get to the installer screen. Select your language and click the arrow and wait until you see the menu bar on top (or it may appear before that) but don't continue through the install just yet. For me, I had to select my language first before the menu bar appeared at the top of the screen. 4. You will see the menu bar at the top of the screen. Go to Utilities/Disk Manager and use the Disk Manager to format (erase) your already created MacOSX partition (Mine is named MacOSX). Select your Mac partition and format it (erase) it as Journaled mode. When it has finished formatting, close Disk Manager and continue on with the setup install package. It takes about 30 minutes. When it is done, it may try to automatically reboot, don't reboot into the new Hackintosh install yet. Shut down. 5. Boot into Windows and open Windows Explorer. You will see the Mac drive there (mine is called MacOSX)... Note: If you don't see the MacOSX drive in Explorer, open Administrative Tools/Computer Management/Disk Management and select your MacOSX partition by right clicking on it and then choose Change/Assign a drive letter. It will then appear in Explorer. Working in Exporer now, go to your MacOSX drive and navigate to System/Library/Extensions... and copy (replace) the three two following kexts... NullCPUPowerManagement.kext and FakeSMC.kext AtherosWiFiInjector.kext now (that you downloaded before). Shut down and reboot. 6. Upon reboot you will need to hit a key to stop the automatic Niresh boot-loader. Now you will have some boot options in the Niresh bootloader of what you can load. Select the MacOSX HD (or whatever you named your Mac partition) and then press the space bar. At the bottom of the screen you'll see a small window to type in bootflags. Type in these boot flags... cpus=1 -f -v Then hit <Enter> The verbose boot process will go again and then you'll get to the Mavericks account setup screen, so go through all that. In my case the screen was all chopped up and full of artifacts but I just clicked around and got through and got my account setup. NOTE: This is due to the fact the new install hasn't been completed and the kext files and all the permissions will need to be updated before it works right. Go ahead and finish the account creation process. 7. Mavericks starts loading... Screen may still look wrong but just go on letting Mavericks load. DON'T CLICK OR TOUCH ANYTHING!!! The Niresh install program starts running (with Indian music playing) and repairs all the permissions and cache. At this point I had a funky looking screen but it still worked and the Niresh updater finished. Remember, don't click or touch anything until it is fully completed and your hard disk light shows no activity. Takes 10 minutes or so. When it is all done, shut down. STOP!!! Now boot back into Windows 7. Go to the MacOSX volume again in Windows Explorer and open the Extra folder (in the root of the drive). Then open up the file called smbios.plist to edit its contents. I use Edit Pad Pro (right click/send to/Edit Pad Pro). Replace the contents with this... <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com...yList-1.0.dtd"> <plist version="1.0"> <dict> <key>SMbiosvendor</key> <string>AppleInc.</string> <key>SMbiosversion</key> <string>MBP81.88Z.0047.B1E.1109091244</string> <key>SMboardproduct</key> <string>Mac-94245A3940C91C80</string> <key>SMfamily</key> <string>MacBookPro</string> <key>SMmanufacturer</key> <string>AppleInc.</string> <key>SMproductname</key> <string>MacBookPro8,2</string> <key>SMserial</key> <string>C02GM530DF8X</string> </dict> </plist> and then save the file. Be sure to make a copy of the original first! Note: You need an smbios.plist that matches as closely to the computer you have in order for it to work properly. I tried several, this one worked. You may have to experiment with different ones. Where to get them? Google it! Or try here... Every Mac 8. After you alter the smbios.plist file, shut down, power up, and then reboot the MacOSX partition again from the Niresh boot-loader, remembering to use the flags... (cpus=1 -f -v ) 9. Upon reboot my system was working perfectly! (I thought). It all works, Sound, Screen Saver, Sleep, HW Monitor, all of it. Wait... except the WiFi. Why? We already installed that kext through Windows Explorer. If the same thing happened to you and you got no WiFi after installing initially, no problem... 10. Open up Kext Wizard and navigate to your Windows 7 drive (I can see my drive C:/ in my Mac install in the Computer tab) and locate the AtherosWiFiInjector.kext on your Windows 7 drive and install it with the Kext Wizard. If you can't open your Windows drive from within your Mac install, then quit, go back into Windows, copy the AtherosWiFiInjector.kext file to a USB drive, boot back into MacOSX (with flags) and then use the Kext Wizard to install the file from the USB stick. After it finishes installing click on maintenance and repair tab in the Kext Wizard and choose the repair all permissions in System and Cache folders option. When that process is complete, shut down, reboot as before, and don't forget the FLAGS! This has since been fixed using a custom DSDT for my laptop. You can learn how to do that by reading other posts of mine and search the forum for how to create your own custom DSDT. Note: I use Windows Explorer to copy all the kext files I need to the Desktop on my Mavericks drive (D:/MacOSX). I created a folder on the Mac Desktop (In Explorer it is found under Users/My user name/Desktop/ and I use that folder to copy things from my PC to the Mac. This is very useful and it works both ways because I can access my Windows partitions from Mavericks and copy/paste/transfer files Win-Mac or Mac-Win. 11. SUCCESS!!! If you are like me, you have a fully functional Toshiba P755 running MacOSX Mavericks! My laptop works flawlessly, it all works, Movies, screen saver, You Tube, Skype, WiFi, iTunes, App store, sound, ethernet, everything. I didn't try the HDMI but I never use it so I am not worried about that. In the System Info app all is present and accounted for including both the Intel and nVidia graphics. I also have a USB WiFi stick and that works perfectly also. Final thoughts: The only thing I haven't figured out is how to boot without having to use the flags (Solved with DSDT) but the way it is is fine with me. I am sure there is a way to boot without them, but right now I have a perfectly dual booting Win/Mac and everything works so I'll leave it at that until I read enough on how to get it to boot right without having to use the flags (fixed). After endless hours of trial and error I found what works. For me that was the Niresh option, I tried all the others without success, but don't let that stop you from trying other methods, use what works for you and your system. Edit: Your next mission is to learn how to create and apply a custom DSDT after you get your initial install working. Fortunately, this laptop is fairly compatible as it is, almost everything worked for me after the initial install, except battery, WiFi, SD Card Reader, but now everything works and I have only minor issues to work on. Your custom DSDT will allow a lot of options and there are a lot of fixes already available as mention above (RehabMan's resources). It really isn't that hard to do if you take the time to study and learn. Once you get the basic understanding of it the process gets easier. I hope this guide was useful and you have the same success I did!