Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#348 Windows Installation annoyances and requests

v4.1.0
closed
Mark Miesfeld
7
2012-08-14
2009-04-13
Garry Smithwick
No

Before I installed 4.0, I had changed the ".rex" files to use the KEDIT
editor.  After the install this has been changed back to notepad. Annoying
to have to go back in and change it back to KEDIT.  Also, I set default
execution for Rexx 3.2 to call rexxpaws.exe, after 4.0, I have to change
this back also.

Discussion

  • Mark Miesfeld
    Mark Miesfeld
    2009-04-13

    This installation annoyance has always been there. It is the same behavior as all the previous ooRexx installers.

    Several people have complained about it in the past, however they never took the trouble to open up a tracker item on it, so it has been at the very bottom of my list to do.

    Unfortunately, changing the installer is not trival, so I don't intend to fix this until the next release.

    It is not really a bug, it is working as designed. So I'm changing this to a request for enhancement. I'll put a high priority on it though. In fact, I already have a RFE opened to fix several areas in the installer.

     
  • Mark Miesfeld
    Mark Miesfeld
    2009-06-14

    I'm changing the title of this a bit. I intend to rewrite portions of the installer and am hoping people will add to this RFE the things they would like to see.

    Here are some so far:

    Install

    1.) Allow the user to select the editor mapped to the Edit function, or to just use Notepad.

    2.) Allow the user to select which executable is mapped to *.rex files, rexx.exe, rexxpaws, or rexxhide.exe.

    3.) Allow the user to map the other 2 executables to an extension of their own. For instance map .wrex to rexxhide.exe

     
  • Gil Barmwater
    Gil Barmwater
    2009-06-14

    I would like to see an option to do a "limited" install. By that I mean allowing the necessary files to be installed but no modifications to paths, file associations, etc. This would allow one to install to a memory stick or portable hard drive that could be moved to different systems. Providing a simple .bat file would allow "temporary" environment changes like path and rexx_path. The obvious things that would be lost by doing this - e.g. file associations - would be need to be documented. The model I'm thinking of is the "Instant Rails" package which provides Ruby, MySQL and Apache in one install that all goes away when it is shut down.

     
  • Mark Miesfeld
    Mark Miesfeld
    2009-06-14

    Thanks Gil. That's the kind of feed-back I was hoping for. A "limited' install would be helpful, fairly easy to do, and something I wouldn't have thought of on my own.

     
  • A closely related one .. currently the installation process removes .rex from the PATHEXT environment variable and then later puts it back -- in a different place. So after every install I have to go in and manually edit PATHEXT (I have .rex before .bat because I have dozens, perhaps hundreds, of ancient .bat files from the days when there wasn't automatic handling of .rex programs, and nowadays they often don't pass the arguments through correctly, etc.)...

    Mike

     
  • Mark Miesfeld
    Mark Miesfeld
    2009-08-22

    Going to add a couple of new items, bringing the list to data:

    Install

    1) During un-install offer the option of not undoing the ftype associations. (Gary) Could / should be extended to not removing .rex from PATHEXT. (Mike) Could be extended to not removing install directory from PATH. (I always move ooRexx to the front of my path. Mark)

    2.) Allow the user to select the editor mapped to the Edit function, or to
    just use Notepad.

    3.) Allow the user to select which executable is mapped to *.rex files,
    rexx.exe, rexxpaws, or rexxhide.exe.

    4.) Allow the user to map the other 2 executables to an extension of their
    own. For instance map .wrex to rexxhide.exe

    5.) Have an option for a minimal install.

    6.) If the user does not uninstall a previous version, do not allow the install to continue. See bug 2842643 rxapi service does not start

    7.) If the user does not stop rxapi during the install, cancel the install. See bug 2842643 rxapi service does not start

     
  • Mark Miesfeld
    Mark Miesfeld
    2010-08-22

    Committed revision 6134.

    That commits refactors oorexx.nsi to make adding some of these features easier.

    Fixes these:

    6.) If the user does not uninstall a previous version, do not allow the
    install to continue. See bug 2842643 rxapi service does not start

    7.) If the user does not stop rxapi during the install, cancel the
    install. See bug 2842643 rxapi service does not start

    Although, the user can over-ride things and skip uninstalling the previous version, if they insist. Message box popups make it clear that this is not supported and is highly unlikely to work.

     
  • Mark Miesfeld
    Mark Miesfeld
    2010-12-18

    Most all of this was implemented and shows up in the 4.1.0 release. The only thing not in that release was the option to do a minimal install. So, I'm going to close this and open a RFE for just that one thing.

     


Anonymous


Cancel   Add attachments