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!

 

[IThelper1]

I have not done one.

I'm also a little confused about the user setup between Windows and Aloha. Maybe this would be where we are running into issues. Forgive my lack of understanding here, but do we need a windows user account with the same name/password as the Aloha manager?

We also had about 20 terminal ID errors that came up last night with closing. I'm going to sleep better once this is all over!

Coorsman, do you ever take any phone consultations?

Thank you again!

 

[coorsman]

The username password really doesn't matter as long as the terms can read and write to each other. Ctrlsvr must be running for aloha manager to work. D for the terminals to communicate. Did you set up the Lana number correctly on term 1. The file called downtime.ini file on term 2 will tell you what terminal is runni g as the master and server. I don't have any documentation on w98 machine setup and can't really remember much about 4.2. What state are you located.

Cheers,
Coorsman

 

[IThelper1]

Thanks Coorsman.

I downloaded Lanacfg.exe and ran it to check the lana number, but I get an error that it timed out after entering the IP and MAC. Any thoughts? Other ways to check/set it?

I'm in Michigan.

Thanks!

 

[coorsman]

You must be using the wrong lanacfg. The one u need is a dos program run inside a dos prompt. You may be able to find it in this forum.

Cheers,
Coorsman

 

[IThelper1]

Sorry, just figured that out.

I did find the right one and now the following error comes up when I try to run the lanacfg showlanapath command.

"A required .DLL files, netcfgx.dll was not found"

Seems that I can't win on this!

 

[IThelper1]

After taking a day off to think this over, I'm starting to lean towards the Lana number issue. Seems like it would be the cause of most issues I've been having.

Are you aware of any other way to check the Lana on a 98box without using lanacfg? I'll keep working on this dll error and see what can be done in the meantime.

Thanks as always!

 

[coorsman]

http://www.mediafire.com/download/569tvmw7tte1696/lanacfg.exe

Try this lanacfg


Cheers,
Coorsman

 

[IThelper1]

Thanks Coorsman. I'm still getting that same error with the new file, so I'm not sure where to go from here. I've been looking for an old 98install to try and find that file.

 

[IThelper1]

Ok, installed WIN2K on the box and lanacfg came right up with no errors! Followed your install instructions Coorsman. Only thing preventing me from testing Aloha is a pesky share issue.

Mapped the server on term2 and can access every folder, but Aloha. If I change the folder name to something else it lets me in just fine. If I click on the Aloha folder I get "E:\Aloha is not accessible. The directory name is invalid."

I've been playing with the network and share settings with no luck. On the bright side, Windows 2000 is much easier to work with then 98.

Scratching my head once again...

 

[coorsman]

I have used a program in the past called tweakui for 98. It allows logon for windows username and password. I know there is a way to edit the registry to do the same. Do you have the W2k server logging in as Aloha and password Hello?
That was the default login for aloha back in the days. BTW file sharing 98 to anything else is a bear. Good luck.


Cheers,
Coorsman

 

[IThelper1]

Ok, share is back up and both terminal login. Still having the one way issue.

So here is my questions: Is the only share on the server/term1 or should I be sharing term2 so the server can access it?

Thanks!

 

[coorsman]

Both terminals must be able to read and write a file on each other.


Cheers,
Coorsman

 

[IThelper1]

I mapped the server to Term2 and it connects just fine. Can copy and write files, so not sure why it's giving me such a hard time.

Also started a new thread since I kind of got off topic here since you fixed my other issues.

Thanks!