Hey Thepatt,
MitchellW0214 is right,
I just corrected the time issue like you can see in my thread and it works!
Make sure the BIOS has also the correct time
Cheers
Liquid
THX DTSMAN and coorsman,
You guys rock(especially dtsman) :-)
Went this afternoon there and fixed the terminals time problems, it then updated the files from the server, rebooted, registered, rebooted again and than...Ta Ta!
Terminals runs just fine, thx again :-)
Cheers
Liquid
Hi coorsman,
Yes you are right, i cloned one term(same hardware) and i made sure the new iber config on the new term is different from the others, each Term has his own #...i also tried the Terminst to no avail i still end up with the error message...:-(
Cheers
Liquid
Hi there,
I have the debout content:
Jan 01, 05:51:47
Jan 01, 05:51:47 ................................................................
Jan 01, 05:51:47 IBER started (robust mode)... version 5.3.16.153
Jan 01, 05:51:48 LoadIberStrings() - Loaded version 5.3.16.0, IBERSTR.DLL
Jan 01...
Cheers "coors"man!
Thx for your fast reply...
I will post the debut file tomorrow when i am at that terminal(i am home now, much needed rest here lol)
I forgot to mention, i did copy the trans.log file to the destkop and deleted it from the data folder :-(
But most important, it started not...
Hi everybody,
I am the IT guy for a Restaurant and they use Aloha (Version 5.3.16) with 6 Terminals(Server is on Win 2000 Pro), the Terminals use all Win98,2 of
the Terminals are Javelin Viper, the rest are POSpioneer.
Their Aloha Dude went MIA and i took over somehow at least the hardware...
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.