Aloha 4.2 Waiting for grind...

[IThelper1]

After all sorts of fun I replaced a main Aloha 4.2 terminal. We seem to be getting close to running, but now I get "Waiting for (date) to grind...". It never goes away and the date is over a year ago. Is there a way to delete these files and get things back up and running?

Thank you!

 

[coorsman]

You can edit the Aloha.ini file in data and newdata - find the "dob" - change it to the current day.

Cheers,
Coorsman

 

[IThelper1]

Coorsman,
Thank you so much, that did the trick!

I now have both terminals working, but terminal1 can not write anything (tables, menu changes) to terminal2. Terminal 2 however does write back to 1.

I've been playing with network settings and no luck. Could I maybe have something pointing to the wrong place?

Thanks again!

 

[coorsman]

Did you check out the FAQ's above on how to set up an aloha terminal and server?


Cheers,
Coorsman

 

[IThelper1]

Nope! Thank you for pointing that out (sorry I'm new to this).

If we only have two terminals, should term1 be called alohaboh?

Thanks again!

 

[coorsman]

Term1 and term2 but the environment variables in the ibercfg.bat for term1 as the server.


Cheers,
Coorsman

 

[IThelper1]

Thanks Coorsman. I seem to get one step ahead and two behind...

I changed all the settings as mentioned in the FAQ. I'm trying to run the terminal setup but it gets the following error:
Failed to copy \\alohaboh\BOOTDRV\Aloha\BIN\iber.exe to c:\Aloha\BIN\iber.exe GetLastError returned 32.

I've made sure to quit iber.exe on the sever and still no luck. I feel like we are close!

Thanks as always!

 

[coorsman]

Do you have a back office computer called alohaboh? and terminals term1 and term2?

Cheers,
Coorsman

 

[IThelper1]

Just the two terminal. Terminal 1 is the server.

 

[coorsman]

If term1 is named term1 then you need to change the server name in the setup program to reflect that. It's looking for \\alohaboh not term1.


Cheers,
Coorsman

 

[IThelper1]

My issue now is the setup program gets that error and will not finish. I've tried everything I can think of and it keeps coming back with:

Failed to copy \\alohaboh\BOOTDRV\Aloha\BIN\iber.exe to c:\Aloha\BIN\iber.exe GetLastError returned 32.

Thanks!

 

[IThelper1]

And I should mention I was able to run the term setup once, but added the wrong name in. When I went back to fix it I just kept getting that error.

 

[coorsman]

You really have all sorts of issues.

crtlsvr.exe is not running or the grind would have already happened.

Is Aloha registered and do you have the key attached?
Did you save the old newdata and data folders from the old install?
What operating system are you running on both machines?
Can you copy files from one to another?

Do you have internet on the main terminal so I can connect and check your system out?




Cheers,
Coorsman

 

[IThelper1]

That's for sure.

Other then Term2 not seeing items added from the main terminal/server, I did have both terminals running until messing up the terminal setup yesterday. Now They just don't see each other at all. I'm sure this is due to me entering the wrong term ID into the setup app.

When I double click on crtlsvr.exe it does not seem to do anything.
Aloha is registered and has the key attached.
Yes, I did copy the folders over.
They are both running Win98 (I wanted to keep running the same OS they were installed on).
I can copy files from one to another.
We do not have Internet. Old school I know.

You're too kind to help with all this. Thank you!

 

[coorsman]

Look in the ibercfg.bat or autoexec.bat file on term2 it should say what the (server) (term1) is called. That's what you should name term1. I really can't remember how to see the services in 98 but check to see I ctrlsvr.exe is running. If not there should be a register.bat and an unregister.bat file on the old server. These batch file register the aloha software on the new terminal.

If you would post the register.bat file and the autoexec.bat and ibercfg.bat file from term2 on your next post.

There's no install procedure in 4.2 It can be copied from dos and registered using those batch files. My next suggestion would be top copy through the network the aloha directory from term 2. Remember - always make a copy of your aloha directory before making changes.

There should also a maintenance program to take term2 out of redundancy.

If you are still getting waiting for grind (date)you can create 2 txt files gnddbf30.xxx and done30 in that dated sub and stop the grind process.
in DOS in the dated sub use
echo > gnddbf30.xxx
echo >done30
to create these files.






Cheers,
Coorsman

 

[IThelper1]

So I have them both back up. The last two issues I have are:

1. ctrlsvr.exe is not running so we get the grind issue.
2. Term2 does not see any table/food added from term1 or updated menu prices.

I'll upload the ibercfg.bat file asap, but I did not see register.bat or unregister.bat on the new server or the old one after doing a search.

Could issue 2 be related to using windows logon? I have no password setup now, but just a thought.

Thanks!

 

[IThelper1]

Here is ibercfg.bat

 

[coorsman]

Term2 is looking for the server name to be alohaboh. You could try changing the ibercfg on term 2 to set server=term1

Cheers,
Coorsman

 

[IThelper1]

I changed the server to be alohaboh after copying the network settings from the old server.

The frustrating thing is they see each other now, but for some reason the server/term1 can't write to term2. My guess is term2 is looking in the wrong place for data. Is there someplace to check I'm missing?

This has to be something on term2. When I still had the old server running, but replaced term2 we ran into the same thing.

Thanks!

 

[coorsman]

Have you done a file server recovery?

Cheers,
Coorsman