Hi,

This problem seems to be more a X-windows one than a specific SeaDAS one...but since you experts are here so pls. allow me to bother...

I have installed two SeaDAS 5.05: (1)a Federa Core 2 version on my office Linux computer, running through Putty in Windows XP and (2) an Intel
Mac version on MacBook Pro with OS X10.4.9, running through X11; both versions have been running well on each machine.

Now here is my question: when I use X11 on Intel Mac to ssh to the Linux computer, I got the following error message after starting SeaDAS:

**********************************************************************
-bash-3.00$ seadas
xdpyinfo:  unable to open display "".
xrdb: Can't open display ''
IDL Version 6.3 (linux x86 m32). (c) 2006, Research Systems, Inc.
Installation number: ******-***.
Licensed for use by: Someone

SeaDAS Version 5.0.5 (pid = 26849)
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

% DEVICE: Unable to connect to X Windows display: :0.0
% DEVICE: Unable to open X Windows display.
          Is your DISPLAY environment variable set correctly?
% Execution halted at: SEADAS_INIT       246
/PATH_to_SeaDAS/seadas5.05/idl_lib/seadas_init.pro
%                      $MAIN$
% Not a legal system variable: !SD.
% Execution halted at: SDP_INIT           22
/PATH_to_SeaDAS/seadas5.05/idl_lib/sdp_init.pro
%                      SEADAS_INIT       246
/PATH_to_SeaDAS/seadas5.05/idl_lib/seadas_init.pro
%                      $MAIN$
SeaDAS>
**********************************************************************

Similarly, other X-Windows applications such as xclock, emacs...do not work properly either. It appears to me that I'm missing sth like a Mac's version of Windows Xming, as on Windows XP if Xming is not run before SeaDAS, Putty would give a similar error message; but I can not figure out why the Intel Mac version SeaDAS works fine at the same time...  

Can someone give me suggestions? Many thanks!

zh

try using the '-X' option in ssh, this will enable X11 forwarding

(e.g. ssh -X -l username my_other_machine )

that works, thanks Sean!