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
MediaPortal 1 Plugins
HTPCInfo plugin v1.15.0 for MediaPortal 1.3.0 and higher
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="Micropolis" data-source="post: 1198324" data-attributes="member: 96567"><p>Hi [USER=128337]@joecrow[/USER], [USER=146416]@Nervesagent[/USER],</p><p></p><p></p><p>nobody has said that one of my plugins or tools are dead, but currently (and announced before) my main focus have my company, own corporate customers and the related journeys. Therefore I'm not able currently to maintain the plugins/tools in a regular cycle, hopefully with the beginning of 2017 I have more slots.</p><p></p><p>[USER=146416]@Nervesagent[/USER]: Your message does not help me (or other community members) to identify the root cause of your issue. In the manual of HTPCInfo TVServer Monitor you can find the following sentence: "This application requires installed MediaPortal libraries (e.g. TvControl.dll, TvLibrary.Interfaces.dll) and PowerScheduler libraries (PowerScheduler.Interfaces.dll) and their dependencies." Do you mean of this assemblies or others? Please prepare clear error reports and I'm sure, you will get the support which you want. Additionally you can check, if the installation/copying of files from <a href="https://forum.team-mediaportal.com/attachments/mediaportal-v1-3-tv-libraries-zip.132011/" target="_blank">this</a> library solve your issue.</p><p></p><p>[USER=128337]@joecrow[/USER]: Regarding your issue with Speedfan sensor data this thread contains a lot of solutions and best practices, e.g. the question how you label sensor names. Is the option "Build skin property from related sensor name" switch on (see manual page 5)? Does your skin support your personal labels? Do you have make modifications to the appropriate skin files according to your property names? There are a lot of questions, most of them are unanswered yet. Finally a short question to understand you better: Could you please explain the definition of "shame"? Is it a shame that developers or plugin authors does not find the time to give answers to each question in a timely manner? I would hold back at your point with certain terms.</p><p></p><p>Regards, Micropolis</p></blockquote><p></p>
[QUOTE="Micropolis, post: 1198324, member: 96567"] Hi [USER=128337]@joecrow[/USER], [USER=146416]@Nervesagent[/USER], nobody has said that one of my plugins or tools are dead, but currently (and announced before) my main focus have my company, own corporate customers and the related journeys. Therefore I'm not able currently to maintain the plugins/tools in a regular cycle, hopefully with the beginning of 2017 I have more slots. [USER=146416]@Nervesagent[/USER]: Your message does not help me (or other community members) to identify the root cause of your issue. In the manual of HTPCInfo TVServer Monitor you can find the following sentence: "This application requires installed MediaPortal libraries (e.g. TvControl.dll, TvLibrary.Interfaces.dll) and PowerScheduler libraries (PowerScheduler.Interfaces.dll) and their dependencies." Do you mean of this assemblies or others? Please prepare clear error reports and I'm sure, you will get the support which you want. Additionally you can check, if the installation/copying of files from [URL='https://forum.team-mediaportal.com/attachments/mediaportal-v1-3-tv-libraries-zip.132011/']this[/URL] library solve your issue. [USER=128337]@joecrow[/USER]: Regarding your issue with Speedfan sensor data this thread contains a lot of solutions and best practices, e.g. the question how you label sensor names. Is the option "Build skin property from related sensor name" switch on (see manual page 5)? Does your skin support your personal labels? Do you have make modifications to the appropriate skin files according to your property names? There are a lot of questions, most of them are unanswered yet. Finally a short question to understand you better: Could you please explain the definition of "shame"? Is it a shame that developers or plugin authors does not find the time to give answers to each question in a timely manner? I would hold back at your point with certain terms. Regards, Micropolis [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Plugins
HTPCInfo plugin v1.15.0 for MediaPortal 1.3.0 and higher
Contact us
RSS
Top
Bottom