Only one Aloha terminal is working.

[ephobia]

I recently replaced an Aloha back house computer and have had moderate success getting it up and running. The BOH computer is running Windows XP and Aloha v 5.3.12. both terminals are running a windows 98 platform. As of right now I have two problems.
Problem one is that only one of the two terminals will work at a time. If one terminal comes up the other one will not. Both are defined as separate terminals (1 and 2) and there are definitely two terminals defined by the system. When the other terminal tries to come up it simply restarts with no error message.
Problem two is much less significant but it may be related in some way. The register that does come up will run the set time .bat file to sync the time with the BOH server but after about 10-15 min it will revert back an hour! We are currently observing day-light savings here on the west coast. so I made sure both clocks are set accordingly as well as the bios time.

Any help would be greatly appreciated!

 

[alohaakamai3]

Problem 1:

Usually when I have seen this problem, its when a computer isn't named properly in windows. For example, if you've got term1 called so in your ibercfg, but call the terminal something else in windows, when the computers try to connect to it, they will simply reboot over and over again. Double check this setting on both terms. Also, I would copy over the ibercfg from one of the terminals you didn't recently rebuild or change. Then go ahead and modify it appropriately. Sometimes on small change that is easy to over look can cause problems.

Problem 2: Probably not related to each other, but who knows? Has the Aloha time change fix been applied to the back office? Has any installation taken place that may have over written it? Had that happen before. Was sure I applied it once before, but forgot that Aloha was re-installed.

 

[pasupport]

You can get around the time problem for now by turning off daylight savings time on the BOH and the terminals and setting the time correctly.

Also there is a SYNC BOH TIME Flag somewhere I think under the system settings but you can search the aloha.ini for it. May even be in the ibercrg.bat file can't remember right now.

Long term you need the DST patch to account for the change in DST




--
Visit my website site a pasupportsolutions.com for cool tips and tricks

 

[posrescue]

Problem 1:
Has anything changed on the terminals or just the fileserver? Make sure the drive that aloha is installed on is shared as "bootdrv" on the terminals as well as the fileserver with maximum access.

Make sure both terminal's are logging into the network with user names and password that are set up on the fileserver. Typically on Win98 terms the user name is term1, term2 ect. with blank passwords. If this is so make sure the fileserver's security settings are set to allow logon using no password.

Make sure you have no "stop" or "exiting" marker files in \aloha\tmp on the terminals or fileserver.

Turn on first terminal and let Aloha start. Start the second terminal and let it attempt to start Aloha. If it restarts let it proceed but when Windows98 starts the next time hold down the shift key on an attached keyboard to keep any startup programs from starting. 15 to 20 seconds after the desktop comes up release the shift key. Navigate to \aloha\tmp and copy the "debout" file to the fileserver. Open the file on the fileserver with notepad and look for the last time you attempted to start the terminal (by time and date). Copy that section of the debout and paste in here so we can see what the problem is.

 

[ephobia]

Thanks for all the replies!
Both Terms are up and working now thanks for the help. The terminals were named correctly, but the computers weren't networking properly.
After checking the debout I realized that the BOH was telling term2 that term1 was the master terminal, but when it tried to access //term1 it said the path was invalid. So I checked the networking properties to make sure everything was enabled and after making sure everything was shared properly I realized that term1 was set to windows logon instead of client for microsoft networks like the other machines.
Stupid mistake I guess. After I was able to access the shared files accross terminals, term 2 was still restarting so I did as posrescue mentioned and checked the "/alohaqs/tmp" folder. There was a file called "exiting" and after removing it everything seems to be in working order.
As for the problem with the time, I don't think I have the patch anywhere so I guess we'll have to set it manually while I try and find it.
Thanks for all your help!

 

[Circle9]

You can download the DST patch here.