Thanks to all for the feedback. I guess we will stick with the OS until a major upgrade of the whole system, which we are beginning to review. We are looking at the latest Micros hardware and software packages as well as a couple of others. We are in the specialty coffee business so looking at...
We have several systems with Micros 2800 terminals in our retail environment and backoffice computers running 3700d software on Windows NT 4 workstations. The NT 4 OS is nearly obsolete. The system itself could go on for a while if the OS could be changed but I am under the impression it cannot...
By way of follow up the rebuild is now complete.
Jrk3, our version is 2.60c like yours. We needed a rebuild because our nightly backup, also like yours, was not verifying and thus not producing 'good' copies. We were also having other problems including the need to start the db manually. The...
To clarify, one day I was trying to restore the database and the log.
By way of follow up, the problem still isn't resolved but I brought the database and the log to another Micros backoffice computer that I have, figuring I could try the rebuild on it, rather than the problematic system...
Here is the log that was saved from the rebuild. It didn't take anywhere close to the time indicated. I would say it was complete in under 30 minutes and the db is 200 MB.
03/25/2008 7:20:43 PM: Renaming database file from micros.db to microsRB.db
03/25/2008 7:20:43 PM: Resetting log file...
We have a number of older Micros systems with the combination of 2700/2800 terminals and 3700 backoffice computers running NT. A few weeks ago I needed to restore a database and log one day from an automatically created backup and since that time the nightly backup routine itself no longer...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.