RE: 8 bit PseudoColor problem
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 that Cadence still does not work with Cygwin/XFree86 even when you are using one of the two options outlined above? That would be disappointing because I did put a lot of time into the PseudoColor support and I was pretty certain that it was working properly. Hmm... Harold -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Charles Wilson Sent: Saturday, December 07, 2002 5:33 AM To: [EMAIL PROTECTED] Subject: Re: 8 bit PseudoColor problem 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 primary reason I'm still using XWin32, personally). Stephen -- nope, I don't think you can xhost cadence using cygwin-xfree yet. (And next time, include a little background. Not everybody instantly recalls every message on this list from the past four years) --Chuck Harold L Hunt II wrote: > Wow, with all of that information that you gave, we will be sure to > answer your question very quickly! > > Harold > > Allott, Stephen wrote: > >> I have just run across this problem using Cadence and wondered if it >> ever got solved?
Re: XDMCP on Windows 95
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] http://www.gotti.org ICQ: 126018723
Re: XDMCP on Windows 95
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 PROTECTED] http://www.gotti.org ICQ: 126018723
Re: XDMCP on Windows 95
/ "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 can | imagine it's going to be huge and I haven't got much time left to sort | this out. 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? 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?)?? /Andy -- The eye of the beholder rests on the beauty!
Re: 8 bit PseudoColor problem
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 primary reason I'm still using XWin32, personally). Stephen -- nope, I don't think you can xhost cadence using cygwin-xfree yet. (And next time, include a little background. Not everybody instantly recalls every message on this list from the past four years) --Chuck Harold L Hunt II wrote: Wow, with all of that information that you gave, we will be sure to answer your question very quickly! Harold Allott, Stephen wrote: I have just run across this problem using Cadence and wondered if it ever got solved?
