Page 1 of 1
1.3.10.0 Release
Posted: Tue Aug 11, 2020 4:37 pm
by StinkyImp
Hi Gary!
Thank you for your recent release and all your hard work and dedication! It truly is appreciated!
I noticed a new file "epgTray.exe" is included and relates to your release note:
[enhancement] added a tray notification program to relay status of updates and ability to access EPG123 programs.
I looked into the client GUI and the Tweak options but I couldn't find an option to disable using the tray icon. The only way I could turn it off was by right clicking on the tray icon and selecting "Exit". Will this have to be performed daily?
Is there a way to permanently disable the tray icon?
Once again, thank you!
Re: 1.3.10.0 Release
Posted: Tue Aug 11, 2020 4:43 pm
by garyan2
If you don't want to use the tray icon, run 'msconfig', select the 'Startup' tab, and uncheck the 'epg123' startup item. It will no longer load when the user logs in after that.
Re: 1.3.10.0 Release
Posted: Tue Aug 11, 2020 10:27 pm
by RyC
Love the tray icon, thanks for continually making improvements to EPG123!
Re: 1.3.10.0 Release
Posted: Wed Aug 12, 2020 6:15 am
by IT Troll
garyan2 wrote: ↑Tue Aug 11, 2020 4:43 pm
If you don't want to use the tray icon, run 'msconfig', select the 'Startup' tab, and uncheck the 'epg123' startup item. It will no longer load when the user logs in after that.
You can also use Task Manager, but not everyone knows about these methods. It would be friendlier to provide a way in the EPG123 GUI to disable and re-enable the tray icon.
I do like the tray icon and will be running with it even though I run Media Center full screen 24/7. Any chance of an “Update Now” on the right-click for those of us cursed by the MS pop-up?
Re: 1.3.10.0 Release
Posted: Wed Aug 12, 2020 2:47 pm
by garyan2
IT Troll wrote: ↑Wed Aug 12, 2020 6:15 amYou can also use Task Manager, but not everyone knows about these methods. It would be friendlier to provide a way in the EPG123 GUI to disable and re-enable the tray icon.
I do like the tray icon and will be running with it even though I run Media Center full screen 24/7. Any chance of an “Update Now” on the right-click for those of us cursed by the MS pop-up?
The Task Manager in Win7 doesn't include the startup items to enable/disable. Win10 does and I assume Win8.x does as well.
I thought about the "Update Now" option but haven't decided yet. The tray will have to be "aware" of the scheduled task so I delayed on including it to figure out what all I need to make work. It will probably be included in a later release.
Re: 1.3.10.0 Release
Posted: Wed Aug 12, 2020 3:39 pm
by IT Troll
I guess you could launch the Config Tool and do an Execute.
Re: 1.3.10.0 Release
Posted: Wed Aug 12, 2020 3:43 pm
by garyan2
I could just be lazy and add the option to run the task and if the task doesn't exist it will give an error. I would prefer to enable/disable the option based on the whether the task exists, but the simple way will work as well. If the task doesn't exist, just pop up a balloon message or message box saying as such.
Re: 1.3.10.0 Release
Posted: Wed Aug 12, 2020 8:00 pm
by garyan2
Next release.
- trayupdate.PNG (6.44 KiB) Viewed 2179 times
Re: 1.3.10.0 Release
Posted: Sat Sep 05, 2020 7:48 am
by IT Troll
garyan2 wrote: ↑Wed Aug 12, 2020 8:00 pm
Next release.
Great to see that Update Guide Now has been added.
The tray icon didn't notify me that an update was available. Should it have or would that be for major versions only?
Re: 1.3.10.0 Release
Posted: Sat Sep 05, 2020 3:25 pm
by garyan2
IT Troll wrote: ↑Sat Sep 05, 2020 7:48 amThe tray icon didn't notify me that an update was available. Should it have or would that be for major versions only?
Major versions only. If I bumped the version number to 1.3.11, you would have seen the notification.
Re: 1.3.10.0 Release
Posted: Sun Sep 13, 2020 4:56 pm
by IT Troll
The System Tray icon proved it's worth today. I happened to switch out of full screen Media Center mode and immediately noticed a red alert!
Turns out my update failed this morning due to SD server problems. I used the icon to check the logs and perform an on-demand update. Which was successful.
I noticed in the log that even when the download fails, the import (of the stale data) is still performed. I guess it doesn't hurt. But is there a reason for this?
Code: Select all
[13/09/2020 06:15:01] ===============================================================================
[13/09/2020 06:15:01] Beginning epg123 update execution. version 1.3.10.20
[13/09/2020 06:15:01] ===============================================================================
[13/09/2020 06:15:01] [ INFO] Beginning EPG123 update execution. 2020-09-13 05:15:01Z
[13/09/2020 06:15:01] [ INFO] DaysToDownload: 14 , TheTVDBNumbers : True , PrefixEpisodeTitle: False , PrefixEpisodeDescription : False , AppendEpisodeDesc: True , OADOverride : True , TMDbCoverArt: False , IncludeSDLogos : False , AutoAddNew: False , CreateXmltv: False , ModernMediaUiPlusSupport: False
[13/09/2020 06:15:02] [ INFO] Token request successful. serverID: 20141201.web.1
[13/09/2020 06:15:04] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (502) Bad Gateway. , Status: ProtocolError
[13/09/2020 06:15:04] [ INFO] Status request successful. account expires: 2021-07-23T10:51:28Z , lineups: 1/4 , lastDataUpdate: 2020-09-12T23:33:48Z
[13/09/2020 06:15:04] [ INFO] system status: Online , message: No known issues.
[13/09/2020 06:15:04] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (502) Bad Gateway. , Status: ProtocolError
[13/09/2020 06:15:05] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[13/09/2020 06:15:05] Entering buildLineupServices() for 1 lineups.
[13/09/2020 06:15:05] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (502) Bad Gateway. , Status: ProtocolError
[13/09/2020 06:15:05] [ INFO] Successfully retrieved the station mapping for lineup GBR-1000029-DEFAULT.
[13/09/2020 06:15:05] Exiting buildLineupServices(). SUCCESS.
[13/09/2020 06:15:05] Entering getAllScheduleEntryMd5s() for 14 days on 16 stations.
[13/09/2020 06:15:07] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (502) Bad Gateway. , Status: ProtocolError
[13/09/2020 06:15:08] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (502) Bad Gateway. , Status: ProtocolError
[13/09/2020 06:15:08] [ERROR] Failed to complete request. Exiting
[13/09/2020 06:15:08] [ERROR] Did not receive a response from Schedules Direct for Md5s of 16 station's daily schedules. (0:00:00:02.0641403)
[13/09/2020 06:15:08] [ERROR] Problem occurred during getMd5ScheduleEntries(). Exiting.
[13/09/2020 06:15:08] [ERROR] Failed to create MXF file. Exiting.
[13/09/2020 06:15:08] [ INFO] epg123 update execution time was 00:00:06.2774578.
[13/09/2020 06:15:08] ===============================================================================
[13/09/2020 06:15:08] Beginning epg123 client execution. version 1.3.10.20
[13/09/2020 06:15:08] ===============================================================================
[13/09/2020 06:15:08] [ INFO] Beginning epg123 client execution. 2020-09-13 05:15:08Z
[13/09/2020 06:15:08] [ INFO] Import: True , Match: True , NoLogo: False , Force: False , ShowProgress: False
[13/09/2020 06:15:08] Entering importMxfFile() for file "c:\users\public\epg123\output\epg123.mxf"
[13/09/2020 06:15:12] [ INFO] Successfully imported .mxf file into Media Center database. Exit code: 0
[13/09/2020 06:15:12] Exiting importMxfFile(). SUCCESS.
[13/09/2020 06:15:12] [ INFO] Skipped matching MORE4 to channel 18 due to channel already having an assigned listing.
[13/09/2020 06:15:12] [ INFO] Completed the automatch of lineup stations to tuner channels.
[13/09/2020 06:15:12] [ INFO] Completed lineup refresh.
[13/09/2020 06:15:12] Entering runWmcTask(ReindexSearchRoot)
[13/09/2020 06:15:12] [ INFO] SUCCESS: Attempted to run the scheduled task "Microsoft\Windows\Media Center\ReindexSearchRoot".
[13/09/2020 06:15:12] [ INFO] Successfully started the ReindexSearchRoot task. Exit code: 0
[13/09/2020 06:15:12] Exiting runWmcTask(ReindexSearchRoot). SUCCESS.
[13/09/2020 06:15:12] [ INFO] MXF file was created on 12/09/2020 06:15:01
[13/09/2020 06:15:12] [ERROR] The MXF file imported is 23.00 hours old.
[13/09/2020 06:15:12] [ INFO] Completed EPG123 client execution.
[13/09/2020 06:15:12] [ INFO] EPG123 client execution time was 00:00:04.5321701.
Re: 1.3.10.0 Release
Posted: Sun Sep 13, 2020 5:41 pm
by garyan2
The scheduled task has 2 actions, run epg123.exe and run epg123client.exe. Regardless on whether epg123.exe was successful or not, the task moves to the next action which is run epg123client.exe. The programs don't talk with each other so if epg123.exe fails, the import will still run. Also, since they don't talk to each other, the client relies on the date/time of when the MXF file was created to determine if epg123.exe was successful as well as a status entry in the MXF file to determine if there were any warnings or update available.
Note: The client is only concerned about the mxf file being imported, and the client is the one that determines the status logos and notification logo. If you had performed a manual update later in the day yesterday then your status would have still been green since the MXF file age was less than 23 hours old, even though epg123.exe failed. The status would have changed to red automatically once 24 hours had elapsed since the mxf file update, though.
On another note, I'm pretty sure the age of your MXF file was more than 23.00 hours old so I'm going to have to see why that didn't calculate correctly. I checked it out here and everything should be using UTC, but I can't deny your result.