Saturday, August 2, 2008

Semi-Silent Saturday




With the Site Meter causing the Blog problems last night....I managed to wipe out my entire site count since February....what the hey? I reloaded it and it's back up and running, but the entire 5 months of data is gone....that was my fault in part(forget my password and code)...but I see where Site Meter would like to blame Internet Explorer....I'm not buying that....Site Meter is to blame...that's what they get when their top blogs are left wing loon sites lite the Daily Kos and Huffington Post, 2 anti-American hate sites.

Anyway, I'll give it one more try...just because it's free and gives me an idea of whom and from where I get hits.















Today was pretty much relaxation, I Sat out back, roasted a cigar, downed a couple of beers, and watched my wife do most of the yard work, edging the sidewalk and digging up and trimming around our yard 'walk stones'..... my contribution was taking the above photos.

Tomorrow or Monday, I'll be back with another installment of RV Travels....this one across the northern Rockies and on to Oregon.


back later>>>>>>>>>>
----------------------------------------------------
Photos-As we enter August, the back yard flowers continue to bloom and prosper....and a set of Pots Patricia bought....she plans on transferring some indoor plants(that spend the warm months outdoors) to them.....I thought they made an "interesting" photo sitting on the back walk.

3 comments:

The Lonely Conservative said...

Site meter screwed everyone up! Thanks for your service!

pat houseworth said...

Thanks for dropping by LC.....

Buck said...

but I see where Site Meter would like to blame Internet Explorer....I'm not buying that....Site Meter is to blame...

You're right in one sense, Pat. The SM guys should have optimized their code for IE (taking into account Microsnot's piss-poor design of IE), but didn't... and that's their fault. But those of us using any browser except IE (e.g., Firefox, Safari, etc.) had no problems whatsoever. I read the inherent "glitch" in IE v.7's code will go away with the release of IE 8. Bottom line: Microsnot is the real culprit here...