MXF import failure

An evolving, supported alternative to Rovi
Forum rules
★ Download the latest EPG123 here: https://garyan2.github.io/ <> Setup guide here: https://garyan2.github.io/install.html
Post Reply
technodevotee

Posts: 963
Joined: Thu Sep 10, 2015 4:10 pm
Location: West Midlands

HTPC Specs: Show details

MXF import failure

#1

Post by technodevotee » Sun Jun 17, 2018 5:46 am

Hi.

thanks to Gary and his EPG123, Media Center has been working well for me until a couple of days ago when the mxf import started failing on both of my PCs.

I get the following messages:

Code: Select all

[17/06/2018 06:18:06] [ INFO] Error: The following error was encountered while processing the file. Aborting.
[17/06/2018 06:18:06] [ INFO] StartTime must be specified for first ScheduleEntry in a block
[17/06/2018 06:18:11] [ERROR] Error using loadmxf.exe to import new guide information. Exit code: -1
[17/06/2018 06:18:11] Exiting importMxfFile(). FAILURE.
[17/06/2018 06:18:11] [ERROR] Failed to import .mxf file. Exiting.
any ideas please?

User avatar
garyan2

Posts: 7438
Joined: Fri Nov 27, 2015 7:23 pm
Location:

HTPC Specs: Show details

#2

Post by garyan2 » Sun Jun 17, 2018 6:22 am

Were there any other errors, possibly during the epg123 update run to create the mxf? I'll send you a PM with my email address so you can send me your zipped up mxf file. The error that it is showing is supposedly not possible.

How are your 2 PCs setup for epg123? Do both download and create their own mxf file or is 1 of them a server/client and the other a client?
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

technodevotee

Posts: 963
Joined: Thu Sep 10, 2015 4:10 pm
Location: West Midlands

HTPC Specs: Show details

#3

Post by technodevotee » Sun Jun 17, 2018 6:39 am

Thanks Gary, I've sent you the file.

The PCs each collect their own data as they have different cards in them - one with two DVB-S2 cards and one with a quad DVB-T2 card.

THE TRACE LOG ENTRIES FOR TODAY WERE:

Code: Select all

[17/06/2018 06:00:02] ===============================================================================
[17/06/2018 06:00:02]  Beginning epg123 update execution.
[17/06/2018 06:00:02] ===============================================================================
[17/06/2018 06:00:02] [ INFO] Beginning EPG123 update execution. 2018-06-17 05:00:02Z
[17/06/2018 06:00:02] [ INFO] DaysToDownload: 21 , TheTVDBNumbers : False , PrefixEpisodeTitle: False , PrefixEpisodeDescription : False , AppendEpisodeDesc: True , OADOverride : False , TMDbCoverArt: False , IncludeSDLogos : False , AutoAddNew: False , CreateXmltv: False
[17/06/2018 06:00:03] [ INFO] Token request successful. serverID: 20141201.web.X
[17/06/2018 06:00:03] [ INFO] Status request successful. account expires: 2018-10-23T08:28:39Z , lineups: 3/4 , lastDataUpdate: 2018-06-17T01:59:09Z
[17/06/2018 06:00:03] [ INFO] system status: Online , message: No known issues.
[17/06/2018 06:00:04] [ INFO] epg123 version: 1.2.0
[17/06/2018 06:00:04] [ INFO] Successfully retrieved TMDb configurations.
[17/06/2018 06:00:05] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[17/06/2018 06:00:05] Entering buildLineupServices() for 3 lineups.
[17/06/2018 06:00:05] [ INFO] Successfully retrieved the station mapping for lineup GBR-1000066-DEFAULT.
[17/06/2018 06:00:05] [ INFO] Subscribed lineup GBR-1000067-DEFAULT has been EXCLUDED from download and processing.
[17/06/2018 06:00:05] [ INFO] Successfully retrieved the station mapping for lineup ZZZ-19.2E-DEFAULT.
[17/06/2018 06:00:06] Exiting buildLineupServices(). SUCCESS.
[17/06/2018 06:00:06] Entering getAllScheduleEntryMd5s() for 21 days on 367 stations.
[17/06/2018 06:01:05] [ INFO] Successfully retrieved Md5s for 238 station's daily schedules.
[17/06/2018 06:01:10] [WARNG] Failed to parse the schedule Md5 return for stationId 90458 (EINSPHD) on 2018-06-17 and after.
[17/06/2018 06:01:10] [WARNG] Failed to parse the schedule Md5 return for stationId 74915 (EINSPLS) on 2018-06-17 and after.
[17/06/2018 06:01:10] [WARNG] Failed to parse the schedule Md5 return for stationId 83868 (ZDFKUHD) on 2018-06-17 and after.
[17/06/2018 06:01:10] [WARNG] Failed to parse the schedule Md5 return for stationId 67299 (ZDFKULG) on 2018-06-17 and after.
[17/06/2018 06:01:16] [ INFO] Successfully retrieved 234 station's daily schedules.
[17/06/2018 06:01:45] [ INFO] Successfully retrieved Md5s for 129 station's daily schedules.
[17/06/2018 06:01:45] [WARNG] Failed to parse the schedule Md5 return for stationId 74767 (CALGR) on 2018-06-17 and after.
[17/06/2018 06:01:45] [WARNG] Failed to parse the schedule Md5 return for stationId 16345 (DW) on 2018-06-17 and after.
[17/06/2018 06:01:48] [ INFO] Successfully retrieved 127 station's daily schedules.
[17/06/2018 06:01:56] [ INFO] Found 5902 cached daily schedules.
[17/06/2018 06:01:56] [ INFO] Downloaded 1630 daily schedules.
[17/06/2018 06:02:26] [WARNG] Time discontinuity detected. Service 103634 (KEEPIC) SH012857740000 (entry 213) ends at 2018-06-25 08:00:00Z, SH026953150000 (entry 214) starts at 2018-06-25 00:00:00Z.
[17/06/2018 06:02:26]         No further discontinuities on KEEPIC will be reported for 2018-06-25.
[17/06/2018 06:02:55] [WARNG] Time discontinuity detected. Service 87335 (C8FR) SH012857740000 (entry 79) ends at 2018-06-22 05:45:00Z, SH019655550000 (entry 80) starts at 2018-06-22 04:45:00Z.
[17/06/2018 06:02:55]         No further discontinuities on C8FR will be reported for 2018-06-22.
[17/06/2018 06:02:55] [WARNG] Time discontinuity detected. Service 87335 (C8FR) SH012857740000 (entry 124) ends at 2018-06-25 05:45:00Z, SH019655550000 (entry 125) starts at 2018-06-25 04:45:00Z.
[17/06/2018 06:02:55]         No further discontinuities on C8FR will be reported for 2018-06-25.
[17/06/2018 06:02:56] [WARNG] Time discontinuity detected. Service 52091 (CNEWSFR) SH012857740000 (entry 67) ends at 2018-06-21 04:22:00Z, SH029587960000 (entry 68) starts at 2018-06-21 04:00:00Z.
[17/06/2018 06:02:56]         No further discontinuities on CNEWSFR will be reported for 2018-06-21.
[17/06/2018 06:02:56] [WARNG] Time discontinuity detected. Service 52091 (CNEWSFR) SH012857740000 (entry 81) ends at 2018-06-22 04:22:00Z, SH029587960000 (entry 82) starts at 2018-06-22 04:00:00Z.
[17/06/2018 06:02:56]         No further discontinuities on CNEWSFR will be reported for 2018-06-22.
[17/06/2018 06:02:56] [WARNG] Time discontinuity detected. Service 52091 (CNEWSFR) SH012857740000 (entry 155) ends at 2018-06-26 04:22:00Z, SH029587960000 (entry 156) starts at 2018-06-26 04:00:00Z.
[17/06/2018 06:02:56]         No further discontinuities on CNEWSFR will be reported for 2018-06-26.
[17/06/2018 06:02:56] [WARNG] Time discontinuity detected. Service 52091 (CNEWSFR) SH012857740000 (entry 185) ends at 2018-06-28 04:22:00Z, SH029587960000 (entry 186) starts at 2018-06-28 04:00:00Z.
[17/06/2018 06:02:56]         No further discontinuities on CNEWSFR will be reported for 2018-06-28.
[17/06/2018 06:02:56] [WARNG] Time discontinuity detected. Service 52091 (CNEWSFR) SH012857740000 (entry 199) ends at 2018-06-29 04:22:00Z, SH029587960000 (entry 200) starts at 2018-06-29 04:00:00Z.
[17/06/2018 06:02:56]         No further discontinuities on CNEWSFR will be reported for 2018-06-29.
[17/06/2018 06:03:23] [WARNG] Time discontinuity detected. Service 38359 (DEUROSP) SH012857740000 (entry 397) ends at 2018-07-02 04:35:00Z, EP023806550230 (entry 398) starts at 2018-07-02 04:25:00Z.
[17/06/2018 06:03:23]         No further discontinuities on DEUROSP will be reported for 2018-07-02.
[17/06/2018 06:03:23] [WARNG] Time discontinuity detected. Service 38359 (DEUROSP) SH012857740000 (entry 488) ends at 2018-07-06 05:15:00Z, SH025204650000 (entry 489) starts at 2018-07-06 04:45:00Z.
[17/06/2018 06:03:23]         No further discontinuities on DEUROSP will be reported for 2018-07-06.
[17/06/2018 06:04:03] [ INFO] Processed 7532 daily schedules for 367 stations.
[17/06/2018 06:04:03] Exiting getAllScheduleEntryMd5s(). SUCCESS.
[17/06/2018 06:04:03] Entering buildAllProgramEntries() for 42000 programs.
[17/06/2018 06:12:09] [ INFO] Found 39633 cached program descriptions.
[17/06/2018 06:12:12] [ INFO] Successfully retrieved 2367 program descriptions.
[17/06/2018 06:12:35] [ INFO] Processed 42000 program descriptions.
[17/06/2018 06:12:35] Exiting buildAllProgramEntries(). SUCCESS.
[17/06/2018 06:12:35] Entering buildAllGenericSeriesInfoDescriptions() for 10002 series.
[17/06/2018 06:13:45] [ INFO] Found 9695 cached series descriptions.
[17/06/2018 06:13:46] [ INFO] Successfully retrieved 307 generic program descriptions.
[17/06/2018 06:13:47] [ INFO] Processed 10002 series descriptions.
[17/06/2018 06:13:48] Exiting buildAllGenericSeriesInfoDescriptions(). SUCCESS.
[17/06/2018 06:13:48] Entering getAllMoviePosters() for 1553 movies.
[17/06/2018 06:13:48] [ INFO] Found 792 cached movie poster links.
[17/06/2018 06:13:48] [ INFO] Successfully retrieved artwork info for 500 programs.
[17/06/2018 06:13:50] [ INFO] Successfully retrieved artwork info for 261 programs.
[17/06/2018 06:13:51] [ INFO] Processed 1553 movie poster links.
[17/06/2018 06:13:51] Exiting getAllMoviePosters(). SUCCESS.
[17/06/2018 06:13:51] Entering getAllSeriesImages() for 10002 series.
[17/06/2018 06:13:51] [ INFO] Found 6599 cached series image links.
[17/06/2018 06:13:51] [ INFO] Successfully retrieved artwork info for 500 programs.
[17/06/2018 06:13:53] [ INFO] Successfully retrieved artwork info for 500 programs.
[17/06/2018 06:13:54] [ INFO] Successfully retrieved artwork info for 500 programs.
[17/06/2018 06:13:56] [ INFO] Successfully retrieved artwork info for 500 programs.
[17/06/2018 06:13:57] [ INFO] Successfully retrieved artwork info for 500 programs.
[17/06/2018 06:13:58] [ INFO] Successfully retrieved artwork info for 500 programs.
[17/06/2018 06:14:00] [ INFO] Successfully retrieved artwork info for 403 programs.
[17/06/2018 06:14:00] [ INFO] Processed 10002 series image links.
[17/06/2018 06:14:00] Exiting getAllSeriesImages(). SUCCESS.
[17/06/2018 06:14:00] [ INFO] Completed compiling keywords and keyword groups.
[17/06/2018 06:14:00] Entering writeMxf().
[17/06/2018 06:14:03] [ INFO] Completed save of mxf file.
[17/06/2018 06:14:03] Exiting writeMxf(). SUCCESS.
[17/06/2018 06:14:03] Entering writeImageArchive().
[17/06/2018 06:14:03] [ INFO] Completed save of image archive file.
[17/06/2018 06:14:03] Exiting writeImageArchive(). SUCCESS.
[17/06/2018 06:14:12] [ INFO] 4132 files deleted from the cache directory during cleanup.
[17/06/2018 06:14:12] [ INFO] Generated .mxf file contains 367 services, 10002 series, 42000 programs, and 42759 people with 10526 image links.
[17/06/2018 06:14:12] [ INFO] Completed EPG123 update execution. SUCCESS.
[17/06/2018 06:14:12] [ INFO] epg123 update execution time was 00:14:10.4372358.
[17/06/2018 06:14:14] ===============================================================================
[17/06/2018 06:14:14]  Beginning epg123 client execution.
[17/06/2018 06:14:14] ===============================================================================
[17/06/2018 06:14:14] [ INFO] Beginning epg123 client execution. 2018-06-17 05:14:14Z
[17/06/2018 06:14:14] [ INFO] Import: True , Match: False , NoLogo: False , Force: False , ShowProgress: False
[17/06/2018 06:14:14] [ INFO] epg123 client version: 1.2.0 for Win8.1
[17/06/2018 06:14:21] Entering importMxfFile() for file "C:\utils\epg123\epg123.mxf"
[17/06/2018 06:18:06] [ INFO] Error: The following error was encountered while processing the file. Aborting.
[17/06/2018 06:18:06] [ INFO] StartTime must be specified for first ScheduleEntry in a block
[17/06/2018 06:18:11] [ERROR] Error using loadmxf.exe to import new guide information. Exit code: -1
[17/06/2018 06:18:11] Exiting importMxfFile(). FAILURE.
[17/06/2018 06:18:11] [ERROR] Failed to import .mxf file. Exiting.

User avatar
garyan2

Posts: 7438
Joined: Fri Nov 27, 2015 7:23 pm
Location:

HTPC Specs: Show details

#4

Post by garyan2 » Sun Jun 17, 2018 7:57 am

I can't find anything wrong in your mxf file. I also created my own mxf file with both of your lineups, all stations, and 21 days and imported successfully with no issues (I did have the same md5 and time discontinuity warnings as you did).

I'm thinking there may be something wrong with your database, but before we try a database rebuild, I would suggest you use the epg123 configuration GUI and reduce your days to download to '1' day. Do a Save&Execute... this will clear out a lot of your cache while creating a new and smaller mxf file. If that file imports just fine, then try a Save&Execute with 7 days, 14 days, or go straight to 21 days again. If the imports don't work, then you'll have to do a [Rebuild WMC Database]. Doing a rebuild will cause your recorded history to be cleared out so all your repeat recordings will be repeated. Otherwise it'll be just fine.

EDIT: For a final check, I imported your mxf file into my WMC database without issues as well. This supports the idea the problem is with your database.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

technodevotee

Posts: 963
Joined: Thu Sep 10, 2015 4:10 pm
Location: West Midlands

HTPC Specs: Show details

#5

Post by technodevotee » Tue Jun 19, 2018 5:45 am

Thanks Gary, didn't get a notification of your message.

I was monitoring one of the PCs with RESMON this morning while EPG123 was running and loadmxf does seem to complete properly as there is a lot of disk write activity on the database and the file size changed.

The re-index isn't being run however so I manually ran a re-index and then a garbage collection to see what happens. Last time I ran a garbage collection it took two days to complete so it will be a while before I know whether it has made any difference.

I'll disable the EPG123 schedule until it has completed and let you know what happened next time it runs.

If there is no change, I'll try your suggestion of setting it to 1 day's worth of updates.

Seems a bit of a coincidence that two PCs running independently of each other should both have database corruption on the same day though.

Thanks again.

User avatar
garyan2

Posts: 7438
Joined: Fri Nov 27, 2015 7:23 pm
Location:

HTPC Specs: Show details

#6

Post by garyan2 » Tue Jun 19, 2018 7:19 am

technodevotee wrote:Seems a bit of a coincidence that two PCs running independently of each other should both have database corruption on the same day though.
I agree. Very strange, but the only thing I can think of. The only thing I have to support it is my test bench here was able to download and import 2 of your lineups and was also able to import the mxf file you provided me without any issues. That would rule out any problems with the mxf file and downloaded data from SD (at that time).

It could very well be that one of the programs downloaded from SD had an incorrectly formatted date/time start time that got carried into the mxf file ... but again, there wasn't any issue in the mxf file you provided.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

technodevotee

Posts: 963
Joined: Thu Sep 10, 2015 4:10 pm
Location: West Midlands

HTPC Specs: Show details

#7

Post by technodevotee » Tue Jun 19, 2018 9:10 am

Yes, it seems that the mxf file is OK as it imported fine this morning and now that the garbage collection has finished I see that the guide end date is 5th July and new scheduled recordings have been added.

I purposely haven't done anything to the other PC so that I can see if there is any difference between them when EPG123 runs tomorrow.

I'll keep you posted.

technodevotee

Posts: 963
Joined: Thu Sep 10, 2015 4:10 pm
Location: West Midlands

HTPC Specs: Show details

#8

Post by technodevotee » Wed Jun 20, 2018 5:30 am

EPG123 mxf import worked without error on my Living Room PC this morning as did the re-index task.

Looks like there was a bit of bad data in the database as you suspected and running the garbage collection sorted it out.

Haven't checked the other PC yet but that is the one with the 'simple' config so I'm not expecting it to be an issue.

Thanks again for your help.

technodevotee

Posts: 963
Joined: Thu Sep 10, 2015 4:10 pm
Location: West Midlands

HTPC Specs: Show details

#9

Post by technodevotee » Thu Jun 21, 2018 4:19 pm

I ran a re-index and garbage collection on my second PC last night and that automatically updated, imported the mxf and re-indexed without errors this morning as well.

So everything is fine again thanks.

technodevotee

Posts: 963
Joined: Thu Sep 10, 2015 4:10 pm
Location: West Midlands

HTPC Specs: Show details

#10

Post by technodevotee » Sun Jun 24, 2018 5:55 am

The daily update works for a couple of days but then starts giving errors importing the mxf and the re-index doesn't run.

Going back through the logs, I can see that it has been doing this for a while but I hadn't noticed it until recently.

Running a garbage collection seems to help but is there a way of finding out what is actually causing the problem?

Any enhanced logging I can enable for example?

User avatar
garyan2

Posts: 7438
Joined: Fri Nov 27, 2015 7:23 pm
Location:

HTPC Specs: Show details

#11

Post by garyan2 » Sun Jun 24, 2018 3:40 pm

technodevotee wrote:The daily update works for a couple of days but then starts giving errors importing the mxf and the re-index doesn't run.

Going back through the logs, I can see that it has been doing this for a while but I hadn't noticed it until recently.

Running a garbage collection seems to help but is there a way of finding out what is actually causing the problem?

Any enhanced logging I can enable for example?
No more logging on the epg123 side. There is a way to make WMC log a ridiculous amount but can't recall how to do that right now. You would get a log file probably >1GB for an import like yours.

The error you are getting makes it sound like it is due to the mxf file created by epg123, so I am a little concerned that there is an invalid timestamp from SD. All epg123 does with the time is remove the 'Z' at the end of it ('2018-06-24T00:00:00Z' -> '2018-06-24T00:00:00'). However there was no evidence that was the case with the mxf file you sent me or the data I downloaded from SD for your lineups. I will try again to see if I can capture anything there.

If the above is the cause, maybe you could delay your updates an hour? I might not be able to recreate due to the time of day I download.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

User avatar
garyan2

Posts: 7438
Joined: Fri Nov 27, 2015 7:23 pm
Location:

HTPC Specs: Show details

#12

Post by garyan2 » Sun Jun 24, 2018 4:09 pm

Actually, no need to delay your update... you can easily test the theory by manually doing a Save&Execute.

I just downloaded and imported all 3 of your lineups as well as your old mxf file into a WMC7 machine. I still didn't have the timestamp error, but I see you are still getting a lot of time discontinuities. You might want to submit a ticket with SD concerning the discontinuities ... it may be related. If you see a "[WARNG] Failed to parse the schedule Md5 ..." in your trace.log file, this means that channel had no data which is also a problem from SD.

EDIT: I also noticed that with all 3 lineups, I am only getting 304 stations compared with 367 stations you had with only 2 lineups a week ago. Another question for SD, I guess.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

technodevotee

Posts: 963
Joined: Thu Sep 10, 2015 4:10 pm
Location: West Midlands

HTPC Specs: Show details

#13

Post by technodevotee » Sun Jun 24, 2018 8:15 pm

Thanks Gary.

I'll try that and see what happens.

Surprised that no-one else here has reported the same problem though.

technodevotee

Posts: 963
Joined: Thu Sep 10, 2015 4:10 pm
Location: West Midlands

HTPC Specs: Show details

#14

Post by technodevotee » Fri Jul 13, 2018 7:16 am

I still have a cycle of success for a few days followed by failure for a few days on both PCs.

I have removed ASTRA 19.2 from the Living Room PC so it is just using ASTRA 28.8 to see if that makes a difference.

I haven't flagged it to SD because it is pretty intermittent and I am surprised that no-one else here seems to be reporting the same issue.

I also don't understand why it is happening on two machines using different line-ups.

User avatar
garyan2

Posts: 7438
Joined: Fri Nov 27, 2015 7:23 pm
Location:

HTPC Specs: Show details

#15

Post by garyan2 » Fri Jul 13, 2018 3:08 pm

Are you still getting the same StartTime error?

Code: Select all

Entering importMxfFile() for file "C:\utils\epg123\epg123.mxf"
[ INFO] Error: The following error was encountered while processing the file. Aborting.
[ INFO] StartTime must be specified for first ScheduleEntry in a block
[ERROR] Error using loadmxf.exe to import new guide information. Exit code: -1
Exiting importMxfFile(). FAILURE.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

technodevotee

Posts: 963
Joined: Thu Sep 10, 2015 4:10 pm
Location: West Midlands

HTPC Specs: Show details

#16

Post by technodevotee » Fri Jul 13, 2018 3:21 pm

Yes, that's the error.

I thought that running a garbage collection was helping it but it just have been coincidence because it hasn't made any difference today.

I tried manually importing the newly created mxf on each PC and it failed on both of them.

In the past, it seems to have failed at different places in each mxf but this morning they both failed after importing the same amount of data.

User avatar
garyan2

Posts: 7438
Joined: Fri Nov 27, 2015 7:23 pm
Location:

HTPC Specs: Show details

#17

Post by garyan2 » Fri Jul 13, 2018 3:34 pm

Could you send that mxf file to me so I can inspect it?

Thank you,
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

technodevotee

Posts: 963
Joined: Thu Sep 10, 2015 4:10 pm
Location: West Midlands

HTPC Specs: Show details

#18

Post by technodevotee » Tue Jul 24, 2018 6:20 am

I'm still getting this 'StartTime' error on both PCs despite having disabled MS updates and running a garbage collection.

It works for a couple of days and fails for a couple of days.

I was told by someone that the listing data downloaded for satellite and terrestrial was exactly the same but I have seen differences between the PCs in the past so that can't be strictly true can it?

Due to a combination of these and other issues with my second PC, I have permanently moved the quad DVB-T2 tuner into what was the spare PC and the download successfully imports into the database on there, which gives credence to your belief that the issue isn't to do with SD or EPG123 and may be database errors. But why both PCs and why does it work for a few days and fail for a few days?

I went back through the logs and it seems that the problem started on the 6th June 2018.

Resolving the issue on the Living Room PC is harder because the last time I set up Media Center from scratch it took me two solid days to get it back as it was.

Can you think of anything else I can try first?

User avatar
garyan2

Posts: 7438
Joined: Fri Nov 27, 2015 7:23 pm
Location:

HTPC Specs: Show details

#19

Post by garyan2 » Tue Jul 24, 2018 6:41 am

Go for the [Rebuild WMC Database] button. It will delete the database but restore all your tuner configurations, custom names and numbers, favorite lineups, and scheduled recordings. You will just lose your recording history. If the problem persists, then you have something else going on. It's a pretty quick process and you will just need to manually import your latest mxf file to get the listings back in the guide.

You could do this on 1 machine to see if it works before trying on the other.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

technodevotee

Posts: 963
Joined: Thu Sep 10, 2015 4:10 pm
Location: West Midlands

HTPC Specs: Show details

#20

Post by technodevotee » Thu Jul 26, 2018 10:16 am

Thanks Gary,

It worked again this morning without me doing anything.

Just don't get it but as long as it works OK every few days I'm going to leave it alone at the moment.

Post Reply