Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<002a01c27059$3cbb8e00$1e02a8c0@VXMLDEV>
From:	"Marius Seritan" <mseritan AT jacent DOT com>
To:	"Uwe Mayer" <merkosh AT planet-interkom DOT de>, <cygwin AT cygwin DOT com>
References:	<128849681 DOT 20021010093339 AT planet-interkom DOT de>
Subject:	Re: remotely executing windows applications
Date:	Thu, 10 Oct 2002 05:32:39 -0700
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2800.1106
X-MIME-Autoconverted:	from base64 to 8bit by delorie.com id g9ACVCe26138

When you login to console you get desktop "winsta0\Default". When you login with ssh you get a totally different desktop, something with a numeric name. Programs inherit their parent desktop unless they take special steps to get another desktop. Even if they try to get another desktop permissions may not allow this.

If you mark a service as interactive (Control Panel/.../Services) then it will get the "winsta0\default". You can try setting ssh as an interactive service and winvnc will inherit the main desktop instead of the non-interactive one. 

Important: I have not tried this configuration. It may totally mess up the permissions on the console and you may have to reboot remote (look for psshutdown at http://sysinternals.com). It's better to test this while you are close to the computer running sshd.


----- Original Message ----- 
From: "Uwe Mayer" <merkosh AT planet-interkom DOT de>
To: <cygwin AT cygwin DOT com>
Sent: Thursday, October 10, 2002 12:33 AM
Subject: remotely executing windows applications


> I have sshd installed on my win2k box. Together with cygwin, of
> course. Recently I needed GUI access to my computer and after logging
> in via ssh I run "cygstart winvnc.exe". The application started, but
> did not show up in the system tray. However, it didn't accept
> connections - although it was started (ps -aW). I couldn't kill it
> though ("no such process").
> 
> Back at home I had the test: running "cygstart winvnc.exe" worked if I
> was not logged on vie SSH.
> 
> Why didn't winvnc start up correctly? How do I change that?
> 
> Thanks
> Ciao
> Uwe
> 
> 
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
> 

- Raw text -