This one really has me stumped but I'm sure as soon as I post this
I'll figure it out. At least that's what happened last time.

I have a few client workstations having problems with function keys
and script calls. These oddball stations will only enter one character
from a string on a function key and only one (leading) character in a
script.

Using winteg 6.1.2 btw

Example - an F-key programmed to enter the string "customers" to
invoke the customer edit program will only enter the leading "c" at
the d3 prompt then nothing else. The f-key also has the \r on then end
to act as a press of the 'enter' key to make the thing go.

And just as in the F-key case, a pick basic program using the
win.pcscript call to run a script file will only output the first
character of the called script and stop.

When I first noticed this behavior I was able to do a hard boot and
clear it up. On some machines that works and others it does not. One
case was even stranger where a hard boot did not clear the problem but
the same machine started up the next day with no problems.
Thanks in advance for any help,
Terry

Took more than a few days to figure this out but finally did. Turns
out it's a problem with a few of the ports on the system not liking
rapid input.

Running D3 7.5.1 Linux on a virtual Red Hat server v 5.3 - a reboot
seems to have fixed this strange behavior.

terry

On Aug 22, 9:33*am, terrymaui <terry... (AT) terrypen (DOT) com> wrote: