I have the same build of Constantin Kaplinskys Tight 1.1p8, which
works fine for Win98 server - however, the WINVNC service under NT
server/workstation crashes consistently, if I request Tight encoding
- the other encodings incl. JPEG works fine.

On one of the NT workstations I got the following crash msg:

Exception c0000005 at address 77f6750b (RtlEnterCriticalSection)

I hope that it is of any use to Constantin - I like Tight encoding
a lot, and I am looking forward to Tight 1.2!

Rasmus Mxller

-- original message ----

Date: Thu, 22 Feb 2001 04:20:48 -0800
From: Bill Taroli <[EMAIL PROTECTED]>
Subject: Tight 1.1p8 Questions

I just dove in and did a build of 1.1p8 for Win32 (wanted the server)
tonight. Seems to work just fine, but I have a few computers on which the
server crashes upon connecting. (These are machines that were running
3.3.3r2 and I dropped the tight 1.1p8 binaries on them.) Has anyone else
running 1.1p8 seen this? I haven't dug in further to debug and find the
cause, so was curious if someone else had already been through this.

When downloading the binary client, I noted that the *nix flavor allows the
preferred encoding to be specified on the command line. Upon inspection, I
believe that the Win32 source does not provide for this. Can anyone
disprove
me and tell me how to do it? Instead, I cheated and modified the viewer's
default preferred encoding to Tight, for now.

Bill Taroli
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------

Reply via email to