Starting SeeYou

On Friday, 24 July 2020 19:36:08 UTC-6, Tony wrote:
Don't even get.me started Ron. The only reason I was.forced.to update to a new laptop was because SeeYou quit supporting Windows 8 or whatever I had..on my old laptop. They did so with no notification and still listing Windows 8 as a support OS on the website! So like a fool I did the update and all the sudden the program wouldn't work. That years subscription was.exoensive since I had to buy a new computer!!

No other program on my laptop seems to be having issues...

Welcome to the slippery slope

At 01:36 25 July 2020, Tony wrote:
Don't even get.me started Ron. The only reason I was.forced.to update to
a
=
new laptop was because SeeYou quit supporting Windows 8 or whatever I
had.o=
n my old laptop. They did so with no notification and still listing
Windows=
8 as a support OS on the website! So like a fool I did the update and
all
=
the sudden the program wouldn't work. That years subscription
was.exoensive=
since I had to buy a new computer!!

No other program on my laptop seems to be having issues...

SeeYou did stop support on Windows XP, but it is still works on Windows 7,
so why Windows 8 should be a problem, I do not know.

The time taken by SeeYou to load can be affected by the size of Airspace
file it has to load. If you are loading the entire US airspace, this could
be a problem.

On Thursday, July 23, 2020 at 9:02:36 PM UTC-6, Tony wrote:
Nothing IBM in the Extensions on Chrome. SeeYou Logs sent to Naviter. I can't be the only one in the world who is having this issue??

https://soaringlab.eu/index.php

Yea it was XP that I had on my old laptop.

On Saturday, July 25, 2020 at 7:52:21 PM UTC-7, Tony wrote:
Yea it was XP that I had on my old laptop.

There is also https://www.soaringlab.eu. Not for planning, but good for viewing a single flight at a time.

On Sat, 25 Jul 2020 20:33:10 -0700, Jonathan St. Cloud wrote:

On Saturday, July 25, 2020 at 7:52:21 PM UTC-7, Tony wrote:
Yea it was XP that I had on my old laptop.

There is also https://www.soaringlab.eu. Not for planning, but good for
viewing a single flight at a time.

I use GPLIGC - https://sourceforge.net/projects/gpligc/

It displays a 3D flight trace, 2D altitude graph and can generate a KML
file for viewing with Google Earth. It also extracts te flight time and
other useful statistics. Its free but requires Perl to be installed on
your PC.


--
Martin | martin at
Gregorie | gregorie dot org

On Friday, July 24, 2020 at 9:33:06 PM UTC-4, Ron Gleason wrote:
On Friday, 24 July 2020 19:27:28 UTC-6, Tony wrote:
15ish minutes to finally start yesterday. No error messages. Latest version.

Version 10.33 of SeeYou, 12 seconds to launch. Tony, like your glider you need to upgrade your PC equipment 8-)

Alternatively, keep the old versions of software, they run even better on newer hardware...

On Friday, July 24, 2020 at 7:27:28 PM UTC-6, Tony wrote:
15ish minutes to finally start yesterday. No error messages. Latest version.

So that is suggestive of something wrong on your end. As Ron's and other's experience indicates, 15-20 seconds is typical. It isn't airspace -- I am indeed loading the entire airspace of the US on startup, and mine is loading in about 20 seconds.

It probably isn't any firewall or security software, because it starts eventually. It isn't just blocked.

Here are some possibles, but not an exhaustive list by any measure.
- Not enough RAM on your computer. If this is the problem, it would be characterized by a crazy amount of hard drive activity (assuming you don't have a solid state drive) during the SeeYou startup as the system tries to swap memory pages to meet the demand. If you have a hard drive activity light, it would help determine this. It might be blinking furiously, or look as if it is stuck on.
- A dicey network connection. Have you been able to try it while connected to a different network?
- Some malware running on your computer, stealing resource. This could be characterized by high CPU, network, or disk usage during the startup.

If you have the skill to monitor the process using Task Manager or some other similar tool, that would be the next step.

Lynn