PHILHARVE  I have discovered a workaround to the problem I reported below.

In order to get iBatt 2.0 to work correctly on a MacBook Pro (say) you must ensure the Graph option must be disabled before exiting the application. After launching iBatt 2.0 the Graph option may be reselected.

I think this workaround demonstrates that there is a minor bug in iBatt 2.0. It is a pity that the developer no longer supports this product because it is an excellent battery monitor.  
(Version 2.0)

PHILHARVE  Hi - I seemed to have stumbled upon a solution to the problem I was having with iBatt 2.0. See previous postings.

To ensure iBatt 2.0 launches properly, switch off the Graph option before exiting. If the Graph option is active when iBatt 2.0 is exited, iBatt 2.0 will probably not launch and run correctly the next time. Correct operation becomes a hit & miss affair; usually misses. I previously reported this behaviour as a program bug and I still believe this is the case. However, the workaround is simple enough.

I have tested my solution dozens of times on my 17-inch MacBook Pro and each time iBatt 2.0 has launched and run correctly. Once running the Graph option may be selected and it will display historical charge/discharge curves OK. REGARDS Phil  
(Version 2.0)

PHILHARVE  I have discovered that iBatt 2.0 works properly if it is the only other battery monitor application, apart from Apple's own offering, installed on my Macbook Pro. I have tried using SlimBatteryMonitor, Battery Health Monitor and cocoanutBattery in different combinations with iBatt 2.0 and almost every time something goes wrong with iBatt 2.0. I therefore recommend that if iBatt 2.0 is adopted as THE battery monitoring tool of choice, no other 3rd party battery monitoring tool be installed because they appear to interfere with iBatt 2.0's operation. Curiously, their own operations appears to be unaffected if installed alongside iBatt 2.0.  
(Version 2.0)

PHILHARVE  PHILHARVE - Further to my last comment, I have noticed that when iBatt provides 'Battery Status' and 'Extra Info' information, it does not provide a 'Health Report' because iBatt cannot determine what type of computer it is installed on. Presumably this prevents iBatt accessing the battery server and retrieving comparative performance data. This must surely be a bug.  
(Version 2.0)

PHILHARVE  I have iBatt 2.0 installed on a 17-inch MacBook Pro (MBP)and it is everything the developer says. It is a vast improvement over 1.x. However, on my MBP the 'Battery Status' and 'Extra Info' does not always populate with information when IBatt is launched. This is an annoyance because these fields convey important information. I have reported the 'apparent' bug to the developer who has yet to reply. If iBatt 2.0 can be made more reliable it will be an excellent tool for monitoring battery life and performance.  
(Version 2.0)

PHILHARVE  I have used CCC for several years in preference to other commercially available and, perhaps, better known backup programs. Each version just gets better and better.

The latest version (3.1.2) is a big improvement. Previously CCC would would create a fresh backup each time it was asked to 'clone' my hard drive. The latest version is different. It normally takes about 2 hours to clone almost 80Gb but on the latest occasion it took barely 20 minutes. It seems that CCC can clone faster if an existing clone/backup already exists. I call this 'incremental cloning' because it is not unlike an incremental backup.

I like CCC because it produces a bootable copy of the source disk and this has proven invaluable when my internal hard drive is in need of routine maintenance. I boot from the clone and use the disk maintenance utilities on it to repair my internal hard drive. No fuss, no bother.  
(Version 3.1.2)