Discussion:
VNC versus Citrix ICA
Severin Olloz
2001-04-20 22:16:12 UTC
Permalink
Hello...

VNC is fast but I heart the Citrix ICA protocol is faster!?

Is this true?
--
Severin Olloz
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to ***@uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
Jonathan Morton
2001-04-21 00:12:55 UTC
Permalink
Post by Severin Olloz
VNC is fast but I heart the Citrix ICA protocol is faster!?
Is this true?
It may be, under certain conditions. If you have any suggestions on how to
improve the VNC protocol, suggest away. Meanwhile, VNC has the big
advantages of being "fast enough" and of being Free.

--------------------------------------------------------------
from: Jonathan "Chromatix" Morton
mail: ***@cyberspace.org (not for attachments)
big-mail: ***@penguinpowered.com
uni-mail: ***@lancaster.ac.uk

The key to knowledge is not to rely on people to teach you it.

Get VNC Server for Macintosh from http://www.chromatix.uklinux.net/vnc/

-----BEGIN GEEK CODE BLOCK-----
Version 3.12
GCS$/E/S dpu(!) s:- a20 C+++ UL++ P L+++ E W+ N- o? K? w--- O-- M++$ V? PS
PE- Y+ PGP++ t- 5- X- R !tv b++ DI+++ D G e+ h+ r++ y+(*)
-----END GEEK CODE BLOCK-----
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to ***@uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
Severin Olloz
2001-04-21 00:44:55 UTC
Permalink
Hello...
Post by Jonathan Morton
It may be, under certain conditions. If you have any suggestions on how to
improve the VNC protocol, suggest away. Meanwhile, VNC has the big
advantages of being "fast enough" and of being Free.
Today I tested a Linux VNC-session with a 33Kbps modem over the internet and
its very very slow with the VNC Tight Encoder too - have I made something
wrong? (will try it with a ISDN connection soon) A M$ user "friend" ;-) has
told me he can use a Windows-session over ICA with a 33 modem without any
problems and with a mobile.phone connection too. I can't believe that!
--
Severin Olloz
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to ***@uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
David Smith
2001-04-21 14:45:48 UTC
Permalink
Post by Severin Olloz
Hello...
Post by Jonathan Morton
It may be, under certain conditions. If you have any suggestions on how to
improve the VNC protocol, suggest away. Meanwhile, VNC has the big
advantages of being "fast enough" and of being Free.
Today I tested a Linux VNC-session with a 33Kbps modem over the internet and
its very very slow with the VNC Tight Encoder too - have I made something
wrong? (will try it with a ISDN connection soon) A M$ user "friend" ;-) has
told me he can use a Windows-session over ICA with a 33 modem without any
problems and with a mobile.phone connection too. I can't believe that!
I did read Michael Milette's excelent post on ICA as well, so this
may have some responses to it as well.

Some background on where I am coming from. I am a UNIX admin who
uses VNC for remote control of various platforms. I also lend a had
to our Metaframe admin when he has trouble.

The basic server (Winframe or Terminal Server) only supports MS
Windows platforms, adding the Metaframe piece to the server, which is
quite a bit of money, is necessary to add support for non MS clients
(MacOS, Java, UNIX, etc). There is now a server for UNIX.

Metaframe is based on Windows NT 4.0 (as Terminal server is based on
Windows 2000) but it is NOT NT. There are separate Service Packs
(and you CANNOT install the normal ones!). We have run into a lot of
application issues. Applications that install or upgrade shared dll
files into the system directory can really screw up things.
Applications that want to write to c:\temp or the application
directory don't work well or at all (since that is a shared
directory, and in most installations locked down). Silly things that
would require a reboot on a Windows NT system will on a Metaframe
server as well, but it is going to affect more than just a single
user.

The client, in particular the Win32 client, is quite fat.

Some of the positive things I have found about Metaframe. You can
export a single application cleanly (very cool). It has build in
compression and encryption that is better than VNC. Users can define
their own display settings (individual settings for depth, sound, and
resolution). The server clustering and application balancing works
well. You can map local printers and drives to your server session.

You can't, to my knowledge, share a session with Metaframe (I know
the admin can view or control a session though).

All in all both fill nitches. Metaframe is better for centralized
application shared (if the application works on it). VNC is great
for individual desktop control and for cross platform connections. I
have also found VNC's client much easier to distribute, since it is
one binary with no required configuration while Metaframe's client
has to be configured for your server (unless you happen to be on the
same local subnet) and has a myiad of configuration options (which is
good for an advanced user but really hard to get set up for a
beginner).
--
--------------
David A. Smith
<***@blkbox.com>
The box said: "Needs Windows 98 or better," so I bought a Macintosh.
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to ***@uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
Mac Reiter
2001-04-23 16:37:34 UTC
Permalink
Having recently had to perform some fairly intensive comparisons of
Terminal Server 2000 (which is either the same as or very close to the
Citrix ICA protocol/system) and VNC, I have discovered the following:

1. TS2000 is *extremely* fast. We can use it to remotely control video
cameras and see the video feed in almost real-time (slight tearing) on a
10Mbps ethernet.
2. TS2000 is 8bit palettized *ONLY*. It will not support 16bit or higher.
3. When VNC is also limited (at the SERVER side) to 8bit, it becomes very
fast as well.
4. Checking the "Restrict to 8 bit depth" on the VIEWER will not result in
as much of a speedup as changing the SERVER depth to 8bit. It is still
useful over slow links, but it increases the server CPU load and thus slows
down overall frame rate over a good link.
5. TS2000/Citrix have the advantage of working much more like the Xvnc
server. They generate a virtual screen that does not exist anywhere except
in memory and on the remote terminal. The server is immediately notified
of all graphics operations, and (as Wez mentioned) it can simply forward
the calls directly to the viewer which can perform the operation there.
For instance, text can be transmitted as a context number and the string in
TS2000. Cross platform transmission requires transmitting the actual pixel
values, which takes quite a bit more (although Tight Encoding can help
quite a bit over a slow link -- not as useful over a fast link)
6. WinVNC serving an 8bit screen appears to have some palette handling
oddities if the hardware palette is being changed extremely rapidly (video
camera, anim playback, etc). This may be a misconfiguration on my part.

Overall, if you set your server to 8bit (which is the only valid way to
compare), WinVNC can perform at only around 3-4 times slower than TS2000
for graphically intensive work, and at almost the same speed for
conventional application work. This is fairly impressive for a free,
no-licensing, cross platform system. Slower links will benefit from Tight
Encoding and maintaining the newest TridiaVNC server/viewer. Also, if you
have a fast connection, Hextile encoding appears to be the fastest option.
I can't give any direct suggestions yet about when to switch to Tight
Encoding and jacking up the compression levels.

BTW, if anyone has a suggestion to avoid the palette mangling on VNC, I'd
like to hear it. Seems like there was a palette problem on an X based CAD
program that changed the palette a lot. Seems like a palette change
triggers a screen update because thats the only way to guarantee the colors
are all right. Really fast palette changes cause the palette to change
faster than the screen updates can be sent, which is probably the source of
the problem.

Hope that others can benefit from my results,
Mac
_____________________________ /"\
Mac Reiter \ / ASCII Ribbon Campaign
Nomadics, Inc. X Against HTML Mail
***@nomadics.com / \
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to ***@uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
Lee Allen
2001-04-23 16:55:02 UTC
Permalink
This is extremely valuable information -- not just the ICA vs VNC
comparison, but, to me, the hints on optimizing performance of VNC on
different connections.

Thank you!

-Lee Allen
Post by Mac Reiter
Having recently had to perform some fairly intensive comparisons of
Terminal Server 2000 (which is either the same as or very close to the
(HUGE SNIP)
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to ***@uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
Jonathan Morton
2001-04-21 01:16:26 UTC
Permalink
Post by Severin Olloz
Post by Jonathan Morton
It may be, under certain conditions. If you have any suggestions on how to
improve the VNC protocol, suggest away. Meanwhile, VNC has the big
advantages of being "fast enough" and of being Free.
Today I tested a Linux VNC-session with a 33Kbps modem over the internet and
its very very slow with the VNC Tight Encoder too - have I made something
wrong? (will try it with a ISDN connection soon) A M$ user "friend" ;-) has
told me he can use a Windows-session over ICA with a 33 modem without any
problems and with a mobile.phone connection too. I can't believe that!
OK, analogue modems are slow. Remember though that both ends of the
connection have to support Tight for it to work correctly. You may also
find that adjusting your display settings helps as well (turn off
background patterns and pictures, for starters). If the server is based on
Windows and has a relatively old processor or video card, this may slow it
down as well (although it shouldn't be that noticeable over a modem).

BTW, "fast" protocols such as ICA probably work by sending relatively
OS-specific information from a fairly low-level part of the system, rather
than the generalised framebuffer protocol that is VNC. VNC's
cross-platform ability is entirely due to this generalised framebuffer
approach.

--------------------------------------------------------------
from: Jonathan "Chromatix" Morton
mail: ***@cyberspace.org (not for attachments)
big-mail: ***@penguinpowered.com
uni-mail: ***@lancaster.ac.uk

The key to knowledge is not to rely on people to teach you it.

Get VNC Server for Macintosh from http://www.chromatix.uklinux.net/vnc/

-----BEGIN GEEK CODE BLOCK-----
Version 3.12
GCS$/E/S dpu(!) s:- a20 C+++ UL++ P L+++ E W+ N- o? K? w--- O-- M++$ V? PS
PE- Y+ PGP++ t- 5- X- R !tv b++ DI+++ D G e+ h+ r++ y+(*)
-----END GEEK CODE BLOCK-----
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to ***@uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
Jeff Boerio
2001-04-21 02:36:35 UTC
Permalink
Post by Severin Olloz
Hello...
Post by Jonathan Morton
It may be, under certain conditions. If you have any suggestions on how to
improve the VNC protocol, suggest away. Meanwhile, VNC has the big
advantages of being "fast enough" and of being Free.
Today I tested a Linux VNC-session with a 33Kbps modem over the internet and
its very very slow with the VNC Tight Encoder too - have I made something
wrong? (will try it with a ISDN connection soon) A M$ user "friend" ;-) has
told me he can use a Windows-session over ICA with a 33 modem without any
problems and with a mobile.phone connection too. I can't believe that!
--
Severin Olloz
Measuring performance is often subjective. Depending on what your friend
and you are doing, that could very well explain differences. For example,
if one of you is doing graphics-intensive work, and the other doing simple
tasks, guess where some differences will be?

Also, keep in mind that the VNC viewer (client) needs to have the tight
encoding enabled; it's not an automatic thing. Obviously, the VNC server
needs to have the tight encoding built in as well.

I have used VNC over dialup sessions at speeds less than you achieved. I
found it to be "acceptable" for what I was doing -- reading my UNIX email
in an xterm.

- Jeff
--
Jeff Boerio, DPG-OR Engineering Computing, ***@ichips.intel.com
Mgr, UNIX Software Applications & Support
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to ***@uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
Michael Milette
2001-04-21 06:25:28 UTC
Permalink
Yes, it is true. The ICA protocol is actually optimized for low bandwidth.
One can actually work quite comfortably over a 28.8k+ connection. Scrolling
is quite good and it can keep up with typing most of the time.

It also has the benefit of automatic local drive mapping, com and lpt port
mapping, printers and sound. Though thin, the client install actually comes
on 2 diskettes so it's not quite as thin as VNC. Connections to the server
can be established over TCP/IP, IPX as well as others and even direct
dial-up. Like VNC, Citrix also has ICA clients available for many
platforms. The minimum hardware requirement is actually a 286 with 640k of
memory running DOS with a mouse and a VGA monitor. Such a machine, equipped
with a network connection or a modem can actually do pretty much anything
that the fastest and biggest machines can do. The resolution of the screen
session is actually determined at the client end and users can concurrently
be using the same server at different resolutions. Certainly an alternative
to consider when you are thinking of upgrading all of the machines in your
organization.

Similarly to VNC running on Unix, there is only one server (although you
can cluster them and do automatic load balancing). People who connect get
their very own virtual NT/Win2k machine, sharing hardware resources. Larger
Citrix servers can support over 80 concurrent connections depending on what
applications everyone is running. The more demanding the applications, the
less people you will be able to support concurrently before you start to
see the performance degrade. Application installation and maintenance is a
snap as long as you know what you are doing. Essentially you perform a
single install, configure the application once and the next thing you know
everybody can use it. Of course you can still restrict access using Windows
NT security and authentication can be controlled locally or though an
external system such as NT domain or Netware. Did I mention they now also
have a Unix version of MetaFrame available?

Even the ICA clients software can be updated remotely. If you update the
server, ICA clients will automatically be upgraded. Unlike VNC, you can
choose the level of encryption used for an ICA session including basic
encryption (kind of like scrambled with an encryption key applied), 40, 56
and 128 bit encryption. You can even choose to encrypt just the login part
of the session or the whole session. You can configure the server to use
any TCP/IP port you want and it works well though most firewalls.

By the way, you can save yourself a little money if you are willing to give
up some of the frills described above and just want to remotely access a
session on the server by dropping the Citrix part of the equation and just
going with the base Microsoft Terminal Server and the RDP Client. But back
to Citrix and MetaFrame.

A lot of off the shelf software will run just fine although some won't. The
only way to find out is to try it or ask the vendor if it is MetaFrame or
Terminal Server compatible. Most well written applications don't have a
problem.

Finally, if you work in a multilingual organization, both the client and
the server software is available in multiple languages.

Now for the down side.

This is not to say that it is without it's share of quirks and issues.
Certainly it can be challenging just like everything else in the IT world.

The biggest issue of course is price. The software doesn't go cheap,
especially once you've muddled your way though Terminal Server Licences,
CALs (Client Access Licenses) and of course the Citrix server software and
client licenses (at least the Citrix software is based on concurrent access
licenses unlike the Micro$oft stuff. Add that to the cost of a decent
server with oodles of memory and gobs of hard disk space and we are talking
pretty big bucks (but that's really a relative issue, isn't it? You should
do a cost benefit for your organization). By the way, if your application
runs on NT 3.51, Citrix still sells its WinFrame server which is a real
bargain since you don't have to deal with Microsoft licensing and you still
get most of the benefits above. Just straight concurrent usage licensing.
Life used to be so simple...

The Citrix ICA protocol isn't something you can just drop on any machine.
It only works as an add-on to Terminal Server. You can't use it to take
over just any old PC running Unix or Windows.

The ICA protocol is also optimized for use with typical applications. It
really slows down when you start displaying images, especially pictures.

There is also the danger of one user crashing the server since NT doesn't
support limiting memory per session. I know, neither does a VNC session
except that when you crash a PC running VNC, you crash one PC for one user.
When someone crashes a MetaFrame server, it goes down for all of it's
users. That's when you start wishing you had implemented that server farms
(clustering/load balancing). One way to reduce the chances of this
happening is to limit what users are able to run and not to allow them to
run anything unauthorized.

As far as I am concerned, VNC and ICA have only one thing in common. They
are both classified as thin clients. VNC to take over the screen of a
single machine (or virtual screen in the case of Unix) and ICA to take over
the screen of a virtual machine.

Sorry for making this such a long message. I guess I had a lot to say.

Michael Milette
Post by Severin Olloz
Hello...
VNC is fast but I heart the Citrix ICA protocol is faster!?
Is this true?
--
Severin Olloz
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to ***@uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
Jonathan Morton
2001-04-21 15:28:26 UTC
Permalink
Post by Michael Milette
The Citrix ICA protocol isn't something you can just drop on any machine.
It only works as an add-on to Terminal Server. You can't use it to take
over just any old PC running Unix or Windows.
The ICA protocol is also optimized for use with typical applications. It
really slows down when you start displaying images, especially pictures.
Just as I thought. It probably works very like the X11 protocol.
Post by Michael Milette
As far as I am concerned, VNC and ICA have only one thing in common. They
are both classified as thin clients. VNC to take over the screen of a
single machine (or virtual screen in the case of Unix) and ICA to take over
the screen of a virtual machine.
Two diskettes doesn't count as "thin client" to me. Fitting both server
AND client on a diskette does (as is currently possible with all VNC
implementations bar Xvnc). Then again, two diskettes is probably an
acceptable size for software with such licence complications (though I'm
glad to hear most of them aren't Citrix-originated).

--------------------------------------------------------------
from: Jonathan "Chromatix" Morton
mail: ***@cyberspace.org (not for attachments)
big-mail: ***@penguinpowered.com
uni-mail: ***@lancaster.ac.uk

The key to knowledge is not to rely on people to teach you it.

Get VNC Server for Macintosh from http://www.chromatix.uklinux.net/vnc/

-----BEGIN GEEK CODE BLOCK-----
Version 3.12
GCS$/E/S dpu(!) s:- a20 C+++ UL++ P L+++ E W+ N- o? K? w--- O-- M++$ V? PS
PE- Y+ PGP++ t- 5- X- R !tv b++ DI+++ D G e+ h+ r++ y+(*)
-----END GEEK CODE BLOCK-----
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to ***@uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
Greg Breland
2001-04-23 01:37:06 UTC
Permalink
-----Original Message-----
Yes, it is true. The ICA protocol is actually optimized for
low bandwidth.
This pretty much sums up ICA's advantage over RDP(Microsofts Protocol) and
RFB(VNC). ICA is fast at any speed. VNC and RDP are good at moderate to
high speed. VNC with the tight encoding is showing very good improvements at
the low bandwidth end of things, so VNC could be considered to be good at
all speeds. Try running a web browser or using Photoshop/Gimp over a VNC
and an ICA connection, and you will like VNC better.

Here is the technical difference.

Both ICA and RFB use the DRI(Direct Rendering Interface) or X11(Unix X
server protocol) calls coming from the windowing environment while VNC is a
"screen scrapper" and uses the actual graphic output to the screen. So if
the windowing env. outputs something like "show the letter 'A'", ICA and RDP
send a command to the remote client telling it to show the letter 'A' using
font Times. VNC actually lets the letter 'A' get written to your a video
buffer once the letter is drawn, VNC scans the letter and transmits the
results.

The only difference between RDP and ICA is that ICA has been optimized in
many ways for low bandwidth connections. If you were running a program over
RDP on a 9600 baud modem and the program was showing a video clip, RDP would
diligently send each and every frame over one frame at a time. ICA, as well
as VNC, would show a frame every so often depending on how big the video
was. This is true because ICA and VNC adjust for slow connections. RDP
might take 5 hours to play a one minute video clip while ICA and VNC will
only take on minute, but may only show 2 frames.

This is a worst case example, but the feedback from the client that ICA and
VNC use makes a big difference in the speed of the product.

The big speed difference between VNC and ICA is latency. Latency is the
amount of time it takes for the client to send a command to the server and
receive a response. ICA uses many techniques to improve latency over high
latency connections. When you click the letter 'A' on the keyboard when
running an ICA client, here is what happens:

1) ICA client draws and 'A' on you screen.
2) ICA client sends the letter 'A' to the server
3) If more letters are pressed before the response from the server returns,
the client keeps drawing letters locally and queuing the key strokes in the
send buffer.
4) When the sever responds with the result of the first key press, the
client draws the result. The server sends all addition key presses to the
server and starts back over at #3.

So if you are typing and email that is 2000 characters long, the client may
only talk to the server 500 times instead of 2000 like VNC would.

When you move your mouse around the ICA clients window, on a slow
connection, you mouse coordinates are sent to the server only every so
often. With VNC, if you move your mouse from the left of the screen to the
right the coordinates are sent as many times as is possible given the
current bandwidth. Tight VNC has actually modified this behavior in their
beta version.


Anyway, sorry for the long post, but someone should really write this up
nice(unlike mine) and put it in the FAQ. Very interesting stuff.

Greg
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to ***@uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
Liqun Xu
2001-04-23 14:42:29 UTC
Permalink
I am new to the VNC community. Can someone help
me here?

My company is trying to use the vnc for project
production, but we are not sure what is the limit
number of vnc servers can be run on a HP-Ux machine.
Our target is around 1500 users. Will this work?

If we use the VNC (which is a great software) in our
production, how can we get technical support ( I mean
not just a mailing list request, but some paid
services)? Is there any way I can find out?

Thank you in advance!

Leo

__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to ***@uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
Greg Breland
2001-04-23 17:07:21 UTC
Permalink
This is only true on Windows VNC servers. A VNC server on a Unix box has no
overhead other than the memory and CPU requirements of the programs run via
a VNC session.

If VNC server could hook Windows DRI calls, PcAnywhere, TS, and Citrix would
go out of business.

Greg
Post by Mac Reiter
It is still
useful over slow links, but it increases the server CPU load
and thus slows
down overall frame rate over a good link.
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to ***@uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
Mac Reiter
2001-04-23 17:34:53 UTC
Permalink
Post by Greg Breland
Post by Mac Reiter
It is still
useful over slow links, but it increases the server CPU load
and thus slows
down overall frame rate over a good link.
This is only true on Windows VNC servers. A VNC server on a Unix box has no
overhead other than the memory and CPU requirements of the programs run via
a VNC session.
The CPU load I was referring to was the load required to convert a 16bit or
higher screen into an 8bit screen for a viewer that has requested one.
That is a CPU overhead regardless of platform. It doesn't matter where the
highcolor pixels came from, it still takes time to shift, mask, and repack
the color components. If you are the only user, or if all users are going
to request 8bit transfers, it is much more efficient to make the server be
8bit native. If running WinVNC, just set the desktop depth to 8bit. If
running an Xvnc server, specify "-depth 8 -cc 3". It is useful to add the
"-cc 3" option to increase application compatibility. Otherwise you get
8bit truecolor, which a lot of programs don't understand.
Post by Greg Breland
If VNC server could hook Windows DRI calls, PcAnywhere, TS, and Citrix would
go out of business.
I heartily agree. I believe Wez is examining some methods for doing this
hooking. The list was pretty active a month or so ago with different ideas
for how to do so. Another thing to remember when comparing Citrix and TS
to VNC is that they only run on NT/2000 boxes. Those systems have clean
hooks into the video stream (which VNC could use, and may already be
using). Win98 and the other "personal" systems have rather hackish,
undocumented methods of doing similar work. I continue to hold out hope
for a breakthrough.

Mac
_____________________________ /"\
Mac Reiter \ / ASCII Ribbon Campaign
Nomadics, Inc. X Against HTML Mail
***@nomadics.com / \
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to ***@uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
Glenn Mabbutt
2001-04-23 19:27:51 UTC
Permalink
<snip>
...
3. When VNC is also limited (at the SERVER side) to 8bit, it becomes very
fast as well.
4. Checking the "Restrict to 8 bit depth" on the VIEWER will not result in
as much of a speedup as changing the SERVER depth to 8bit. It is still
useful over slow links, but it increases the server CPU load and thus slows
down overall frame rate over a good link.
...
</snip>

OK, I've check the docs and I've checked the default settings on a running
machine, and I'm obviously missing something vital - how do I get the WinVNC
server to run in 8 bit depth, and run as a service (NT machine)??

Glenn
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to ***@uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
James ''Wez'' Weatherall
2001-04-24 14:33:20 UTC
Permalink
Run as a service using "winvnc -install" to install the service and "net
start winvnc" to start it.

The server depth is whatever depth the server PC's display is set to.

Cheers,

James "Wez" Weatherall
--
"The path to enlightenment is /usr/bin/enlightenment"
Laboratory for Communications Engineering, Cambridge - Tel : 766513
AT&T Labs Cambridge, UK - Tel : 343000

----- Original Message -----
From: "Glenn Mabbutt" <***@quartetservice.com>
To: <vnc-***@uk.research.att.com>
Sent: Monday, April 23, 2001 7:08 PM
Subject: RE: VNC versus Citrix ICA
Post by Glenn Mabbutt
<snip>
...
3. When VNC is also limited (at the SERVER side) to 8bit, it becomes very
fast as well.
4. Checking the "Restrict to 8 bit depth" on the VIEWER will not result in
as much of a speedup as changing the SERVER depth to 8bit. It is still
useful over slow links, but it increases the server CPU load and thus slows
down overall frame rate over a good link.
...
</snip>
OK, I've check the docs and I've checked the default settings on a running
machine, and I'm obviously missing something vital - how do I get the WinVNC
server to run in 8 bit depth, and run as a service (NT machine)??
Glenn
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to ***@uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
Gonzalo Palma
2001-04-24 16:55:10 UTC
Permalink
Windows NT 4.0 - VNC 3.3.3r9

Hi,
I would like to get a log file.with all conection history.
is it posible?

Thanks

----- Original Message -----
From: "James ''Wez'' Weatherall" <***@cam.ac.uk>
To: <vnc-***@uk.research.att.com>
Sent: Tuesday, April 24, 2001 10:27 AM
Subject: Re: VNC versus Citrix ICA
Post by James ''Wez'' Weatherall
Run as a service using "winvnc -install" to install the service and "net
start winvnc" to start it.
The server depth is whatever depth the server PC's display is set to.
Cheers,
James "Wez" Weatherall
--
"The path to enlightenment is /usr/bin/enlightenment"
Laboratory for Communications Engineering, Cambridge - Tel : 766513
AT&T Labs Cambridge, UK - Tel : 343000
----- Original Message -----
Sent: Monday, April 23, 2001 7:08 PM
Subject: RE: VNC versus Citrix ICA
Post by Glenn Mabbutt
<snip>
...
3. When VNC is also limited (at the SERVER side) to 8bit, it becomes very
fast as well.
4. Checking the "Restrict to 8 bit depth" on the VIEWER will not result in
as much of a speedup as changing the SERVER depth to 8bit. It is still
useful over slow links, but it increases the server CPU load and thus
slows
Post by Glenn Mabbutt
down overall frame rate over a good link.
...
</snip>
OK, I've check the docs and I've checked the default settings on a running
machine, and I'm obviously missing something vital - how do I get the
WinVNC
Post by Glenn Mabbutt
server to run in 8 bit depth, and run as a service (NT machine)??
Glenn
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to ***@uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
Mac Reiter
2001-04-23 20:52:57 UTC
Permalink
Post by Glenn Mabbutt
machine, and I'm obviously missing something vital - how do I get the WinVNC
server to run in 8 bit depth, and run as a service (NT machine)??
WinVNC runs at the same depth as your windows desktop. Go to Display
Properties (Start - Settings - Control Panel, then Display applet, then go
to the Settings Tab). You can change color depth from there.

Your VNC group in the Start menu should have a submenu for "Administrative
Tools", which should have an entry for "Install WinVNC Service"

Mac
_____________________________ /"\
Mac Reiter \ / ASCII Ribbon Campaign
Nomadics, Inc. X Against HTML Mail
***@nomadics.com / \
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to ***@uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
Greg Breland
2001-04-23 21:17:45 UTC
Permalink
You must reboot the machine after making this change. For some reason, the
login screen uses the resolution and color depth the machine was booted
into. So if you change the res or depth and logout, you will notice that
the login screen is still in whatever res/depth you booted with. Weird.

Greg
Post by Glenn Mabbutt
Post by Glenn Mabbutt
machine, and I'm obviously missing something vital - how do
I get the WinVNC
Post by Glenn Mabbutt
server to run in 8 bit depth, and run as a service (NT machine)??
WinVNC runs at the same depth as your windows desktop. Go to Display
Properties (Start - Settings - Control Panel, then Display
applet, then go
to the Settings Tab). You can change color depth from there.
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to ***@uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
Seth Kneller
2001-04-23 22:01:10 UTC
Permalink
Post by Greg Breland
You must reboot the machine after making this change. For some reason, the
login screen uses the resolution and color depth the machine was booted
into. So if you change the res or depth and logout, you will notice that
the login screen is still in whatever res/depth you booted with. Weird.
Its also worth noting that if you are using NT, then unless you are logged
in as the Administrator then when you change the resolution, you only change
it for the person you are logged in as. If you do change the master
resolution then you have to reboot the box for it to become the default -
you will notice that if you don't that the resolution will keep switching
around.

Seth
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to ***@uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
Glenn Mabbutt
2001-04-23 23:16:05 UTC
Permalink
Thanks - I was under the impression the colour depth was a WinVNC
command-line or registry option of some sort.

-----Original Message-----
From: Mac Reiter [mailto:***@nomadics.com]
Sent: Monday, April 23, 2001 3:46 PM
To: vnc-***@uk.research.att.com
Subject: RE: VNC versus Citrix ICA
Post by Glenn Mabbutt
machine, and I'm obviously missing something vital - how do I get the
WinVNC
Post by Glenn Mabbutt
server to run in 8 bit depth, and run as a service (NT machine)??
WinVNC runs at the same depth as your windows desktop. Go to Display
Properties (Start - Settings - Control Panel, then Display applet, then go
to the Settings Tab). You can change color depth from there.

Your VNC group in the Start menu should have a submenu for "Administrative
Tools", which should have an entry for "Install WinVNC Service"

Mac
_____________________________ /"\
Mac Reiter \ / ASCII Ribbon Campaign
Nomadics, Inc. X Against HTML Mail
***@nomadics.com / \
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to ***@uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to ***@uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
Jannik Tonsberg
2001-04-25 08:36:03 UTC
Permalink
Hey,

It's if you are running linux (unix), it will look like this:

xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" -e sh -c
"telnet subdomain.domain.com \
| tee /var/log/consol/log_of_all" &

Insert this line into ~/.vnc/xstartup

If you are running win NT 4.0 as I can see, I don't know the answer.

Regards..

-----Original Message-----
From: Gonzalo Palma [mailto:***@yahoo.com]
Sent: 24. april 2001 16:51
To: vnc-***@uk.research.att.com
Subject: Log file?


Windows NT 4.0 - VNC 3.3.3r9

Hi,
I would like to get a log file.with all conection history.
is it posible?

Thanks

----- Original Message -----
From: "James ''Wez'' Weatherall" <***@cam.ac.uk>
To: <vnc-***@uk.research.att.com>
Sent: Tuesday, April 24, 2001 10:27 AM
Subject: Re: VNC versus Citrix ICA
Post by James ''Wez'' Weatherall
Run as a service using "winvnc -install" to install the service and "net
start winvnc" to start it.
The server depth is whatever depth the server PC's display is set to.
Cheers,
James "Wez" Weatherall
--
"The path to enlightenment is /usr/bin/enlightenment"
Laboratory for Communications Engineering, Cambridge - Tel : 766513
AT&T Labs Cambridge, UK - Tel : 343000
----- Original Message -----
Sent: Monday, April 23, 2001 7:08 PM
Subject: RE: VNC versus Citrix ICA
Post by Glenn Mabbutt
<snip>
...
3. When VNC is also limited (at the SERVER side) to 8bit, it becomes
very
Post by James ''Wez'' Weatherall
Post by Glenn Mabbutt
fast as well.
4. Checking the "Restrict to 8 bit depth" on the VIEWER will not result
in
Post by James ''Wez'' Weatherall
Post by Glenn Mabbutt
as much of a speedup as changing the SERVER depth to 8bit. It is still
useful over slow links, but it increases the server CPU load and thus
slows
Post by Glenn Mabbutt
down overall frame rate over a good link.
...
</snip>
OK, I've check the docs and I've checked the default settings on a
running
Post by James ''Wez'' Weatherall
Post by Glenn Mabbutt
machine, and I'm obviously missing something vital - how do I get the
WinVNC
Post by Glenn Mabbutt
server to run in 8 bit depth, and run as a service (NT machine)??
Glenn
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to ***@uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to ***@uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
Loading...