So in my ongoing saga of replacing two 4.2 Aloha terminals (1 server/main, 1 bar) I still can’t get the bar terminal to see the server/main. I’ve installed WIN2K on a new box and I want to replace the main. Do I need the install CD to do this or can I use the terminal setup app from the bar...
Thanks posrescue. So I should change the server name to term1? I've left it's settings alone so far because everything worked with the old term2. I just did not know its settings.
You are right on credit cards. We are not running them through Aloha.
It's set as ALOHABOH. I know the terminals can see each other in some form because when one is down the other gives that terminal down error on the login screen.
Thanks!
They both are setup with the user TD. I'm not sure why the Server/Term1 box uses that, but I did not want to change anything on it because everything was working until the original Term2 died.
I checked it out, but it does have everyone checked. That box I've not changed at all since we replaced Term2, so I know it was working before.
Just thinking maybe something is not pointed at the right dir.
Thanks!
I should bring up that Term2 is mapped to the Aloha folder on the server. It would not let me map BOOTDRV and access the Aloha folder inside, but it would let me map right to Aloha.
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!
I wanted to start a new thread on this because my other issues are now resolved.
So here is my issue:
We have two terminals running Aloha 4.2. Term1 is also acting as the server and its running WIN98. Term2 is a new box running WIN2K.
If I enter a table in Term2 it shows up just fine on Term1...
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!
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...
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.
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...
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!
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.