Problems running wine on a remote XTERM

[Larry Merritt-Gilbert]

I had a similar problem trying to remotely display Wine progs to an
HPUX machine.  After an extensive amount of probing, my colleague and
I discovered that the target machine (the one being displayed to) had
some kind of wierd, hybrid color depth that was confusing to Wine. 
You might want to make sure the color depth on the target box is one
that Wine likes.  Or, I could be totally wrong, and in that case, feel
free to let the flames fly.

2names




brian at cruik.org (Brian Cruikshank) wrote in message news:<448e21c4.0202121333.36dc785a at posting.google.com>...
> I have wine running pretty well locally, but I am running into
> problems if I try running it through an XTERM on another machine.
> 
> I have DISPLAY mapped and can display other programs, so I know there
> is not a problem there.
> 
> Any ideas?
> 
> Wine says one of two things.  Here is the larger message:
> 
> > wine SOL.EXE                                     
> wine: Symbol `Dosvm' has different size in shared object, consider
> re-linking
> X Error of failed request:  BadMatch (invalid parameter attributes)
>   Major opcode of failed request:  1 (X_CreateWindow)
>   Serial number of failed request:  13
>   Current serial number in output stream:  15
> err:ntdll:RtlpWaitForCriticalSection section 0x40116ad0 "syslevel.c:
> Win16Mutex" wait timed out, retrying (60 sec) fs=008f
> fixme:pthread_kill_other_threads_np
> Console: Making console complex (creating an xterm)...
> fixme:pthread_kill_other_threads_np
> fixme:pthread_kill_other_threads_np
> fixme:pthread_kill_other_threads_np
> fixme:pthread_kill_other_threads_np
> fixme:pthread_kill_other_threads_np
> fixme:pthread_kill_other_threads_np
> fixme:pthread_kill_other_threads_np
> passed master doesn't match slave name