Bad com settings (3 Viewers)

[Aged]

TV-Server Version:RC/3
MediaPortal Version:RC/3
MediaPortal Skin:
Windows Version:XP PRO SP2
CPU Type: Intel Dual Core XEON X5272
HDD: 2 ea Seagate Cheetah 15K.5 400GB RAID 1
Memory: 4 GB
Motherboard: Supermicro X7DWA-N
Video Card: ASUS EAH3870X2 - ATI Chipset
Video Card Driver: ATI
Sound Card: Intel
Sound Card AC3:
Sound Card Driver:
1. TV Card: VisionTek TV Wonder HD600
1. TV Card Type:
1. TV Card Driver: ATI
2. TV Card:
2. TV Card Type:
2. TV Card Driver:
3. TV Card:
3. TV Card Type:
3. TV Card Driver:
4. TV Card:
4. TV Card Type:
4. TV Card Driver:
MPEG2 Video Codec:
MPEG2 Audio Codec:
h.264 Video Codec:
Satelite/CableTV Provider:
HTPC Case:
Cooling:
Power Supply:
Remote:
TV:
TV - HTPC Connection:

With RC3 TV Sercer Configuration works well, scanning and finding analog TV Channels, but MediaPortal Configuratin stops with a Microsoft .Net Framework Message Box. The contents of the box are as follows;

Unhandled exception...
Bad com settings

...

JH.commBase.commPortException: Bad Com settings

...

at MediaPortalSerialR.SerialVIR.SetPort (String Comm Port)
at MediaPortal.ConfigurationSections.Remote SerialVIR.ComPortCombo_Selected Index Changed(Object sender,Event Args e)

Can anyone suggest a way of correcting this problem?

 

[HenriM]

Same issue happens with me with RC4

 

[HenriM]

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'.