Page 2 of 3

Posted: Thu May 24, 2007 12:21 pm
by ElizabethD
Greg, previous version was at SourceForge and I was able to downoad. But once again, my company's blocking rapidshare. Had I downloaded at home I would be trying at work today :( but I didn't. I'll try it over the weekend on some other computer.
Access Denied (content_filter_denied)
The following URL is blocked by xxxxxxx policy because of its content categorization by our subscription service: "Personal Network Storage"
http://rapidshare.com/files/32936074/Re ... 9.exe.html

Posted: Thu May 24, 2007 12:31 pm
by The Robman
I can't guarantee how long this link will work, but you can use this in the meantime...

http://hifi-rem.ipower.com/~rockabil/te ... _v1-79.exe

Posted: Thu May 24, 2007 3:12 pm
by ElizabethD
Rob, it worked, slooowly bit by bit, it came in intact. Thanks. Good move.

This is one slick packaging :), with a slick uninstaller which gives a list of files not deleted, really handy. (I can't delete them manually at this point. Likely after reboot it will work, as 1.78 did)

Question - Is it possible to also display OBC on the external functions sheet and separate hex from efc? I can't enter hex, only EFC. This from the .err file

Code: Select all

Exception in thread "AWT-EventQueue-0" java.lang.NumberFormatException: For input string: "2Bh"
	at java.lang.Void.<unknown>(Unknown Source)
	at java.lang.Void.<unknown>(Unknown Source)
	at java.lang.Void.<unknown>(Unknown Source)
	at java.lang.Void.<unknown>(Unknown Source)
I know the logic of RM translations is somewhat different, just asking, it's no big deal.

Posted: Thu Jun 28, 2007 9:19 pm
by ElizabethD
gfb107 wrote:Here's a build of RM v1.79 built using Excelsior JET 5.0 Professional Edition. It should not have an expiration date. Please give it a try.

It should also address Liz's protocols.ini issues, and the S3F80 issues.

http://rapidshare.com/files/32936074/Re ... 9.exe.html
Well, here we are Jun 28 and the May 23 installation still functioned at work. No expiration messages. Nice job, Greg. Thanks.

Posted: Sun Jul 08, 2007 1:17 am
by Capn Trips
gfb107 wrote:
Capn Trips wrote:
gfb107 wrote:Here's a build of RM v1.79 built using Excelsior JET 5.0 Professional Edition. It should not have an expiration date. Please give it a try.

It should also address Liz's protocols.ini issues, and the S3F80 issues.

http://rapidshare.com/files/32936074/Re ... 9.exe.html
Is RM 1.79 a new release?
Not yet. Soon. It is in progress, but I thought it worth a trial of the new JET release.
Is 1.79 "official" yet? I notice that it's pretty hard to find (hidden in this thread, but not linked in the Flie Section>Tools>Main folder, nor available on SourceForge)

Posted: Fri Jul 13, 2007 6:19 pm
by sfhub
I was having problems with RM processing the unit # for ReplayTV (Official). It doesn't seem to do anything when the unit # is changed.

My experiences are detailed here:
http://www.hifi-remote.com/forums/viewtopic.php?t=8524

I also found the same problem for TiVo (Official) protocol. The Unit # is not processed.

Any comments? Am I doing something obvious wrong or is RM misbehaving? KM works fine for both protocols.

Posted: Sat Jul 21, 2007 4:43 am
by sfhub
sfhub wrote:I was having problems with RM processing the unit # for ReplayTV (Official). It doesn't seem to do anything when the unit # is changed.

My experiences are detailed here:
http://www.hifi-remote.com/forums/viewtopic.php?t=8524
I made the following changes to protocols.ini to fix the problem. I probably should only translate 4 bits ( TranslatorFromDev(1,4,4) ) because Replay Unit Code only has valid values 0-15, but I left it as 1,8,0 to remain consistent with KM behavior.
[ReplayTV (Official)]
OldNames=ReplayTV Official
PID=00 92
CmdTranslator=TranslatorFromDev(1,8,0) Translator(0,8,8 )
CmdParms=OBC=0
Notes=official version
DevParms=Device Code=1,Unit Code=0
DeviceTranslator=Translator(0,8,8 )
FixedData=e0 01
DefaultCmd=00 00
CmdIndex=1
Assuming I haven't done anything incorrect, would it be possible to add the fix to the next version of protocols.ini? Thanks.

Posted: Fri Aug 10, 2007 11:27 pm
by Mark Pierson
I just got an automatic update to Java 1.6.0 and RM refuses to load. I tried a fresh download of RM but that didn't help either.

Here's the brief contents of rmaster.err:

Code: Select all

Adding to classpath: file:/C:/Program Files/JP1/RM/
Caught exception in RemoteMaster.main()!
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
	at java.lang.String.substring(Unknown Source)
	at com.hifiremote.jp1.Remote.<init>(Remote.java:31)
	at com.hifiremote.jp1.RemoteManager.loadRemotes(RemoteManager.java:57)
	at com.hifiremote.jp1.RemoteMaster.createAndShowGUI(RemoteMaster.java:837)
	at com.hifiremote.jp1.RemoteMaster.access$200(RemoteMaster.java:20)
	at com.hifiremote.jp1.RemoteMaster$3.run(RemoteMaster.java:884)
	at java.awt.event.InvocationEvent.dispatch(Unknown Source)
	at java.awt.EventQueue.dispatchEvent(Unknown Source)
	at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
	at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
	at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
	at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
	at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
	at java.awt.EventDispatchThread.run(Unknown Source)

Posted: Sat Aug 11, 2007 6:05 am
by gfb107
See RM stopped working. This has nothing to do with the Java update.

Posted: Sat Aug 11, 2007 9:11 am
by vickyg2003
Well that's 3 of the 8 people who downloaded my first try at 8820 extender. :oops:

Posted: Sat Aug 11, 2007 9:32 am
by underquark
I'm still in therapy :cry:


[Edit]
Of course, I'm not. Break away to your heart's content, Vicky - it's to be expected when you're pushing the boundaries. I'm, sorry I haven't tried everything in the extender yet - part of the reason is lack of time this week and part the fact the URC8820 is fairly well set up out of the box with macros programmable on the device keys and IR coping with shuffling memory around. Have tried the vanilla URC8820 via IR and currently have 14 devices contributing to a very over-stuffed upgrade space with no problems (other, of course, than "loss" of the learning facility). I'll see if I can set up some DKPs etc. this weekend and maybe venture into toadtog.

Posted: Sat Aug 11, 2007 2:59 pm
by Mark Pierson
gfb107 wrote:This has nothing to do with the Java update.
:oops: The RDF issue never occurred to me. That's what I get for staying up so late last night (this morning?)... :oops:

Posted: Sat Aug 11, 2007 3:05 pm
by Mark Pierson
Just a thought... maybe RM can skip any offending RDF's with an appropriate message to the user instead of ceasing to function?

Posted: Sat Aug 11, 2007 3:48 pm
by gfb107
Mark Pierson wrote:Just a thought... maybe RM can skip any offending RDF's with an appropriate message to the user instead of ceasing to function?
YEs, that fix will be part of the next release. There's some other stuff I am working that I just haven't had a chance to finish up yet.

Posted: Thu Aug 23, 2007 5:49 am
by gfb107
I never saw the specifics of the problems with the TiVo (Official) protocol and unit code. Did you come up with a fix for that as well? I am almost ready to release v1.80
sfhub wrote:
sfhub wrote:I was having problems with RM processing the unit # for ReplayTV (Official). It doesn't seem to do anything when the unit # is changed.

My experiences are detailed here:
http://www.hifi-remote.com/forums/viewtopic.php?t=8524
I made the following changes to protocols.ini to fix the problem. I probably should only translate 4 bits ( TranslatorFromDev(1,4,4) ) because Replay Unit Code only has valid values 0-15, but I left it as 1,8,0 to remain consistent with KM behavior.
[ReplayTV (Official)]
OldNames=ReplayTV Official
PID=00 92
CmdTranslator=TranslatorFromDev(1,8,0) Translator(0,8,8 )
CmdParms=OBC=0
Notes=official version
DevParms=Device Code=1,Unit Code=0
DeviceTranslator=Translator(0,8,8 )
FixedData=e0 01
DefaultCmd=00 00
CmdIndex=1
Assuming I haven't done anything incorrect, would it be possible to add the fix to the next version of protocols.ini? Thanks.