He's referring to a very old message on this list concerning 8bit
PseudoColor support in cygwin-xfree and Cadence. Cadence is a CAD
package that requires that feature -- and since PseudoColor support in
cygwin-xfree is sketchy at best, you can't really use it to xhost
cadence. (Which is the
/ J S [EMAIL PROTECTED] wrote:
| All i did was :
| xwin -query host -fp host:7100 -from mypc
| I didn't pass the extra parms so I guess there was a flaw in that
| theory! I'm clutching at straws a bit now though 'cos I'm desperate to
| sort this out. I would have a look at the source code but I
J S wrote:
Would I be right
in saying though that the most likely cause has got to be something windows
95-network related since the original message said invalid address and this
only occurs on win 95?
Have you already tried the ls_netdev tool as suggested?
bye
ago
--
[EMAIL
Andrew Markebo wrote:
Just another wild thought.. not only VPN.. any other socket
handling/protecting software on the 95? Does the machine have winsock
2 (does cygwin require winsock 2?)??
no. cygwin does work even with the old win95a class socket layer
bye
--
[EMAIL PROTECTED]
Chuck,
I wouldn't say that PseudoColor support is sketchy. I mean, it works fine
either in fullscreen or if you are running Windows in 8 bit color mode.
Granted, PseudoColor is not available when you are running in windowed mode
with Windows set at higher than 8 bit color.
Are you telling me
