|
Posted by reng on August 3, 2007, 3:08 pm
Please log in for more thread options We're still investigating this sporatic problem. One idea may be the windows
taskbar. We've configured the touchscreen layout to use the entire window.
We've designed these windows to not overlap. Occassionally, I see that when
the taskbar appears, it looks like it tries to shift the touchscreen buttons
window upwards into the transaction window.
To test this, we're going to see if the problem appears when we move the
taskbar over to the left. Also, we are turning off the auto-hide and on-top
options.
"reng" wrote:
> the touchscreen is part of a "built-in" all-in-one unit.
> it doesn't happen every time, just once in a while. if we can figure this
> out, we'll certainly post the answer here.
>
> we have a pole display and two printers. i will look into the device
> drivers. we're using a USB hub, but we haven't had problems like this since
> we opened the store over 3 years ago.
>
> thanks for your suggestion.
>
> "Gaz" wrote:
>
> > I could be very wrong but it sounds like an opos problem. If it is always at
> > the end of the sale it could be something to do with trying to print a
> > receipt or open a cash drawer, if you are using them.
> >
> > How is your touchscreen connected, com port? Do you simply restart RMS or do
> > you have to reboot the entire machine to get it back up and running?
> >
> > "reng" wrote:
> >
> > > We are running RMS 1.2. Recently we noticed the application will "hang"
after
> > > the completion of a transaction. The PioneerPOS touchscreen will not
accept
> > > input (yet the mouse still works). If we toggle between the task manager
and
> > > the POS application, we find that RMS's title bar will show
> > > non-responsive/not responding. The difficult thing is it happens only
> > > sporatically, maybe 2-3 times a day.
> > >
> > > Anyone have an idea of what could be the problem? We've run a chkdsk and
the
> > > disk looks fine. We have 20GB disk with about 4GB free, the database is
about
> > > 1.3GB, we only have 256MB RAM, but we are careful not to run any other
> > > applications on the machine.
> > >
> > > We're stumped. Also, we assume if it is a database issue, SQL MSDE has
> > > basically no maintenance error checking utilities.
> > >
> > > Suggestions?
> > >
> > >
|