Hackintosh disaster recovery part 2
24 04 2008In part one I looked at the steps I took to get my hackintosh working again after accidentally overwriting the boot information. The computer has been working fine for over three weeks since, and I haven’t found any side effects with software or hardware. My latest efforts have been focused on making bootable backups for use in the event of an unbootable hackintosh. Read the rest of this entry »
Tags : 10.5.2, apple, backup, carbon copy cloner, ccc, clone, firewire, hackintosh, kalyway, Leopard, macintosh, superduper, usb
Categories : apple, backup, computer, hackintosh, macintosh, software
I’ve wanted to compare different operating systems on the same hardware for several months, to see how much of an impact the OS has. Now that I have been using my hackintosh daily for over a month with no major issues I felt it was time to start doing some comparisons. One of the benefits of using generic hardware to run Mac OS is that it will happily run any other x86 operating system you care to try. The difficult bit seems to be getting them to co-exist without conflicting.
Apple products have had a reputation for ease of use for a long time, but I’m starting to think this has gone seriously awry with Leopard. Up to the release of 10.5 I didn’t have a problem operating Macs on a mixed Mac and Windows network. Leopard brought the promise of automatic discovery and display of network shares in the Finder sidebar. I think I mentioned this before, but it worked for half an hour then disappeared. I’ve spent several hours yesterday and today trying to figure out what is going wrong with this, and got to the point where my Macbook and Hackintosh were both visible to each other. The Macbook could connect to the Hackintosh shares, but not the other way round. Add to this the problems I had when upgrading my Macbook to 10.5.2 where the wireless access points became unconnectable and there’s some serious networking issues with Leopard. Does anyone have a fix for this?
Until yesterday my Macbook sat next to a 20 inch monitor, keyboard and mouse acting as my main computer. With the success of my new DIY Mac I unplugged all of that with the intention of finally using it around the house as originally intended. This was the first time I tried using a wireless network connection since upgrading to 10.5.2, and to my surprise it no longer works. I currently have two wireless routers in occational use, an old Benq 802.11b AWL500 and a belkin Pre-N F5D8230-4 v2. The Belkin router is now invisible to my Macbook, and although the Benq can be seen and I cannot connect to it unless I disable the wep security. Not an advisable practice. So I no longer have a wireless Macbook.
One of irritations of Leopard since it was released last year was the shared computers list in the Finder sidebar. Not that it’s an irritating feature since it stopped the requirement of connecting to servers to access them. The irritation is that it doesn’t work. The shared section on my macbook lasted around an hour after I first installed Leopard, and has been AWOL ever since. I’ve scoured the net for any method of restoring this feature with no joy. Other Macs show up if they are using AFP, but anything SMB (that’s windows and my Synology Diskstation) are missing. I’ve disabled Little snitch and the Leopard firewall. Deleted the smb.conf file so a new one was generated. I even followed 
I can understand wanting to get the next Mac OS update right but how long do we have to wait? I’ve delayed starting on my hackintosh until 10.5.2 is out to make sure I buy hardware that will work with the minimum of patching. There are so many reputed fixes in the update that it’s going to be a must for all Leopard users, finally giving us the quality we were originally promised.