Filed under: OS, Software, Odds and ends

From time to time we have shared hidden settings in applications which can be used to “tweak” an app’s behavior, such as forcing Snow Leopard’s dictionary to reuse the same window or make the print dialog expanded by default. These settings are normally changed using the Terminal.app which can be daunting to some.

Secrets is a (free!) preference panel which has collected a bunch of these settings and made changing them as simple as checking a box or choosing from a drop-down panel of possible choices. It includes settings for about 40 different applications, from Apple applications such as Mail, iCal, iChat, Finder, Front Row, Keynote, DVD Player (and more) to third-party applications including Adium, Audio Hijack Pro, BBedit, EyeTV, VMware Fusion, and TextMate (just to name a few). Some applications have a lot of hidden settings, and some have only one or two.

If you see a setting but don’t know what it does, click it and Secrets will show a brief explanation (these are also available on the Secrets website, but they are easier to read in the preference panel). If you change a setting which requires you to restart the application, Secrets will tell you, and even give you a “Quit This” button. (It’s usually best to make these changes when the app isn’t running.)

Unfortunately at least one of the secret settings from 10.5 doesn’t seem to work in 10.6. That is, the setting to turn HelpViewer into a regular (instead of floating) window. There may be others.

I’m off to explore and see what new goodies Alcor (the developer of Secrets, who you may also know as the creator of Quicksilver) has uncovered.

Thanks to the recently-revived Hawk Wings site for bringing this to my attention. If you use Apple’s Mail.app, Hawk Wings is a great site for tips and information.

Update: We seem to have taken down the Secrets website (oops!) but you can download the preference panel from a mirror (zip) (166kb).

TUAWSecrets preference panel updated for Snow Leopard originally appeared on The Unofficial Apple Weblog (TUAW) on Thu, 05 Nov 2009 13:00:00 EST. Please see our terms for use of feeds.

Read | Permalink | Email this | Comments

Go to Source

Secrets preference panel updated for Snow Leopard originally appeared on Shai Perednik.com on November 12, 2009.

Filed under: OS Updates, Hardware, Apple

According to OSXDaily, Apple’s next scheduled update to Snow Leopard, OS X 10.6.2, doesn’t support Intel Atom processors. This is no problem for anyone on Apple hardware, because no Mac product runs an Atom. If you’re on a hacked netbook, though, it looks like this is the end of the line for your OS X updates.

Although it’s not confirmed, rumor has it that next update to Apple’s previous Leopard OS (10.5.9) will also knock out Atom support. Until a workaround pops up from netbook hacker circles, Atom machines running 10.6.1 and 10.5.8 should probably avoid upgrading. Is Apple sending a message to users running its software on third-party machines? It seems likely, but it also doesn’t seem like it will do much to stop determined netbook enthusiasts.

Apple breaks Atom Hackintoshes with upcoming OS X 10.6.2 update originally appeared on Download Squad on Mon, 02 Nov 2009 10:00:00 EST. Please see our terms for use of feeds.

Read | Permalink | Email this | Comments

Apple – Operating system – Mac OS X – Intel Atom – Download Squad

Go to Source

Apple breaks Atom Hackintoshes with upcoming OS X 10.6.2 update originally appeared on Shai Perednik.com on November 5, 2009.

Filed under: Hacks, Mods, Snow Leopard

Psystar, that pesky little thorn in Apple’s side, has released Rebel EFI. According to Psystar, the app, available for $49.99 through the company’s site, “allows for the easy installation of multiple operating systems,” including Mac OS X, on a vanilla PC. Besides bypassing EFI requirements, Rebel EFI can also detect for Mac OS X compatible and incompatible hardware, and automatically download appropriate drivers. Skeptical? No worries: the app is free to try (as an ISO download), with a two hour time limit.

To each their own, and if running Mac OS X on non-Apple specified hardware floats your boat, then you should also be aware of the risks involved. In other words, back up your data if you are attempting such a thing. Second, and more importantly, there’s the issue of licensing: Apple prohibits the installation of Mac OS X on non Apple-branded machines.

Psystar giveth and Psystar must also taketh. One wonders how Psystar will react when people illegally use Rebel EFI, just like Psystar is allegedly misusing Mac OS X, as pirated versions inevitably circulate around the Interwebs.

Thanks to everyone who sent this in.

[via The Loop]

TUAWWith a rebel Dell, Psystar tries more, more, more originally appeared on The Unofficial Apple Weblog (TUAW) on Thu, 22 Oct 2009 19:00:00 EST. Please see our terms for use of feeds.

Read | Permalink | Email this | Comments

Go to Source

With a rebel Dell, Psystar tries more, more, more originally appeared on Shai Perednik.com on October 22, 2009.

Most people who have designed websites or apps in Photoshop will, at one point or another, have had issues trying to match colors in images to colors generated by HTML, CSS or code. This article aims to solve those problems once and for all.

Color Management to Match Colors Across Multiple Devices

In the print world, color management typically involves calibrating your entire workflow, from scanner or digital camera to computer display to hard proofs to the final press output. This can be quite a tall order, especially when the devices use different color spaces — matching RGB and CMYK devices is notoriously hard.

When designing or editing for TV, calibrating the main editing display and using a broadcast monitor are common; these show real-time proof of how the image will look on a typical TV in a viewer’s home. In such a scenario, color management offers many benefits and is highly recommended.

When building Web and application interfaces, the situation is a little different. The final output is the same device that you’re using to create the artwork: a computer display (putting aside for now differences in gamma between Windows, Mac OS X prior to 10.6 and the iPhone, which we’ll cover later.)

There is a catch, though. Even though you’re creating the Web or app interface on the same device that the final product will be shown on, the colors will have various sources: images (typically PNG, GIF and JPEG), style markup (CSS) and code (JavaScript, HTML, Objective-C, etc). Getting them all to match can be tricky.

The Goal

When designing websites or app interfaces, we want to perfectly match the colors that are displayed on screen in Photoshop and that are saved in files with what’s displayed in other applications, including Firefox, Safari and the iPhone Simulator. Not only do we want the colors to look the same, but we want the actual values saved in the files to perfectly match the colors we have defined in Photoshop. Colors should not shift or appear to shift in any way, under any circumstance.

Why Is This So Difficult?

Photoshop applies its color management to images displayed within its windows and to the files it saves. This is a bad thing if you’re working exclusively with RGB images for Web or on-screen user interfaces. With the default Photoshop settings, #FF0000 will actually display as #FB0018, and #BB95FF will display as #BA98FD. The differences are subtle but definitely there.

How Does Photoshop Differ From OS X And Windows?

OS X’s color management is applied to the entire display at the very end of the processing chain, after the main buffer in video ram. This means that although color management is applied, the software utilities that measure color on screen (like /Utilities/DigitalColor Meter) will report the same values that you have saved in the file or entered as your code. I believe the color management in Windows Vista and Windows 7 (Windows Color System) works in a similar fashion.

Photoshop’s color management is applied only to the image portion of its windows and to the files it saves. This color correction happens as Photoshop draws the image on screen, so software utilities that measure color on screen often report different colors from the ones you have specified. It’s worth noting that OS X’s color management is applied on top of Photoshop’s.

The best solution I’ve found is to disable Photoshop’s color management for RGB documents as much as possible. Doing so forces the RGB colors that are on screen and saved to the file to match the actual color value. If you need to calibrate your monitor for Web and app design work, then you would best be served by changing it at the OS level.

Disabling color management used to be quite easy in Photoshop CS2 and all versions prior, but it now requires a little more skill.

Disabling Photoshop’s RGB Color Management

These instructions are for Photoshop CS4 on Mac and Windows. Setting up CS3 is very similar.

Step 1: Go to Edit ? Color Settings and set the working space for RGB to Monitor RGB.

Step 2: Open a document and go to Edit ? Assign Profile, then set it to Working RGB. This must be done for every single document you work on.

Step 3: Ensure View ? Proof Colors is turned off.

Step 4: When saving files with Save for Web & Devices, ensure that Convert to sRGB is turned off. If you’re saving a JPEG file, then also turn off Embed Color Profile (you may want this turned on for certain photos, but chances are you’ll want it off for interface elements and icons).

Difference Between “Assign Profile” And “Convert To Profile”

Now would be a good time to mention the difference between Assign Profile and Convert to Profile, so that you know which to use when.

Each Photoshop document contains a color profile that’s separate from the actual color data stored for each pixel. Assign Profile simply changes the profile in the document, without affecting any of the color data. It’s a non-destructive action: you can assign a new color profile to your documents as often as you like without doing any damage. Assigning a new profile may change the way your document appears on screen, but the data contained in the file will remain unaltered.

Convert to Profile is quite different. Not only does it assign a color profile to the document, but it tries to keep your image looking the same on screen. It does this by processing the color data contained in the file for each pixel. Converting to a new profile will more likely preserve a document’s color on screen, but the data contained in the file will be permanently altered. Use with caution.

If you’re copying layers from one Photoshop document to another, you will want to ensure that the documents have been assigned the same color profile.

Illustrator Is The Same As Photoshop

If you would like images saved in Illustrator or imported from Illustrator to Photoshop to match as well, then follow the steps below. These instructions are for Illustrator CS4 on Mac and Windows. Setting up Illustrator CS3 is very similar.

Step 1: Go to Edit ? Color Settings, and set the working space for RGB to Monitor RGB.

Step 2: Open the document and go to Edit ? Assign Profile. Then set it to Working RGB. This must be done for every single document you work on.

Step 3: Ensure that View ? Proof Colors is turned off.

Step 4: When saving files with Save for Web & Devices, ensure that Convert to sRGB is turned off. If you’re saving a JPEG file, then also turn off Embed Color Profile (again, you may want this turned on for certain photos, but chances are you’ll want it off for interface elements and icons).

Gamma Differences

Windows has used a gamma of 2.2 since its introduction. Mac OS X has used a gamma of 1.8 for all versions except Snow Leopard (the latest release), which uses 2.2. What does this mean? Prior to Snow Leopard, Web pages looked darker on Windows. Thankfully, both operating systems are now in sync, so a Web page should look very similar on a Mac and PC that use the same monitor.

Information about the iPhone’s gamma is a little hard to come by; I couldn’t ascertain whether it is 1.8 or 2.2. This is another reason to test your interface on an iPhone.

Final Check For iPhone UI

Your iPhone or iPod’s screen and calibration will likely be different from your Mac or PC’s screen and calibration. I often import full-screen images of the UI into iPhoto and sync them with an iPhone to see exactly how the final interface will look on the device (on Windows, you can sync photos using iTunes). This gives you another chance to make adjustments before slicing up images or committing anything to code.

This article explains how to handle the problem that while testing some landscape iPhone app interface mocks, they seem blurrier than they appear in Photoshop.

Please note: For some bizarre reason, the Photos app on the iPhone doesn’t display landscape images at 1:1. Instead, it scales them slightly or shifts them to a sub-pixel position, making the images blurrier than they should be. To avoid any issues, always save images in portrait mode (320 pixels wide by 480 pixels high) to test your user interface mockups (read more about this issue).

On Mac, moving colors between Photoshop and code can be made easier with Developer Picker, Hex Color Picker and Colors (all free).

Conclusion

Now, you’re able to move bitmap and vector images between Photoshop and Illustrator without any color shifts at all, and using any method. You’re also able to grab a color using the color picker in Photoshop, and then use the same HEX color value in your CSS, HTML, JavaScript, Flash or Objective-C code, and it will match your images perfectly. I hope this article has helped. If you have any questions, feel free to ask in the comments below.

Related posts

You may be interesting in the following related posts:

• 20 Time-Saving Tips to Improve Designer’s Workflow
• Clever PNG Optimization Techniques
• PNG Optimization Guide: More Clever Techniques
• Clever JPEG Optimization Techniques

(al)

© Marc Edwards for Smashing Magazine, 2009. |
Permalink |
64 comments |
Add to del.icio.us | Digg this | Stumble on StumbleUpon! | Tweet it! | Submit to Reddit | Forum Smashing Magazine

Post tags: cmyk, photoshop, rgb, workflow

Go to Source

Setting Up Photoshop For Web, App and iPhone Development originally appeared on Shai Perednik.com on October 17, 2009.

Filed under: Analysis / Opinion, Apple Corporate, Hardware, OS

Apple and Psystar have been embroiled in litigation for quite a while now. At the core of the dispute: Psystar modifies Apple’s operating system software so that it can run on its clone machines. It then sells its computers with Mac OS installed to, well, anybody who wants one. As you can imagine, this does not make Apple happy.

Anybody familiar with The Great Clone Crackdown of 1997 will tell you that Apple likes to keep a very tight grip on any device that presumes to run its software. Apple points out that Windows machines are a mishmash of often conflicting hardware and suffer from quirks and errors and incompatibilities that such a set up can bring.

So Apple’s cadre of lawyers descended quickly on Psystar. In July of last year, the company sued Psystar for copyright and software licensing violations, quickly amending its lawsuit to additionally charge Psystar with violations of the Digital Millennium Copyright Act (DMCA).

And there was much lawyering.

More than a year later, now that discovery has been completed, the two parties have each filed for summary judgment, which, in effect, asks the judge to rule in favor of the filing party because enough evidence has been shown that either makes or breaks the lawsuit.

Psystar’s argument, and the one covered in its motion, somewhat relies on the “first sale doctrine” which says that any purchaser of a copyrighted product can then take that lawfully-made copy and sell it, so long as no additional copies can be made. For its part, Apple says that when one “purchases” its OS, you are only purchasing a license to use the product. Its Software Licensing Agreement (SLA) quite clearly states [PDF link to Snow Leopard SLA] that the user cannot modify the software to run on a non-Apple system.

The idea that what you are purchasing is a license to use the product is pretty commonplace among software manufacturers, because, the argument runs, you can cut any software company’s profits off at the knees if every purchaser became an owner with free rein to redistribute the software. Apple states that no software company in its right mind would put the money into research and development of any software product at all if that were the end result of bringing its product to market. Groklaw suggests this could have ramifications for FOSS and and the GPL.

Continue reading Psystar, Apple file motions for summary judgment

TUAWPsystar, Apple file motions for summary judgment originally appeared on The Unofficial Apple Weblog (TUAW) on Wed, 14 Oct 2009 16:30:00 EST. Please see our terms for use of feeds.

Read | Permalink | Email this | Comments

Go to Source

Psystar, Apple file motions for summary judgment originally appeared on Shai Perednik.com on October 17, 2009.

Filed under: Cool tools

Every “point-oh” version of Mac OS X usually brings some small bit of pain, as I find some little utility no longer works. Snow Leopard has been no exception. I had been using the version of Screen Sharing from 10.5.4 because it had some “hidden” features which I liked. Unfortunately those “hidden” features were also “unsupported” features. When 10.5.5 came out, they were gone, but I continued to use the version of Screen Sharing from 10.5.4 which worked until 10.5.8. Sadly for me, it does not work at all in 10.6.

The biggest drawback of Screen Sharing was the removal of the Bonjour Browser, which showed a list of computers available for Screen Sharing (both locally and via Back to My Mac). Now I had to type them in manually, which isn’t such a big deal when you are trying to connect to a machine on a local network. If you are trying to connect over the Internet, however, you need to use the full hostname, which may look something like this: macbook.yourname.members.mac.com. Plus, it just seems like one of those things that the computer ought to do for me. [Side note, if you are looking for a handy way to see all the Bonjour services on your local network, check out Tildesoft's free Bonjour Browser utility.]

While looking through a bunch of old files in my ~/Downloads/ folder, I found a version of ScreenSharingMenulet. I checked its webpage and saw what I was looking for: “ScreenSharingMenulet 1.7.1 and higher is compatible to Mac OS 10.6 Snow Leopard.” ScreenSharingMenulet sits in the menu bar along with your other menu extras. Simply click on its icon (shown above) and choose which computer you wish to connect to via a dropdown list. In my testing it worked very well over a LAN although it did not seem to pre-populate with the machines over the Internet. Given the flakiness of Back To My Mac over ther Internet, I can hardly fault this program for that shortcoming.

ScreenSharingMenulet is free (donations accepted) from Stefan Klieme who has several other handy-looking utilities at his website. If you use Screen Sharing a lot, it’s definitely a handy tool to have around.

TUAWScreenSharingMenulet fills a gap in Snow Leopard’s Screen Sharing.app originally appeared on The Unofficial Apple Weblog (TUAW) on Sun, 20 Sep 2009 21:30:00 EST. Please see our terms for use of feeds.

Read | Permalink | Email this | Comments
Go to Source

ScreenSharingMenulet fills a gap in Snow Leopard’s Screen Sharing.app originally appeared on Shai Perednik.com on September 21, 2009.

Filed under: Humor, Software, Snow Leopard

Some of you may have noticed that some of your screensavers don’t work after upgrading to Snow Leopard. If you’re running a 64-bit instance of the operating system, you won’t be able to use most of your old third-party screensavers because they’re probably not compatible. Many of our favorite screensavers weren’t working… so instead of waiting for the developers to release them in 64-bit, we decided to see what else was out there.

iSight Screensavers from Majic Jungle (the creators of FluidTunes) isn’t new, but it’s something we’ve never covered here on TUAW. It was one that showed up first in our search and ended up killing our productivity for the rest of the day. And the next day. In fact, we’ve not really recovered productivity since we clicked the “test” button in System Preferences.

Majic Jungle has made a killer screensaver that allows you to interact with different effects and filters using the iSight camera, or any webcam attached to your mac. I won’t get into the countless scenarios we created (we’re pretty easily entertained), but here’s a list of interactions from the creators’ site to help explain what it does:

• Fluid – Play with a beautiful fluid dynamics simulation
• Particles – Create magical looking brightly colored particles wherever you move
• Champagne – Immerse yourself in a champagne world and watch as bubbles appear all over you
• Fire – Set yourself or your desktop on fire – in a painless kind of way!
• Water – Ripples appear wherever you move
• Flipping Grid – Can you get all of the squares to flip over together?
• Core Image – Over 30 configurable effects using powerful Core Image filters

iSight Screensavers is Universal Binary and Shareware. If you’d like to remove the watermarks, you can purchase a license for $4.99 — pretty cheap considering my wife and I are more entertained by this than by a $25 night at the movies.

TUAWiSight Screensavers: Interact with your screensaver originally appeared on The Unofficial Apple Weblog (TUAW) on Thu, 17 Sep 2009 12:00:00 EST. Please see our terms for use of feeds.

Read | Permalink | Email this | Comments
Go to Source

iSight Screensavers: Interact with your screensaver originally appeared on Shai Perednik.com on September 20, 2009.

Last year we have spoken about what seemed to be the future eldorado of Hackintosh, the USB key EFI-X. 

It made it possible to the owners of PCs (with the specifications close to the Mac) to easily create Hackintosh. It was enough to connect the key before installing completely the standardl Mac OS X. 
A little time ago, the company announced that version 1.0 of its key would not function with Snow Leopard and that a new version, 1.1, would be needed.
Tom’s Hardware UK reports the story of the administrator of the blog AsereBLN who was irritated by this news and decided to see what this key contained.

After having removed the black epoxy resin that protected the components from inquisitive eyes, he was surprised to see that it did not have much more than in a banal USB key and than this product should not cost more than 10€ to manufacture; however it is sold for more than 200€. 

One may have thought that the price was justified by the software development, but he also decided to decipher the firmware of the key and  found there… open source code developed by OSx86 group and hardly any attempt to hide it.
He thus decided to shout about this in a high voice on his blog, and to even propose an open source clone of EFI-X, the EXI-X.

It was learned that the manufacturers of the EFI-X key decided to prosecute him. We will keep you informed of the current situation during this process and we ask you to moderate your remarks in the reactions to this information. We have made some efforts during the drafting of this so that no-one can reproach us, since we have only reported the facts without making any assessment. Make of this as much as you like.

Go to Source

A squabble over EFI-X originally appeared on Shai Perednik.com on September 16, 2009.

Two years ago, I detailed how to build a Hackintosh for under $800—then covered how to do the same with less hacking. Now that Snow Leopard’s out, we’re revisiting the Hackintosh, building a Hack Pro from scratch for roughly $900.

For folks eager to try a Mac but never wanted to plunk down the high price tag to get it, the Hackintosh—that is, a regular PC tweaked to run OS X—has always been an attractive option. That said, it’s not something you should take on lightly unless you’re willing—even enthusiastic—to build and maintain a PC entirely from scratch. I can’t guarantee it’ll be easy, but if you follow this guide step-for-step (it’s exhaustive) and stick with the same (or at least roughly the same) hardware as I am, I can vouch for a rock solid system that also happens to cost a good deal less than you’d pay for a comparable Mac.

Price Comparisons

Most Hackintosh enthusiasts will say you shouldn’t build a Hackintosh primarily to save money, as it’s more than just an insert-disc-and-click install. Still, I always enjoy looking at the price differences between my Hackintosh and Apple’s current offerings. At the moment, the cheapest Mac in the Apple store is a Mac mini sporting a 2.0GHz Core 2 Duo processor, 1GB of RAM, and a 120GB hard drive. For $300 more, I’m running a 3.0GHz Quad-Core processor, 8GB of RAM, a 1TB hard drive, and a damn saucy video card. I could have made this build much cheaper by skimping on hardware and still ended up with a great little machine, but I liked aiming for around the $800 price point from my last build—plus I really wanted to make it fly.

The most expensive iMac, by comparison, has only a 3.06GHz Core 2 Duo with 4GB of memory for $2,200 ($1,300 more than my build, but it is built into a monitor), while the cheapest Mac Pro has a single 2.66GHz Quad-Core processor, 3GB of RAM, and a 640GB hard drive—and it costs $2,500 ($1,600 more than mine, though it’s a different and better processor and DDR3 rather than DDR2 RAM). In short, my $900 “Hack Pro” sports nearly as good or better hardware than any Mac that Apple sells short of the $3,300 8-Core Mac Pro (which can, incidentally, get more expensive, but it won’t get much better).

The Hardware

You can find plenty of hardware capable of supporting OS X on a Hackintosh—there’s no definitive build—but we’re not going to go into that here. I’ve put together a list of hardware that I’m using and that I can guarantee will (or at least has) run Snow Leopard like a dream.

Here’s a link to everything I bought over at Newegg:

• Antec Sonata III 500 Black ATX Mid Tower Computer Case 500W Power Supply
• GIGABYTE GA-EP45-UD3P Intel P45 ATX Intel Motherboard
• Intel Core 2 Quad 3.0GHz LGA 775 95W Quad-Core Processor
• GeForce 9800 GTX+ 512MB 256-bit GDDR3 PCI Express 2.0 x16
• Patriot Extreme Performance 4GB (2 x 2GB) DDR2 800 (PC2 6400) Dual Channel Kit Desktop Memory x 2 (for a total of 8GB)
• Western Digital Caviar Green WD10EADS 1TB SATA 3.0Gb/s 3.5″ Internal Hard Drive
• Pioneer CD/DVD Burner Black SATA Model
• 10/ 100/ 1000/ 2000Mbps PCI Copper Gigabit Network Adapter (The motherboard has onboard Ethernet, naturally, but this particular board has some problems with onboard in the Hackintosh world. Luckily, Ethernet cards are extremely cheap.)

The Build

Rather than detail every step necessary to put the actual pieces of your new computer together (this guide already reads like the Bible as is), I’m just going to point you to our first-timer’s guide to building a PC from scratch. Do your building, make sure everything’s booting up as it should be (i.e., you can boot the computer to the point where it does nothing, because you have nothing installed on it), then let’s move on.

What Else You’ll Need

Assuming you’ve purchased all the necessary parts for your build (linked above), you’ll still need a few other things before you get started:

• A USB thumb drive that’s at least 8GB in size (I’m using this 16GB Corsair drive, but obviously any sufficiently sized thumb drive should do just fine.)
• A copy of the Snow Leopard Install DVD. You can use the $29 “Upgrade” disc to install, even though this is a fresh installation. Note: If you feel like being completely honest, go ahead and buy the Mac Box Set—though, honestly, Apple’s practically made it hard *not* to buy the fully functional install disc.
• Another Mac to do some Terminal work on. (You’ll only need this other Mac for a few steps. I used my MacBook Pro, but you could also borrow a friends for an hour or so, too.)

Step One: Prepare Your Thumb Drive

We’re going to be installing Snow Leopard to your Hackintosh from your thumb drive rather than from the Snow Leopard install DVD, since in order to run the installer on your PC to begin with, you’ll need to slightly customize the way the installer is loaded. (More specifically, we’ll be loading a custom bootloader onto the thumb drive that will make booting into the install work like a charm.*)

So first things first: You need to format your thumb drive and then turn your Snow Leopard install disc into a disk image on your desktop. Here’s how to do it:

1. Launch the Disk Utility application on your borrowed Mac (located at /Applications/Utilities/Disk Utility)
2. Format and partition your thumb drive: Insert your thumb drive; after a second, it should show up in the Disk Utility Sidebar. When it does, (1) click on it, then (2) click on Partition. (3) Choose 1 Partition from the Volume Scheme, (4) give it a name (I called my HackintoshInstall) and select Mac OS Extended (Case-sensitive, Journaled) from the Format drop-down. Now—and this is important—(5) hit the Options button and make sure GUID Partition Table is selected as the partition scheme. Once you’ve made sure to set all the appropriate settings, just (6) click Apply and Disk Utility will get to partitioning your thumb drive.
3. Copy the Snow Leopard Install DVD image to your hard drive: In the following step we’ll be turning your thumb drive into a Snow Leopard Install drive, but before we do that, we need to get the installer off your DVD and onto your hard drive. To achieve this, insert the Snow Leopard DVD. When it shows up in the Disk Utility sidebar, (1) click on it, then (2) click New Image in the Disk Utility toolbar. Choose where you want to save it (for the sake of convenience, I put it on my Desktop), then click the Save button. Now go grab yourself a cold drink. This will take some time. When it finishes, move on to the next step.
4. Restore the Snow Leopard Install disk image to your thumb drive: Now, in Disk Utility, (1) click on HackintoshInstall (or whatever you called your partitioned thumb drive) and (2) click on Restore. (3) Drag and drop Mac OS X Install DVD.dmg from the sidebar to the Source field, then (4) drag and drop your thumb drive from the sidebar to the Destination field. Now simply (5) click on Restore and enter your password when prompted. Disk Utility will take everything on the Snow Leopard Install DVD and restore that image to your thumb drive—since, like I said above, we’ll be installing Snow Leopard from our thumb drive instead of the DVD. Again, go grab yourself another drink; this will take a few minutes. When it finishes, your thumb drive has basically been turned into a Snow Leopard installation drive.

As I said earlier, the thumb drive needs a little finesse before you can boot the Snow Leopard installer on your PC hardware; let’s apply that finesse now.

Warning: Semi-heavy Terminal work ahead. It’s not that difficult, and I’ve gone into a lot of detail to make it as easy to follow along as possible, but if you’re not at least a little comfortable with the command line, it may make you pretty uncomfortable. Beg or borrow a command line geek for an afternoon, if needed.

1. Make sure your thumb drive is still plugged in, open Terminal (/Applications/Utilities/Terminal) and type in:
   diskutil list

   
   We’re interested in two pieces of information here. The first is the root identifier for your thumb drive (mine looks like disk2, as you can see in the screenshot). The second is the specific identifier for the portion of the thumb drive that contains the Snow Leopard installer. (Again, see the screenshot.) In my case, the first is disk2 and the second is disk2s2. Yours may vary depending on how many disks are on your system. Copy your identifiers down somewhere. We’ll need them later.

2. Head to the Chameleon homepage, find the Latest Releases section of the site’s sidebar, and download the latest version of Chameleon. (As of this writing, it’s Chameleon-2.0-RC2-r640.) Uncompress the download and move the Chameleon folder to someplace that’s easy to access. I’m putting it on my Desktop.
3. Now, in Terminal, cd to the i386 folder of the Chameleon folder. On my Mac, the command looks like this:

   
   (1)

   cd /Users/adam/Desktop/Chameleon-2.0-RC2-r640-bin/i386/

   Yours should look similar if the Chameleon folder is on your Desktop, except your username should replace mine. (Quick shortcut: In Terminal, type cd , then drag and drop i386 folder inside Chameleon-2.0-RC2-r640 to Terminal.) Hit Enter.

4. You’re going to be running a couple of Terminal commands that will use Chameleon to make your thumb drive friendly to booting up the OS X installer. They are, as follows:

   (2)

   sudo fdisk -f boot0 -u -y /dev/rdisk2

   IMPORTANT: On your computer, replace rdisk2 with whatever you copied down above. In my case, the thumb drive’s root identifier was disk2, so /dev/rdisk2 is as it should be.

   After you type in that command and hit Enter, you’ll need to enter your user password to execute it. Do so, then execute the following command, again paying special attention to the disk identifier we took note of above:

   (3)

   sudo dd if=boot1h of=/dev/rdisk2s2

   IMPORTANT: As I noted, my Snow Leopard partition was disk2s2, so that command is right for me. You should replace the disk2s2 portion of the command with whatever you noted as the portion of your thumb drive that contains the Snow Leopard installer.

5. Now we’re going to place an awesome, custom EFI bootloader on your thumb drive that lets us load into the installer (and into Snow Leopard in general). So first, head over to netkas.org and download the bootloader from the bootloader link. Make sure you download it somewhere convenient. (Again, I’ve just downloaded it to my Desktop.)

   Now head back into Terminal, where we’re going to copy the boot file to your thumb drive. (One might think that you could just do this using Finder via drag-and-drop, but in this case, doing it via Terminal is necessary.) So, in Terminal, your command should look similar to this:

   sudo cp /Users/adam/Desktop/boot /Volumes/HackintoshInstall

   The easiest way to do this is simply type in sudo cp , (1) drag and drop the boot file into Terminal, then (2) drag and drop your mounted thumb drive from the desktop into Terminal. (The drag-and-drop method is a quick Terminal trick that pastes the full path to each file or directory.) After that, simply hit Enter. (Enter your password if necessary.)

6. I know it seems like we’ve already run a marathon, but you’ve got one last step and then it’s relatively smooth sailing from here on. Download Extra.zip, unzip the file, and then drag and drop the Extra folder into your thumb drive. Nothing fancy, a simple drag and drop with your trusty old mouse will do. Once you’ve done that, open up your thumb drive and verify that it looks something like the screenshot below. (Notice the Extra folder, the boot file, and the OS X installer.)

Take a deep breath. By this time, you’ve completed all the hard work. Now it’s time to boot up your machine, tweak your BIOS settings so they’re ready for your OS X install, and then it’s smooth sailing.

Step 2: Set Your BIOS

Before you can boot into or install OS X on your Hackintosh, you’ve got to make some small adjustments to your BIOS. Rather than taking you step by step through every change you need to make, I’ve simply snapped a picture of the relevant BIOS screens and added some notes. Just click through these images and make sure your BIOS settings match up.

Step 3: Install Snow Leopard

If you’ve made it this far, the hard part is over. Now it’s time to install Snow Leopard, which—unlike what we’ve done so far—is extremely easy.

Make sure you’ve set the boot priority in your BIOS to boot from your thumb drive (you can see how in this pic), then simply plug your prepared thumb drive into your Hackintosh and power it up. Since screenshots aren’t really an option—and since it’s a fairly easy process—my install instructions come in video format:

The quick version goes like this: Boot into the Snow Leopard installer, format the hard drive you want to install Snow Leopard to (go to Utilities -> Disk Utility, then click on the drive, select 1 Partition, Mac OS X Journaled (Case-Sensitive Update: Several readers have suggested that case-sensitive formatting can cause problems with some applications, like Adobe’s Creative Suite, so you may be better off sticking with plain old Mac OS X Journaled.), give it a name, and make sure GUID Partition Table is set in the Options. After you Apply the new partition, go back to the installer and install like normal to that drive. When you reboot after the install completes, press the arrow keys at the graphical boot menu and select the drive you just installed Snow Leopard to.

A Few Final Tweaks

You’ll notice that, the first time Snow Leopard boots up, you’re not enjoying any sound along with that snazzy intro video. We’ve got one small, but very simple tweak to make to get sound up and running. Here’s how it works:

1. Download the Kext Utility, then download this audio kext (a kext is kind of the Mac equivalent of a driver) and unzip it to your Desktop. Once you’ve got both in front of you, drag and drop the ALC889.Fix.kext file onto the Kext Utility. You’ll be prompted to enter your password, so go ahead and do that when you’re prompted.
2. Once the Kext Utility finishes running, open up Disk Utility (/Applications/Utilities/Disk Utility.app). Once it loads up, (1) click on your Snow Leopard drive (mine’s called Hack Leopard), then (2) click Repair Disk Permissions.
3. Once Disk Utility finishes repairing your disk permissions, just restart. After your computer reboots, your audio should be working like a charm. (If not, open up Sound in your System Preferences and try changing the Output device.)

As things stand on your system right now, you need to have your thumb drive plugged in every time you reboot in order to load the bootloader that allows your Hackintosh to load OS X. There are certain benefits to this (for example, right now you could quite likely unplug this hard drive from your Hackintosh, plug it into a Mac Pro, and it would work just fine), but it can also be a bit of a hassle. At this point, though, you can load the bootloader and other necessary components onto the Snow Leopard hard drive and change that drive to your primary boot drive in your BIOS. All you’ve got to do is head back to the step-by-step bootloader guide above and repeat every step, except this time you’re applying each step to your hard drive rather than your thumb drive.

Congratulations! You’ve Got a Fully Functional Hackintosh

“But for realz,” you ask, “does it actually work well?”

I’ve been using one or another Hackintosh as my main computer for two years now, and while I’ve run into the occasional bump in the road, they’ve generally run extremely well. In fact, things just seem to keep on getting better and better, and the current build I’m running (the one I walked you through above) feels like the fastest, most stable build to date.

That’s not to say that you won’t experience an occasional kernel panic—you may very well. But I get crashes on my MacBook Pro, too, and I’ve never felt that my current Hack Pro has any more problems than any other proper Mac I’ve used on a regular basis. That may seem a bit crazy, but it’s true.

As for upgrading—often, you’ll be able to upgrade your Hack Pro without any problems. That said, it’s something you normally need to check on beforehand, and you should take all of the upgrade precautions before giving it a go.

I’m planning on letting readers know how my Hack Pro handles various 10.6.x updates shortly after they happen, though, and if it requires a little extra work, I’ll show you how to handle it.

Let’s hear your thoughts—whether you’ve dabbled in the world of Hackintosh, are interested in doing so, or just think it’s plain crazy—in the comments.

Adam Pash is the editor of Lifehacker; he loves a good hack, cherishes his Macintosh, and craves a Mac Pro, so building a Hack Pro was a perfect fit. His special feature Hack Attack appears on Lifehacker. Subscribe to the Hack Attack RSS feed to get new installments in your newsreader.

* OS X boots in a different way than, say, Windows, using a boot tool called EFI (Extensible Firmware Interface). On store-bought Macs, EFI is loaded on the hardware by default (in fact, in place of the standard BIOS most of us are used to). In order to boot OS X on our non-factory Macs, we need to create our own custom path to EFI.

Huge thanks to stellarola, Onetrack, and weaksauce12 for all their help in getting me up to speed on installing Snow Leopard on a Hackintosh PC. The Hackintosh community is large and active, and they are awesome.

Go to Source

How to Build a Hackintosh with Snow Leopard, Start to Finish [How To] originally appeared on Shai Perednik.com on September 7, 2009.

For those of you who have tested the beta or the Windows 7 RTM code, this might not come as any surprise. For those of us whose production machines still run Windows XP (Ziff-Davis and Intel, among others) the improved performance of Microsoft’s new operating system is a nice surprise.

One of those surprises was delivered Wednesday, when Microsoft paired a quad-core Intel Core i7 microprocessor with a solid-state-disc drive and what Ruston Panabaker, the principal program manager for strategic silicon partnering at Microsoft, called a generic build of Windows 7. Panabaker fired up the system, and presto! An 11-second boot time.

Sure, this was most likely a fresh build on fresh hardware, and an SSD makes all the difference in the world. But there was a little magic going on behind the scenes, as well

According to Panabaker, the boot process can be parallelized across all
four cores and all eight threads provided by Intel’s hyperthreaded
processor. “It’s an Intel reference design,” Panabaker said. “But with
high-performance hardware, this shows what system manufacturers can do.”

Part of the improved performance comes from the telemetry data that helped Microsoft boost battery life by a significant amount when running on Intel’s next-generation processors.
Other work was done by Microsoft itself, removing “thread locks” that
stalled the system. Intel also works with the Windows 7 scheduler to
migrate threads to idle cores, and then to shut those idle cores down
if there truly is no work to do.

Microsoft has been working with the software ecosystem to take
advantage of the battery-boosting, low-power API. And Intel executives,
like others in the industry, have reported that Microsoft has been
diligent about providing its partners time (about 12 months) to nail
down drivers and the like.

Panabaker did say that there will likely be a Knowledge Base article
listing incompatible hardware, as Apple’s Snow Leopard does. When that
will be released is not known, but it will likely be closer to launch,
he said. One feature that Microsoft plans to include: community
features, which will help users and Microsoft nail down what doesn’t
work, he said.

Go to Source

Windows 7 Will Boot in as Little as 11 Seconds? originally appeared on Shai Perednik.com on September 4, 2009.