Hi @dosdude1You can get one from a Late-2009 MacBook model A1342, take the casing off, and it'll fit in just fine.
@foxlet, if you haven't already done so, you can use Cloudflare to cache the URLs to further offload traffic.Thanks for the amazing work!
Any chance you can release the source of your tool, so we can self-host the feed?
Can you make this avail over HTTPS? Let's Encrypt offers free certs...
Uhh, both load balancing and HTTPS is already available, and has always been active since the inception of the project. Just add an S if you want that; https://swdist.furcode.co/ (I don't support the Let's Encrypt project so you won't see those certs there).
Glad to hear it @dosdude1 i will try replacing the card, but in mean time i still have problems withNope, should work after replacement.
are you sure?You can get one from a Late-2009 MacBook model A1342, take the casing off, and it'll fit in just fine.
The cards look different, but the actual connector is the same and in the same place.are you sure?
comparing the A1342 and the A1283 airport cards, the board layouts look different to me (screw hole placement ecc)
I have been trying to upgrade the airport card on my late 2009 mini for a while now and have not been able to find a more recent and compatible version of that card (except for external solutions such as wifi / bluetooth usb dongles ...)
Did you patch the recovery partition? (that's an option on the post-install tool) - it also has to be patched to allow our non-supported systems to work.In the meantime I was able to install Sierra with the patch tool (version 4.1.2) on a 13" MacBookPro5,5 (Mid 2009) and everything works as expected – just the recovery partition, although it's there (checked this in Terminal), isn't shown on the boot screen or in System Preferences. CMD-R at startup results in a prohibitory symbol. The post install patch doesn't help either. I erased the recovery partition completely and installed Sierra again. But booting from it simply doesn't work. Any suggestions? Thanks in advance.
Try with another USB key. Your problem looks like a damaged key. Follow the instruction of Dosdude1I tried a clean instal.. So I remover el captain etc. And now it stil instelling wont work..
"THE operation couldn't be compleated. Undentificated error: 0
Quiz the installeren to restart your computer and try again.
USB key -> USB port?Try with another USB key. Your problem looks like a damaged key. Follow the instruction of Dosdude1
you need a different disk usb, your problem looks like a corrupted file (did a search on youtube with your error code). However, you need a different layout macUSB key -> USB port?
I have a MacBook Pro 2009 and I tried on both.
I already tried a USB (the prevuses didn't boot)
Is there a way to fast reinstall el captain so I can do things on my MacBook again?
(I don't have a other mac at home, so I can't get software from there... only PC/laptops)
sorry I'm french, my english is not very good. you need a Mac to make a second installation usb disk (with another USB drive)Uhh? From most sites I see a MacBook Pro is good at specs to run it...
So could you be more specific than just different layout mac.
MY iSIGHT CAMERA IS WORKING AGAIN! SEE POINT #11 BELOW FOR DETAILS
11. In a last-minute post, only minutes before I was going to perform a clean install of 16A323 Final on my early 2009 iMac's internal hard drive, using my USB external hard drive where I had installed Sierra Final using dosdude1's macOS Sierra Patch Tool, a MacRumors newbie named "brunsik" mentioned that he had VirtualBox installed, and that from reading an article on another website, he resolved his iSight camera issue by detaching his iSight camera from VirtualBox.
As it turns out, I also have VirtualBox installed.
While brunsik offered some instructions regarding how to do this, I couldn't quite make sense of them. I had already been contemplating uninstalling VirtualBox for some time, being as I no longer run SheepShaver in it anyway. So I ran the VirtualBox uninstaller script that is included in the VirtualBox DMG file.
While I was hopeful, given everything that I have tried thus far -- which has all failed -- my expectation was not too high.
After removing every shred of my VirtualBox installation from my hard drive -- please note that you do need to do a spotlight search and/or use something like CleanApp, because the VirtualBox uninstaller leaves a lot behind -- I ran the System Information app in the Applications/Utilities folder again, and looked under the Hardware/Camera section. Lo and behold! My camera was listed again!
So I launched FaceTime, followed by Photo Booth, and my camera is indeed working again in both of them!
That is great news! You are at least the 4th person now who has publicly noted this serious problem between macOS Sierra, VirtualBox and the iSight camera.Same here, had virtualbox installed, and by starting a virtual machine and connecting/disconnecting the isight to it the webcam came back to life.
Even though connecting the camera, starting up a VM, then disconnecting it, and shutting down the VM works, it always reverts to not working after logging out/restarting... although it sounds like if you remove it entirely, the problem goes away..That is great news! You are at least the 4th person now who has publicly noted this serious problem between macOS Sierra, VirtualBox and the iSight camera.
May I ask what machine you did this on?
As I explained earlier, I didn't quite understand brunsik's instructions, so I just deleted VirtualBox in its entirety, since I really didn't need it.
However, I don't doubt that there are still many others out there who are having this very same problem, but who don't know yet what the solution is to their broken iSight camera problem.
Having said that, I would like to ask a favor of you.
If you have the time and the interest, would you be willing to write a brief, clear, step-by-step tutorial -- including a few screen captures -- which explains exactly where and how to connect and disconnect the iSight camera within a VirtualBox VM?
I think doing so will help anyone else who comes along in the future, looking for a solution to the broken camera.
I would make it a brand new thread, with a very distinct name, so that forum members know exactly what the thread is about.
Thanks for considering it.