v1.1.6 Release

[garyan2]

In light of the recent issues, I thought I would do a quick release that contains one more check to help mitigate any impact to the user's guide listings when something like this happens again.

What is in place:

• v1.1.0 and above counts the number of stations downloaded during an update and evaluates against the "expected" number in the configuration file. If the number is less than 90% of expected, guide update will be aborted.
• v1.1.5 and above will abort any update if the number of stations downloaded is zero due to the configuration file not having any stations identified for download. (passes the 90% check).
• v1.1.6 will now prompt the user for all count changes when saving the configuration file and will also alert to a 0 count. This way, if the lineup has lost stations, the user will be alerted to the change prior to overwriting the current config file.

Notice that for anyone still using v1.0.2 and below, there are no safety checks like the above. I strongly recommend updating to v1.1.6 when you can.

[IT Troll]

Some useful checks. Thanks.

Second time of using the installer and it didn't prompt for the installation folder as it has learnt this from the first time. Which is nice.

[garyan2]

Some useful checks. Thanks.

The first 2 checks is why I still have a functional guide ... came in very handy for this outage.

Second time of using the installer and it didn't prompt for the installation folder as it has learnt this from the first time. Which is nice.

Yah, I was very happy to see that option in the installer. It avoids problems down the line.

[12noon]

I don't want to create more work for you, but would it be possible to provide a ZIP file that can simply be extracted into the installation folder? (In my case, I'd like to extract it into a folder that's sync'd with my media center.)

[garyan2]

I don't want to create more work for you, but would it be possible to provide a ZIP file that can simply be extracted into the installation folder? (In my case, I'd like to extract it into a folder that's sync'd with my media center.)

That was the very first request when I released v1.1.5 ... I just haven't created the script yet to create the portable zip files. When I get them created and on the website, I'll let everyone know.

EDIT: Oh hey, look ... you weren't the first, but you were the second to request it in v1.1.5. Nag much?!?

[12noon]

Yeah, someone beat me to it. Thanks for putting it on your list. Instead of "nagging," I prefer to call it "reminding."

[garyan2]

I don't want to create more work for you, but would it be possible to provide a ZIP file that can simply be extracted into the installation folder? (In my case, I'd like to extract it into a folder that's sync'd with my media center.)

That was the very first request when I released v1.1.5 ... I just haven't created the script yet to create the portable zip files. When I get them created and on the website, I'll let everyone know.

EDIT: Oh hey, look ... you weren't the first, but you were the second to request it in v1.1.5. Nag much?!?

Okay, you've got portable zip files on the website now.

[12noon]

Geez, what took you so long? It's been like two hours! Thanks!

[Doctor Feelgood]

Geez, what took you so long? It's been like two hours! Thanks!

Agreed! Thanks for everything on this!

[Sancho]

Just upgraded from 1.1.5 via the installer and ran Save & Execute. I checked the trace log and noticed that the time stamps are off by 4 hours. The previous, scheduled run this morning with 1.1.5 show the correct time, as usual (5:30 AM and on), while the 1.1.6 time stamps show 14:49:04, with the last entry of 14:55:44. trace.log was last modified at 10:55. My HTPCs all sync their clocks twice daily, so it ain't that.

I just updated another install, and it shows the same behavior. Otherwise, it's all good. Just thought I'd mention it.

[garyan2]

Yah, this might change on next rev, I have to decide what I want to do with it. The times shown in the trace.log file for 1.1.6 are Zulu/GMT/UTC time. It makes it easier to understand when things are happening around the world but can cause some confusion locally. I had actually intended the same for v1.1.5 but didn't verify ... it used the local time and stamped it as Zulu time.

[Sancho]

Had a feeling it was intentional. Personally, I like local time.

[Doctor Feelgood]

Just jumped from 1.0.2 to 1.1.6... There are obviously still voids in the near future on many channels, but the switch was easy enough. Hopefully Gracenote gets things together soon, as that is really what made my attempt at going to 1.1.5 seem horrible last week.

Thanks.

[garyan2]

^just in time to update to 1.1.7 if you're up to it!