Red V symbol (log file not valid) after OLC upload.
Am sort of wondering if the most recent "support" that was done had
its own Y2K issue? Meaning that the conversion program to make a
valid file was only going to create one named correctly for that
year. My understanding was that Carl Ekdahl's program would work if
you went back and changed the name of the .igc file it created to
match the year convention that the OLC validation program was looking
for. In other words, Carl's program had its own "Y2K" sort of issue,
as well. All of which has me waiting until January 1 to make a log
file, convert it using the program that works right now, see the name
the program gives the file, alter it if necessary, and try to upload
it and see what comments I get back from them.
I hope that they simply took an easier way out when the latest
conversion program was made, and that the older Model 10/20/25 files
can still be uploaded for full OLC "Green" status by using the same
program we currently use and then jumping through yet one more hoop
before uploading and hoping it will "take" on the first attempt. I
certainly don't like all the extras those of us with Original GPS
Equipment have to go through. But, I am an insane child of the
Microsoft Generation. Keep doing the same thing over again long
enough, and it will work. If not, hit the start button to shut the
system down, and try again. Isn't it wonderful?
Anyone willing or able to ask the OLC folks if the above might be
true? I mean, if there is a program that can make an acceptable igc
file from a cai file now, what is changing in the igc file format
effective 1-1-12 that would make that same program no longer work?
Sounds like they don't want to spend time fixing a Y2K sort of issue
with a cai to igc conversion program.
Any better theories?
Steve Leonard
(still got a boat load of them Cambridge Loggers)
|