Aloha How to Migrate V5.044 BOH from Win2000 Servr To a New XP Servr 1

[JJP2]

I first installed Aloha in 1996 and a dealer has never crossed my threshold. Currently I have been running and self maintaining V 5.044 since ?2002? with no problems on a 3 terminal mixed win 98 and 2000 system. A dealer will upgrade me over the internet to V 6x along with the PCI compliant EDC but wants all my computers to be running xp. I have purchased 4 new computers and succeeded in upgrading the three workstations to xp currently running aloha. Now I have to transfer the Aloha BOH software from the Old Win 2000 Server to the new XP Server.

Assuming that I have set up the Server properly according to AKBID1177 “Win XP File Server Setup”, how do I transfer the Aloha Files to the new xp server.

Will this work? Or is there a better way?

1. Begin after EOD on a closed day before anything is entered into the system.
2. Unplug the network from the 2000 Server.
3. Shut down the terminals?
4.Plug the Hasp Key into the Parallel port of xp server.
5. Plug my external Robotics Sportster 33.6 Fax/Modem into the proper com port
6. Plug the ISPY box into the proper com port
7. Using my V5.0 Rev A Installation Disc install Aloha onto the XP Server following the prompts.
8. Connect the network to the Server and fire up the terminals.
9. Go to Utilities-Fileserver Recovery and initiate recovery which causes the terminals to set up the new fileserver's data from their data.
10 Load any dated history files into the Aloha directory.
11. cross fingers

 

[coorsman]

Check the network settings from the Aloha NIC - IP scheme - and computer name. I'm not sure about version 5.0 but I think you still need to open then Advanced.exe program from the install disk to install Aloha.

Make sure the lana number is set to 0 on the Aloha NIC card.

Check for read/write ability between terminal and server and server and terminal.

Copy the DATA, NEWDATA, BMP and RPTSET folders before installing and make sure the trans.log is deleted from the data folder before installing.

cross fingers

 

[JJP2]

Thank you, Coorsman.

I believe the lana number ends up being 0 when you first set up a new computer with net capabilities built into the motherboard. The three terminals I set up must have gone to lana 0 because they all worked.

I will copy the folders you mentioned before installing the software from the disk along with deleting the trans.log in the data folder.

I will do this on Monday when we are closed.

Another problem has developed. The old server has to be rebooted once a day because it runs out of resources and can't even run the BOH print module.
Also Retropect, my backup program, runs too slowly to work. I then reboot the server and it speeds up again. I have 750 megs of ram with a pentium II CPU on the soon to be retired server. Do you have any idea what the problem is? Does the server need more memory due to xp on the terminals rather than win98? Will the problem go away when I put in the new server with a dual core e7500 cpu and 2 gigs of ram? Meanwhile do I have to keep on rebooting the server when it runs out of resources.

 

[coorsman]

How often and what are you backing up.

Are you backing up thru the network, internet or to a usb type device.

The best and cheapest is a second hd.

750 is plenty for a 2000 machine. I have seen some on 256.

Could be a bad hd or needs to be defragged, processor overheating - check cpu fan for dust "they get real bad in the restaurant environment".

Good luck, I'll check back with you.

 

[JJP2]

I back up the last aloha dated directory and all the aloha files at 5:30 every morning after the eod to an external hard drive.

Sometimes the cpu sits at 100% in "Task Manager" performance screen and won't go back down until I reboot.

If the cpu was getting too hot wouldn't the system crash? But I'll check the cpu. The fan is running and fins are clean. This is a pentium single edge processor.

Why does rebooting solve the problem for a day. I'm turning off retrospect to see if tomorrow morning the system isn't out of resources.

At a minimum, I sure hope the new xp server solves the problem but won't know till Monday when I migrate the software. But if 750 megs and a pentium II is enough to run the server the problem should persist.