RE : RE : RE : DOS command window problem for Windows 2000

2003-11-20 Thread Seak, Teng-Fong
Please do a Reply all so that your email is sent to the list, but not to me 
only.

 -Message d'origine-
 De : Crewdson, Dave [mailto:[EMAIL PROTECTED] 
 
 I have tried the DOS window with both machines on the same 
 network, and also with my laptop at home via VPN, and the DOS 
 window is flaky with both interfaces.
 
 Otherwise, all desktop remote functions are working fine through VNC.
 
 Memory and speed on both machines is fine. 
 I have not tried lowering my colors to 256 and it does not 
 seem to like me doing that remotely;

I could change color depth to all my VNC client machines without any problem.  
Strange that you can't do so.

  I will have to wait 
 until I am back in the office.  I doubt that will help any.

How can you judge an efficiency without even trying it before?

 DOS commands are executed but the echo of my commands is very 
 sporadic.
 
 Yes we have a firewall.   Others in the office do not have 
 this problem, so
 it's not our network.  I need to have someone else try 
 VPC'ing to my server.

Do you mean when others're using THEIR computers to connect to YOUR (VNC 
server resided) computer, they don't have the problem?  Or do you mean when they're 
using SOME computers to connect to THEIR (VNC server resided) computers and there's no 
problem?

 My server is W2k and my laptop is xp.  I have tried both VNC 
 3.3.6 and 3.3.7 and neither work for my DOS window.

OTOH, you said that behaviours of DOS windows are different according to the 
way they're called, right?  One is by shortcut icon, the other is by Run  cmd.

Have you compared their properties?  DOS window called by shortcut contains 
some properties configured in the shortcut.  Check this.

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On Behalf  Of Seak, 
 Teng-Fong
 Sent: Tuesday, November 18, 2003 7:07 AM
 To: [EMAIL PROTECTED]
 Subject: RE : RE : DOS command window problem for Windows 2000 
 
 
   You haven't mentioned if both server and client machine 
 are connected in ethernet or just dial-up connection (through 
 Internet) or what. And also the machines themselves?  Are 
 they fast enough, like at least 500MHz?
 
   Since VNC just reproduced what is drawn, and as Dos 
 cursor is changing all the time, maybe the connection or CPU 
 frequency is the cause?
 
   Also, what's your screen's resolution and depth?  Have 
 you tried to reduced its depth to 256 colors (and wall paper)?
___
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list


RE : RE : DOS command window problem for Windows 2000

2003-11-18 Thread Seak, Teng-Fong
You haven't mentioned if both server and client machine are connected in 
ethernet or just dial-up connection (through Internet) or what.  And also the machines 
themselves?  Are they fast enough, like at least 500MHz?

Since VNC just reproduced what is drawn, and as Dos cursor is changing all the 
time, maybe the connection or CPU frequency is the cause?

Also, what's your screen's resolution and depth?  Have you tried to reduced 
its depth to 256 colors (and wall paper)?

 -Message d'origine-
 De : Crewdson, Dave [mailto:[EMAIL PROTECTED] 
 Envoyi : mardi 18 novembre 2003 00:41
 @ : Seak, Teng-Fong
 Objet : RE: RE : DOS command window problem for Windows 2000 
 
 
 I have the problem in both 3.3.6 and 3.3.7.  I gave up on 
 RealVNC and tried TightVNC instead, which someone suggested 
 to me, but I have the same problem with TightVNC also!!
___
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list


RE : DOS command window problem for Windows 2000

2003-11-17 Thread Seak, Teng-Fong
 -Message d'origine-
 De : Crewdson, Dave [mailto:[EMAIL PROTECTED] 
 Envoyi : vendredi 14 novembre 2003 21:37
 @ : '[EMAIL PROTECTED]'
 Objet : DOS command window problem for Windows 2000 
 
 
 I have seen several people in the past commenting that they 
 have no cursor control in DOS windows when using VNC.
  
 The only solution I saw was to click command prompt instead 
 of Start..Run...cmd.  This does not work for me.  
  
 I am running VNC from Windows XP to log into a Windows 2000 
 machine.  The DOS window appears but typing in it or pressing 
 ENTER is very sporadic.

As far as I remember, this problem happened in very old version (more than 3 
years ago) and I don't see this problem again nowadays in 3.3.7.  What version are you 
using?
___
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list


Re: dos command window problem for windows 2000

2003-11-17 Thread Jerry Trowbridge
On , [EMAIL PROTECTED] wrote:

I have seen several people in the past commenting that they have no cursor
control in DOS windows when using VNC.

Flakey dos commands are a problem for my partner, who tries to run a
console app over VNC and has terrible latency and cursor control
problems. We are running the version 4 betas.

I don't have the problem. He's running XP and viewing on XP. I am
running 2000 and vuewing on XP. 
- 
Jerry Trowbridge
--at Flying Pig Ranch
___
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list


DOS command window problem for Windows 2000

2003-11-14 Thread Crewdson, Dave
I have seen several people in the past commenting that they have no cursor
control in DOS windows when using VNC.
 
The only solution I saw was to click command prompt instead of
Start..Run...cmd.  This does not work for me.  
 
I am running VNC from Windows XP to log into a Windows 2000 machine.  The
DOS window appears but typing in it or pressing ENTER is very sporadic. 
___
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list