Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 1165568" data-attributes="member: 82144">Ahh, you're right - there's only one &quot;debug&quot; entry in the log file that you provided, and I missed it. Just wanted to make sure. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />Okay. I will be here and ready! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin&nbsp; &nbsp; :D" loading="lazy" data-shortname=":D" />The TV service log file that your provided is &quot;cut off&quot;. Loading was done successfully, but it was done before the start of the log file so I cannot see it. That's why I asked for a new log.Ahhh, very interesting.TV Server should detect the tuner as soon as Windows detects it (ie. when it is plugged in).So, does the machine crash as soon as the tuner is plugged in? ...or what do you mean by &quot;access&quot;?I suspect &quot;access&quot; might mean &quot;load&quot;, and that's why I asked for the loading log files.In general you might be right. If you get a kernel error during boot then the driver must surely be incompatible with W10... unless that error is triggered by TV Server attempting to preload the tuner.Yes, the log files are the part that I wanted to see. Hopefully you will have a chance to grab them in future.Thanks for all the info. It's a very interesting problem/situation for me. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /></blockquote>

[QUOTE="mm1352000, post: 1165568, member: 82144"] Ahh, you're right - there's only one "debug" entry in the log file that you provided, and I missed it. Just wanted to make sure. :) Okay. I will be here and ready! :D The TV service log file that your provided is "cut off". Loading was done successfully, but it was done before the start of the log file so I cannot see it. That's why I asked for a new log. Ahhh, very interesting. TV Server should detect the tuner as soon as Windows detects it (ie. when it is plugged in). So, does the machine crash as soon as the tuner is plugged in? ...or what do you mean by "access"? I suspect "access" might mean "load", and that's why I asked for the loading log files. In general you might be right. If you get a kernel error during boot then the driver must surely be incompatible with W10... unless that error is triggered by TV Server attempting to preload the tuner. Yes, the log files are the part that I wanted to see. Hopefully you will have a chance to grab them in future. Thanks for all the info. It's a very interesting problem/situation for me. :) [/QUOTE]

Verification