Google Earth & Mapsource - problem?

Problem: Gooble Earth starts very slowly.
Reason: MapSource and GE improperly sharing some resource?


Sometimes (not every time, perhaps 3...5 out of 10), when I have
MapSource (6.9.2) running and I start Google Earth (3.0.693), the latter
gets very (!!) slow. GE eats practically all processor power, and is
dozens of times slower than usually.
So far I haven't found any other logic behind this, but it seems to
occur only if I have at least one instance of MS running while starting
the GE (or am starting GE via MS, through menu/View/View in Goolge
Earth). However, usually GE starts normally even if MS is running behind.

Occurs in both Win2000 and XP.


Usually it gets apr. 5 sec for the GE bootup screen (before the
application window appears), another 5 sec until the globe is shown, and
less than 5 sec more to show all the details (i.e. < 15 sec to get it up
an running, release the CPU).
But when the problem occurs, the application windows showing the
"Loading" dialog (after the GE "bootup screen") remains on the screen
for half a minute, and when the globe is shown, the streaming indicator
at the bottom of the GE window progress very slow. Windows Task Manager
indicates that the GE is the process using the 99% of the CPU, and the
used memory is getting up slowly (it seems like it would eventually end
up to the same value as in the "normal" case, but I have never waited
for more than 15 minutes before killing the process).

Any ideas what might cause this and/or what could help?

MP wrote:

Perhpas you need a Cray, or something similar from IBM. Tell your wife what
lovely cabinets they come in, so the living room can be used to house your
new purchase.

Dennis.

Dennis Pogson wrote:

Well, i already have an IBM laptop...

But in this case, the reason is not that the PC is too slow. Usually the
GE starts "relatively" quickly (well less than 15 sec), but sometimes it
gets sooooo slow.
BTW: I just noticed that if I have MS running with lots of long routes
set up, then starting the GE is always slow. However, if I do it other
way around (start GE first, and only then start MS and read the .gdp
file with lots of long routes), everything works just fine (i.e.
relatively smoothly, even on my laptop).

("long" above refers to the number of via points).