You can use the keys of the working Enterpad to send the programmed string for each key to a new configuration file.
That’s all, if the programming of the working Enterpad only contains strings. If it contains non-string codes (e.g., Shift, Ctrl, F1, Enter), you will need something to translate them into strings for the configuration file. The following utility will translate common non-character codes received from an Enterpad or from a regular keyboard into strings:
https://www.cedeq.com/enterpad-p120/down...nslate.exe
The utility (
KBTranslate) generates the following strings (for the corresponding non-character codes): “<shift>”, “<ctrl>”, “<alt>”, “<win>”, “<app>”, “<bksp>”, “<esc>”, “<prt>”, “<tab>”, “<cap>”, “<scrl>”, “<num>”, “<enter>”, “<eenter>”, “<F1>” to “<F24>”, “<eIns>”, “<eDel>”, “<eHome>”, “<eEnd>”, “<ePgup>”, “<ePgdn>”, “<eUp>”, “<eDn>”, “<eLf>”, and “<eRg>”.
KBTranslate also generates the string “<space>” for each space received. So, if something looks like a space in the output document, it is not a space; it is a non-character code not recognized by KBTranslate. You would have to investigate.
You can see how
KBTranslate works using your regular keyboard and a text document.
To stop
KBTranslate from running, right-click the ‘H’ icon in the taskbar and choose exit.
Use the latest
EPConfig (v5.16+) to load the new configuration file into an Enterpad.