> }> All,
> }> I agree with the customer that this cannot be normal behaviour, however,
> }> I am using TNG Console Manager with the serial line connected into a
> }> terminal server and over the network as the box is in Holland and I'm in
> }> the UK.
> }> Ade
> }I remember my first use of the swxcrmgr utility running on a VT terminal.
> }After about the 10% stage you could see what it was doing to update
> }the screen which must have been doing an update after every I/O. It
> }got slower and slower. You could see the cursor going crazy all over
> }screen. Doing the same thing using a graphics monitor the time was
> }about 40 minutes as opposed to about 12 hours on the VT.
> }An absolutely dreadful piece of software.
> Which brings up the question of what communication speed his terminal
> is set to use.
> If it is something unusually slow, like 4800 bps or lower since 9600 bps
> is generally the "normal" speed, then that (in conjuntion with the very
> poor design of the software) could explain why it is taking him even longer
> than everybody else.
> Simply doubling the communication speed setting of the terminal could
> cut the time in half, unless there are serious bottlenecks in his
> network connection as well. Likewise for quadrupling it to cut the time
> by a factor of 4.
> --- Carl
The console port is set to the usual 9600. Unfortunately, I would have to stop
the procedure to change it - not an option at this stage.
By the way, we're almost there now with the last two sets reporting 92 and 85%.