I have a new Inteset INT-422-3
Setup was fine with RMIR in windows
but with Linux the remote's image would not show up just generic circles for buttons
After checking a few things I came upon the INT-422-2.map that the INT-422-3
uses, the line #$GIF:INT-422-2.JPG needs to be #$GIF:INT-422-2.jpg
The extension ".jpg" needed to be in small letters not capital for Linux to work right
because the actual jpg is in small letters. I guess Linux is pickier
Hope this helps out anyone else using Linux
Inteset INT-422-3 Linux vs Windows
Moderator: Moderators
I've not had that problem in Linux, maybe the remotes I've had have the correct extension in their image files. But for the benefit of Windows users, all file names and extensions are case-sensitive in Linux. So these extensions are all different.
jpg JPG Jpg JPg jpG jPG
jpg JPG Jpg JPg jpG jPG
URC7560/URC7562, URC8910, URC7980, URC6440/OARUSB04G and URC3661
I would phrase it like this:
In this community, we create "portable" software, i.e. software that runs on different systems. No assumption must be made on the case sensitivity of the user's system: the software should run correctly on both case sensitive as well as case insensitive file systems.
For the ones developing on case insensitive file systems (i.e. Windows), file names have to coincide in the code and on the disc, including case. The ones developing on case sensitive file systems (Linux, often MacOSX) must take care not put files differing only on case in the same directory (for example README, Readme and readme).
Violations should be considered as bugs.
BTW, relying on "the file system is case insensitive" is fragile and can easily wrong. Just (using Java as example)
and search (case sensitively) in filesInDirectory...
In this community, we create "portable" software, i.e. software that runs on different systems. No assumption must be made on the case sensitivity of the user's system: the software should run correctly on both case sensitive as well as case insensitive file systems.
For the ones developing on case insensitive file systems (i.e. Windows), file names have to coincide in the code and on the disc, including case. The ones developing on case sensitive file systems (Linux, often MacOSX) must take care not put files differing only on case in the same directory (for example README, Readme and readme).
Violations should be considered as bugs.
BTW, relying on "the file system is case insensitive" is fragile and can easily wrong. Just (using Java as example)
Code: Select all
File directory = new File(....); // an existing direcory
File[] filesInDirectory = directory.listFiles(); // produce array of (abstract) file names
-
HamburgerHelper1
- Posts: 702
- Joined: Sat Feb 22, 2014 2:58 pm