I haven't experienced what you described, but I would recommend
using either vnc (tightvnc) or NX (nomachine or freeNX) to connect
to the the windows machine. Having this extra layer in here may make
things work.
There is a side benefit that we noticed in that the programs run much
faster. With using only X-windows the coregistration routine only ran
at about 10% CPU, with tightvnc or NX the cpu utilization jumps
to near 100%. I believe that essentially buffering the X displays, allows
the server to just move along, instead of waiting for the remote display
to be constantly updated. Of course, our increase was only because our
connection to our server is a little slower because it is located at another
campus.
After using vnc and nx, I can't imagine ever going back to a straight remote
X-windows display to a windows machine.
I know I haven't directly answered your problem. But it may give you a
working alternative.
I hope it helps.
david wack
university at buffalo
Hannah Faye C. Chua wrote:
> This is not an SPM question, but it's related since SPM is called
> within Matlab.
>
> In our lab, the Matlab program is in a linux cluster. If I use the
> linux machine, the Matlab program successfully launches. And I used to
> be able to launch Matlab using an XWindows program from a regular PC.
>
> However, right now, if I use a PC (I tried different PCs) and use an
> XWindows program like Exceed or CygwinX, the program launches the
> Matlab graphics (saying Matlab 7.x) and hangs there. It doesn't launch
> the Matlab interface.
>
> Exceed doesn't tell me what happens, but CygwinX says something like
> "Xlib: unexpected async reply (sequence 0x149)!"
>
> I was told that there was nothing that changed in Matlab, so the
> problem shouldn't exist.
>
> If you have any insights as to how to fix this problem, that'll be
> helpful, and the PC users in my lab can also do some work remotely.
>
> thanks, Hannah
>
|