Keith & John: This should give me enough information to fix this pesky problem.
Thanks again. Bill -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Keith Johnson (DSLWN) Sent: Monday, November 05, 2007 4:02 PM To: [email protected] Cc: [EMAIL PROTECTED] Subject: RE:[U2] UD - SYSTEM(14) Hi Bill, There is a vague memory at the back of my mind that SYSTEM(14) could be problematical. Would it work in your circumstance to change the last line to use the "INPUT ..., -1" mechanism? EG * UNTIL NOT(SYSTEM(14)) DO REPEAT ; ** UD version INPUT ANYTHING.THERE,-1 WHILE ANYTHING.THERE DO REPEAT Regards, Keith -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Jenkins Sent: Monday, November 05, 2007 3:48 PM To: [email protected] Subject: RE: [U2] UD - SYSTEM(14) Bill The usual candidates: UDT.OPTIONS 109 ON (Telnet nodelay) for input Otherwise the likely candidates are: 1. VPN tunnel configuration 2. WAN network configuration 3. Any contention on the TELNET port? (change it from port 23 to something else and see). 4. (maybe) Broadcom NIC and driver combination 5. Dell management software True test: Open a DOS session on the CONSOLE (to localhost) and see if you have the same problem. If you are LOCAL and on the CONSOLE and have no problem then it's not UniData - it's something else. At that point it's a matter of elimination. At that point I'd try Microsoft Telnet and see if the problem exists there as well. Hope this helps..... Regards JayJay ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
