Saturday, October 26, 2013

Updating The 2009 LifeHacker QuadCore Hackintosh to Mavericks

In October 2009 the birthday present to myself was the LifeHacker QuadCore Hackintosh

I spent a bunch of time updating it to Mountain Lion, it is fairly successful now. I still need to straighten out the sleep function. The OS works, but it was not an easy install, for me that is.

My first hackintosh was the MSI Wind netbook, it was an easy install, bittorrent down a DVD ISO and install. There was one aftermarket driver for the wifi card and it was good! :)

The above lifehacker link has the hardware list. The unit now has 8 GB of RAM and two removable drive bays. I like to be able to pull the boot drive and swap it for any OS I need. The second bay is great for backup! Click the image for the link to see the product.

This week Mavericks came out, I update my one year old MacBook Pro, it seems OK so far, but it broke my ColdFusion install.

I was browsing around, looking to fix the Mountain Lion hackintosh sleep issue and saw that TonyMaxX86 had an article about building a Mavericks hackintosh.

It promised to be nooby easy, and was! :)

You need an 8 GB or better USB drive, a Mavericks Mac and MultiBeast & UniBeast.

The only thing that was not exactly as what the article said was that the original Mavericks install file still needs to be in the Applications directory. I backed it up before I upgraded the MacBookPro.

After that, the install was straight forward. Except to get it to boot right, I had to add some boot flags:
GraphicsEnabler=Yes, PCIRootUID=1

These boot flags are included in the MultiBeast Config file found here.

When following the instructions, at step 7 choose upload, and upload the config file, then skip to step 11.

I'll post updates if any events occur during the test drive.

Please donate to whose goal is to make computers accessible to all!

Enjoy Mavericks!

UPDATE #1 Want the stock on board audio to work properly also?

Download this package from Niresh!

UPDATE #2 Want iMovie? Torrent down a copy, and the app store will see it and offer you a new fresh copy

Wednesday, October 16, 2013

Horrible service from Sears Repair Service

Saturday October 12th we had an appointment with Sears Service for between 1:00pm - 5:00 PM

Every single time I spoke to them on the phone, they could not find my record. I had a service order number and they could not look up the record based on that. They barely spoke English.

I called and asked for an update, they said they would page the service person and he would call me. It did not happen.

I asked them to put my cell phone number on the account. It did not happen.

On two separate calls I asked to speak to a manager, I was put on hold and then hung up on.

One time I had to repeatedly asked to be connected to a supervisor and I was just ignored and talked over.

They came 45 minutes after the window closed. They took one look at the vertical stack washer dryer combo & left saying they needed a second man to move it.

I got home five minutes later, called the service to have the repairman to return. I moved the unit myself.

I was told they will page the repair man and call me back letting me know the result. There was no return call.

Today, Wednesday October 16th, the repair man called, my wife explained that they needed two people, he had no knowledge of the situation.

When the two repair men came, they did not have the hose. They were going to duct tape the broken hose and put the unit back.

I went online to entered an online chat at noon, asked to get a call from a supervisor.

I did get a call, he was not a client advocate, he promised to call be at 2:00 pm with status. There was no call.

I tweeted @SEARS & @Searscares

I sent them a PM with my contact information and I am now waiting.

I spoke to a really nice rep, that understands customer TLC.

Unfortunately it took my wife calling 3 times and me posting again on Twitter to get a response from her.

She was able to arrange for the service techs to be there first thing Saturday morning to take care of the issue.