After upgrading to POS 2.0 (NOT RMS) over the Thanksgiving holiday hoping to take advantage of the reputedly improved reporting and feature set, we now experience a 10-15 minute boot duration waiting for Point of Sale to fully start. Now, if the system crashes or loses database connectivity (over the wired LAN) during business hours, which it's prone to do at least once daily since upgrading, a reboot is required to get the cashier station to reconnect to the office db.
The POS Manager (also POS 2.0) is installed on a backoffice PC running dual processors and 4GB RAM. The cashier station is a Casio QT8000 with Embedded XP and has no other application installed other than POS 2.0.
Is anyone else experiencing this boot delay using POS 2.0 (NOT RMS)? Is this a typical reboot duration? Is there a hotfix or workaround? Is there a logfile we can consult and identify a stalled process or service?
I suspect the SQL 2005 bundled with POS 2.0 is nothing but bloatware disquised as a robust db. I see numerous tables that inexplicably have no bearing on the Point of Sale application we purchased.
M Kalmus