Few things first:
1. Are you licensed for Video?
2. Are you replacing a controller box or is this a new station?
3. Have you already done the Aloha Manager programming for Video.
If you do not run the setup with "Use Compatibility Mode" and select "Windows XP," you will get that error. Also, you will need to make sure you have installed the correct V++ versions as well...Also, I believe there is a version issue with 6.7.22. I would bump up to 6.7.28 or higher.
Restaurants purchase the license to use the software, they do not actually purchase the software. Obviously, there are certain items that the resellers do not want you, the end user to know, but in the end you should be able to manipulate it to your heart's content. There are some resellers...
It is the motherboard and since NCR/Radiant manufacture their own terminals, you probably will not be able to just "buy" a motherboard. Really you would only be able to buy another 1520 and swap it out that way.
There is a language code on the debit card that forces the data to use French. There have been instances where the card was setup to use French even though the card holder did not ask for it. There was an actual defect that was in version 6.5.17, but if it continues to happen then it has to do...
Once the end of day has processed, you cannot change any previous day's sales data, other than labor. This would have to be an internal note on your books.
Maintenance -> Store Settings -> Labor (Over Time Calculations)
Maintenance -> Store Settings -> System (First Day of Week)
If you cannot get to that section, then you do not have the necessary security rights. You may have to contact your reseller to grant you that access.
You also need to make sure that you run the vcredist_86.exe as an administrator. Also, run the update as the administrator, if you do not it will look like it all went through, but in reality it did not. You can also double check the debout.set located in the root of C. This will help you get...
The PXE software is what is used to reimage the terminal. I would suggest going into the Bios of the terminal and letting it boot off of the HDD first and avoid looking for the network boot. If it continues to happen, then I would look at the electricity of that particular terminal location as...
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.