In the interest of being green, I have been looking at the idea of building a lightweight machine with a reasonably low power consumption to do simple tasks computing tasks, like updating a blog, writing documents and simple editing of multimedia projects and occasionally running software for art exhibitions. When I first looked around the market, the obvious choice was a computer built around Intel’s Atom processor. It has all the right lows, such as low price and low wattage, but unfortunately it also has a low in performance as well. There are also solutions available from vendors such as VIA, but having owned an HP 2133 that was built around the Via Nanobook platform, I am not convinced that it will be one that can easily run multiple operating systems without a major effort to find drivers, etc.

For the sake of simplicity, I decided to just build around a motherboard from Foxconn with an Intel Atom processor 330 (dual core) built-in, or rather soldered onto the board. The model number for the board is 45CSX and it has 1 slot for DDR2 RAM with a 2GB ceiling. To house the board I also bought a Foxconn RS-338 case which comes with a 150W PSU and enough space for a 3.5″ HDD and a DVDRW drive. Since RAM is so cheap these days, I bought the maximum 2GB size for $40. All up, the rig cost a little under $300 and I decided to mate it to a 24″ widescreen 1920×1080  LCD from ViewSonic.

After installing Windows XP SP3 (yes, I know I should have installed Linux, but I wanted to test the performance of the CS3 suite on this rig), I installed the Adobe CS3 suite to test the machine and see how it performs. Upon running Photoshop CS3 and even together with AfterEffects CS3, I came to the conclusion that this machine is not as bad as it’s been cracked up to be. Photoshop launch seems to be quite snappy and AfterEffects seems to run just fine (takes just as long to launch on my MacBook).

Everything seems to work fine and yes, there was a performance difference compared to my MacBook with a C2D 2.16Ghz processor, but for something that costs a little over a quarter the price I think it is a quite acceptable trade off. So unless you work with Photoshop and AfterEffects in a heavy-duty production, I can recommend this setup as a secondary machine.

In case you are interested, I tested Photoshop on this machine with a file that has 134 layers, each with a mask of its own. AfterEffects was tested with a six layer 1:30:00 length animation.

330 · Atom · computing · dual core · Linux · MacBook · windows · xp

I have been somewhat troubled by the inability of my MacBook running 10.4.11 version of OS X to hibernate properly (suspend to disk). It all started when I upgraded the RAM from the standard 1GB to the 4GB it is now. After the upgrade, it could not reliably wake up from hibernation without a crash occuring after using some memory-intensive programs such as some Adobe software and Aptana and such, which would require a forced reboot. Having lived with this issue for sometime (started shutting down instead of hibernating), I decided to try to Google some answers.

After trawling through some forums and blog discussions, I found a Dashboard widget called Deep Sleep which is easy to use (one click) and seems to reliably put the notebook to sleep without wake up crashes (that’s what happens to me when waking up early morning). So if your macbook is a little insomniac like mine, then do give it a try.

apple · hibernate · hibernation · MacBook · notebook · OS X · suspend · tiger

For about 3 months I have been having a problem with my Macbook running OS X Tiger with 3GB of RAM. The problem seems to only occur when I run a resource intensive application such as Photoshop, Illustrator, Premiere, Final Cut or even Garage Band. What happens is normally when I close those applications then put the notebook to sleep (safe sleep aka hibernation), when I wake it up it goes through the process slowly (slower than normal wake up from hibernation) then it crashes. Because I very rarely shut the notebook down, this seems to happen at least two or three times a day.

Annoying? Well what do you think? The waking up process, which is supposed to be quicker than starting it cold, takes a lot longer and then you have to force the notebook to reboot. This is unacceptably inefficient and not to mention scary. I keep thinking that there is something wrong with the hardware, but it does not get worse, it just seems to happen with any resource-intensive application.

The solution is apparently very simple: just open terminal and type sudo rm /var/vm/sleepimage, then enter your password and then if there is no error, you have just deleted the sleepimage file, which is where the content of your RAM gets dumped when the computer goes to sleep. When done, just reboot the machine and all should be fine. I even tried running Photoshop and then putting the Macbook to sleep and it wakes up fine.

So if your MacBook has a crash on wake up (that’s what happens to me in the mornings), then just delete that sleepimage file in /var/rm and it should be recreated afterwards and everything should be fine. It is particularly wise to do this after upgrading your RAM. I upgraded mine from 1GB to 3GB and did not know that I had to do this.

apple · crash · hardware · hibernate · hibernation · MacBook · OS X · safe sleep · sleep · upgrade