JP1 Remotes

I'm using a diygadget.com JP1.x serial cable & USB adapter, Atlas 1055 (day) remote (label in battery compartment reads: 1055BC2-XXX-0001-0001 C070301), Win XP. Using the USB connection (and Ir.exe) I'm able to download data from my remote, but when uploading I get an "Error writing to remote" message and the data already on the remote becomes corrupted. If I use the serial port directly everything works fine. Has anyone experienced this particular problem?
I've tested the cables on two computers, same results each time. I've tried every USB driver I could download. I've read that removing pin 5 from my JP1.3 remote might help; I thought I should get expert advice before trying something drastic. Any recommendations would be greatly appreciated.

Below is the result from the Debug_Tester.bat tool. Results are the same from the real serial port and the USB to Serial adapter (except for the port number), and the same whether or not the remote is connected. I don't know what the results should look like.

Opening COM4
DCB paramaters:
DCBlength=28
BaudRate=38400
fBinary=1
fParity=0
fOutxCtsFlow=0
fOutxDsrFlow=0
fDtrControl=1
fDsrSensitivity=0
fTXContinueOnXoff=0
fOutX=0
fInX=0
fErrorChar=0
fNull=0
fRtsControl=1
fAbortOnError=0
fDummy2=0
wReserved=0
XonLim=2048
XoffLim=512
ByteSize=8
Parity=0
StopBits=0
XonChar=17
XoffChar=19
ErrorChar=0
EofChar=0
EvtChar=0
wReserved1=0
CLRRTS
CLRDTR
SETDTR
SETBREAK
CLRBREAK
Purging RX and TX buffers
Reading up to 20 bytes to flush out spurious data
Didn't get any spurious data
Sending tEst command (45h)
Reading up to 20 bytes of response
Got no response
CLRDTR
SETDTR
SETRTS
CLRRTS
Purging RX and TX buffers
Reading up to 20 bytes to flush out spurious data
Didn't get any spurious data
Sending tEst command (45h)
Reading up to 20 bytes of response
Got no response
SETBREAK
SETRTS
CLRRTS
CLRBREAK
Purging RX and TX buffers
Reading up to 20 bytes to flush out spurious data
Didn't get any spurious data
Sending tEst command (45h)
Reading up to 20 bytes of response
Got no response

palintl wrote:If I use the serial port directly everything works fine.

Is there a reason you want to use the USB-serial adapter if you have access to a serial port that works?

Is there a reason you want to use the USB-serial adapter if you have access to a serial port that works?

Many new computers don't have a serial port, and I like to plan ahead. A more immediate concern is whether the USB adapter I just purchased is damaged. If I can't figure out why it doesn't work perhaps I should request a replacement.