Tag Archives: bookmarks

Google Chrome On Windows XP Does Not Properly Support GoDaddy eMail! That Is Diabolical.

Dec2013x125

..
.
by
Anura Guruge


A Few Pertinent Posts:
  +++++ Do a SEARCH (>>>>) on ‘FireFox’ or ‘Chrome’ for others >>>>>
1. Switching from FireFox to Chrome  — Mar. 23, 2013.
2. Two things I like about Chrome … — Mar. 25, 2013.


I have now been using Chrome, exclusively, for just under a month. On the whole it has been ‘seamless’. I can’t believe that I was able to walk away from FireFox that easily, without nary a backward glance after over 12 year association. I really haven’t encountered any insurmountable problems with Chrome, on Windows 7, though I will continue to contend that I find it a tad sluggish compared to FireFox!

Last night I used Chrome on my Windows XP machine (which I still keep around because I still, alas, use FrontPage 2003). I was all excited that Chrome was going to automatically sync all my bookmarks, extensions etc. as soon as I signed in. It did all of that and I was happy.

But, I noticed that it would not render [i.e., display] my Bookmark Toolbar icons! That is a bummer because in some cases, especially with the very distinctive icons [e.g., Marketwatch, Bloomberg, Yahoo] I do not have any text next to them. Just the icon. On Windows 7 this works like a champ. On XP you get the generic ‘page’ icon for all. I thought this was a screen resolution issue so I ‘reduced’ my screen resolution to make the icons bigger. Still no joy.

Then I went to access my e-mail and I nearly fell off my kneeling stool seat. I reloaded and reloaded again. I even restarted XP!

GoDaddy e-mail, the e-mail service that I have used for eons (if not longer), just does not render in Chrome!

So I fired up FireFox. E-mail is just fine. I fired up this Windows 7 PC. Accessed e-mail. Just dandy. Went back to XP. Damn thing looks like somebody puked on the screen.

Here. This is what it looks like on Chrome on Windows XP.

Remember how GoDaddy rushed to my aid when I ran into traffic issues on my blog when the pope resigned. That is GoDaddy. Google should learn from them (though I have to say that Google was pretty awesome when we have had hardware issues with our Google Nexus 7 pads).

Click to ENLARGE.

Click to ENLARGE.

For a start, look at the parts I have underlined, twice, in red. Look at the BIG button. Notice that you can’t read the TEXT … which actually says ‘Move’ because it is displaying white text on a white background! All those little blobs you see, like bleached mouse droppings … those are supposed to be full size buttons.

This is crazy. This is stupid. This is unacceptable.

So, I Google. A known problem, going back to at least 2011. That is diabolical.

Click to ENLARGE.

Click to ENLARGE.

Notice that there is now a Chrome APP to access GoDaddy e-mail. I refuse to go that route. I have accessed GoDaddy e-mail from a browser for longer than most Google programmers have been out of diapers. I am not going to go down the slippery slope of relying on an APP to access Web-based e-mail.

That Chrome can be site-specific, depending on the version of the Operating System is beyond pathetic — and I am here talking as an ex-professional programmer for IBM, an ex-microcode programmer, a person who started programming in 1969, somebody with both a B.Sc (Hons.) & M.Sc. (Distinction) in Computer Technolgy/Science and somebody who taught computer programming at College level. This is just piss-poor programming. Simple as that.

I am not amused. Can’t believe that Google hasn’t fixed this or that GoDaddy, with their enormous clout, hasn’t leaned on Google and forced them to do the decent thing. Amazing.

Two Things I Like About Google Chrome 25 Over FireFox 18.

Dec2013x125

..
.
by
Anura Guruge


A Few Pertinent Posts:
  +++++ do a SEARCH (>>>>) on ‘FireFox’ for others’ >>>>>
1. Switching from FireFox to Chrome  — Mar. 23, 2013.
2. FireFox 18.0.1: ‘Clear History’ hang — Jan. 30, 2013.
3. FireFox 16.0.1 to 18.0.1: — Jan. 27, 2013.


I have now being using Chrome Version 25.0.1364.172 m full-time as my default Web browser for 2 days.

I am getting used to it. 

There are two features that I found that I think are dynamite:

1/ As long as you permit it to logon to you Google account (and why not given that I am logged on anyway for Google Search, Google News and Analytics) Chrome automatically synchronizes your Bookmark Toolbar anytime you invoke Chrome on another machine — provided, of course, that you are logged onto the same account. For me this is a lifesaver since I keep a backup machine. With FireFox I had to manually synchronize the Bookmark Toolbar. I found out today that I can even access the Bookmark Toolbar on our Google Nexus 7 pads. Remember, I am not talking about Google Bookmarks. Of course you expect that to be available across machines. I am here talking about the Bookmark Toolbar. I like that feature.

2/ This actually has to do with WordPress and is kind of ‘cute’. When creating a post, such as this, I use the standard WordPress editor. This editor has a title trench up at the top where you enter the desired title for the post. With FireFox there was NO SPELL CHECKING of that title line! Honest. I had got into the habit, when I remembered, of copying the title and then pasting it into Twitter to see if there were any spelling errors! Yesterday when I was typing in a title the squiggly red lines appeared in the title bar. I nearly fell off my chair. I had always assumed that this was a WordPress anomaly. Never thought it would be browser related. Just shows ya.

A few other things I have noticed. No question, Chrome consistently gets lower download and upload speeds on speedtest.net. We are not talking in the 1% to 3% range. But it is consistent. Maybe it is the rendering engine. Google must know about this.

After complimenting on its spelling prowess with WordPress titles, I have to now say that Chrome’s spelling dictionary is not as good as that used by FireFox! Again something that Google could asily fix.

One last thought. Did Avast, with their invasive Release 8, which promotes Chrome, set out to sabotage FireFox. I did a quick search. FireFox users with Avast 8 are noticing erratic performance. I had noticed this too which is what promoted me to switch to Chrome. So if this was a dastardly conspiracy between Google and Avast, it worked.

I had one inexplicable quirk last night. My whole PC blinked twice, momentarily, last night, i.e., both my monitors went black and just came back up again! Related to Chrome or is it Avast?

Mariner 2: 50 Years Since First Encounter With Another Planet, Venus, On December 14, 1962.

Anura Guruge, laughing, picture November 16, 2011.

….

..by Anura Guruge


My Book On ‘Dwarf Planets’.




Just a couple of weeks ago, I was writing about ‘Mariner 2‘ in what hopefully and with luck might be my next book; my 12th (not counting those that I have co-authored or edited). Given that this book is meant to be the first book I have written specifically as an eBook (i.e., Kindle, iPad, Google etc.), I am not that concerned about copyright because I fully appreciate that eBook content is readily ‘shareable‘ — which is why I have refrained from making all my books eBooks.

≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

In December 14, 1962, the 447 lbs U.S. ‘Mariner 2’, became the first successful interplanetary space probe when it passed, as planned, within 21,648 miles of Venus following an incident-prone 108-day voyage from Earth. It had a pyramidal structure, consisting of a solid base topped off by a skeletal mast that culminated in a cylindrical housing. Much of probe’s seven scientific instruments were contained within the mast structure; the total weight permitted for these instruments capped at 40 lbs. The base 41” across was hexagonal in shape, and was made up of six magnesium compartments. It had a total height of 12’. For comparison, Dawn, when launched, was six times heavier and its base over one-and-a-half times longer.

The six compartments in the base housed: a small rocket engine for course-correction, the required propellant, a bottle of nitrogen gas for altitude adjustments, most of the electronics, all of the communications equipment, a 1000 Watt-hour sealed silver-zinc battery and a battery charger. The only radio transmitter on-board had a 3 Watt transmission power, this being comparable to that of a contemporary car phone and about one-third that of a modern cell phone. Three huge steerable antennas, one in California, the other in Australia and the third in South Africa, had to be used to capture the weak radio signal from the probe, the geographic separation of the three compensating for Earth’s unceasing rotation around its axis. One of the key objectives of the mission was to explore the limits of long-range, extraterrestrial communications, particularly as it related to spacecraft command and control.

There were two solar cell wings, one 6’ x 2.5’ the other a foot shorter; a large directional dish antenna was mounted off the bottom of the base unit, a cylindrical omnidirectional antenna sat at the top of the mast while two smaller antennas for command and control were embedded into the solar panels. When deployed the two solar panel wings had a total span of 16.5’. The solar panels were extended within 45 minutes of launch. With the solar panels deployed Dawn has a wingspan of 64.75’.

The seven scientific instruments borne aloft by ‘Mariner 2’ consisted of: two radiometers (one microwave and the other infrared) for measuring Venusian atmospheric and terrestrial radiation [in particular temperature]; a fluxgate magnetometer to monitor and measure magnetic fields; an a Geiger counter equipped ionization chamber to determine high-energy cosmic radiation; a particle detector [i.e., a modified Geiger counter] to establish the presence of lower-energy radiation particularly the x-ray and ultraviolet range; a cosmic dust detector and a solar plasma spectrometer to study the solar wind. No cameras were included since Venus was known to be shrouded by a dense, amorphous cloud blanket.

‘Mariner 2’ was launched from the Cape Canaveral Air Force Station, on Florida’s eastern seaboard, around 2 a.m. local time, on August 27, 1962. It was launched atop a two-stage ‘Atlas-Agena’ rocket, the first-stage ‘Atlas’ part derived from the United States’ first intercontinental ballistic missile (ICBM) system, the ‘SM-65 Atlas’; the first of which was produced in 1959. The Atlas burn lasted just five minutes, the first-stage then separating from the Agena-Mariner section. Two burns of the upper-stage ‘RM-81 Agena’ followed, prior to its separation. Earth orbit escape resulted 26 minutes and 3 seconds after liftoff.

On July 22, 1962, NASA launched ‘Mariner 1’, a twin of ‘Mariner 2’, its first foray into robotic interplanetary probes. Within five minutes of launch, due to erroneous guidance, the ‘Atlas-Agena’ launch vehicle had veered off-course and had to be destroyed. Thirty-four days later, the Soviets launched ‘Venera 2 MV-1 No.1’ [‘Sputnik 19’] with the intent of it becoming the first man made object to land on another planet.

Mariner 2 never let those on Earth forget that most of its technology was still in the experimental stage and that it was boldly blazing into truly uncharted territory. Its journey, as was to be expected, was not without incident. In those early days launch accuracy was still a bit iffy, mandating a need for midcourse corrections. Thus, a week after launch a midcourse correction maneuver sequence was initiated using the onboard rocket engine and gas jets. Eleven days into the flight, ‘Mariner 2’ unexpectedly switched off its navigational gyroscopes and lost orientation [i.e., ‘attitude’] control. Mariner 2, however, managed to automatically recover from this glitch. Three weeks later there was a similar loss of orientation, again Mariner being able to quickly recover from it without any intervention from home. Just over a month later, the output from the smaller solar panel abruptly dropped.

On December 14, 1962, Mariner reached its expected target distance from Venus. The goal had always been to flyby rather than getting too close and running the risk if getting yanked in by Venus’ gravitational field. During the flyby Mariner’s radiometers, magnetometer and Geiger counters made repeated scans, back-and-forth, across both the dark and light sides of the planet – the radiometer readings for surface temperature involving three separate scans over a thirty-five minute period. The results indicated that the Venusian surface was extremely hot, its thick carbon dioxide heavy atmosphere causing rampant greenhouse effect heating.

The last radio transmission from Mariner 2 was received on Earth on January 3, 1963, twenty days post the Venus flyby. This groundbreaking mission to that point had lasted 129 days. It is thought that Mariner 2 entered heliocentric orbit soon after that and has remained so since.

There Is Now A FireFox 16.0.2 BUT I Have Not Installed. Worried What It Will Do.


Anura Guruge, laughing, picture November 16, 2011.

….
by Anura Guruge


Click to access Mozilla FireFox release note page.


After nearly a decade of being a beta tester and a recipient of AUTOMATED FireFox updates, just 2 days ago I changed my preferences in FireFox ‘options’ so that I get notified of updates, but they are not automatically installed.

So, a few minutes ago I got a notification that FF 16.0.2 was available — which is not a surprise given what a disaster 16.0.1 has proved to be. I am going to be cautious. I will wait to read reaction on the Web BEFORE I do the deed.

So, this is a heads up to you all. PLEASE share your experiences with FireFox 16.0.2, hopefully ALL GOOD, with us. I will post them for you.

Thank you. Cheers, Anura.

New Delicious Add-On For FireFox 16.0.1!


Anura Guruge, laughing, picture November 16, 2011.

….
by Anura Guruge


Delicious FireFox 16.0.1

Click image to get details directly from FireFox

New Delicious Add-On installed in my FireFox 16.0.1.

New Delicious Add-On installed in my FireFox 16.0.1.


There is a NEW Delicious bookmarking add-on that works with FireFox 16.0.1!

But, you don’t get it automatically even if you have the previous, now defunct, Delicious add-on installed (albeit disabled). That is crazy. There is NOT even a notification that a new version is available. Stuff like this drives me nuts. FireFox has an incredibly loyal user base — some of us who have been with them for over 10 years. Don’t be so hostile! Communicate. Help us, and we will help you.

When you install the add-on you will have to re-install the menu bar buttons IF you disabled them when Delicious stopped working with FireFox 16.0.1.

I haven’t used the add-on much at all, as yet. Just installed it a few minutes ago. Accessing Delicious via the menu bar icon seems to work. Haven’t tried to bookmark anything as yet.

Just a heads up, because I know that there is a lot of angst about Delicious and FireFox 16.0.1.

Hope this helps. Cheers.