Help! Press NP Add not working

E Coli · Post by **E Coli** » Tue Feb 04, 2003 10:45 pm

Hope you all don't lose patience with a newbie. So far things have been going very well. However, I'm stumped again with this one.

When entering text into our AS400 emulator, the NP Add key clears the remaining portion of the active field, then moves down to the next field. Very important function. However, when I use the

Press NP Add

it simply does not register. So far, all other functions have. I made sure to set the focus to the proper window, tried it with the NumLock on and off, but nothing seems to make my AS400 "see" it when I use the Press NP Add. I can press the button myself and everything it works fine manually. I've used Press Tab and Press Enter with no problem. Why won't it send Press NP Add?

Anyone have any ideas?

Special thanks to Lumumba for your help so far!

Eric

Dave · Post by **Dave** » Thu Oct 25, 2007 3:27 pm

I have the exact same problem. The AS400 IBM I Series client will not take any characters using either send or press. ??? Whats up with that? How can I correct this / work around?

Dave

Dave · Post by **Dave** » Thu Oct 25, 2007 3:56 pm

So far I have done some more digging, on this issue. I found that the AS400 will recognise MS Scripted characters sent to it up to a certain point the you can hear a windows sound ("dom"), after that sound is herd, Macro Scheduler becomes usless, as you cannot send any characters to the session window. I think this might be some sort of security feature. Windows on screen key board works though. Any ideas?

Post by **Marcus Tettmar** » Thu Oct 25, 2007 4:12 pm

Sounds like there is too much in the keyboard buffer.

Try slowing the key send rate down:

Let>SK_DELAY=100

That inserts a 100 millisecond delay between characters. 100 may be more than necessary ... experiment.

Dave · Post by **Dave** » Thu Oct 25, 2007 4:17 pm

But the regular keyboard works just fine and so does the Windows accessibility on screen keyboard. That may the answer in itself.... Make many macros to click the On screen keyboard but it would be better to be able to use MS commands stright outright.
Dave

Post by **Marcus Tettmar** » Thu Oct 25, 2007 4:25 pm

Yes, but it could be related to the send-rate. Macro Scheduler sends much faster than you can type. Have you tried my suggestion?

Dave · Post by **Dave** » Fri Oct 26, 2007 4:00 pm

Yes, experimented a whole lot with it. Did not work. The only work around I havecome up with is to use the on screen keyboard and create a macro for each character.

Post by **Marcus Tettmar** » Fri Oct 26, 2007 4:27 pm

What about SK_LEGACY=1?