Smart questions
Smart answers
Smart people
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Member Login




Remember Me
Forgot Password?
Join Us!

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips now!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

Join Tek-Tips
*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Donate Today!

Do you enjoy these
technical forums?
Donate Today! Click Here

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.
Jobs from Indeed

Link To This Forum!

Partner Button
Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.
Just copy and paste the
code below into your site.

asimeqi (Programmer) (OP)
2 Nov 04 17:00
I have an IBM SurePOS 500, running Windows NT4, Aloha TS 5.27.
The mag swipe is an IBM OPOS.
OPOS MSR Control is version 1.5.3 beta
Service object is IBM OPOS ver 1.4 build 401

The card swipe usually works fine. But if I run a program, any program, using a button created via TSBUTTON.CFG, the card swipe stops functioning.
As I said, any program causes this. So for example I have right now a button that launches Notepad.exe. As soon as Notepad comes up I close it. After that the card swipe doesn't work anymore. I need to restart the Aloha FOH for the card to start working again.

Does anybody know anything about this?
Thanks a lot.
DTSMAN (TechnicalUser)
3 Nov 04 11:13
Have you tried it in keyboard wedge mode?  There is switch on the mag reader for this.  I have never run nt on one of those before.
asimeqi (Programmer) (OP)
3 Nov 04 11:28
I am not sure how to do this. Just by selecting "Keyboard Wedge" as the type for Mag Stripe Reader, doesn't work. In fact if you select that the swipe will not work at all.
I have another terminal that has keyboard wedge. It doesn't have the problem I am describing.
But I am writing a program that has to run with both types of readers. So even if I were able to change the OPOS reader to act as a keyboard reader (I know Micros can do this), I still need to solve the problem that I have.

Any help would be appreciated.

Thanks
DTSMAN (TechnicalUser)
5 Nov 04 14:33
there is a dip switch on the reader if you take it you will see it on the back,and also set it up in aloha as wedge.  When we use opos mode we use the ibm opos suite and it works just fine.  
asimeqi (Programmer) (OP)
5 Nov 04 16:22
Thanks for the tip. I was not aware of the presence of the dip switch.
I tried to make the change but unfortunately it does not work. I have no idea why.
If that worked it would not solve my original problem but it would be an workaround.
Is it possible that I have the wrong version of device drivers? Or some other setting is wrong?
JamesG68 (IS/IT--Management)
20 Dec 04 18:22
We are having the same problem. We switched to Keyboard and seems to be working ok. We have a call open with Radiant to research this issue.
asimeqi (Programmer) (OP)
21 Dec 04 0:28
Thank you James,
I would appreciate if you could keep us posted on this issue. I still haven't been able to resolve it.
POSsouth (Vendor)
3 Feb 05 2:28
Is this terminal used as a bartender terminal trying to name tabs with a credit card? If not try setting Alona to use stripe 2 only. This can be done in wedge or OPOS mode.
JamesG68 (IS/IT--Management)
10 Feb 05 16:19
The issue was not naming tabs, it had to do with using the TSButton.cfg. Aloha identified the problem and has fixed it. I was told that a fixed release was coming. No date given. Check with Radiant or reseller for details of when fix will be available.
asimeqi (Programmer) (OP)
10 Feb 05 16:26
Thanks a lot James. I can't wait for the new code.
Alohaboy (Programmer)
22 Feb 05 15:13
YOu need an OPOS driver.
JamesG68 (IS/IT--Management)
28 Mar 05 16:39
The fixed was released in 5.3.17. No longer an issue for us.
asimeqi (Programmer) (OP)
1 Apr 05 18:56
Yes, it is fixed in 5.3.17. They released this on January 31, but I was able to test it today. I can confirm that it works fine. Thanks everybody for their help.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close