JP1 Remotes

I think that the Runtime Library was installed by another program. It is not in Win XP SP1/SP2/SP3. Most of the computer failures (3 of 4) were in machines not connected to Internet (old programs). I believe that, in some way, the Library update the system call LoadLibrary in Kernel32.dll.

IRScope loads all the dlls now!

Using DisplayLoadedModules I have compared two different computers (one that worked and other that didn't) and I have found that, in order to load all the dlls, the Microsoft C++ Runtime Library 2008 vcredist_x86.exe is required.

Is that the same folder as IRScope.exe, or have you put the DLLs into a different folder, such as Windows\System32?

All the files are in the same folder (dlls and IRScope). I am using the same version in all computers. I only have the beta 2. I have renamed (hidden) "DecodeIR.dll" to test if ...

I'm sure it's a silly question, but have you checked that ExchangeIR.dll and MakeHex.dll are actually present in the same folder as IRScope.exe? The loading command is identical for all three DLLs, so at present I cannot understand how one of them can load but the other two do not. Their absence ...

I am logged on as administrator in all computers.

I can't choose the "Export" menu item . In "Actions on items selected" doesn't appear the "Export" button. It seems that neither "ExchangeIR.dll" nor "MakeHex.dll" are loaded . The "DecodeIR.dll" works fine.
IRScope_201_Image

Summary:
1 computer ...

I've tried the new version in 8 different computers and it works flawlessly in four of them. In the others, I can't use the "Export" item and pressing "Summary" after a capture makes the program crashes.
I've been trying to solve this problem for a week but I have no clue.
Does anyone have the same ...

You can't read them from your remote directly. Currently your best source for that information is from Devices.xls or the Lookup Tool.

Is it and advanced topic?
Or people are patiently reading OFA flash upgrades and studying them to update devices.xls or your Lookup Tool?

I think this ...

It works!

Thank you for your help, Vicky

I've made an upgrade for the Siemens Gigaset MV740 PVR:

http://www.hifi-remote.com/forums/dload.php?action=file&file_id=7702

I have several questions:
What is the third fixed byte used for? (it's not send by the IR engine)
How do we say it (don't send ...

Thanks, Vicky

I understand that the protocol ID is 0171, it's in the ROM of my remote, but we need to call it properly (with the right parameters), and it is not implemented in protocols.ini yet.

Is that correct?

Hi
Maybe it is a strange question, because my remote is working flawlessly.
But I am curious!

I'm triying to make a device upgrade for SAT 1657 (Siemens Gigaset MV740 PVR), but I can't find the protocol ID.

I can both use the native URC implementation in my remote (URC-7950)
and Rob's upgrade ...

Thank you for the information.

I am making an upgrade for a device without the original remote, and I was confused about protocols. I have now more options to test.
I let you know if it works.

I understand that NEC1 only has only two fixed device bytes.
Looking for a nec 1, device 0 compatible code I have found 00 FF FF and 00 FF 00 as a fixed device bytes.
What is the difference between 00 FF FF and 00 FF 00?

Thank you!