• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 770
  • Last Modified:

How to keep Keystroke POS running

I have Keystroke POS running in a SBS2003 environment and we continue to have problems with files locking or network connections timing out.  I have contacted the company and have worked through the resolutions suggested.  They don't have a lot of experience with Server 2003, so I'm left to figure out some things on my own.

I can tell you that I have given Everyone full control and have set the net config server timer to 9999.  

I hope there are some folks out here with experience with this program.  It runs most of the time, but does require a daily server reboot.  
  • 3
1 Solution
Are you referring to Keystroke POS at www.keystrokepos.com?

If so, how many people do you have using Keystroke simultaneously?

If it is a handful or more, and if you haven't done so already, you should consider doing 2 things:

1) Assign a Register and Machine Number to each user
2) Assign a directory on each user's local machine for Resource and Temp files

You can do both with the following startup switches (pasted from the Keystroke Helpbook):

/R      Designate the Register Number (and INI file).
/MNUM      Sets the Machine Number.
/K      Set the directory where Keystroke will store its Resource files.
/U      Set the directory where Keystroke will store the Temporary user files.

Here's an example of what the TARGET line would look like in the Properties of a Keystroke Desktop/Shortcut Icon assuming Keystroke were installed at F:\KEYSTROKE\WINSTROKE.EXE (yours may be on a totally different network drive and potentially in a different directory):

F:\KEYSTROK\WINSTROK.EXE /r100 mnum=rnum /u c:\temp\keystroke /k c:\temp\keystroke

Of course, you'll want to make sure that you've created the location(s) you chose to use in association with the /U and /K Startup Switches.

All of those switches will also help to speed up the overall response time and processing of Keystroke besides separating out user-related resource and temp files (which should also resolve your file locking problems).

The other thing to make sure you've done is to do a Workstation Install rather than the Client Install at each each workstation. It's a pain but worth it because you have to go to each workstation (or you could use remote desktop if you want). On each workstation, you want to browse to the network location of Keystroke, find and double-click on the SetupWS.exe file and choose the Workstation Install instead of the Client Install.

Hope the information helps.

Here is some good information to now and/or take into account with regard to my previous answer/post on assigning and using Register and Machine Numbers:

1) When assigning register/machine numbers, the resource and temp files are named the same as normal except they have a prefix or suffix unique to the assigned register/machine number. (just letting you know that in case you like to watch the \DATA\ directory - you'll begin noticing the temp files for each assigned register/machine number in there)

2) When assigning register/machine numbers to your users, start at 10 or 50 or 100, and go sequentially from there. That way, if you ever need to do some testing, you'll have a few unassigned register/machine numbers to play with.

3) Don't assign register/machine number 1 (one) to anyone. That one is used by default when no register/machine number startup switches are used. And that is most likely the primary (if not the singular) reason why you're having so many file locking problems -- because all your users are effectively using the same-named resource/temp files -- in essence, they are butting heads electronically and (unwittingly) giving you a headache in the process. :)

4) Use the same number for both register and machine to keep yourself sane

5) It might not be a half-bad idea to keep track of who was assigned what register/machine number in a simple txt or xls file in case you need it sometime down the road

6) For any of your users who bring up more than one instance of Keystroke, you'll want to assign them multiple register/machine numbers. For Example: If user Betty likes to keep 2 Keystrokes up at once, assign her register/machine number 101 and 102. And if user Joe likes to keep 4 Keystrokes up at once, assign him 103, 104, 105 and 106. So on and so forth for other users in your environment. Some may have 1, others 2, and if your environment is like ours, others may have as many as 4 or 5 assigned register/machine numbers.

7) If you assign multiple register/machine numbers to one or more users, those users will need multiple Keystroke Shortcuts / Desktop Icons - one for each Keystroke instance where the "/r### mnum=rnum" part of the TARGET line is unique to each of their assigned register/machine numbers.

Hope the additional information helps.


Just checkin'in to see if my suggestions above helped with your file locking issues?

Always remember to help the community help itself. If someone's answer solves your problem, be sure to accept their answer so that it gets into the solutions area asap.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Python 3 Fundamentals

This course will teach participants about installing and configuring Python, syntax, importing, statements, types, strings, booleans, files, lists, tuples, comprehensions, functions, and classes.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now