Link to home
Start Free TrialLog in
Avatar of maxtexgr
maxtexgrFlag for United States of America

asked on

HP ThinPro COM1 Redirection Incomplete

HP T510 with Thinpro and Topaz T-S460-B-R serial signature pad to COM1.  Serial port redirection setup to a 2k8 R Standard terminal server cluster.  When I test the signature pad through HyperTerminal or Putty the result that Topaz sees is near what I signed though with obvious dips or corrupt data parts of the signature which causes the signature pads to not work at all in the desired application.  Topaz has indicated that some HP thin clients have had this issue before.  Any suggestions on how this could be resolved?  Topaz has pointed towards HP and a call to HP I'm afraid will end up in phone transfers for a while and potential loss time.

Couple notes:
- Topaz's DemoOCX.exe doesn't work at all.
- Latest BIOS and OS from HP on the thin client.
- Works fine on XP embedded, unfortunately I don't have a license for this or 7e.  I'd rather use ThinPro if at all possible.
- Works fine on 7 Professional from my laptop.
- Tried multiple different signature pads and multiple thin clients.
- Unchecked compression, encryption, and every other options on the thin client possible with no luck.
- May try to upgrade the xfreerdp package on Linux to the latest, looks like it may be a version or so behind.

Thank you for your help.
ASKER CERTIFIED SOLUTION
Avatar of Gary Case
Gary Case
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of maxtexgr

ASKER

We ended up using some older Wyse SX0 thin clients with an eventual plan to change them to newer embedded OS's.  Haven't tried the ThinPro VMWare player yet though I plan to.  I did encourage Topaz to adjust their documentation on their site to reflect our experience and their feedback pointed in the direction that they may do so.  I was hoping getting xfreerdp to work would be an option as we end up having to support two different types of thin clients: embedded and ThinPro.  Thank you for your input.