RE: Getting Windows GUI applications to work

My own problem with copSSH is that (the last time I checked) it could
only install in one place; there was no facility to install it to
another location. This meant that the root directory on connecting to a
given machine was always the same -- C:\ if I recall correctly.
 
For business applications, it is important to our customers to be able
to install it on different drives, and in a lower directory -- e.g. to
F:\application\ssh-home. With such an install location, we can access
the machine securely without having access to the *whole* machine... not
all of which may be 'ours' to play with.
 
Has this changed in the last year-ish? (Been about that long since I
last looked at it.) Or did I perhaps misunderstand how to run the
installer in the first place?
 
(I think the other problem our customers had with copSSH was that it was
not truly 'open source', in that we could not look at the installation
code to see exactly what it was putting where. OpenSSH provides its
installer's source code, which we have examined and recompiled for our
own usage.)
 
I would love to go to copSSH (or any other 'more current' SSH
installation for Windows), and am probably not alone... but for us, at
least, these two items stand in the way of us doing so.
 


________________________________

	From: [email protected] [mailto:[email protected]] On Behalf Of
Herr, Stephen
	Sent: Saturday, January 20, 2007 12:59 AM
	To: [email protected]
	Subject: RE: Getting Windows GUI applications to work
	
	
	Kyle,
	 
	OpenSSH for Windows was the same as SSH on Cygwin 2 or 3 years
	ago.  OpenSSH for Windows has not been improved in quite a
while.
	The Cygwin solution is the most direct way but the copSSH
solution
	is basically the same but has the advantage of an installer that
wraps
	all the necessary Cygwin stuff in one package without all the
decision 
	making and all the individual configuration steps.  It sets up a
couple
	of very handy scripts to add, remove and configure various parts
of the
	ssh(d) environment.  I would give copSSH a whirl and see if it
meets 
	your needs before continuing on down the OpenSSH for Windows 
	path.  Why start on a dead branch when there is an actively
supported
	branch that is very up to date relative to the original OpenSSH
in the 
	BSD world.
	 
	Stephen

	Stephen A. Herr 
	[email protected] <mailto:[email protected]>  
	 

	 

________________________________

	From: [email protected] [mailto:[email protected]] On Behalf Of
Kyle Getz
	Sent: Friday, January 19, 2007 1614
	To: [email protected]
	Subject: Getting Windows GUI applications to work
	
	

	Hi everyone,

	 

	I'm trying to execute Windows GUI applications through SSH but
I'm running into some problems. 
	 
	Here's what happens on a Windows XP machine running OpenSSH for
Windows: 
	 
	1. I open a Remote Desktop session to the machine. 
	2. I also log into the machine via PuTTY. 
	3. After logging in, I run "calc" via PuTTY. I am immediately
returned to the prompt. 
	4. When I look at the Task Manager (through Remote Desktop), I
see calc.exe, but there is no window. 
	 
	 
	Here's what happens on a different Windows XP machine running
sshd through Cygwin: 
	 
	1. I open a Remote Desktop session to the machine. 
	2. I also log into the machine via PuTTY. 
	3. After logging in, I run "calc" via PuTTY. I am not returned
to the prompt. 
	4. In the Remote Desktop window, I see the calculator window pop
up. 
	5. I close the calculator window (through Remote Desktop), and I
am returned to the prompt in my PuTTY window. 
	 
	 
	Obviously, I want the latter behavior, but I want it to work
with OpenSSH for Windows. Does anyone know what I need to do?

	 

	- Kyle Getz

	 

	

	The information contained in this message may be confidential
and/or proprietary, and legally protected from disclosure. If the reader
of this message is not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, you
are hereby notified that any retention, dissemination, distribution or
copying of this communication is strictly prohibited. If you have
received this communication in error, please notify us immediately by
replying to the message and permanently deleting it from your computer.
Thank you, CONTECH Construction Products Inc.