Archive for the ‘XP’ Category

Yes, I bit the bullet and did for YOU FOLKS.

I kept on checking last night and this morning … following yesterday’s report that someone using Windows 7 got clobbered once they installed the February 9 updates. But since then I could only find one other report of a problem. Though I am sure that MANY Windows 7 users have judiciously refrained from installing these updates, if there were innate problems related to Windows 7 we would have heard by now.

The Web is ablaze with reports that XP users really got clobbered with these updates. Microsoft even WITHDREW one of the XP updates! Nice move Microsoft. Real smooth. So they confirmed what I have always thought of them. No testing. Just throw the software over the wall. Joys of having no competition and having so much lobbying in D.C. that they know that the Feds will never look at them. Keep on saying to yourself, like a mantra, ‘Ballmer looks best in drag.’

OK. So far so good. That is not saying much.

I have a legit copy of 64-bit Windows 7 Professional installed from an OEM DVD that I got from newegg.com … on the day Windows 7 became available (Oct. 22, 2009). I had pre-ordered a few days earlier along with all the hardware to build a new system.

The updates require a restart. During the restart a screen comes up saying ‘Configuring the Updates.’ I was on tenterhooks. But, it said … ‘successful’ … and then restarted.

Since, being paranoid, I restarted again. SO FAR, SO GOOD.

It is up to YOU. YOU might want to hold out longer. I had to see if the updates would work with Windows 7. But, this was but one system. Doesn’t prove anything. So, if you are cool, MAYBE you should wait. All I can say is that it worked on this particular system.

Right now I have a few days ‘down time’ for the first time in 15 months. I finished my book, 322 pages, 150,000 words and send the PDFs to the printer Wednesday night. Had an email last night to say the proof copy is with FedEx. So, I would not have been totally out of my mind if this Windows 7 system got fried. I have two, maybe three, possibly four XP systems as backup … with all my files, backed up, up to date on them … as well as online (with GoDaddy). Did I tell you I am paranoid. So, I could have got by using XP until I got the Windows 7 system fixed.

IF you are interested here is a PREVIEW of the book. It is 11MB,so will take a few minutes to download.

No More Updates For ME Till April Fool’s

I have now TURNED OFF Windows Updates!

That is IT.

I do not want to be pestered with the February 16, 2010 WAT update for checking the validity of my Windows 7 copy. My copy is 100% legit, but I am not sure that Microsoft’s update will be legit. I just have a feeling that we might get another outcry.

I am fed up of the icons rotating on my Task Bar telling me I have updates. Leave me BE. I will check the Web to see what mayhem Microsoft is unleashing on us.

It now transpires that Microsoft ‘just’ discovered a major SSL/TLS bug on all versions of Windows. GREAT. SSL/TLS is what we all use when we ask for an encrypted session. So, Microsoft is now telling us that our encrypted sessions might be vulnerable.

‘Ballmer looks best in drag.’

On March 1 all the Release Candidate (RC) copies of Windows 7 will go into forced shutdowns. Many of the pirated copies of Windows 7 out there are based on RC code. Post March 1 we will have convulsions as the Windows 7 community gets bombarded with folks who will not understand why their systems are not working.

So it was time to batten down the hatches. I will of course keep you posted.

So, this was my strategy. Install the February 9 updates. Then turn off updates until at least April 1 and see what happens.

All the best. Good Luck.

Anura Guruge

Read Full Post »

I got this for YOU from the ‘Microsoft Answers’ forum. Go there by all means to get all the dirt, and in this case we really are talking about DIRT. Unmitigated dirt.

So here are the steps. THIS IS NOT FUNNY. May Steve Jobs help you IF you do not have a Windows XP install disk.

1. Boot from your Windows XP CD or DVD and start the recovery console (see this Microsoft article for help with this step)

Once you are in the Repair Screen ..

2. Type this command: CHDIR $NtUninstall
<< NO space before that second ‘$’ prefixing \spuninst. >>

3. Type this command: BATCH spuninst.txt

4. Type this command: systemroot

5. Repeat steps 2 – 4 for each of the following updates provided by FindMeFollowMe:

  • KB978262
  • KB971468
  • KB978037
  • KB975713
  • KB978251
  • KB978706
  • KB977165
  • KB975560
  • KB977914

6. When complete, type this command: exit

Your computer should restart and everything should be back to normal.

Keep your toes crossed and keep on chanting: “damn you Microsoft, damn you Microsoft, Balmer looks best in drag.”

Good Luck.


Anura Guruge

Read Full Post »

Just saw the first real damaging post re. KB978262 as it pertains to Windows 7.

Please read this on the ‘Microsoft Answers’ forum. Damn YOU Microsoft.

This is the first report of this February 9 update clobbering Windows 7. But, it is enough.

DO NOT INSTALL these updates. Wait.

The XP community is getting hammered and they are not amused. The same Microsoft community is beside itself … but there is even a comment from a MVP talking about ‘dead bodies.’ CUTE. This is what we need. Microsoft MVPs talking about dead bodies when it comes to Windows Updates.

Some are claiming that this is a  Microsoft conspiracy to get XP users to upgrade to Windows 7. I doubt that. Microsoft isn’t that clever. Trust me, on this.

So, my recommendation for Windows 7 users: DO NOT INSTALL KB978262, KB971468, KB975560, KB978251 and KB890830 as yet, though from all we can see it is KB978262, the ActiveX kill bits update that is the culprit.

Better to be SAFE than sorry.

Good Luck. We really need it.

Thanks & Cheers.

Anura Guruge

Read Full Post »

I feel GOOD that I urged you all to hold off on the February 9 Security Updates.

The FIRESTORM has started today — albeit mainly on XP systems. Here is a good article on the problem, published today, by ComputerWorld.

This is not funny, especially coming just three weeks after the great KB977074 fiasco. I have said it once, I will say it again. Congress needs to look into Microsoft.

Here is the link to Microsoft’s forum JUST on problems with this update.

Again, most people are reporting problems on XP … and PLEASE note that Microsoft currently doesn’t have a workaround for this … other than booting off the original XP install disk.

Not good.

HOLD OFF. Though we are not hearing much on the Windows 7 front, if it clobbers XP this badly … it could blow us out of the water TOO.

I will keep you posted.

Good luck. We need it.


Anura Guruge

Read Full Post »

A reader of this blog just sent me an email giving me a ‘heads-up’ of this free offer.


ALL I am doing right now is passing it onto you. I think I tried to use this earlier this year and was foiled because I didn’t have a license.

They CLAIM that you will now get FREE product code, with no time limitations.

Again, I am NOT endorsing this product. I haven’t even tried it. But, IF you need PDF-to-Word, which always worth having around, YOU might as well grab this.

But, as ever, proceed with caution. There could be a catch.

Good luck. Share your feedback.

I THANK my reader for this ‘heads up.’ That was kind and thoughtful.


Anura Guruge

Read Full Post »

On Saturday night I ran Auslogics Registry Cleaner again. It had been 4 days since I had last run it. Since it is the ONLY registry tool that I now have on my Windows 7 machine the Registry had not been cleaned since I last ran Auslogics.

I ran the Registry Cleaner in ‘Advanced Scan’ [i.e., scan everything] mode. Didn’t take long. Said I had 10 errors. That surprised me, but in a good way. When I had System Mechanic 9.5 I used to run it most nights before I would Shut Down the PC. Invariably, with monotonous predictability, I would always be told that I had between 12 and 22 registry errors that needed to be fixed. Most nights I would tell SM to fix it. Then the next night I would have much the same amount again.

I checked the list of 10 errors found by Auslogics. Six related to Word documents that I had renamed (reflecting their new status within the proofing cycle). So that made sense. So 60% of the errors were beyond kosher. The other 4 looked reasonably legit too.

That the Auslogics Registry Cleaner found less errors after a 4 day hiatus than SM used to find in a night … leaves me in the proverbial no man’s land. Who is right? Which is better? But, at least Auslogics as yet to hang. So that is a definite plus. It is possible that it is not as thorough as SM. I hope it is, but right now I don’t have the time to determine if Auslogics skips records that SM would analyze and report. Time will tell.

Auslogics Disk Defrag

I then downloaded and ran the Auslogics Disk Defrag. I had used it on XP so I knew what to expect.

I did an analyze. It came back and said that I DID NOT need to defrag my C-drive. That was good.

Unlike its Registry Defrag which does NOT have an option for insisting on a defrag … the Disk Defrag does, Praise be to Shane (though Mulli’s KING), have that option.

I adjusted the settings so that it did not try to defrag 10MB or larger segments. I also asked it to DEFRAG & OPTIMIZE [i.e., move my System Files towards the ‘front’ of the disk].

My C-drive is a ‘nominal’ 750GB … with 42GB currently used. I think it found close to 12,000 files — 90 of which needed to be defraged.

I watched it for a few minutes. Then I went to have breakfast and watch a recorded rerun of “All Creatures Great and Small.”

When I came back it was done. It had taken 46 minutes and 14 seconds. That is probably not bad.

They give you fairly impressive report. I had a quick glance at it. That too looked Kosher.

So far, so good. No hangs. My system works. It hasn’t made any difference to my performance but my performance is OK … given that this is a i7-920 with 12GB of DDR3 memory.

The Not So Good

I found to my cost and chagrin that the Auslogics Registry Defrag will install itself on ‘top’ of an existing version without any warning message or an attempt to uninstall the installed version.

Though this was MY FAULT, I was not amused.

I did the Disk Defrag download past midnight. All my downloads go to my ‘DOWNLOADS’ folder. I had been indexing my book for over 2 hours. Trust me, there is nothing guaranteed to screw-up your eyesight like heads-down, indexing.

I had 4 install execs in my folder. I clicked the wrong one. Instead of activating the new Disk Defrag .exe, I without realizing (of course) clicked on the Registry Defrag.

The installation went through WITHOUT any mention that I already had a PERFECTLY good copy of Registry Defrag installed on my machine.

That was NOT GOOD. Not amused.

So, so far, I have found three things that I do not like when it comes to Auslogics:

  1. Registry Defrag install exec NOT checking for a prior install. Bad, bad, bad.
  2. Registry Defrg not having a ‘do a defrag any way’ option (for Power Users who know what they are doing). This is an annoyance.
  3. Auslogics BootSpeed finding errors on your machine BUT then saying it won’t fix them until you buy a license. That is bad. That is duplicitous since it doesn’t warn you of this before you fire it up. It is childish. It is NOT CRICKET. It is Greg Chappell bowling underarm. It is Rod Marsh betting against his own team. It is Kim Hughes crying like a 4 year old on TV.

Anura Guruge

Read Full Post »

I was updating FireFox on one of XP boxes when I saw that we had rc2.

Jumped on the Windows 7 box to see if I could update. FireFox had already downloaded rc2 and was waiting for a restart of FF. Pretty neat. Just restarted FF. It came up, with the tabs intact. So I am posting this using FireFox 3.6 rc2.

So far, so good. So maybe the hangs I experienced with rc1 are now history. But, I will keep my toes crossed. The release notes do say that rc2 addresses stability issues. So this all good.

One small thing. ‘About Mozilla FireFox’ on the HELP menu doesn’t tell you the ‘rc’ version. Just says 3.6. Might be nice to be reminded of what ‘rc’ one is at.

I haven’t tried Google Chrome on this my Windows 7 rig.

But over the last 48 hours we installed Chrome on 3 of our XP boxes. My daughter, nine, who longer has a TV in her room (because she watched it incessantly) now thinks her PC is a TV. She watches a lot of ‘disney’ ilk stuff on the Web. She likes Chrome. She told me last night, that in terms of performance it is Chrome, FireFox (3.6rc1) and IE 8. That is pretty good. She does not like IE and I have not brain washed her — that not being my style. My logo, as you can see on my Web site, is “Think Free, Or Die”. So she makes up her own mind.

My wife ditched Chrome within minutes! Even uninstalled it from her XP laptop. What can I say.

I used Chrome today. I was putting up pictures of our airport on ice. You hadn’t heard about it. The Alton, NH Air Port on Ice. Frozen lake. We spent a couple of hours there yesterday. Warm. In the 40s. About 35 planes. Saw dozens of take offs and landings. No mishaps, so far. Most years we have small, non-serious ‘fender benders.’ There was even a helicopter.

Try FireFox 3.6 rc2. What do you have to lose? << smile >>

Good luck. Cheers.


P.S. We had 102 hits on this blog yesterday. Not bad for a Sunday.

Read Full Post »

Continuation of my evaluation of TuneUp Utilities 2010 versus System Mechanic 9.5.5 that I started on Jan. 15. If you want to read the whole evaluation saga, blow-by-blow, twist-by-twist here is the Jan. 15 first post and the Jan. 16 second post.

On Friday night I ran TuneUp Utilties’ 1-click maintenance three times in a row until it told me that there were NO PROBLEMS on my PC. I had also done a registry compact using TuneUp Utilities and had the C-disk checked, thoroughly, by Windows.

To keep this as pithy as possible, I will try it in bullet form, each bullet dealing, chronologically, with the sequence of events:

  • Just to make sure that TuneUp Utilities was ‘A-OK’ with the PC I ran it again. Now, I had shut-down that PC after I had previously run TuneUp Utilities. So all I had done in between the two invocations of TuneUp Utilities was to shut-down and then power-up this PC. TuneUp Utilities said it found 4 broken shortcuts! Strange. It had fixed 2x the first time around the day before. Where did these 4 come from? Checked? All to do with Office applications. Strange. Hadn’t run Office on that machine in a week. So where did these come from. Does TuneUp Utilities do an incremental search; i.e., not a full scan each time? I know System Mechanic has a deep-scan for broken shortcuts. Well, I was not amused or too impressed. So here was I running TuneUp Utilities 2010 for the 4th time and it is now finding new problems … WHEN I haven’t done anything else on this machine. Hhhhmmmmm.

  • I fired up System Mechanic 9.5.5. [I had to update. This PC which had not been powered up for a ‘week’ was at 9.5.3. Install was clean and trouble free.] It found 8 problems; 176 registry errors. Sacré Bloody bleu! 176 registry errors. TuneUp Utilities 2010, first time around, said it found and fixed 265 registry errors. That was 3 invocations ago. The last two times TuneUp Utilities 2010 said I had NO registry errors. Now System Mechanic is saying I have 176 registry errors. << John 11:35 from the Bible. >> I checked. Looked like the usual litany of registry errors that System Mechanic picks up. Yes, I was expecting this. Yes, I had heard of this. But, who is right?

  • The Windows Registry isn’t ‘American Idol.’ There can’t be shades of gray. We either have invalid entries or not. I don’t think it can be subjective. If you have a registry entry that is pointing at something that no longer exists … that is an error.
    This is not right. Wish I was MORE motivated with this stuff. Way back, in the 1970s, before PCs came to be and before I became “Mr. SNA,” I was, for a couple of years, a VTOC guru — IBM disk Volume Table of Contents (VTOC). I would read VTOCs, in hex, like others read the Old Testament. So yes, I could, if I was interested dive in and start reading the damn Registry and see who is pulling my middle leg … is it TuneUp Utilitites 2010 or System Mechanic 9.5.5. I don’t think, and I could be wrong, that they can BOTH be right. But, I am not really motivated. This coming week I have to do some serious work on a Network Monitor for a client. That will be enough technology to keep me going.

  • I don’t know. But I do know that in the seven years (or more) that I have used System Mechanic … it has never screwed me. Yes, with Windows 7 it hung; it hung more than once. But, it never screwed anything up. In contrast, Avast, with its ‘false positive,‘ on December 3, 2009, did screw me (and I have had prior ‘false positives’ with them though none were as debilitating as the last). Adobe Acrobat has taken years off my life. Thanks to Microsoft I am dependent on red wine. But, System Mechanic. Ah! As far as I KNOW, and I could be wrong, it has done me or my PCs no (major) harm. As with my gas permeable contact lenses, ‘experts’ who get to see my PCs invariably comment as to how well they appear to be looked after. Yes, I nurse all my PCs. And System Mechanic has been my primary tool in doing that for 6-7 years. So I can’t just stop believing System Mechanic. So I am in a quandary.

  • The glutton for punishment that I am, I then ran TuneUp Utilities 2010 again. Four (4) registry errors. That didn’t seem too bad. I checked. All four entries started with ‘SM’ — System Mechanic. I can buy that. SM creates some duff entries. Yep, I can buy that. But, just 4. But, we are neither here nor there. Did System Mechanic find and fix 176 errors? Or, is it that TuneUp Utilities doesn’t check for the same types of registry errors.

Bottom line, I am still not sure about TuneUp Utilities 2010. For the time being, System Mechanic 9.5.5 will prevail per the age old adage, the ‘Devil You Know.’ Maybe the person who asked me to review TuneUp Utilities 2010 (and she is probably regretting this request already) may help me get to the bottom of this. But, for now lets us just say that I am very confused. Not amused. If any of you reading this can shed some light … PLEASE do. I need all the help I can.

Good luck. Cheers.

Anura Guruge

Read Full Post »

Having first tried it out on my daughter’s XP SP3 system yesterday evening, I installed TuneUp Utilities 2010 on my latest XP SP3 box a few hours later.

Installation again was hassle free and slick. I like their install. It is bright, breezy and keeps you engaged. That is a PLUS in the TuneUp Utilities 2010 column. Well done.

Ran 1-click maintenance. Told me I had 265 registry errors and 2 unnecessary start-up items. It fixed my 265 registry errors. But, insisted that the registry did not need compacting. I do not agree with that. 265 fixes is a fair amount. I want my registry compacted after that.

I ran 1-click maintenance again. So all I had done was run 1-click maintenance, fix the reported errors … which told me that it fixed 265 registry errors (and two start up items) … and then run 1-click maintenance AGAIN.

Told me I had 46 registry errors!

  1. I had heard that this happens with TuneUp Utilities 2010. < See yesterday’s post about the stories I had heard before I ever got around to testing this product. >
  2. I have seen this happen with System Mechanic too, though a 17% resurgence is high. Not good. Not happy. It said it fixed all. I couldn’t have got 46 new registry errors that soon. I hadn’t run anything other than TuneUp Utilities 2010. So this has to be checked.

It still said I did not need my registry compacted. Poppycock. By now, I needed a registry compact. Could NOT get it to compact the registry. I was getting kind of frustrated.

The Tools Are There, But They Are Artfully Hidden

I just could not find a way to do a registry compact (or defrag as some call it).

Then lo and behold I found it. << smile >> You have to get to it from the START button. There are TWO (2) TuneUp Utilities entries in the START button ‘Program’ menu. One is a folder. Click on that. You get another folder called ‘All Functions’. BINGO. All the tools are there.

Lucky I found that. I was actually looking to see if they had provided an UNINSTALL ‘link.’ They hadn’t. Naughty, but neither does System Mechanic. I guess that is a part of their customer retention strategy. make it as difficult to uninstall as possible. They might not like us, BUT they also can’t get us off their PCs.

Anyway … that was bittersweet. I find the tools, when I go looking for UNINSTALL.

I did a registry compact (or ‘defrag’) as they call it. Similar to System Mechanic. Needed a restart. Not the same, but similar narrative as to what was happening during the compact. The TuneUp Utilities messages are slightly more user friendly than the more technical ones generated by SM.

Told me my registry was 7% fragmented. So why the hell did I have to jump through hoops to have it compacted. This aspect needs to be fixed.

Complete Disk Drive Check Done By Windows CHKDSK à la System Mechanic

On this system I asked it to do a full disk check. It scheduled Windows to do it, using the standard ‘DOS’ CHKDSK. This is exactly the same as what System Mechanic does.

So on that score TuneUp Utilities 2010 and System Mechanic 9.5 are on a par.

But by now I had seen a theme. TuneUp Utilities 2010 is an intentionally ‘dumbed down’ product. System Mechanic has seen the light.

TuneUp Utilities 2010 Must Cater For Power Users

I could be wrong, but I get the impression that TuneUp Utilities 2010 is focused entirely at the PC amateur market — i.e., PC users that get disk capacity and memory confused and have never heard of a registry outside of where they go for their shotgun weddings.

Nothing wrong with this. Probably 90% of Windows users fall into this. My 81 year old father falls into that as does my 9 year old daughter. They just want a tool that will do everything automatically to fix their PC and make it faster.

I have nothing against that provided that it does not violate the Hippocratic Oath for PC tools. FIRST, DO NO HARM.

Right now, I am not sure about TuneUp Utilities 2010. My PCs still work but not sure what they did. Oh, their logs need to be more detailed.

But for now, there is only one BIG thing I want. Make it easier to find and invoke the individual tools à la System Mechanic. Put it as an option under MAINTENANCE.

So that is it for now. I will do more testing. Right now I am ambivalent. Not sure whether it is good, bad or indifferent.

Next major test. I will get it to a point where it says NO registry errors. Then I will stick System Mechanic 9.5.5. If SM says it found registry errors …

Good luck. Thanks. Cheers.

Anura Guruge

Read Full Post »

I am trying to find out.

I have never really used TuneUp Utilities though I kept on hearing about it in the last few months vis-à-vis tools for tuning up PCs running Windows 7. Yesterday I got an email from the TuneUp Utilities folks (actually their PR firm) asking whether I would check out TuneUp Utilities 2007. With six PCs running Windows in the house it wasn’t a bad idea to check out a new tool, especially since the System Mechanic license on my daughter’s XP system is ready to expire next month.

Now, remember I do not use System Mechanic Pro. I only use System Mechanic; i.e., I do not rely on System Mechanic for anti-virus or spyware protection. I use Avast! 4.8 Professional on my systems (despite the hiccups), while the other PCs have various flavors of AVG. [My wife prefers AVG to Avast. What can I say?] So in my case TuneUp Utilities could be a viable alternative — given that TuneUp Utilities, true to its name, only does system tune-up functions and stays away from the anti-virus stuff.

I downloaded and tried it a few minutes ago on my 9 year old daughters XP SP3 system. That system is old and needs all the help it can. So in a way it was a good system to start on. [There was NO WAY I was trying it on this my production Windows 7 machine until I had a good handle on it … running on a couple of ‘non-critical’ machines.]

The install was quick and painless. I am still not used to it. I tried the new Turbo option. Clicked around a bit before I found the 1-click optimization. Tried it. Told me that it found and fixed 430 registry errors. Hhhmmm. Hhhmmmm! I have System Mechanic on that PC and I had cleaned it out, myself, just two weeks ago. Find it hard to believe that there could have been 430 new registry errors in two weeks … on a system that is not that heavily used … and used mainly for Web browsing. I will have to see. Yes, I have heard folks tell me that TuneUp Utilities finds registry errors ‘missed’ by System Mechanic.

The Two-Step Tango Of The Tune-Ups, One Step Forward, One Step Back and Shake Your Head In Wonder

You can already see it coming. Yes, I fired up System Mechanic … which was now at 9.5.5. 65 registry errors for a start.

I knew that that was coming. I had heard stories about System Mechanic and TuneUp Utilities never being able to agree when a registry was fixed. People tell me a lot of stories like this.

I decided to start with a level playing field. I restarted … since a lot had happened.

Then, this is what we did:

  1. I ran TuneUp Utilities. It said 16 registry errors. OK. I see that with System Mechanic. Windows itself creates invalid entries. So I was cool. I looked at the supposed errors. TuneUp Utilities, as far as I can work out at present, doesn’t show me the complete string as does SM. So, I was a bit at sea. With SM I kind of know the ‘strings’ and what to expect.

  2. Did 1-click Maintenance using TuneUp Utilities and told it to fix everything. Fixed the registry. Said it wanted to check the C-drive. Said OK. A bit confused. It showed a DEFRAG type graphic though it wasn’t doing a defrag. It was just checking the drive. But, I can live with that. It was kind of 1960s psychedelic and I am a product of the 60s. When it finished it said, drive was fine. Which is what I had expected. I had really cleaned out and optimized this system for my daughter on Dec. 30.

  3. Ran TuneUp Utilities and 1-click Maintenance AGAIN. Came back and said NO PROBLEMS. Bingo.

  4. Guess what. I ran System Mechanic 9.5.5 Deep Analysis. The suspense must be killing you. Sorry. System Mechanic told me that my PC was in Poor Health. I am glad it didn’t tell me to take it to the nearest PC doctor. Eight (8) problems. Yes, the C-disk was fragmented. I had the inescapable SM clutter. My C-drive had a fault! And I had 76 errors. Not Funny. It is the registry errors that bug me. I don’t put much stock in System Mechanic’s reporting of disk fragmentation — any more. I think they are using the old metric. They have also given me too many ‘false positives‘ on disk errors — though that was pre 9.5.3 with Windows 7.

It was like watching MSNBC and switching over the Fox News (which on my cable are on adjacent channels). Same news story different numbers. But at least when it comes to MSNBC vs. Fox News I know which numbers I would trust.

Next step. Going to install TuneUp Utilities 2010 on my latest (refurbished) XP. That is nice machine. Fast. Clean and I have a fully-paid up System Mechanic 9.3.3. [I haven’t powered it up THIS YEAR.] So stay tuned. I will get to the bottom of this.

So as Churchill used to say to FDR, I have no choice but to ‘KBO’. Good luck.


Anura Guruge

Read Full Post »

Older Posts »