Aloha Time is not windows time

[jjkm4]

am running aloha ver 6.1.19 and windows time is 1 hr ahead of aloha time . On BOH and FOH windows time is correct but when aloha program runs, aloha shows time 1 hour behind. Help and thanks

 

[bigblok403]

Terminals probably running wrong(old) DST. Apply Aloha patch(best bet) or Windows DST patch on terminals and server.

 

[rockwellsbakery]

is the time different at each termianl? or is the time off at one station only? if it is at one station i could be the battery for the cmos that is bad, which is very cheap to fix, once you know where it is located. you best bet is to look on line by manufactor and model number and search for tech support on its location, then off to radio shack.

you are lucky you are not getting a file server error,

 

[apna06]

i need help too! my BOH has correct date but FOH terminal has 2 diffrent dates at bottom of the screen ie.
DOB 12 09 08 AND SYM 12 08 08.
PLZ. HELP THANKS

 

[bigblok403]

apna06 - you have a different issue. There could be several reasons for this depending on what time your End of Day runs. DOB (date of business) is what day Aloha is on and Sysdate is what date Windows is. DOB changes at End of Day and can also be changed in Aloha Manager>Store Settings>System>Date/Time. System Date will change if you change the Date under Windows Date and Time. I would check with your reseller to help fix the problem correctly.

The POS Forum

 

[alohaakamai3]

Bigblok is right- the post by apna is a completely different issue. And yours in a little more unusual (the DOB usually lags behind the system date when there is a problem).

If I had to guess, someone was messing with the clock on the back of house an temporarily changed the date/time temporarily- thus Aloha threw in an extra EOD, putting your DOB ahead.

I have also seen this condition when the BIOS on the master terminal was wrong and would jump ahead. Since the master technically fires EOD, and the BIOS time will usually trump the windows time and change it when the unit boots up. Make sure the BIOS time is correct.

I've found it to be good practice on most of the systems I've worked with to put the following batch file in the startup menu in windows:

cd\
net time \\alohaboh /set /y



(or whatever the name of the server happens to be).

This will set the time to whatever the server time is, regardless of the bios.