home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Support
General Support
MediaPortal 1.13 and Windows 10 Crash
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Brownard" data-source="post: 1194524" data-attributes="member: 48291"><p>In short no <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink ;)" loading="lazy" data-shortname=";)" /> but I believe his changes were primarily made to allow the custom version to upgrade existing installations of MP. Previously existing installs had to be removed and the custom version installed from scratch.</p><p></p><p>I don't think he ever made his changes public , I believe that when upgrading from an official MP release there are some missing column in the DB which ears' code added, if I recall correctly this didn't occur in fresh installs of the custom release, only when trying to upgrade an official install of MP.</p><p>The installer changes were to remove the check that the installer does to not allow upgrades from non official releases of MP, so it became possible to upgrade an existing installation of the custom release.</p><p></p><p></p><p>I have previously had a look at decompiling the binaries which works reasonably well, I'm willing to offer tentative support for rewriting the plugins from the decompilation if this will help support this making it into an official release.</p><p></p><p>I run this build on my main HTPC because it basically gives a 1 click setup of TV, all channels are found, grouped, the correct regional variations of the channels are selected and epg is grabbed. All in under 5 minutes and without any user input <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p></blockquote><p></p>
[QUOTE="Brownard, post: 1194524, member: 48291"] In short no ;) but I believe his changes were primarily made to allow the custom version to upgrade existing installations of MP. Previously existing installs had to be removed and the custom version installed from scratch. I don't think he ever made his changes public , I believe that when upgrading from an official MP release there are some missing column in the DB which ears' code added, if I recall correctly this didn't occur in fresh installs of the custom release, only when trying to upgrade an official install of MP. The installer changes were to remove the check that the installer does to not allow upgrades from non official releases of MP, so it became possible to upgrade an existing installation of the custom release. I have previously had a look at decompiling the binaries which works reasonably well, I'm willing to offer tentative support for rewriting the plugins from the decompilation if this will help support this making it into an official release. I run this build on my main HTPC because it basically gives a 1 click setup of TV, all channels are found, grouped, the correct regional variations of the channels are selected and epg is grabbed. All in under 5 minutes and without any user input :) [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
General Support
MediaPortal 1.13 and Windows 10 Crash
Contact us
RSS
Top
Bottom