<br><br><div><span class="gmail_quote">On 11/5/06, <b class="gmail_sendername">Brian Wood</b> <<a href="mailto:beww@beww.org">beww@beww.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
v 5, 2006, at 1:52 PM, William Pettersson wrote:<br><br>>><br>> Bad idea. Home brew serial port transmitters rarely use RS232<br>> signalling. They actually just hijack the port, disable regular RS232<br>> comms, and then signal by manually toggling different wires. Of
<br>> course,<br>> doing this over USB means the USB device needs to also support manual<br>> toggling of all (or at least some) of the various wires.<br><br><br>Quite right, and I am sure the reason the LIRC folks said it was a
<br>bad idea.<br><br>I was thinking of the MyBlaster device, which is known to work well<br>with the USB-to-Serial converters, but it uses true RS-232 signaling.<br><br>But of course The MyBlaster costs $$$, as does a serial port card.
<br>The OP indicated that a port card had some sort of problem, not sure<br>why.<br><br>But the solution might just come down to available slots on the<br>motherboard, the MyBlaster not requiring one and a port card doing
<br>so. Some modern motherboards do have two serial ports, I have a<br>Gigabyte K8NSC-939 that has 2 serial and 5 PCI slots, it would<br>probably make a nice Myth system.<br>_______________________________________________
<br>mythtv-users mailing list<br><a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br><a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
</a><br></blockquote></div>no. both receivers use the same codes. they are identical and when i
used the old machine i had no problem but i had two serial ports.<br>
<br>
so what i am looking for is a system that can control two identical
receivers. before i had to turn one around backwards so one did not
interfere with the other.<br>
<br>
Thanks Guys.<br>
<br>
Brian.<br><br>