problem with run.exe in Windows-startup (Autostart) directory

problem with run.exe in Windows-startup (Autostart) directory

[Paul Maier]

Hi,

yesterday I upgraded Cygwin, all packages to current version, and I find a problem in run.exe (it used to work before the upgrade):

When I start a run.exe command manually, it hides fine both, the window and the task bar entry;
but I have 3 scripts containing run.exe commands in the Windows startup (autostart) folder, and there one (only one) script brings
up an unwanted entry in the task bar (the window itself is fine invisible). It is always another one out of the 3 scripts, but each
time at most one (i. e. zero or 1 unwanted entries).
Since I start a server here, that task bar entry stays there all day (and of course there is no visible window attachted to it), and
if I select close, I also shut down the server by this.

This seems a racing condition to me:
If I disconnect the internet LAN cable (then the evaluation of possible connections is much faster) _or_ if I move my mouse up and
down right after Windows login to make the task bar appear and disappear some times, then all autostart run.exe scripts hide their
task bar entries fine.

I have never seen more than 1 such unwanted task bar entry appearing. The first one seems to initialize the environment somehow, so
that the other run.exe instances work as expected.

I also added a 4th script:
run /bin/sleep 10,
That improved the situation in a way, that unwanted task bar entries were less likely to happen, but they still came then and when.

It worked fine with the run.exe that I downloaded 1 year ago.

Thank you for help.

Regards,
  Paul



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: problem with run.exe in Windows-startup (Autostart) directory

[Andrey Repin]

Greetings, Paul Maier!

> When I start a run.exe command manually, it hides fine both, the window and
> the task bar entry; 
> but I have 3 scripts containing run.exe commands in the Windows startup
> (autostart) folder, and there one (only one) script brings up an unwanted
> entry in the task bar (the window itself is fine invisible). It is always
> another one out of the 3 scripts, but each time at most one (i. e. zero or 1
> unwanted entries).
> Since I start a server here, that task bar entry stays there all day (and of
> course there is no visible window attachted to it), and if I select close, I
> also shut down the server by this. 

What exactly is in your scripts, and in the links in StartUp dir?

> This seems a racing condition to me:

This seems to be a wrong link/improperly designed script for me.
Or a use of a wrong tools for the task.

> If I disconnect the internet LAN cable (then the evaluation of possible
> connections is much faster) _or_ if I move my mouse up and down right after
> Windows login to make the task bar appear and disappear some times, then all
> autostart run.exe scripts hide their task bar entries fine.

> I have never seen more than 1 such unwanted task bar entry appearing. The
> first one seems to initialize the environment somehow, so that the other
> run.exe instances work as expected. 

> I also added a 4th script:
> run /bin/sleep 10,
> That improved the situation in a way, that unwanted task bar entries were
> less likely to happen, but they still came then and when. 

> It worked fine with the run.exe that I downloaded 1 year ago.


--
WBR,
Andrey Repin (anrdaemon@freemail.ru) 22.07.2012, <18:03>

Sorry for my terrible english...


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

AW: problem with run.exe in Windows-startup (Autostart) directory

[Paul Maier]

> Greetings, Paul Maier!
> 
> > When I start a run.exe command manually, it hides fine both, the window and
> > the task bar entry;
> > but I have 3 scripts containing run.exe commands in the Windows startup
> > (autostart) folder, and there one (only one) script brings up an unwanted
> > entry in the task bar (the window itself is fine invisible). It is always
> > another one out of the 3 scripts, but each time at most one (i. e. zero or 1
> > unwanted entries).
> > Since I start a server here, that task bar entry stays there all day (and of
> > course there is no visible window attachted to it), and if I select close, I
> > also shut down the server by this.
> 
> What exactly is in your scripts, and in the links in StartUp dir?
> 
> > This seems a racing condition to me:
> 
> This seems to be a wrong link/improperly designed script for me.
> Or a use of a wrong tools for the task.
> 
> > If I disconnect the internet LAN cable (then the evaluation of possible
> > connections is much faster) _or_ if I move my mouse up and down right after
> > Windows login to make the task bar appear and disappear some times, then all
> > autostart run.exe scripts hide their task bar entries fine.
> 
> > I have never seen more than 1 such unwanted task bar entry appearing. The
> > first one seems to initialize the environment somehow, so that the other
> > run.exe instances work as expected.
> 
> > I also added a 4th script:
> > run /bin/sleep 10,
> > That improved the situation in a way, that unwanted task bar entries were
> > less likely to happen, but they still came then and when.
> 
> > It worked fine with the run.exe that I downloaded 1 year ago.
> 


Hi Andrey,

thank you very much for looking into this issue.

With "scripts" I mean:
In the folder "C:\Users\<Username>\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\"
I have 2 files with ending .lnk. They are normal Windows links. In their execute line they have the following:

1.) D:\Programme\cygwin\bin\run.exe /cygdrive/d/Programme/Subversion/bin/svnserve.exe -d -r "<Path>" --log-file "<Path>"
    To work around the run.exe problem, I changed this one from "-d" to "--service" and run it as Windows service.

2.) D:\Programme\cygwin\bin\run.exe /bin/tcsh.exe -c startx
    And startx is an alias to: /bin/startxwin -- /bin/XWin
    This one I can't run as Windows service, because I don't know how to.
    It works fine, when I stop the X server and double click on that .lnk file in the explorer.
    It also used to work fine before my Cygwin upgrade.
    But the current Cygwin version leaves an entry in the task bar, when executed automatically during the Windows startup.
    The X Server starts fine; the problem is the unneccessary entry in the task bar, staying there for the whole day.

Thank you!

Regards,
  Paul
 



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: AW: problem with run.exe in Windows-startup (Autostart) directory

[Andrey Repin]

Greetings, Paul Maier!

> With "scripts" I mean:
> In the folder "C:\Users\<Username>\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\"
> I have 2 files with ending .lnk. They are normal Windows links. In their execute line they have the following:

> 1.) D:\Programme\cygwin\bin\run.exe /cygdrive/d/Programme/Subversion/bin/svnserve.exe -d -r "<Path>" --log-file "<Path>"
>     To work around the run.exe problem, I changed this one from "-d" to "--service" and run it as Windows service.

That's not workaround, that's the right way to do it.

> 2.) D:\Programme\cygwin\bin\run.exe /bin/tcsh.exe -c startx

>     And startx is an alias to: /bin/startxwin -- /bin/XWin

Why not start it directly, then?
It's not cygwin-specific, both are remote access services. Using intermediate
scripts only blurring your picture, and taking more time for system to
startup.

I would understand, if you were using run-parts ~/profile.d/ kind of scripting, like me.
But it seems it's not the case and all you want is to start certain
application on startup. Do it!


--
WBR,
Andrey Repin (anrdaemon@freemail.ru) 23.07.2012, <05:03>

Sorry for my terrible english...


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

AW: AW: problem with run.exe in Windows-startup (Autostart) directory

[Paul Maier]

> 
> > 2.) D:\Programme\cygwin\bin\run.exe /bin/tcsh.exe -c startx
> 
> >     And startx is an alias to: /bin/startxwin -- /bin/XWin
> 
> Why not start it directly, then?
> It's not cygwin-specific, both are remote access services. Using intermediate
> scripts only blurring your picture, and taking more time for system to
> startup.
> 
> I would understand, if you were using run-parts ~/profile.d/ kind of scripting, like me.
> But it seems it's not the case and all you want is to start certain
> application on startup. Do it!
 


Hello Andrey,

thank you very much for your answer!


> Why not start it directly, then? [...] Do it!

What do you mean by "start directly" and "Do it"?:

- Do you mean that I should start the X Server manually every time I boot Windows?
  That certainly would work, but that's not a solution for me. I want the X Server to start automatically on Windows login.

- Or do you mean that I should register XWin as Windows service? I looked through the Cygwin manual, but I didn't find a solution
how to register XWin as Windows service.
  I also tried out; but these tree attempts don't work:


sc create testabc binpath= "D:\Programme\Alias\startx.bat" displayname= "testabc" start= demand

sc create testabc1 binpath= "D:\Programme\cygwin\bin\startxwin.exe -- /bin/XWin -clipboard -emulate3buttons 100 -nounixkill
-nowinkill -xkboptions nbsp:level3" displayname= "testabc1" start= demand

sc create testabc2 binpath= "D:\Programme\cygwin\bin\XWin.exe -clipboard -emulate3buttons 100 -nounixkill -nowinkill -xkboptions
nbsp:level3" displayname= "testabc2" start= demand


They all come with the same error message on startup:

sc start testabc2
[SC] StartService FEHLER 1053:
Der Dienst antwortete nicht rechtzeitig auf die Start- oder Steuerungsanforderung.


Thank you very much!

Regards,
  Paul



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple