|
JP1 Remotes
|
View previous topic :: View next topic |
Author |
Message |
The Robman Site Owner
Joined: 01 Aug 2003 Posts: 21247 Location: Chicago, IL |
Posted: Thu Jan 13, 2011 8:43 am Post subject: Suggestion for IR (and RMIR) |
|
|
Could we disable the "clean upper memory" function for extenders? _________________ Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help! |
|
Back to top |
|
|
vickyg2003 Site Admin
Joined: 20 Mar 2004 Posts: 7073 Location: Florida |
Posted: Thu Jan 13, 2011 8:57 am Post subject: Re: Suggestion for IR (and RMIR) |
|
|
The Robman wrote: | Could we disable the "clean upper memory" function for extenders? |
You have no idea how many people do clean upper memory regularly because they think it makes there remotes more efficient. I get PM's on this all the time.
I've tried to address this in IRHELP but yes disabling clean upper memory would be a great start, and perhaps a warning dialog box might be in order too
2) I'd like to request that IRHelp.PDF be used in place of IRHelp.hlp too, since this is a much better document. _________________ Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
|
|
Back to top |
|
|
mathdon Expert
Joined: 22 Jul 2008 Posts: 4524 Location: Cambridge, UK |
Posted: Fri Jan 14, 2011 4:14 am Post subject: |
|
|
vickyg2003 wrote: | ... and perhaps a warning dialog box might be in order too |
I thought the current warning message that appears every time you select "Clean Upper Memory" in IR.exe was good enough. It reads:
Quote: | Please be aware that Clean Upper Memory will destroy most extenders, as they place at least part of their code in the memory that will be cleared. Are you sure you want to proceed? |
If you proceed past this, it surely is "at your own risk".
There is a similar warning in RMIR. _________________ Graham |
|
Back to top |
|
|
vickyg2003 Site Admin
Joined: 20 Mar 2004 Posts: 7073 Location: Florida |
Posted: Fri Jan 14, 2011 4:24 am Post subject: |
|
|
mathdon wrote: | vickyg2003 wrote: | ... and perhaps a warning dialog box might be in order too |
I thought the current warning message that appears every time you select "Clean Upper Memory" in IR.exe was good enough. It reads:
Quote: | Please be aware that Clean Upper Memory will destroy most extenders, as they place at least part of their code in the memory that will be cleared. Are you sure you want to proceed? |
If you proceed past this, it surely is "at your own risk".
There is a similar warning in RMIR. |
I stand corrected, That is a fair warning! I've never actually done a clean upper memory in my 10 years of JP1ing. But still I've had at least 60 extender user's PM me about there non-working remotes, after doing a clean upper memory since I wrote my first extender in 2006. _________________ Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
|
|
Back to top |
|
|
The Robman Site Owner
Joined: 01 Aug 2003 Posts: 21247 Location: Chicago, IL |
Posted: Fri Jan 14, 2011 8:26 am Post subject: |
|
|
You would think that warning would be good enough, but unfortunately, the evidence seems to indicate otherwise. Given that every extender has code hidden in the area that would get cleaned, I still think it's a good idea to completely prevent use of this function when the RDF indicates an extender is being used. _________________ Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help! |
|
Back to top |
|
|
mathdon Expert
Joined: 22 Jul 2008 Posts: 4524 Location: Cambridge, UK |
Posted: Fri Jan 14, 2011 1:54 pm Post subject: |
|
|
The Robman wrote: | You would think that warning would be good enough, but unfortunately, the evidence seems to indicate otherwise. Given that every extender has code hidden in the area that would get cleaned, I still think it's a good idea to completely prevent use of this function when the RDF indicates an extender is being used. |
I'm not sure about the evidence. You have told me before, Rob, that a lot of people don't bother updating to the latest software versions. I added that warning in IR.exe v8.01, so anyone with a significantly out-of-date version won't see it, and if a complete bar is added in a new version now, it will again only help those who keep their software up-to-date. _________________ Graham |
|
Back to top |
|
|
xnappo Expert
Joined: 30 Dec 2003 Posts: 861
|
Posted: Fri Jan 14, 2011 2:29 pm Post subject: |
|
|
mathdon wrote: | The Robman wrote: | You would think that warning would be good enough, but unfortunately, the evidence seems to indicate otherwise. Given that every extender has code hidden in the area that would get cleaned, I still think it's a good idea to completely prevent use of this function when the RDF indicates an extender is being used. |
I'm not sure about the evidence. You have told me before, Rob, that a lot of people don't bother updating to the latest software versions. I added that warning in IR.exe v8.01, so anyone with a significantly out-of-date version won't see it, and if a complete bar is added in a new version now, it will again only help those who keep their software up-to-date. |
Is there something we can change in RDFs to protect extender areas?
xnappo |
|
Back to top |
|
|
vickyg2003 Site Admin
Joined: 20 Mar 2004 Posts: 7073 Location: Florida |
Posted: Fri Jan 14, 2011 2:34 pm Post subject: |
|
|
mathdon wrote: | The Robman wrote: | You would think that warning would be good enough, but unfortunately, the evidence seems to indicate otherwise. Given that every extender has code hidden in the area that would get cleaned, I still think it's a good idea to completely prevent use of this function when the RDF indicates an extender is being used. |
I'm not sure about the evidence. You have told me before, Rob, that a lot of people don't bother updating to the latest software versions. I added that warning in IR.exe v8.01, so anyone with a significantly out-of-date version won't see it, and if a complete bar is added in a new version now, it will again only help those who keep their software up-to-date. |
Yes, I can say that although I have had LOTS of users do this, it has tapered off quite a bit over the past year or so. _________________ Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
|
|
Back to top |
|
|
Barf Expert
Joined: 24 Oct 2008 Posts: 1416 Location: Munich, Germany |
Posted: Mon Jan 17, 2011 3:17 pm Post subject: Re: Suggestion for IR (and RMIR) |
|
|
vickyg2003 wrote: | You have no idea how many people do clean upper memory regularly because they think it makes there remotes more efficient. |
Then it appears to me that the naming is, at least, misleading. "Cleaning" is, a priori, a good thing (TM) to do; and on a regular basis. Who wants to live in unclean home, come unclean to work, write unclean code, or propose unclean solutions to problems? Not me!!
Renaming seems to be a natural step: Zero/nuke/iron (over)/squish/exterminate/eradicate/kill/wipe/terminate upper memory? |
|
Back to top |
|
|
ElizabethD Advanced Member
Joined: 09 Feb 2004 Posts: 2348
|
Posted: Mon Jan 17, 2011 5:45 pm Post subject: Re: Suggestion for IR (and RMIR) |
|
|
Barf wrote: | Renaming seems to be a natural step: Zero/nuke/iron (over)/squish/exterminate/eradicate/kill/wipe/terminate upper memory? |
Good point. I like that.
Perhaps in addition to renaming this menu item, it could also be moved down to join the other risky-looking (initialize to 0 or FF, etc.) items. _________________ Liz
Tweeking 8910, HTPro/9811, C7-7800, 6131o, 6131n, AtlasOCAP-1056B01, RCA-RCRP05B and enjoying the ride |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|