Reply to thread

Message

<blockquote data-quote="JimCatMP" data-source="post: 1224687" data-attributes="member: 103549">Missed 'two RX units' - now that is bizarre and a total buggeration<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite10" alt=":oops:" title="Oops!&nbsp; &nbsp; :oops:" loading="lazy" data-shortname=":oops:" />Occam would therefore suggest problem with system then - possibly the drivers are mincing the output before it gets as far as being recognised as valid keyboard input [W10 updates have a reputation<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite9" alt=":eek:" title="Eek!&nbsp; &nbsp; :eek:" loading="lazy" data-shortname=":eek:" />.&nbsp;&nbsp; Do you have keyboard plugged in at same time [assume yes otherwise with no IR you can't control system at all] so can you test with the keyboard unplugged [ideally from boot], also as per MM's suggestion check RX unit on another device - laptop would do, using the QiPress tool to confirm it?Cheers - JCMP</blockquote>

[QUOTE="JimCatMP, post: 1224687, member: 103549"] Missed 'two RX units' - now that is bizarre and a total buggeration:oops: Occam would therefore suggest problem with system then - possibly the drivers are mincing the output before it gets as far as being recognised as valid keyboard input [W10 updates have a reputation:eek:. Do you have keyboard plugged in at same time [assume yes otherwise with no IR you can't control system at all] so can you test with the keyboard unplugged [ideally from boot], also as per MM's suggestion check RX unit on another device - laptop would do, using the QiPress tool to confirm it? Cheers - JCMP [/QUOTE]

Verification