Reply to thread

Message

<blockquote data-quote="Soxbrother" data-source="post: 945613" data-attributes="member: 80141">I think I found the problem.&nbsp;The first 2 times, I had the receiver plugged in when starting my pc.2 times the remote worked.&nbsp;The 3rd time I plugged it in after the startup of windows.The remote didn't work.&nbsp;The 4th &amp; 5th time plugged the receiver back in before I start the pcThe remote worked.&nbsp;The .lnk doesn't work, even when you put in the registry &quot;CurrentVersion\Run&quot;&nbsp;I know this because when I double click on the .lnk, the command prompt comes up,and does what it's supposed to do.Now I see no such thing when windows starts.I guess Windows 7 Home Premium, doesn't like to start .cmd and .lnk <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite12" alt="o_O" title="Er... what?&nbsp; &nbsp; o_O" loading="lazy" data-shortname="o_O" />&nbsp;So the solution is to keep that receiver plugged in at all times !!!!!!!!!!</blockquote>

[QUOTE="Soxbrother, post: 945613, member: 80141"] I think I found the problem. The first 2 times, I had the receiver plugged in when starting my pc. 2 times the remote worked. The 3rd time I plugged it in after the startup of windows. The remote didn't work. The 4th & 5th time plugged the receiver back in before I start the pc The remote worked. The .lnk doesn't work, even when you put in the registry "CurrentVersion\Run" I know this because when I double click on the .lnk, the command prompt comes up, and does what it's supposed to do. Now I see no such thing when windows starts. I guess Windows 7 Home Premium, doesn't like to start .cmd and .lnk o_O So the solution is to keep that receiver plugged in at all times !!!!!!!!!! [/QUOTE]

Verification