Reply to thread

Message

<blockquote data-quote="DragonQ" data-source="post: 1028626" data-attributes="member: 115209">I upgraded my main system to Windows 8.1 and I wish I hadn't. Can't reboot or shut down any more, but the main problem is MediaPortal doesn't start. Should've checked whether 1.4.0 supported Windows 8.1 but I don't really understand why the developers would purposefully block future OS numbers instead of just having the &quot;unsupported OS&quot; message but oh well, lesson learned. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite3" alt=":(" title="Frown&nbsp; &nbsp; :(" loading="lazy" data-shortname=":(" />Where exactly in the database do the tuner names need changing for Custom Data Grabber to recognise them both? I had a similar issue with MDAPI because it would use the tuner names to uniquely identify them. Of course, they were the same, so I needed to do some manual tweaking to get it to work with both of them. It's a bit weird that Custom Data Grabber now has the same problem when it didn't before...</blockquote>

[QUOTE="DragonQ, post: 1028626, member: 115209"] I upgraded my main system to Windows 8.1 and I wish I hadn't. Can't reboot or shut down any more, but the main problem is MediaPortal doesn't start. Should've checked whether 1.4.0 supported Windows 8.1 but I don't really understand why the developers would purposefully block [i]future[/i] OS numbers instead of just having the "unsupported OS" message but oh well, lesson learned. :( Where exactly in the database do the tuner names need changing for Custom Data Grabber to recognise them both? I had a similar issue with MDAPI because it would use the tuner names to uniquely identify them. Of course, they were the same, so I needed to do some manual tweaking to get it to work with both of them. It's a bit weird that Custom Data Grabber now has the same problem when it didn't before... [/QUOTE]

Verification