-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
In my defence, I've searched the FAQ and tried to read the
documentation/troubleshooting help carefully. I've seen no reference to an
error like this, but it's horribly persistant here.
Running the server on a WIN2000 SP1 machine, running the clien
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20 Mar 01, at 11:15, [EMAIL PROTECTED] wrote:
> On Sat, 17 Mar 2001, Tim Waugh wrote:
>
> > It means that anyone who is on the path that the TCP/IP packets take
> > through the Internet can do bad things. So for instance, if you are
> > using ca
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21 Mar 01, at 10:23, Mac Reiter wrote:
> Of course, it is Linux GCC code, so I have no idea how nasty it will be
> getting it into VC...
>
Getting a bit off the subject here (PLEASE, could someone say something
about my posting about "VNC freez
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21 Mar 01, at 15:31, Mac Reiter wrote:
> >Getting a bit off the subject here (PLEASE, could someone say something
> >about my posting about "VNC freezes and then disappears"; it's unusable
>
> I have absolutely no idea if it will help, but I'll
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21 Mar 01, at 17:30, Neel, Steve wrote:
> Are you running any kind of firewall. For example, is zonealarm, blackice,
> or other program of this type installed?
>
Not between the two machines in question. They are on my internal home
network. Th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All right. I give up. How do I turn on logging?
Yes, I did read the FAQ. I tried putting things in various order, such as :
- -logfile logfile.txt -loglevel 12 90.0.0.2:0
90.0.0.2:0 -logfile logfile.txt -loglevel 12
but I just get the -h window telli
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All right. I finally got VNC to generate a level 12 logfile.
Here is what it says immediately before it hangs and disappears.
I hope that it means something to someone! "Socket error" doesn't tell me
very much without a winsock error number.
Doc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 26 Mar 01, at 11:50, Steve Palocz wrote:
> yeah,
> I think it means that there is a driver problem. I would assume nic but
> might be video. What kind of nic and video are you using, and what
> drivers?
>
On the client (one-year-old Win98SE mach
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 26 Mar 01, at 17:18, Steve Palocz wrote:
> If you search the mail archives I think you will find that other people
> that have had similar problems as you had the intel nic or older drivers
> for various other cards. But you might see if linksys h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
A review of old mail didn't really turn up anything negative about Intel
NICs (the opposite, in fact). However, it did make it pretty clear that
poor NIC drivers seem to have a habit of causing the kind of symtom that I
am seeing.
Odd that the NIC
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OK! It was a NIC on the client.
I switched a couple of the NIC cards in the client and now everythig works.
Interestingly, the NIC that was failing with VNC seems to be working just
fine as main my power-horse NIC to the Internet.
It's very strang
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
What I forgot to say was the most important thing:
THANK YOU VERY MUCH!
Doc Evans
On 27 Mar 01, at 9:12, D. R. Evans wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> OK! It was a NIC on the client.
>
> I switch
A search of the archives didn't seem to mention this one.
Configuration:
Running the client on Win98
Servers on both Linux and Win2000
I observe the following behaviour:
If I minimize the main VNC window on the Win98 machine, and then de-
iconify it, no more updates are visible.
This is com
On 25 Apr 01, at 18:02, James ''Wez'' Weatherall wrote:
> When minimised, the viewer will stop requesting updates until it is
> restored. It may take some time for updates queued while the viewer was
> "asleep" to arrive, if a lot of changes occurred in the meantime.
>
Hmmm... I'm running over
On 25 Apr 01, at 18:02, James ''Wez'' Weatherall wrote:
> When minimised, the viewer will stop requesting updates until it is
> restored. It may take some time for updates queued while the viewer was
> "asleep" to arrive, if a lot of changes occurred in the meantime.
>
It turns out that the be
I've seen a few references in the archives to running xemacs over VNC
connections, but nothing that mentions the problem that I am seeing.
When I run VNC (Win98 client; Linux server) and fire up xemacs on the
server, I see four keymap warnings. These warnings take up the bottom
half of the edi
On 30 Apr 01, at 13:39, Nigel Morse wrote:
> I've seen similar problems when using Exceed as well. I can't remeber how it
> was fixed as the Xemacs guru has left now. You may get some luck on an
> xemacs mailist (if you haven't tried already!)
>
Well, at least it's not one of those "no one els
On 30 Apr 01, at 20:26, James ''Wez'' Weatherall wrote:
>
> That's strange. I bet the powerpro program does something naughty to
> minimise and restore apps. Difficult to see how, though.
>
Aye, that's what I thought, too. However, another user on the PowerPro
reflector has confirmed the be
Thanks for this. I'll try this as soon as I get the chance.
(Thanks also to the person who suggested I try tightvnc. When I have
some time to spare, I'll try experimenting with that as well.)
Doc Evans
On 1 May 01, at 13:28, Levy Rami-ERL005 wrote:
> Hi,
>
> I regularly experience the same
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 26 Mar 01, at 11:50, Steve Palocz wrote:
> yeah,
> I think it means that there is a driver problem. I would assume nic but
> might be video. What kind of nic and video are you using, and what
> drivers?
>
A response! A response! Excuse me for a
On 25 May 01, at 10:06, Frank Evan Perdicaro wrote:
> > > I too am experiencing Windows freeze and have been working on narrowing
> > > down the problem. Later today I will be trying another configuration.
> >
> > The problem you describe is completely different from the problem described
> > b
21 matches
Mail list logo
