Walter,
It depends on how your machine has been configured. If the machine is
running xfs (X font server), then it could be one way. If not, it could
be the other. Wez has some a good suggestion - confirming how X11 is
configured for the console logins on that machine.
You will likely need to
Real VNC 4.0 will build on a SUSE-based 32-bit platform straight out of the box.
However, on the em64t platform, it will not. Enclosed is the patches I
applied in order to get it to build.
I know that I set some of the following variables: CFLAGS, CXXFLAGS,
LDFLAGS, and CXXLDFLAGS. The value w
I'm trying to configure Xvnc so that it will accept multiple color
depths on the same screen. We have two applications, one which is
required to run in 8-bit pseudocolor mode, and another which requires a
24-bit color depth.
There are ways to tell the Xvnc server that you want to use multiple
pix
I'm trying to build VNC 4.0 against X.org on SUSE and I'm having some
difficulties.
It appears that things aren't getting hooked in properly at "patch"
time, as if I look inside .../xc/programs/Xserver/vnc, no Makefile gets
created. Same as in .../xc/programs/Xserver/vnc/Xvnc.
On a tangent, has
Glad to see it!! Were there any differences between this and the 4.0b5
that recently came out?
Thanks,
- Jeff
On Tue, 2004-06-15 at 09:22, James Weatherall wrote:
> RealVNC is pleased to announce the release of VNC 4.0. VNC 4.0 is a
> complete redesign of the VNC system, but maintains ba
Just to follow on to what Wez says here, you may not enjoy the optimal
performance in this situation. In order to see the best performance,
using 4.0 Windows clients with 4.0 servers (I only care about servers
running on UNIX) is the best way to go.
- Jeff
On Tue, 2004-05-25 at 06:08, James
This isn't the first time I've received messages of this type, and I've
tried in the past to politely use their process to get off the list, yet
I remained for the most recent dose. So this time I sent email directly
to the person sent out the message asking them to clean up. I doubt it
will have
I've written an entirely custom vncserver script that we use
internally. One of the customizations we have allows for "global"
settings for things like the geometry and color depth and those settings
can be overridden by user customizations by looking at parameters inside
a ~/.vnc/Xvnc.rc file.
You might have better luck trying to build VNC against XFree86 4.3.0 or
4.2.0 (the latter is what Real VNC builds against in their binary
packages they distribute).
I tried building VNC 4.0b4 against XFree86 4.4.0 on Linux and was able
to get an Xvnc binary, but it segfaults very early on:
(gdb)
I'll second Wez's statement here. I've got 4.0b4 in production with my
customers because they have been begging me for the performance
improvements it brings. I've filed a couple of reports against this
version, but expect them to be rolled into the next beta/production
release.
- Jeff
On
The linker line does show libvnc.a before librfb.a in the Makefile.
Entering the command by hand doesn't change anything.
/opt/aCC/bin/aCC -o Xvnc +O1 -AA -L../../exports/lib -L/usr/lib
vnc/Xvnc/stubs.o vnc/Xvnc/miinitext.o \
dix/libdix.a os/libos.a ../../exports/lib/libXau.a
I may not have been clear ... I'm interested in 4.0 VNC source, not
older versions.
- Jeff
On Tue, 2004-03-23 at 17:14, Jeff Boerio wrote:
> Has anyone out there successfully built an Xvnc binary from source?
>
> I'm getting extremely close, but I get a ton of unr
Has anyone out there successfully built an Xvnc binary from source?
I'm getting extremely close, but I get a ton of unresolved/unsatisfied
symbols at link time. If anyone has gotten past this, I (and others on
the list) would appreciate hearing from you.
Thanks,
- Jeff
/opt/aCC/b
Has anyone been successful in using icfb (v4.x) with VNC?
It appears to want to use an 8-plane pseudocolor visual, but even in a
minimalist environment, there are shortcut windows that do not appear to
be getting the correct colors (specifically, the black background color
is very pale, as is text
We have a customer group using a CAD application from a company called
FEI. The application suite is called Knights. There is a colormap
utility with this program called Rainbow Maker (rmaker).
Besides being forced to run in 256 color mode (Xvnc -depth 8 -cc 3),
this rmaker utility appears to be
I wound up modifying my vncserver perl script to include launching
vncconfig. That saved having to tell many, many users to change their
xstartup file (or me having to do it).
- Jeff
On Wed, 2004-01-07 at 15:53, James Weatherall wrote:
> Lionel,
>
> You should use Xvnc 4b4 and remember to
I found that by moving to Windows viewer VNC 4.0b4, performance is
greatly improved over 3.3.7. Movign to UNIX Xvnc 4.0b4 only enhances
the performance improvements.
- Jeff
On Wed, 2004-01-07 at 14:33, Tim Wood wrote:
> VNC is great technology I've used over 3 years, so I was very surprised
I'd like to agree with William's statement that, if VNC is installed
system-wide in /usr/bin, that changing the permissions on Xvnc is the
right way to go. You could also customize your vncserver script to test
for the user ID and print a message that says only root can run VNC.
But this is reall
With Cadence, you may need to restrict the colormap. With VNC 3.3.x, I
have to launch Xvnc with -cc 3. With VNC 4.0, I need to use -depth 8
-cc 3.
- Jeff
On Mon, 2003-09-15 at 02:46, Fernando Rangel wrote:
> Hello,
>
>I just set up may VNC environment. It works with many X applicatio
Which version of VNC? 3.x versions of VNC did not build with IA64, and
I suspect that's because XFree86 3.x pre-dated the IA64 platform.
Real VNC 4.0b4 is based on XFree86 4.x, which does build cleanly on
IA64. I don't have much reason to test tight VNC, though.
- Jeff
On Sat, 2003-09-13
What version of the compiler are you using? Using gcc 3.2.2, I bomb
here, too. But with gcc 2.96, I can build the whole thing.
- Jeff
On Fri, 2003-08-01 at 06:08, Jason wrote:
> nobody's running freebsd?! ;)
> or do I need to provide more info?
>
> regards,
> Jason
>
>
> -- Forw
I've had success in building "older" versions of VNC (3.3.7 and earlier)
for both HP 10.20 and HP 11.00. But with VNC 4.0 beta 3, I have not
been successful.
For Linux, I used gcc 2.96 and got it to build. I could not get it to
build using gcc 3.0 and later. And on HP, I only have gcc 3.0 and
l
VNC 4.0 beta 3 includes support for this.
- Jeff
On Tue, 2003-07-29 at 14:14, Jayson Kempinger wrote:
> I have a computer running Windows XP with dual monitors. I have my
> desktop extended onto my second monitor and would like to access it from
> VNC. Is there any way to set this up?
>
>
veral people in the
> last month had a similar query regarding "Cadence Slowness"
>
> Jeff Boerio remarked that he had worked with the developers about fixing
> the problems.
>
> 1. I would like to get a better idea about what exactly the problem is and
> so would a
On Mon, 2003-07-28 at 13:48, Mike Miller wrote:
> On Mon, 28 Jul 2003, William Hooper wrote:
>
> > Li, Charles said:
> > > What is the difference between realvnc and tightvnc?
> > > Which is better?
> >
> > What is the difference between blue and red?
>
> They are that different now?
blue and re
I have gotten the sources to build on Red Hat 7.1 for both Pentium and
Itanium platforms. gcc 2.96 is what I used successfully for both. I
was NOT able to do this with gcc 3.x and have reported the feedback to
Real VNC.
I also have not been successful at all with HP-UX compiles (don't have
gcc
I have no idea if there's any collaboration going on between the folks
doing Tight VNC and those at Real VNC. Somehow, I'm not optimistic
about that.
- Jeff
On Wed, 2003-06-11 at 01:14, Fred Ma wrote:
> Jeff Boerio wrote:
> >
> > Fred,
> >
> > This
Fred,
This is a problem we have observed as well. I'm sure you notice that
the CPU of your Windows VNC client goes through the roof as it attempts
to do things such as redraws. It is not a network issue at all, it is
in the Windows client itself.
I spent a lot of time working with the folks at
ugging symbols found)...(no debugging symbols found)...
>(no debugging symbols found)...(no debugging symbols found)...
>(no debugging symbols found)...(no debugging symbols found)...
>#0 0x43574 in QueryFont+0xd8 ()
>(gdb) bt
>#0 0x43574 in QueryFont+0xd8 ()
>#1 0x2cbc4 in ProcQuer
would
likely work on HP11. The compile I get on 10.20 generates a binary, and
it runs. But as soon as a client connects, it does.
The binary I get on HP11 dumps core, unless you just say -help :)
I would really like to hear what people did to get this to compile on
those platforms.
Thanks,
30 matches
Mail list logo
