Code: Select all
c:\temp\epg123client -i c:\programdata\garyan2\epg123\output\epg123.mxf -nogc -verbose
Thank you,
Code: Select all
c:\temp\epg123client -i c:\programdata\garyan2\epg123\output\epg123.mxf -nogc -verbose
All, I have replaced the zip file for v1.5.0.40 to include a .config file for .NET. I forgot that without the installer setting things up for you, a "portable" install needs that file for Win7.garyan2 wrote: ↑Wed Oct 28, 2020 4:29 pm For those having problems with the verification, could you please download epg123client.exe v1.5.0.40. Extract it to a temporary folder and run the following command from a command prompt. The example is with the exe in the c:\temp folder and using the default MXF file location... replace folder paths as necessary.This version does not perform an import, it just does the verification so it should take <30 seconds to complete. Please send the trace.log file (c:\temp\trace.log) to support@garyan2.net.Code: Select all
c:\temp\epg123client -i c:\programdata\garyan2\epg123\output\epg123.mxf -nogc -verbose
Thank you,
When epg123 performs a garbage cleanup, it writes a date/time in the registry 4 days and 12 hours in the future. So for any imports, if the registry value is in the past, it will kickoff a garbage collection. The command is "c:\windows\ehome\mcupdate.exe -dbgc -updatetrigger" (without quotes). The -UpdateTrigger just prevents mcupdate from trying to download/update packages from the MS servers which are turned off.
1.5.0.20 seems to have fixed the problem for at least two people in this thread (myself and The Mac), I know you said you made one small change (other than the extra logging), so that may have fixed at least one of the problems causing this (although I think at least one person still had the issue with 1.5.0.20).garyan2 wrote: ↑Thu Oct 29, 2020 12:21 am I might have to abandon this. Even having all my interactions with the database inside a try/catch, embedded in a try/catch, which is embedded in a try/try catch, the process can still be terminated. The only thing I can think of is what I see in the client when I add or undelete a channel. Ten seconds after I do that, WMC fires off some PVR task which kills all threads connecting to the database and that is pretty much what is happening here.
I'm going to do a little more research, but I will probably post a new version with the verification process being optional (user will have to modify the task in order to enable it). I don't want to completely get rid of it yet. At least get a version out there that includes the fixes for problems with 1.4.x.x without the concern of the verification process causing epg123client not to complete.