Hello everyone,

I want to provide an update on my Rexx issues.  At this time I have a work around, but not a fix.  What I found does work is to install with RXAPI not being a service and thus not started.  Once the Rexx installation completes, I then manually install using the "sc" command RXAPI as a service.  It is running great!!

As for the suggestion about running a Rexx program at start up, I have been using a program I call:  Delay_Startup_Program.  The purpose is to start in a time delay manner certain applications, such as MagicISO.  I start it late to insure its tray icon starts properly.  I also use another script for insuring all network drives are up and running properly and a method to state if they're not operating properly.

In this respect RXAPI start off when the first person logs into Window, which is one of the suggested workarounds.

As of today (12/22/2013), I've yet to see the issue with starting a Rexx program causing a new CMD.EXE to occur.  Hopefully, the reinstall fixed the issue.

QUESTION:  Is there a method / way to have a Rexx program start before the first person logs into Windows?

I appreciate all the feedback and found it helpful!

Bert Moshier


On Sun, Dec 22, 2013 at 5:57 PM, <oorexx-users-request@lists.sourceforge.net> wrote:
Send Oorexx-users mailing list submissions to
        oorexx-users@lists.sourceforge.net

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.sourceforge.net/lists/listinfo/oorexx-users
or, via email, send a message with subject or body 'help' to
        oorexx-users-request@lists.sourceforge.net

You can reach the person managing the list at
        oorexx-users-owner@lists.sourceforge.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Oorexx-users digest..."


Today's Topics:

   1. Re: Problem installing ooRexx 4.1.2 and 4.1.3 Windows x76_64
      on Windows 7 Ultimate x64 (Mark Miesfeld)
   2. Re: Problem installing ooRexx 4.1.2 and 4.1.3 Windows x76_64
      on Windows 7 Ultimate x64 (Bertram Moshier)
   3. Re: Problem installing ooRexx 4.1.2 and 4.1.3 Windows x76_64
      on Windows 7 Ultimate x64 (Mark Miesfeld)
   4. Announce: ooDialog 4.2.3 release candidate now    available
      (Mark Miesfeld)


----------------------------------------------------------------------

Message: 1
Date: Wed, 11 Dec 2013 09:49:46 -0800
From: Mark Miesfeld <miesfeld@gmail.com>
Subject: Re: [Oorexx-users] Problem installing ooRexx 4.1.2 and 4.1.3
        Windows x76_64 on Windows 7 Ultimate x64
To: Open Object Rexx Users <oorexx-users@lists.sourceforge.net>
Message-ID:
        <CAE7rnYRamWNXYnsYTwYk3QStaNDORGRaqjLQugO=v2W9Y1a5TA@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

On Wed, Dec 11, 2013 at 9:17 AM, Ruurd Idenburg <ruurd@idenburg.net> wrote:

> I've seen some of these decribed problems but always when I was fooling
> around with the 64- and 32- bit versions on my 64 bit Ultimate System. I
> think that the installer wasn't able to kill/start rxapi  when switching
> from one mode to the other.
>


Thanks Ruurd.

That's interesting.  If you had the 32-bit version installed and then
started the 64-bit installer, the installer would detect the installed
ooRexx.  It would then attempt to execute the the 32-bit uninstaller from
the 64-bit process space.  This wouldn't work.

I guess it would be the same going the other way.

In this case, you would need to run the current uninstaller first, before
starting the installer.  The uninstaller program would be the same bitness
as the running rxapi and should have no problem stopping it.  Actually, it
first tries to stop the service using the service manager calls.  I think
those calls should work even if rxapi was 32-bit and the process was 64 bit.

The installer used to have some loop holes where if rxapi was not stopped,
the installer just continued on.  I think I have those fixed so that if
rxapi is not stopped, the installer will not continue.

We need to point out in the installation notes or read me files that on
Windows if you have ooRexx installed and are going to install a new version
that is not the same bitness as the installed version, you need to do it in
two steps.  You need to first run the stand alone uninstaller and then run
the installer.

--
Mark Miesfeld



>
> I could always recover by doing what Mark wrote down, making sure no
> rxapi was running (either as a service or in it's process).
>
> -- Ruurd Idenburg
>
>
> ------------------------------------------------------------------------------
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics
> Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
> _______________________________________________
> Oorexx-users mailing list
> Oorexx-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-users
>
-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------

Message: 2
Date: Thu, 12 Dec 2013 11:07:20 -0600
From: Bertram Moshier <bertrammoshier@gmail.com>
Subject: Re: [Oorexx-users] Problem installing ooRexx 4.1.2 and 4.1.3
        Windows x76_64 on Windows 7 Ultimate x64
To: oorexx-users@lists.sourceforge.net
Message-ID:
        <CA+EVRAMcRTE5dc5JgX-qMgoOor_HAgUTF6MCdmwnnyQcMVtrCA@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

Hello Mike,

At first I thought you found my mistake:

2.)  Right click on the installer package and select run as Administrator.
Or if you are executing the installer from a command prompt, open up a new
command prompt window by right-clicking on a console icon and selecting run
as Administrator.

I ran the installer from the browser download list and thus it might not
run in administration mode.

Yet, I also ran the installer from the command line of a command prompt
with administrator privileges and it also hung / froze on installing and/or
starting the service.

BUT!  I was able to get it working on one of my systems.  What I did was:


   1. Install without making RXAPI a service (as you suggest).  The
   installer runs quickly through and without any problems.
   2. Insured the RXAPI service did not exist in the service's list.
   3. At the point in time, I didn't know about "rxapi /i" command.  Thus I
   used the command:  sc create RXAPI binpath= "C:\Program
   Files\ooRexx\rxapi.exe" to install the RXAPI service
   4. I started services and manually set up the properties to auto start
   the service

When I do "sc query rxapi" the response I get is:

SERVICE_NAME: rxapi
        TYPE               : 10  WIN32_OWN_PROCESS
        STATE              : 4  RUNNING
                                (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0

QUESTION:  Did I manually install RXAPI in an acceptable manner?

I'm now running ooRexx 4.1.3 fine and will wait to see if my problem with
starting Rexx programs (e.g. rexxtry) from the command line occurs again.
Typically, I find the system needs to be up for several days before the
issue rears its ugly head.  Maybe the issue isn't just one with Rexx but
many other commands from the command line.  I just use Rexx a lot and thus
it is the one I see having the issue.  Should it happen again, I'll try to
do more analysis.

So, in the end, I got it working, but still don't know why the installer
hung on installing RXAPI as a service.  I was able to do it manually using
the sc command.

OH!  One last question:  Is it possible to have a Rexx program run before
an user logs into Windows?  If yes, how?  If no, would it be possible to
add this to the product, in the future?

Sincerely yours,

Bert Moshier
-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------

Message: 3
Date: Thu, 12 Dec 2013 09:32:41 -0800
From: Mark Miesfeld <miesfeld@gmail.com>
Subject: Re: [Oorexx-users] Problem installing ooRexx 4.1.2 and 4.1.3
        Windows x76_64 on Windows 7 Ultimate x64
To: Open Object Rexx Users <oorexx-users@lists.sourceforge.net>
Message-ID:
        <CAE7rnYQbO9NVKFOJoe4zUKp61UkruA7AZKUFB3gdFnyb_TCF=Q@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

On Thu, Dec 12, 2013 at 9:07 AM, Bertram Moshier
<bertrammoshier@gmail.com>wrote:


>
> At first I thought you found my mistake:
>

The installer should elevate automatically, so not starting it with 'run as
Administrator' should not make any difference.  It was just a suggestion,
for just in case.


> When I do "sc query rxapi" the response I get is:
>
> SERVICE_NAME: rxapi
>         TYPE               : 10  WIN32_OWN_PROCESS
>         STATE              : 4  RUNNING
>                                 (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
>         WIN32_EXIT_CODE    : 0  (0x0)
>
>         SERVICE_EXIT_CODE  : 0  (0x0)
>         CHECKPOINT         : 0x0
>         WAIT_HINT          : 0x0
>
> QUESTION:  Did I manually install RXAPI in an acceptable manner?
>

Looks okay.


> I'm now running ooRexx 4.1.3 fine
>

Okay, great.


> OH!  One last question:  Is it possible to have a Rexx program run before
> an user logs into Windows?
>

it should be possible.


> If yes, how?
>

One way would be to set it up as a service, they may be other ways.  It has
been many years since I fooled with it and I don't remember the details off
the top of my head.  An Internet search should turn up some help.

There is an ooRexx user, Jeremy Nicoll, who runs Rexx programs on start up.
 Maybe he'll answer here.

Otherwise, you could post the question on comp.lang.rexx and maybe he'll
answer there.

--
Mark Miesfeld
-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------

Message: 4
Date: Sun, 22 Dec 2013 15:57:40 -0800
From: Mark Miesfeld <miesfeld@gmail.com>
Subject: [Oorexx-users] Announce: ooDialog 4.2.3 release candidate now
        available
To: Open Object Rexx Announcements
        <oorexx-announce@lists.sourceforge.net>,        Open Object Rexx Users
        <oorexx-users@lists.sourceforge.net>,   ooRexx Dev List
        <oorexx-devel@lists.sourceforge.net>,   RexxLA Members mailing list
        <rexxla-members@rexxla.org>
Message-ID:
        <CAE7rnYSyHxT15JZCk9vL37oTn3DJUimzTEEpDyuJ9=kDDrZ6ow@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

Installation packages for ooDialog 4.2.3, final release candidate, are now
available on SourceForge at:

https://sourceforge.net/projects/oorexx/files/ooDialog/4.2.3%20%28release%20canidate%29/

The ooDialog 4.2.3 release is a routine update, providing some incremental
improvements and a few bug fixes.

ooDialog 4.2.3 can be installed to any ooRexx installation, 4.1.0 or later.

4.2.3 has been in beta now for over 3 weeks with only 1 minor bug reported
and fixed.  Unless some other bugs are reported in the next few days, it is
anticipated that the official release version of ooDialog 4.2.3 will be
done on Christmas day 2013.

This may be your last chance to ensure your ooDialog applications run
correctly before the official release.  If problems are discovered please
report them immediately using the SourceForge bug tracker at:

https://sourceforge.net/p/oorexx/bugs/

--
The ooRexx Development Team
-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------

------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk

------------------------------

_______________________________________________
Oorexx-users mailing list
Oorexx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-users


End of Oorexx-users Digest, Vol 45, Issue 14
********************************************