eMac Restoration

20. September 2019 09:35 by Cameron in Mac  //  Tags: , , , , ,   //   Comments

Continuing retro Mac collecting, I picked up an eMac! Upon receiving the eMac, it was packed very well and the shell was mostly undamaged. There are a few small cracks on the front bezel, but mostly cosmetic. When I tried to boot up the eMac, it failed to load any operating system. I booted up the Mac OS X Tiger installer and tried to format the hard drive, but kept getting errors during formatting. Ultimately, I had to replace the original 60GB HDD with a spare 250GB HDD I had. The replacement wasn't too bad, but it is more involved than servicing an iMac G3. I also replaced the DVD drive since it is a standard 5.25" IDE DVD drive.

In the process of putting the case back on, I accidentally snapped the wires to the power button because I forgot to disconnect it until the case was properly aligned. This is a common problem with eMacs. Thankfully, I was able to find some replacement power button assemblies from a computer recycling company. While I waited for this to arrive, I fashioned a makeshift power button. My plan is to desolder the original power button connector and solder on a JST connector in its place. While I have the case open, I will be replacing the PRAM battery too since it seems to have gone bad.

Once I have everything reinstalled, I hope to not need to open the case again for a while since it's a bit of a hassle to service an eMac. The screen is a beauty though. Apple used Trinitron CRTs in their vintage iMac, eMac and studio displays. It will be nice to keep these in working order as long as I can. Next, I would like to find a classic 68k Mac. I haven't decided on which model yet, but I will keep my eyes open for a good deal.

iMac G3 Update

21. August 2019 20:35 by Cameron in Mac  //  Tags: , , , , , , , ,   //   Comments

Well, after about a week's usage, it would appear that my flyback transformer died on my Graphite iMac G3. I verified by booting up the iMac with an external display and verifying that the Apple bootloader was present. The flyback dying is unfortunately a common occurrence with these late 90's early 2000's iMacs and CRTs. I looked at replacing this part, but they're very hard to come by these days and Apple used a variety of parts for the flyback. One part I found was about $50, but it would require a lot of work and would ultimately not be worth the effort.

I decided to buy one more iMac G3 to satisfy my classic Mac wants. It's either an Indigo or "Fruit" iMac G3, but I will need to wait and see. The seller didn't take a picture of the sticker on the bottom of the unit so I'm not sure. I purchased this model for $69.99 with the known issue of not having a hard drive. It did however have pictures showing the CRT in working order. I have accepted now that whatever happens with this iMac happens. It's possible I get a few years out of it, but it's possible I get a week. It just depends on the previous owner's usage.

There was no mention on condition of the CD (maybe DVD) drive so I will need to proceed with caution on using the internal disk drive. I will try putting in a blank CD to make sure it ejects disks correctly before attempting to use the internal disk drive. If the internal disk drive doesn't work, then I will use Target Disk Mode from my iBook G4 like I did on the previous iMac G3. I did see that there are some "salvaged" slot loading CD drives on eBay so I may give those a look at a later point. I didn't see any replacement DVD drives though. I did actually confirm that my external Pioneer Blu-Ray drive works on the USB 1.1 ports on these iMacs so that could work in a pinch.

For the storage,  will see about using a 250GB IDE HDD since it is the standard 3.5" form factor and should fit nicely without modification. There might be some compatibility issues preventing all 250GB from being seen. I've heard that you can just partition the drive into smaller partitions for it to be recognized by the system. If that doesn't work, I guess it will only be able to address the first 128GB of the drive. Another option will be to use my original SD to IDE adapter with the Class 10 128GB SD card. This should be fast enough with 80MB/s read and write.

Once I've confirmed installation of Mac OS 9 and Mac OS X Tiger, I will do a logic board swap (assuming the logic board needs swapping). Then, I will make sure that the PRAM battery is replaced and re-install the 2x512MB of RAM. I could get an AirPort card, but there isn't much point since it would be 802.11b which would heavily cripple the rest of my 2.4GHz network. I will likely keep it hooked up via 100Mbit ethernet on my desk. Hopefully after all that everything will still work!

Once all of the parts are salvaged from my previous iMac, I will need to see about taking the CRT to an ecycler which is kind of a bummer. I could also try to sell for parts first and then go the ecyle route if that doesn't work.

I will post an update following my reassembly of the next iMac shortly!

HDMI Audio Kext for NVIDIA Graphics - Hackintosh

6. January 2014 22:40 by Cameron in   //  Tags: , , , , , ,   //   Comments

I've been searching for HDMI audio for quite some time for my desktop hackintosh and tonight I found just the right thing! Simply install the kext by running the install.sh script from the dmg image and voila! I have tested my NVIDIA GTX 660 on OS X Mavericks 10.9.1 and it works beautifully! I tried the DSDT editing but I don't think I got it quite right and it wasn't detecting my TV as an audio output device. After I installed the kext, all was good! Note that all volume control must be done through your TV or audio receiver. OS X doesn't support volume control on digital audio devices. Also, I'm not sure if you can use this kext in conjunction with AppleHDAEnabler, but I don't see why this would be a problem. TonyMacx86 should include this in Multibeast as it would make life much easier for those who don't want to mess with their DSDT.

NVAudio-1.0.dmg (27.02 kb)

Qt Development on OS X Mountain Lion

1. October 2012 21:18 by Cameron in C++, Mac, Mac OS X, Qt  //  Tags: , , , , , ,   //   Comments

OS X Mountain Lion changes a few things on how XCode is installed. Xcode is now contained in an app bundle and the SDKs directory is part of the bundle contents, thus you will need to update your SDK paths in your project file like so:

MAC_SDK  = /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.7.sdk
    if( !exists( $$MAC_SDK) ) {
        error("The selected Mac OSX SDK does not exist at $$MAC_SDK!")
    }
    QMAKE_MAC_SDK = $$MAC_SDK

If you want to support Snow Leopard as a target platform with your Qt applications, be sure to use the 10.7 SDK and not the default 10.8 SDK. Your app should work just fine in Snow Leopard provided that you don't make any calls to Lion specific features while using the 10.7 SDK.

Another important thing is to install the command line tools for GCC so that Qt can find the compiler during installation and successfully compile C/C++ applications from Qt Creator. If you do use the 10.8 SDK with any Qt version less than Qt 5.0, it will give warnings that OS X 10.8 is unsupported during compilation. These warnings can be safely ignored. Aside from that, everything else should be the same as before. Happy coding!

Qt Application Development in Mac OS X Lion

1. February 2012 01:52 by Cameron in Qt, Mac OS X, C++  //  Tags: , , , , ,   //   Comments

I've been working on some code using the QtSDK lately and I've been researching how to deploy applications for Mac OS X 10.6 and above. Luckily, it's pretty simple to deploy applications as the QtSDK includes a tool called macdeployqt. The tool copies all required Qt frameworks to the app bundle and re-assigns the library reference paths for the app to use the libraries within the app bundle and not the user's system directory (/usr/lib). It doesn't copy 3rd party libraries that aren't in the /usr/lib directory so you will have to manually add those.

Please note that macdeployqt on Qt 4.7.x doesn't seem to assign the correct library paths when linking against QtWebKit. This is a known bug that was fixed in Qt 4.8.0.

Also, if you want to insure that your app will not have problems on Snow Leopard, be sure to add this to your .pro file: 

macx:QMAKE_MAC_SDK=/Developer/SDKs/MacOSX10.6.sdk

This tells Qt to use the Snow Leopard SDK instead of the Lion SDK. If you build your application with the 10.6 SDK, it will work with Mac OS X 10.6 or higher.

One last thing is that there seems to be a problem with Xcode 4 and Qt Creator not being able to find g++-4.2 which is installed with older versions of Xcode. A work around for this until a new version of Qt Creator:

sudo ln -s /usr/bin/g++ /usr/bin/g++-4.2

sudo ln -s /usr/bin/gcc /usr/bin/gcc-4.2

I hope this helps anyone experiencing the same issues.

 

EDIT:
As of the February 1, 2012 QtSDK update, it appears as though the problems with g++ and using macdeployqt have been fixed. Please be sure to update to the latest SDK release. 

Month List

Tag cloud