Recent Virtual PC (Mac) posts* * * * * * * * * * * * * * * * * * * *
|
Add Solution
Latest Topics
Post Reply |
This is Spam! | Mark as Spam
VPC 6.1, OS X 10.3.9, Windows 98 and telnetSource: microsoft.public.mac.virtualpc Sent: 05/11/2005 From: (email address - cut out) Message:I have a new, obscure and confounding problem with VPC. Although my
environment and the issue at hand is probably rare, I'm hoping someone
here might have some insight:
I've been using VPC with Windows 98 since day one of OS X (and before).
My most-used Windows application is a host-specific terminal emulator
(specifically, Avaya's Site Administration ["ASA"] for managing its PBX
and voice mail products). I use Cisco's Mac VPN client to connect to a
corporate network across the Internet and then telnet from within ASA
to any of several Avaya PBXs. I use Windows 98 because it is much less
bloated than later Windows releases and, therefore, performs better for
my limited uses. BTW, VPC is set up with shared networking.
This setup has always worked beautifully, and fast. But after I updated
to OS X 10.3.9 around April 15 (no other concurrent changes
whatsoever), I started experiencing significant delays displaying
incoming ascii data within ASA's terminal window. The data flow would
often stop completely for anywhere from 10 seconds to as much as two
minutes or more, and then resume with no lost characters. Occasionally,
data would stop and never resume, but this was less common. Logging in
to the target PBX from another avenue would show that as far as the PBX
was concerned, it was done sending the requested screen of information.
So, clearly, the data was being buffered somewhere between the PBX and
ASA.
At first, the Cisco VPN client or something in the corporate LAN/WAN
infrastructure was suspected as the cause. But I have been able to
eliminate those possible causes by installing PowerTerm, a Mac-specific
generic terminal emulator. PowerTerm performs like lightening with the
same VPN/telnet connection; never any pauses whatsoever. So the issue
has to be somewhere between OS X 10.3.9 and VPC.
Has anyone else seen this, or is anyone in a position to try it out
with their setup? Can anyone tell me if updating to VPC 7.0 might solve
the problem?
Any help or advice would be greatly appreciated.
Brian Shaw
Post Reply |
This is Spam! | Mark as Spam
Related Messages
Post Reply |
This is Spam! | Mark as Spam
Other groups
|