Reply to thread

Message

<blockquote data-quote="HenriM" data-source="post: 337014" data-attributes="member: 10451">This is really a serious issue, because I noticed that the settings after the [Remote] Settings seems not updated anymore due to this configuration application bug.I investigated this a little further and I noticed that something is wrong in the SerialUIR part. As a test I adapted the next configuration-file manually:C:\Users\All Users\Team MediaPortal\MediaPortal\MediaPortal.xmlIn the section&nbsp; &quot;SerialUIR&quot; I changed&nbsp; &nbsp; &lt;entry name=&quot;commport&quot;&gt;COM1:&lt;/entry&gt;into&nbsp; &nbsp; &lt;entry name=&quot;commport&quot;&gt;&lt;/entry&gt;Now you will notice that the next time you start-up the configuration application this will succeed without any COM error message-box.However as soon as I press the [OK] button of the Configuration Application again, I see that it's again updated with COM1:. This causes with the next startup again the mentioned COM error message-box.I also suspecting that settings after [Remote] are not updated anymore due to this problem. As a test I changed the VideoRenderer Settings from VMR9 into EVR and this seems not 'remember' after pressing [OK] and restarting configuration application.Interesting enough the behaviour of the Configuration Application is not consistent among my PC's I have. I don't have the issue with my Shuttle, but do have it with my Server (Asus P5B-V MOBO). The OS is the same (Vista Ultimate). I also tried adapting COM-Port Settings in my BIOS, but to no avail yet...I keep investigating this issue.[edit: Workaround found]I found a workaround for the problem:Disable your COM port in the BIOS settings of your motherboard.Now the settings after [Remote] are also 'remembered'.</blockquote>

[QUOTE="HenriM, post: 337014, member: 10451"] This is really a serious issue, because I noticed that the settings after the [Remote] Settings seems not updated anymore due to this configuration application bug. I investigated this a little further and I noticed that something is wrong in the SerialUIR part. As a test I adapted the next configuration-file manually: C:\Users\All Users\Team MediaPortal\MediaPortal\MediaPortal.xml In the section "SerialUIR" I changed <entry name="commport">COM1:</entry> into <entry name="commport"></entry> Now you will notice that the next time you start-up the configuration application this will succeed without any COM error message-box. However as soon as I press the [OK] button of the Configuration Application again, I see that it's again updated with COM1:. This causes with the next startup again the mentioned COM error message-box. I also suspecting that settings after [Remote] are not updated anymore due to this problem. As a test I changed the VideoRenderer Settings from VMR9 into EVR and this seems not 'remember' after pressing [OK] and restarting configuration application. Interesting enough the behaviour of the Configuration Application is not consistent among my PC's I have. I don't have the issue with my Shuttle, but do have it with my Server (Asus P5B-V MOBO). The OS is the same (Vista Ultimate). I also tried adapting COM-Port Settings in my BIOS, but to no avail yet... I keep investigating this issue. [edit: Workaround found] I found a workaround for the problem: Disable your COM port in the BIOS settings of your motherboard. Now the settings after [Remote] are also 'remembered'. [/QUOTE]

Verification