agit8.org

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.

After two years of using the I-mate Jamin smartphone, I finally decided that it was time to upgrade to something with better feature set and a more open connectivity options. This time around, data was becoming more of a priority, since I don’t seem to use voice calls terribly much. I needed a phone that I could get on a contract that has a cheaper monthly payment than what I was paying before. While I was with Vodafone with the Jamin, the best I could get was $50 plan and $20 repayment for the handset. It offered GPRS EDGE connectivity with no included monthly data allowance which was charged at a rate that would give anyone a heartburn . With the least addictional cost, the best Vodafone could offer was an extra $10 on top of the already quite expensive plan to give me a mere 5MB of data per month. It definitely hurt.

Soon after i Acquired the I-mate Jamin, to make the experience even worse, I ended up buying a MacBook. The first thing I wanted to do was install Thunderbird (my favorite email client on all platform) on it and to my disappointment, I discovered that I could not do a sync between Mac and Windows Mobile without either using Parallels and Windows (and then only with that beast called Outlook) or buying some third party software. It seems that neither Apple or Microsoft wanted to know about people in my situation who did not want to subscribe to either one of the platforms (aka platform agnostic) for everything. The only thing that came close to being a solution was to use a Funambol Server installed on one of my servers, which was not only clumsy to use, but also difficult to manage. In the end I settled with using Schedule World so I could do sync between my Windows XP, Linux and OS X notebooks and my Windows Mobile 5.0 phone. This approach, while it works, is not really ideal since I have to rely on an external server to manage the synchronisation and the data.

The I-mate Jamin was a reasonably good phone, but its shortcomings were mainly caused by the Windows Mobile platform it was built on. While it works almost seamlessly in a Windows world, when you start venturing outside that walled garden the problems become unbearable. The minute you don’t want to use Outlook anymore (did I mention that an early version of Microsoft anti-virus product ate my entire Outlook database because of a single infected email?) you start seeing the ugly brick walls and quickly hitting your head against it. This gets a lot worse when you decide to try working on another platform such as Mac OS X. While there is Microsoft Office for Mac, there is no activesync for Mac. Entourage which was supposed to resemble Outlook on the Mac does not have support for syncing with Windows Mobile.

The only way you could access the files on your Windows Mobile was to use the Acitvesync software which was not a good thing when Activesync decides to play up. In the end I basically had had enough of the “closed” way in which Windows Mobile was working, so this time around I decided to look around for a phone built on a platform which supports open standards.

My first choice would have been the iphone from Apple. It is a beautifully-designed piece of technology with a very nice and intuitive interface, based on a platform which originated from a Unix world. I was quite sure about getting the iphone, until I discovered that despite its appeal, it does not really support open standards that well and I just could not understand why they would limit the bluetooth profile to headset-only. So the iphone is out.

The next on my list was the Nokia E71. Ever since my partner acquired the E65 phone from Nokia I was always a little partial to the Symbian platform, so when the Nokia E71 was released I was itching to get my hands on one to try it out. However, when I read more about the specs it soon looked like a very good candidate for my next phone. It supports 3G HSDPA, most of the common bluetooth profiles, SyncML synchronisation standard, Wifi, Assisted GPS, Flash Lite 3.0, push email  and the list goes on. It even has IRDA support.

The day I went to a Three shop in Sydney, I just wanted to check it out and hold it in my hands. The phone feels very nice to hold. Its thin and wide frame sits well in my hand and having a qwerty keyboard definitely makes things a lot easier when it comes to hammering an email or a text message. The screen looks nice and smooth and the phone is suprisingly large. It definitely amazes me what Nokia engineers manage to fit into such a thin and small device.

I liked the device so much that I decided to sign up for a plan right away. What I ended up getting was the E71 on a $29 cap plus $10 handset repayment a month on a 24-month contract. This was cheaper than getting the E71 on a $69 cap plan with no repayment. To quench my thirst for mobile data, I added $20 X-series (1GB/month) to the plan which brought the total to $59 per month including 1GB of data. This is definitely in my ball park and having 1GB of mobile data to play with means I will not hesitate to use the phone as a modem with either my Nokia N800 tablet or a notebook when needed.

After two weeks of living with the HP 2133 mini-note, I have had to change a few things to make it more livable with. I used this machine for a few days with the default Windows Vista Basic and it was quite hard to live with. First, the (lengthy) boot time and then the issue of a long wake up time (from hibernation), so it does not give me much of what I want from a small carry-everywhere notebook. Even to adjust the wireless and other settings which needs to be done quickly when you are on the go, takes a while for the window to even open up. While it may not be a problem for some, this is a problem when you need to quickly open the computer up to take notes or to look something up.

I was then wondering whether it was worth installing XP on this machine to somehow speed things up as far as boot and wake up times were concerned. I then proceeded to create a custom install disc using nlite. I thought:”why not install SP3 as well while I am at it?”, so I slipstreamed SP3 to my XP SP2 install disc and created a streamlined and slipstreamed install disc with SP3 built in. The wonderful thing about nlite is that it also allows you to incorporate drivers for your computer into your installation disc, so I incorporated all the XP drivers from the HP site. Everything was going really well until I actually installed it on the notebook.

After installation, the notebook booted fine and I must say it was noticeably quicker and wake up time was what I expected. There was, however, a problem between explorer and the graphics driver. On wake up from hibernation, the screen would flicker uncontrollably for about a minute or two. Sometimes this craziness will stop when I open a window, but not always. This cancels out the advantages of the quicker boot time with XP.I would have to wait a couple of minutes before the machine would settle and be usable again. I was glad to discover that Via had put out a new driver for its Chrome 9 integrated graphics chip. Alas, after installation of the latest driver, the machine still had the uncontrollable case of the flicker.

Working with a notebook that flickers after hibernation is almost impossible. In fact, it makes this notebook pretty useless since I bought it to be able to take notes and work pretty quickly during my day at work and during times I spend on public transport. I had to come up with a solution, so I gave XP SP2 a try and it seems to have made it a better notebook. I can put it into hibernation at anytime without any concern for what will happen when I start it up again. So, if you are having trouble with XP SP3 on your HP mini-note 2133, do not hesitate and install XP SP2 on it and you will have a nice and usable notebook.

I wish there was a netbook like the mini-note that has an instant-on feature to allow working in shorter stretches of time with a lot of sleep in between. Such a notebook, couple with a decent battery life will make a nice companion to people who need a lightweight machine to either write or code while on the move. Did you hear that HP?

I recently acquired the HP mini-note 2133 netbook and I have been using it almost constantly for the last few days. It is a very nice little machine to use on a day to day basis, although in terms of raw power and speed it is no match for my Dell Inspiron and my MacBook. A lot of people seem to forget the fact that this machine was built to a price to occupy the same market segment as the Asus Eeepc. In my view, this machine is superior to the Eeepc in many ways and it is working very well in what it was designed to do: lightweight ultra-mobile computing.

For a while I was really comparing this machine to the Eeepc and the clincher for me was the storage capacity (120GB) as opposed to the various flavours of Eeepc which come in anything from 4-20GB, which means that this machine could also function as a mobile storage unit for photographs and other files when on the go. The other factor was the size of the keyboard. While it may be difficult to type quickly and accurately on the Eeepc’s cramped keyboard, it is, by comparison, quite effortless on this machine, which means that for typing documents and code the HP wins hands down.

The few gripes that I have with this machine are: no booting from the SD card slot, Windows Vista pre-installed (only the vista version is available here in Australia), it only comes with a 3-cell battery and (because of Vista) a long boot time and wake up time (from hibernation).
The specs:

• 1.6Ghz Via C7 processor
• Via Chrome graphics adapter
• 1GB of RAM
• 120GB HDD
• a/b/g Wifi
• Bluetooth
• VGA Webcam
• SD card slot
• 3-cell battery (expandable to 6)
• Express Card 54 slot
• 1280×768 8.9 inch screen

Pros:

• Relatively light, therefore easy to carry
• Large 8.9 inch screen
• Nice 92% size keyboard
• Spacious storage

Cons:

• Battery could be larger
• Awkward power switch
• Only comes with Windows Vista Home Basic
• Webcam utility (modelled on Apple Photo Booth) does not work properly

All in all, this notebook makes a great companion when you are out and about and not wanting to carry a 3kg+ load on your shoulders.

Recently while I was on the run I needed to find a location on a map and of course I immediately fired up my trusty new netbook and launched Firefox. Lo and behold, I could not get Google Maps to display whatsoever. I tried refreshing the page, I tried relaunching it and finally I had to fire up Internet Explorer to access the map. Since I usually avoid using Internet Explorer at all costs, this was really an exception.

I thought it might have something to do with my connection setup, but after a little bit of digging and retracing of my actions, I remembered that I had just updated Skype and I noticed that it installed an add-on onto Firefox. After I disabled this add-on from Skype, Google maps loaded effortlessly. Since I do not know what this add-on does and why it is there in the first place, I am probably not going to miss it.

So if your google maps not loading in Firefox 3.0, do not hesitate and disable that plug in to get your maps back. Someone at Skype needs to check this.

Recently while I was upgrading a hard drive on one of my servers, I found a webcam that I purchased around 18 months ago. It was one of those cheap webcams that I bought,installed for a test then I just promptly forgot about. Somehow I must have stored it on the top of the server case (under a desk) and then I somehow must have pushed it to the back of the case and guess what happened next? It fell off to the back of the server.

Not remembering what I had done with the camera box and the driver disc, I tried to search for a driver online. Since there was hardly any marking on the camera itself, except the word “kinstone” on the front of the clip that forms the base of the camera. Well, lo and behold, I found a website called kinstone.net. I quickly found the download section and before I knew it I had downloaded a driver to my desktop.

After decompressing the file, I found a folder called kinstone_xxx_xxx on my desktop. I opened the folder and found a sub folder called “setup”. After I double-clicked the installer file (setup.exe) it installed all the files and created shortcuts. However, using this method, the camera was not recognised and therefore was not working. I attempted to install the driver through the “found new hardware” wizard and it was still no go.

When I tried to find the instaleld files in “Program Files” directory I found a folder called “vimicro” which the installer had created. So when multiple attempts to get windows to install the driver for the camera failed, I put vimicro into Google and then voila! I found out that vimicro was a company that made the chipset for the kinstone webcams. So I downloaded a driver from their website and there was even a tool which will tell you which driver to download (can identify the chipset of the camera). The driver downloaded from vimicro works flawlessly.

So if you have a Kinstone USB webcam it might be best to head straight to the vimicro website.

With rumours circulating in the last couple of months of Apple’s plans to open new stores in Sydney, I wonder if this will mean a vastly improved customer experience at the store level. If it is, then it will be the one-stop shop for all my Apple needs (everyone has an Apple need, right?).

Read the rest of this entry »

Read part 1 of this article

Right after I had had enough of Knoppix in a PMI (poor man’s install) configuration, I decided to look for something better. While Knoppix was a great beginning and an eye-opener to what could be achieved in a well-configured Linux laptop, it was not enough. It did not allow for software install (well, without a lot of difficulties anyway) and everything I worked on had to be saved onto an external USB drive.

Read the rest of this entry »

Having three notebook computers has its own problems. My main notebook at the moment is the Macbook that I purchased nearly 11 months ago. It has been a solid companion of mine in doing teaching work and general everyday computing. Then I have my old Dell Inspiron 8600 which functions similarly to an everyday desktop computer. It is also the machine on which I play games such as Colin McRae and Medal of Honor (not the latest ones, of course).

Read the rest of this entry »

The other day I was working on my file server after a couple of hard drives failed within almost an hour of each other. Bizzare and unfortunate as it may sound, I was not in so much of a panic as I had the two drives mirrored onto another large, hard drive daily using Delta Copy. While potentially I could have lost nearly 200GB of data on the two drives, the fact that they were mirrored meant that I only lost around 10GB of files that were mainly DVD rips (will have to rip them again).

To cut a long story short, I was waiting for Windows to install on my server when I noticed that the response time for my web server seemed to have increased considerably. While it is not the fastest web server around, it has been doing its job well for nearly five years with a few reboots in between. Usually it responds to web requests quite speedily, but for some reason it was taking its time. For a very brief period I felt a little panicked about the possibility of the server’s main hard drive failing, but after seeing half of my website load I figured something else was up.

I looked at the netstat and it showed there were quite a few connections open and on reading the server’s log file life (via tail -f) I realised that not only I had Googlebot crawling my site, I also had Slurp from Yahoo and another bot from Webalta in a Russian domain all crawling all over my web server at the same time. This kinda crawling gave my web server the creeps.

Can’t these bots at least have a roster about who was going to crawl which site at any given time? What is the point of being indexed by the search engines if no one can reach your site without patiently waiting for nearly a minute?