Windows XP SP2 and IR 5.15

Hahnter · Post by **Hahnter** » Thu Oct 14, 2004 1:52 pm

Hi,

I have a computer with XP SP2 an a OFA URC-7552. To get the remote connected to the computer i build the simple interface rev. 5. My problem is, that i get no connection. The connection test always say : "No response from interface. Make sure that the interface is connected to the PC, and that you've specified the correct port."

I tried the following things:
- different transmission delays
- with and without batteries in the remote
- LPT as standard and EPP/ECP
- without the interface but pin 2 and 11 shorted
- with nothing at the lpt port

The last to points make me think, that the problems is in my computer. What can it be?

Greetings,
Sebastian

BTW. same problem on a notebook with XP SP2 too.

Mark Pierson · Post by **Mark Pierson** » Thu Oct 14, 2004 2:01 pm

For starters, you are using an account with Admin rights, correct?

The LPT port is enabled and configured in both the BIOS and Windows Device Manger (and the LPT port the PC is using matches what IR is using)?

Are you using any printer software (i.e. drivers) that might be hogging the port?

Have you verified that the interface is properly constructed?

Nils_Ekberg · Post by **Nils_Ekberg** » Thu Oct 14, 2004 2:29 pm

Also make sure that the PC and IR are set for the same port like 378 or 278.

Check it by going to tools in IR and clicking on Parallel. Then check it on the PC in the bios settings for the LPT

Hahnter · Post by **Hahnter** » Thu Oct 14, 2004 11:41 pm

Hi,

thank you for the hints, but it's all set up properly. Port of LPT is in bios, Windows and IR 378. Some weeks ago I had a printer connected to this port, so I think it's ok. The driver is totally removed, of course. But correct me if I am wrong, I thought that no user program under NT/2000/XP has direct access to hardware ports. So IR should communicate with the LPT over the WinAPI. Does IR really works under XP?

Greetings,
Sebastian

Post by **The Robman** » Fri Oct 15, 2004 6:33 am

When XP first came out, we did indeed have problems with IR for the very reasons you state, but then we found PortTalk, which is a Windows NT/2000 I/O Port Device Driver. It's "allowio.exe" program let's you communicate with the port, so we built this into IR. The only caveat is that you need to be logged on with admin rights, hence Mark's question.

Nils_Ekberg · Post by **Nils_Ekberg** » Fri Oct 15, 2004 7:42 am

You beat me to it Rob.

I am on Win XP sp2 also so I just went and tried to run IR from a none admin ID and had the same problem.

Hahnter · Post by **Hahnter** » Fri Oct 15, 2004 11:16 am

The account I am using has administrative rights but has not the name "Administrator" is it that, that you mean with ID?

Greetings,
Sebastian

Post by **The Robman** » Fri Oct 15, 2004 11:44 am

Log on as "Administrator" and see if it works, then you'll have answered your own question. If it does, maybe you didn't give your personal account as much power as you thought.

AndyInNYC · Post by **AndyInNYC** » Sat Oct 16, 2004 2:54 pm

While this may not help, I found that my 15-2117 wouldn't talk to the port while my 6131 did (this is under Windows 2000 Pro). I changed the transmission delay under the Advanced menu choice (I selected the slowest speed setting). Both remotes now communicate through IR (and since the amount of info being sent isn't huge, the delay is only a few seconds total for a download).

Andrew

Hahnter · Post by **Hahnter** » Sun Oct 17, 2004 8:21 am

Hi,

I have good news. I tried it under the original Admin-Account and I have tried to start it witch "allowio 0x378 ir.exe". Finally I tried another Notebook with Win98SE but the same problem. I realy don´t know where my fault is. LPT is working on all three computers at port 378. Delay is set to 750. I really despair of this.

Greetings,
Sebastian

Mark Pierson · Post by **Mark Pierson** » Sun Oct 17, 2004 8:57 am

Hahnter wrote:I really despair of this.

I assume this means you still cannot get the interface to work?

I'd suggest at this point that you go back and double-check all the connections on the interface to make sure that they're correct. You especially want to ensure that the diode is in the proper orientation. Since you mentioned you tried on a notebook, it's possible that you'll need to replace the standard diode with a Schottky type, since voltages on a laptop's printer port are generally lower than those of a desktop.

What size resistors did you use? Earlier designs used 10k while the latest calls for 1k.

sergioe · Post by **sergioe** » Sat Oct 23, 2004 7:01 pm

I am experiencing the same problem. IR 5.15 doesn't recognize my remote (RS 15-2116) in my PC running Win XP Pro SP2. The same remote and cable work well in another PC running Win 2000 SP4.

I checked that the program is set to LPT1, that my accout has adminstrative rights and tried to add transmission delays. Nothing worked!

My guess is that the parallel port driver may not work with XP SP2. Anyone out there with a similar configuration that works?

Any help is much appreciated.

Thanks,
Sergio

Mark Pierson · Post by **Mark Pierson** » Sat Oct 23, 2004 7:44 pm

sergioe wrote:IR 5.15 doesn't recognize my remote (RS 15-2116) in my PC running Win XP Pro SP2.

Have you tried it with and without batteries?

sergioe · Post by **sergioe** » Sun Oct 24, 2004 3:56 pm

I also tried removing the batteries, and it still didn't work.

Sergio

Capn Trips · Post by **Capn Trips** » Sun Oct 24, 2004 5:34 pm

Try reversing one of the four batteries for your uploads/downloads.

My experience with the 2116/2117 remotes has uniformly been that all upload/download/connectivity problems have been related to the batteries.

This has been the case through several iterations of desktops and laptops, running Win95, Win98SE, WinME and now WinXP Home SP2.

As I have related in other threads, if the batteries are relatively new and powerful, I have no communication with the remote.

REMOVING the batteries also results in no communication.

I must have batteries for continuity in the power circuit, but they must be pretty weak.

Rather than keep a set of dead batteries around, my to-date- successful workaround is reversing one battery FOR UPLOADS AND DOWNLOADS ONLY.

This reduces the battery supply voltage from 6v to 3v and the interface works like a champ.

Give it a shot.