Something is not correct in RMIR
Jp1 downloads just do not work for me. Work fine from IR.
I don't know why jp1.x serial is dragged into this error log since I'm downloading from 8910 using Tommy's cable for USB port and using the Delcom driver in WinUSB driver and what looks like correct pid and all that was in the RMIR window for linking the interface
Loaded S:\JP1\RM\RemoteMaster.v2.00\Windows\jp1usb.dll
JP1USB version 0.03
EEPROM size returns -1
EEPROM address returns 0
Loading S:\JP1\RM\RemoteMaster.v2.00\Windows\DecodeIR.dll
Loaded S:\JP1\RM\RemoteMaster.v2.00\Windows\DecodeIR.dll
Starting normal download
Interface Name = JP1 USB
Port Name = NULL
Testing interface: JP1 Parallel
Testing interface: JP1.X Serial
Testing interface: JP1 USB
Interface matched. Trying to open remote.
Failed to open
Starting normal download
Interface Name = NULL
Port Name = NULL
Testing interface: JP1 Parallel
Port Name = NULL
Testing interface: JP1.X Serial
Port Name =
Interface opened successfully
Base address = $0
Read first -1 bytes: 00 00 00 00 00 00 00 00 00 00
Searching for RDF
Final signature sought =
No matching RDF found
In device manager DelcomProxy is fine. No yellow !
This is frustrating.
Liz Tweeking 8910, HTPro/9811, C7-7800, 6131o, 6131n, AtlasOCAP-1056B01, RCA-RCRP05B and enjoying the ride
Well, this used to work, but I'm seeing the same behavior here. It seems to me that JP1USB.dll isn't working correctly, but I don't have the source code to check into it.
The dll is loaded successfully, and the interface itself is recognized, but OpenRemote fails-- I don't know why it no longer works.
Have you tried replacing the v2.00/v2.01 jp1usb.dll with the one from v1.97 or v1.99b? Could just be the copy my build script is picking up got corrupted.
This post shows that the size difference is expected, and that dlls from 1.97 or 1.99 aren't able to access the Delcom chip via WinUSB.
However, mathdon's 0.3 version did (if I recall correctly) work with RMIR 2.00, and now it seems to not work. Makes me wonder if a Windows or Java update has broken it.
Have you tried replacing the v2.00/v2.01 jp1usb.dll with the one from v1.97 or v1.99b? Could just be the copy my build script is picking up got corrupted.
I thought of it when I saw the differences, but I could not determine from my scant notes and 1 error log whether those versions worked then or not. And I gather not from 3fg's subsequent post.
I'm on XP-SP3. Graham tested his, short version, on Win2K.
Liz Tweeking 8910, HTPro/9811, C7-7800, 6131o, 6131n, AtlasOCAP-1056B01, RCA-RCRP05B and enjoying the ride
gfb107 wrote:I was going to try building jp1usb.dll version 0.03 under MinGW to see if that works any better, but I can't find the source. Anyone know where it is?
My apologies. It seems that I didn't upload the source. I've now done so, here.
My absence from these forums for the past few months has been the result of personal events, and is likely to continue. I still keep an occasional eye on things, however, and have just seen this thread and noticed my oversight.
I've just done a JP1 download from my URC-8550 with the following setup: RMIR v2.01 Alpha 8, jp1usb v0.03, java version 1.6.0_23, WinUSB driver, interface set to JP1USB with auto-detect, and MS Vista. It worked without any problem. In case it is relevant, I haven't done any Windows updates for some weeks. So unless I misunderstand the problem, I am unable to reproduce it.
Graham, great to see you stopped by
XP here and I, too, did auto-detect in one of many trials.
3FG wrote:Makes me wonder if a Windows or Java update has broken it.
My java version is 6.0.24. I updated java 2/23/2011.
Last few Windows XP updates were 6/18/2010, 10/8/2010, 12/21/2010, 2/24/11 and 3/20/2011, in case any of it matters.
Liz Tweeking 8910, HTPro/9811, C7-7800, 6131o, 6131n, AtlasOCAP-1056B01, RCA-RCRP05B and enjoying the ride
Using the debugger and attaching to the Java process shows that the call to CreateFile (which opens the USB interface) fails with the error Access Denied. Using jp1usb.dll with a Windows test program does succeed-- at least past the call to CreateFile.
I haven't found a fix yet, but I suspect that the issue is increased security in Windows or Java. Can't let the computer get a virus from our remotes!
