Trouble assigning a keyboard file to terminal type 2

[HarrisD1200]

Hi, I'm trying to assign a keyboard edit file to a terminal, and am having no luck. The keyboard file I'm using is dacs.kbd, and is changing the F7 function to work with Tellabs DACs. I go into OPTIONS, DATA OPTIONS, and TERMINAL OPTIONS, and assign the file to VT-320 terminal. VT320 shows dacs.kbd in terminal keyboard file and seems fine. I shut down PP, and when I come back it, it still says assigned. Now, the problem is, F7 doesn't work, and shows the wrong mapped info. But, if I go OPTIONS, KEYBOARD EDITOR, OPEN, then open dacs.kbd, it works and shows fine. I also created a new terminal type and assigned dacs.kbd to it, and that failed in the same way. Any ideas on what to try?

I couldn't find any pathing statements on where to put it, so placed dacs.kbd in D:\programs\Symantec\procomm plus\.

Thanks for any suggestions, while it's not inconvenient to load the file each time, it just seems unnecessary.

 

[knob]

Which version of Procomm and Windows are you using? I'm not seeing this problem on XP with version 4.8.

You are using the correct path for the .kbd file.

http://www.aspectscripting.com

 

[Firebird Scrambler]

As stated above, the path looks fine. is the file read only?.

All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

http://www.linkedin.com/in/davidbromley

If it's working, then leave it alone!.

 

[HarrisD1200]

Hi, thanks for the replies. The file is not read only. PP is 4.8, Build 71. This happens on both XP and Windows 7. No further progress sad to say. Thanks!

 

[HarrisD1200]

Ok, thanks both. I didn't find any attributes associated with the file, but it did start me thinking. I was given the file, and no matter what I did, I had the same problem. So, given that this is a unique problem, I opened one of the standard PP keyboard files, and cut and paste every keystroke from the DACS.KBD file into it. Saved it as DACSTST.KBD, and it works fine! I wish I'd been able to find what was wrong with the original file, but for now, I'm happy. Thanks for putting me on the correct path.