Search results for query: *

trying to set the dinner menu at 3pm everyday. I put an event for it to go at 3pm, but the menu is still using the lunch menu. currently using aloha 6.2 table service. am i missing a step?

also make sure to check the terminal is plugged into a ground guard. I have seen faulty power make terminals loose calibration. run the linearazation.

try going into the back of the house pc(alohaboh) and delete the trans.log should be located in C: or D:aloha/data. and delete it in the terminal. C:aloha/data. reboot both units.

did you reboot your pc after you changed the lana?

make sure the terminal has the same login name as the master

also in edc, check to make sure process ssl box is checked or anything of that nature.

If you had the same settings and, edc keeps rolling to the backup modem, it sounds like you internet connection might be dropping packets. to check this, open up the command box then type ping -t www.websitename.com . i usually ping like comcast or verizon. when you run the test it should keep...

it looks like its trying to end of day. locate the aloha.ini file in c:/aloha/data. change the dob to read current date.

if im not mistaken, cc companies are starting to turn off ssl processing for businesses that are not on a compliant version.

does the terminal reboot at determining fileserver 0? if not when does it reboot? you can attach a keyboard to the terminal and hold down the shift key as its loading to desktop, that will prevent aloha from starting. check the debout and post here.

vpn is easy. you can also use a program from sonic wall called net extender and have that running.

FTCD1 or RSDirect.CD1 depending on what terminal model you have

your aloha.ini most likely got corrupted. Take the aloha.ini from one of the dated and make sure to put todays date on it. Copy that aloha.ini to the data and newdata folders and restart cltsvr in the services.

Aloha enterprise is more like gift certificates. The new aloha takeout is supposed to be able to track customers habits

6.5

6.2 is not gonna be compliant in a few months

z is the mapped drive on the network. from that error message try going into the data folder and delete all the prt logs

if you do not have aloha 6.xx and above then you wont have rfs available to you. only way around that with 5.x sites is having the alohaboh fileserver running windows 2k or 2k server. The master has to be 98 on the floor. then the rest of the terminals can be xp.

i have access to the radiant knowledge guides, from the website if that does not help you. but im not sure if i feel comfortable handing my user-name and pw out.

if you are taking over a site, then there should always be manuals on the hard drive.