JP1 Remotes

e34m5 wrote:So if you use the same name as a previuosly converted file, IR has no way of knowing that it already existed and assumes that ExtInstall is complete.

Does this mean that a user CANNOT specifiy an existing filename (i.e. they want to overwrite it with new contents) because IR will think ExtInstall is finished before it really is?

No it will overwrite it...

However I found that sometimes ExtInstall is a bit slow and then IR thinks it's complete because the file is alredy there.

Normally ExtInstall gets a hold of the file quickly and all is fine..think DLL

Does that makes sense.....

Mark Pierson wrote:

e34m5 wrote:So if you use the same name as a previuosly converted file, IR has no way of knowing that it already existed and assumes that ExtInstall is complete.

Does this mean that a user CANNOT specifiy an existing filename (i.e. they want to overwrite it with new contents) because IR will think ExtInstall is finished before it really is?

I have successdfully replaced an existing file with no trouble.

If it helps at all here is how I am set up and working with no problems

XP Pro
c:\jp1 = IR.EXE, KM and RM, and IR upgrade files (.txt and .ir)
c:\jp1\RDF = All RDF's and ExtInstall
c:\jp1\Images = All RM Images and Maps
c:\jp1\Upgrades = All RM upgrades

RDF path in IR is setup for c:\jp1\RDF

e34m5 wrote:As I said before

IR Release 5.03 Notes

.......... For this to work the ExtInstall.exe and the RDF’s must be in the same directory. This includes the normal and the extended version of the RDF’s in question

I really don't think the large red text was necessary. I have been doing exactly what the release notes say, unless the notes implicitly mean that extinstall.exe and the RDFs must be not only in the same directory as each other but also in the same directory as the IR text files (unconverted and converted). That's not the way I read the notes. Please correct me if I'm wrong, because restating what I have already read is not helping me.

Let me explain once more a setup that works for me:

C:\IR = ir.exe, extinstall.exe, all RDF files
C:\IR\15-2116ex2 = 2116ex2.hex
C:\Documents and Settings\Charlie\My Documents\Remote Control Programming = IR text files ("convert from" file "My Remote Unextended.txt" and "convert to" file "My Remote Extended.txt") and extinstall.exe
RDF path in IR = C:\IR

Let me reiterate that having extinstall.exe in the same directory as the RDF files is not adequate. I must also place a copy of extinstall.exe in the directory with my IR text files (...\Remote Control Programming). Interestingly enough, however, I have found that I can avoid the "ExInstall Missing" error without a copy of extinstall.exe in my Remote Control Programming directory by opening the "Set RDF Path..." dialog and then closing it with either OK or Cancel before doing the conversion. I am at a complete loss to explain that behavior.

The only other suggestion I might make at this point is that someone try to reproduce my problems using the specific path and file names that result in failure on my machine:

C:\Program Files\IR = ir.exe, extinstall.exe, all RDF files
C:\Program Files\IR\15-2116ex2 = 2116ex2.hex
C:\Documents and Settings\Charlie\My Documents\Remote Control Programming = IR text files ("convert from" file "My Remote Unextended.txt" and "convert to" file "My Remote Extended.txt")
RDF path in IR = C:\Program Files\IR

Testing with these values may be inconclusive, but testing with anything else is probably a waste of time.

e34m5 wrote:Therefore the calling program has to have a loop that checks if the file is there and if it can be opened. This then signifies that ExtInstall has released the file and it is complete. So if you use the same name as a previuosly converted file, IR has no way of knowing that it already existed and assumes that ExtInstall is complete.

I understand the intent, but a couple of things would have saved me a lot of time:

1) Include a timeout in IR while waiting for ExtInstall to complete, and display an error if a timeout occurs. That way, if something goes wrong, the user isn't left wondering why IR just hangs.

2) If file creation is the signal that ExtInstall completes, make sure that file does not exist before ExtInstall is run (i.e., delete it, if necessary).

Please don't get me wrong: I realize that all of the programming that has been done for this group has been on people's free time and that the goal has been to produce tools that do the job but do not necessarily anticipate every error condition. As a fellow software person, I appreciate this more than you may realize.

For the record: This problem is not impeding my ability to work with my remote. I have only debated this issue in the interests of improving the products and perhaps saving some time for others.

I can't understand why this setup does not work for you. Paul and I have both tried your setup and it works. I am also on XP Pro so I am curious, do you have Administrator rights on the ID you are working from? This could have an impact because IR needs the registry for read and write.

Nils_Ekberg wrote:I am also on XP Pro so I am curious, do you have Administrator rights on the ID you are working from?

Yes, I am using an ID with Administrator rights.

If there is continued interest in troubleshooting this problem, I think it may be necessary to modify IR to provide some additional information in the event of an error. Here is what I would recommend:

1) If the error resulting in the "Missing ExInstall.exe" dialog occurs, print the full path name of the directory (or directories) in which IR attempted to find extinstall.exe.

2) Implement the timeout when waiting for ExtInstall to complete that I mentioned in my last post. If the timeout occurs, display an error dialog that shows all of the information IR passed to ExtInstall.

Putting this information into a file instead of in dialogs would be equally satisfactory. I would also recommend the use of quotes or some other delimiter when printing string values so that it is clear what the strings are even when they contain spaces.

I am still willing to work to find a solution if anyone is still willing to work with me.

1) If the error resulting in the "Missing ExInstall.exe" dialog occurs, print the full path name of the directory (or directories) in which IR attempted to find extinstall.exe.

Good idea..will do

2) Implement the timeout when waiting for ExtInstall to complete that I mentioned in my last post. If the timeout occurs, display an error dialog that shows all of the information IR passed to ExtInstall.

See my explanation about EXE's vs DLL's.

Putting this information into a file instead of in dialogs would be equally satisfactory. I would also recommend the use of quotes or some other delimiter when printing string values so that it is clear what the strings are even when they contain spaces.

?????

I am still willing to work to find a solution if anyone is still willing to work with me.

So are we. When only one person is having an issue and no else can reproduce it, it is hard to solve.

Bottom line..you were able to get it work from IR once you understood the instructions???? If yes then probelm is solved.

The recommendations I made in my last post were in the context of creating a temporary version of IR with debugging information that might better allow me to determine what the problem is on my system. Readdressing each of my points individually:

e34m5 wrote:

1) If the error resulting in the "Missing ExInstall.exe" dialog occurs, print the full path name of the directory (or directories) in which IR attempted to find extinstall.exe.

Good idea..will do

It was not necessarily my intent that this modification be made in a formal release of IR, but it certainly couldn't hurt.

e34m5 wrote:

2) Implement the timeout when waiting for ExtInstall to complete that I mentioned in my last post. If the timeout occurs, display an error dialog that shows all of the information IR passed to ExtInstall.

See my explanation about EXE's vs DLL's.

I read and understood your explanation about EXEs versus DLLs. I was suggesting a temporary modification to IR in its current form to determine what information was being passed to ExtInstall, again, for debugging purposes. If you are planning to create a version of IR using a DLL for ExtInstall in the near future, then my continuing to troubleshoot IR in its current form is probably a waste of time. If, on the other hand, you are interested in knowing the specific problem that exists on my system, I believe I would need the ExtInstall parameter information to continue.

e34m5 wrote:

Putting this information into a file instead of in dialogs would be equally satisfactory. I would also recommend the use of quotes or some other delimiter when printing string values so that it is clear what the strings are even when they contain spaces.

?????

What I was trying to say is that the debugging information I suggested in the two points above could be written to a file instead of being displayed in dialogs, if that is more convenient. Whether or not you would choose to use a dialog probably depends on whether or not you intend to make the dubugging information a permanent feature of the program.

My discussion of using quotes or some other delimiter when printing out string values (i.e., the path names) was just a suggestion that would help clarify entire strings in the debugging information, since the path names I am working with contain spaces.

e34m5 wrote:Bottom line..you were able to get it work from IR once you understood the instructions???? If yes then probelm is solved.

My problems have never been an issue of whether or not I understood the instructions. The fact remains that, on my system, I must use path names without spaces for certain ExtInstall parameters, and I must take special actions not discussed in the release notes to get ExtInstall to work from IR. So, yes, I have been able to work around the problems and get ExtInstall to work from IR, but I honestly do not believe my workarounds constitute a solution. If you disagree, then we are finished, because I cannot proceed with this problem without more information that only you can supply--that is, the debugging information I discussed previously.

Playing Devil's advocate for a moment...

Paul, are you sure that all of the path strings you're passing from IR to ExtInstall include quotes? Being a command line app, any pathsecs containing spaces must be enclosed in quotes. Of course, whether or not you are doesn't explain why you're unable to reproduce chasman's problem.

Chasman, are you sure the admin account has write privledges to all the folders you're trying to access? I had a problem at work where my PC was setup with admin rights, but only My Documents and Settings had write access, while all my JP1 stuff was under Program Files. I had a heck of a time convincing the IT guys to change it!

Mark Pierson wrote:Chasman, are you sure the admin account has write privledges to all the folders you're trying to access? I had a problem at work where my PC was setup with admin rights, but only My Documents and Settings had write access, while all my JP1 stuff was under Program Files. I had a heck of a time convincing the IT guys to change it!

Thanks for the idea, Mark. I do have full admin rights on my machine, and I am able to read and write all of the directories I am accessing.

Mark Pierson wrote:Playing Devil's advocate for a moment...

Paul, are you sure that all of the path strings you're passing from IR to ExtInstall include quotes? Being a command line app, any pathsecs containing spaces must be enclosed in quotes. Of course, whether or not you are doesn't explain why you're unable to reproduce chasman's problem.

My point exactly...I tried it with spaces in my path..I renamed all my JP1 subdirectories with spaces and had no issues.

We'll figure it out some day..

See this release...

http://www.hifi-remote.com/forums/viewt ... 5734#15734

e34m5 wrote:See this release...

http://www.hifi-remote.com/forums/viewt ... 5734#15734

I tried to follow the link above but got this message:

The topic or post you requested does not exist

Try this

IRv5.06

Hey, Paul.

IR 5.06 works like a champ in my original configuration (C:\Program Files\IR, etc.). Thanks! What changed?

Small observation: The most recent entry in the 5.06 release notes lists the version as 5.05 again instead of 5.06.