v1.2.2 Release

[garyan2]

New release out. Some improvements and enhancements added in this one as well as some significant change in the architecture. Updating will require your current scheduled task to be deleted and created again due to a change in the location of the MXF file.

Read all about it on the website. For those that can't stand to have a program outside the Program Files/ProgramData folders ... you'll like this one.

Updating Scenarios

Previous installation is not in a Program Files folder:
v1.2.2 will install over the current location. The generated MXF and XMLTV files will now be located in the [epg123]\output folder. Action: create a new scheduled task.

Previous installation is in a Program Files folder:
v1.2.2 will install over the current location. The generated files will now be located in the ProgramData\GaRyan2\epg123 folder and subfolders. Action: move the \backup, \cache, \logos, and \sdlogos folders to ProgramData\GaRyan2\epg123 folder along with the epg123.cfg, EPG123Status.png, epg123Task.xml, guideImages.xml, and your trace.log files. Create a new scheduled task.

Uninstall previous version and install v1.2.2 to Program Files folder:
Action: move the same files as above to the ProgramData\GaRyan2\epg123 folder and create a new scheduled task.

NOTE: For those that install in the Program Files folder, the ProgramData\GaRyan2\epg123 folder will not be created until you open either EPG123 or EPG123 Client.

[mldenison]

Hi Gary,

I just installed 1.2.2 and am getting this. What am I forgetting?:

[mldenison]

I should have mentioned that this was an install over 1.2.1.

I also noticed that these files were also created (attachment).

Here's the trace.log from this new directory (no longer in my EPG123 program directory).

Code: Select all

[8/6/2018 7:29:08 AM] ===============================================================================
[8/6/2018 7:29:08 AM]  Beginning epg123 update execution.
[8/6/2018 7:29:08 AM] ===============================================================================
[8/6/2018 7:29:08 AM] [ INFO] Beginning EPG123 update execution. 2018-08-06 11:29:08Z
[8/6/2018 7:29:08 AM] [ INFO] DaysToDownload: 14 , TheTVDBNumbers : True , PrefixEpisodeTitle: True , PrefixEpisodeDescription : True , AppendEpisodeDesc: False , OADOverride : True , TMDbCoverArt: True , IncludeSDLogos : True , AutoAddNew: False , CreateXmltv: False , ModernMediaUiPlusSupport: False
[8/6/2018 7:29:08 AM] [ INFO] Status request successful. account expires: 2019-03-25T01:38:33Z , lineups: 1/4 , lastDataUpdate: 2018-08-06T03:07:24Z
[8/6/2018 7:29:08 AM] [ INFO] system status: Online , message: No known issues.
[8/6/2018 7:29:08 AM] [ INFO] epg123 version: 1.2.2
[8/6/2018 7:29:08 AM] [ INFO] Successfully retrieved TMDb configurations.
[8/6/2018 7:29:08 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[8/6/2018 7:29:08 AM] Entering buildLineupServices() for 1 lineups.
[8/6/2018 7:29:08 AM] [ INFO] Subscribed lineup USA-PA37649-X has been EXCLUDED from download and processing.
[8/6/2018 7:29:08 AM] [ERROR] There are 0 stations queued for download from 1 subscribed lineups. Exiting.
[8/6/2018 7:29:08 AM] [ERROR] Check that lineups are 'INCLUDED' and stations are selected in the EPG123 GUI.
[8/6/2018 7:29:08 AM] [ERROR] Failed to create MXF file. Exiting.
[8/6/2018 7:29:08 AM] [ INFO] epg123 update execution time was 00:00:00.3990229.

[garyan2]

So it looks like you uninstalled 1.2.1 and then installed 1.2.2 to the default Program Files location. For your first post, click the INCLUDE/EXCLUDE button (red dot) in the configuration GUI to include you lineup for download. Or, you can copy move/copy your old epg123.cfg into the ProgramData\GaRyan2\epg123 folder.

Code: Select all

[8/6/2018 7:29:08 AM] [ERROR] Check that lineups are 'INCLUDED' and stations are selected in the EPG123 GUI.

For your second post, that is where everything will be located for the Program Files/ProgramData installation.

Note: For anyone that just installs v1.2.2 over v1.2.1, everything will be installed in your current location. The difference will be another folder will be created ([epg123]\output) which will contain the epg123.mxf, epg123.xmltv, and mmuiplus.json output files. <- the reason to create a new scheduled task.

EDIT: Just realized while I was in the shower there is a scenario I hadn't tried. If your previous installation was already in a Program Files location, then the ProgramData folder will automatically start being used. The program will not realize the cfg files and output files are in the Program Files folder.

[mldenison]

I didn't uninstall 1.2.1 which was in the default Program Files location, just installed 1.2.2 over it.

I just did a full uninstall and reinstall.

The initial run was successful with no errors in the trace log. WMC Guide is fine.

[newfiend]

just did an uninstall of 1.2.1
then install of 1.2.2

it created a epg123 folder here C:\Program Files (x86)\epg123

your instructions say to copy files to programdata file but none was created in programdata, only program files (x86)...

do I copy all the files to program files (x86) or create the .dir you mentioned in your instructions in programdata ?

newfiend

[garyan2]

just did an uninstall of 1.2.1
then install of 1.2.2

it created a epg123 folder here C:\Program Files (x86)\epg123

your instructions say to copy files to programdata file but none was created in programdata, only program files (x86)...

do I copy all the files to program files (x86) or create the .dir you mentioned in your instructions in programdata ?

newfiend

The first time you open the EPG123 Configuration GUI, or the EPG123 Client, the ProgramData folders will be created. I don't have the installation create the folders.

[newfiend]

just did an uninstall of 1.2.1
then install of 1.2.2

it created a epg123 folder here C:\Program Files (x86)\epg123

your instructions say to copy files to programdata file but none was created in programdata, only program files (x86)...

do I copy all the files to program files (x86) or create the .dir you mentioned in your instructions in programdata ?

newfiend

The first time you open the EPG123 Configuration GUI, or the EPG123 Client, the ProgramData folders will be created. I don't have the installation create the folders.

well don't I feel silly.. lol thanks Gary.

[garyan2]

well don't I feel silly.. lol thanks Gary.

You shouldn't. I'm the one that should have shared that little tidbit of information.

Thank you!

[Sammy2]

Whoopie!

Another installation to do!

Your instructions state the following

Code: Select all

Previous installation is not in a Program Files folder:
v1.2.2 will install over the current location. The generated MXF and XMLTV files will now be located in the [epg123]\output folder. Action: create a new scheduled task

What if I want the new installation to be in the Program Files folder? Do I have to follow instructions #3 or can I choose where to install on installation? Either way, moving the data around around seems semi-tedious. Can this be automated with the installer?

[garyan2]

Whoopie!

Another installation to do!

Your instructions state the following

Code: Select all

Previous installation is not in a Program Files folder:
v1.2.2 will install over the current location. The generated MXF and XMLTV files will now be located in the [epg123]\output folder. Action: create a new scheduled task

What if I want the new installation to be in the Program Files folder? Do I have to follow instructions #3 or can I choose where to install on installation? Either way, moving the data around around seems semi-tedious. Can this be automated with the installer?

The only way to change the location of epg123 is to uninstall and reinstall (third scenario above). I am not going to do anything with the installer to do anything... as far as it is concerned, this is a first time install since the previous version was uninstalled.

You don't have to move any files/folders if you don't want to. At a minimum, I would suggest moving your epg123.cfg file to the new location so you don't have to set that up again. Moving over everything else is just to give your next update a boost by not having to download everything and build channel logos again.

Special note for you: Once you install the new version, be sure to [Save] a new configuration file. This will create a new element in the file, <BrandLogoImage>, with a default value of 'none'. Change that to 'light' and after the next update your extenders will see a status logo in the guide.

[mafaldatv]

I've been happily running 1.17 on theory ain't broke. (except, off topic, WMC failed silently to record the other day, don't think it was epg's fault, but can't figure that one out. reboot fixed). Is there a compelling reason to update? And because I'm dense, as I understand it I just install over the old one then go to EPG123, delete scheduled task, then create new one there. And that's it (?!)

Thx!

[garyan2]

I've been happily running 1.17 on theory ain't broke. (except, off topic, WMC failed silently to record the other day, don't think it was epg's fault, but can't figure that one out. reboot fixed). Is there a compelling reason to update? And because I'm dense, as I understand it I just install over the old one then go to EPG123, delete scheduled task, then create new one there. And that's it (?!)

Thx!

No real compelling reason. There has been some reliability and logging improvements since 1.1.17, but for the most part it has been about adding features to improve the initial setup, guide tweaks, adding ability to create XMLTV and now the MM UI+ files... Basically, if you update, but don't use any of the new features, you won't see any real difference (though the status logo on the WMC homepage is a nice feature to let you know if anything is going wrong).

That being said, the install path for you can simply be install over the old one, delete scheduled task, and create a new one. That's it.

[Sammy2]

I've been happily running 1.17 on theory ain't broke. (except, off topic, WMC failed silently to record the other day, don't think it was epg's fault, but can't figure that one out. reboot fixed). Is there a compelling reason to update? And because I'm dense, as I understand it I just install over the old one then go to EPG123, delete scheduled task, then create new one there. And that's it (?!)

Thx!

No real compelling reason. There has been some reliability and logging improvements since 1.1.17, but for the most part it has been about adding features to improve the initial setup, guide tweaks, adding ability to create XMLTV and now the MM UI+ files... Basically, if you update, but don't use any of the new features, you won't see any real difference (though the status logo on the WMC homepage is a nice feature to let you know if anything is going wrong).

That being said, the install path for you can simply be install over the old one, delete scheduled task, and create a new one. That's it.

Think I'll just install it in my epg123 folder.. why not?

Sent from my SM-G930P using Tapatalk

[stefanr]

Hi Gary,

I have installed 1.2.2 over my 1.2.1 release, which was already in Program Files(x86). I have moved the related files to C:\programdata\GaRyan2\epg123\ and I have deleted the old scheduled task and created a new one. I can open EPG123 and execute it without any problems and everything is working OK.

However, when the sceduled task runs (or if I run it manually) it comes back with a return code of 0xE0434352 and nothing is written to the trace file. There is nothing in the event viewer, but if I turn on the history for scheduled tasks I see this:

Task Scheduler started "{2ce74aa6-2165-4cb4-845a-c070f89345f1}" instance of the "\epg123_update" task for user "(NONE)".
Task Scheduler launched action "epg123 Execution Action 1" in instance "{2ce74aa6-2165-4cb4-845a-c070f89345f1}" of task "\epg123_update".
Task Scheduler launched "{2ce74aa6-2165-4cb4-845a-c070f89345f1}" instance of task "\epg123_update" for user "NETWORK SERVICE" .
Task Scheduler successfully completed task "\epg123_update" , instance "{2ce74aa6-2165-4cb4-845a-c070f89345f1}" , action "epg123 Execution Action 1" with return code 3762504530.

[UPDATE]
In testing EPG123 maually, I realised that it worked OK if I ran it as Administrator, but it failed if I ran it as a normal user. Looking at the folder permissions for C:\programdata\GaRyan2\epg123 I realised that normal users do not have write access to this folder. Once I changed the security permissions, EPG123 works OK if launched with normal privledges and the Scheduled Task runs OK as well.

[garyan2]

[UPDATE]
In testing EPG123 maually, I realised that it worked OK if I ran it as Administrator, but it failed if I ran it as a normal user. Looking at the folder permissions for C:\programdata\GaRyan2\epg123 I realised that normal users do not have write access to this folder. Once I changed the security permissions, EPG123 works OK if launched with normal privledges and the Scheduled Task runs OK as well.

I had assumed the group 'Users' gets 'Read & execute' as well as 'Write' to the ProgramData subfolders. Is that not the case, or is this unique to your setup?

[garyan2]

[UPDATE]
In testing EPG123 maually, I realised that it worked OK if I ran it as Administrator, but it failed if I ran it as a normal user. Looking at the folder permissions for C:\programdata\GaRyan2\epg123 I realised that normal users do not have write access to this folder. Once I changed the security permissions, EPG123 works OK if launched with normal privledges and the Scheduled Task runs OK as well.

I had assumed the group 'Users' gets 'Read & execute' as well as 'Write' to the ProgramData subfolders. Is that not the case, or is this unique to your setup?

I see that since your user for the task is NETWORK_SERVICE that you are running on Win10. I just ran a scheduled task on my Win10 machine and it did the same thing. On a Win7 machine there is no issue because the user of the task is actually a User and has read/write permissions. Win10 was unique because MS screwed up the scheduled tasks with one of their updates whereas the only way to run multiple actions in a task was to run as admin or a service. That has since been fixed in later updates but I don't know when and there are probably a lot of people that refuse to update Win10 due to it breaking DRM in WMC.

I'll see if I can find a suitable fix for everyone and release it as soon as possible. Anyone want to contribute ideas, shout them out!

Thank you,

[stefanr]

I had assumed the group 'Users' gets 'Read & execute' as well as 'Write' to the ProgramData subfolders. Is that not the case, or is this unique to your setup?

I just checked 3 Windows 10 machines, all running release 1803, and Users only have read, read & execute and list permissions on the Programdata folder. However, they do not have write access.

[garyan2]

I had assumed the group 'Users' gets 'Read & execute' as well as 'Write' to the ProgramData subfolders. Is that not the case, or is this unique to your setup?

I just checked 3 Windows 10 machines, all running release 1803, and Users only have read, read & execute and list permissions on the Programdata folder. However, they do not have write access.

Did you click the [Advanced] button when looking at the folder properties/security? The folder should have "special permissions" that give write access but will only be visible when you click the [Advanced] button.

[stefanr]

Did you click the [Advanced] button when looking at the folder properties/security? The folder should have "special permissions" that give write access but will only be visible when you click the [Advanced] button.

I can see that under Advanced properties write access is given for Users to the programdata folder, but importantly this permission is only given for "This folder and subfolders" - other permissions are for "This folder, subfolders and files" - by manually adding the write permission to users, write access to files is given.