WildernessSB
Technical User
I am running Aloha Tableservice Version 5.3.47, one File server running XP pro, and 5 IBM SurePOS 500's running Win 98. Today when I went to refresh some info, 4 of the FOH compters rebooted normally but one did not. After some trouble shooting I traced it back to a bad harddrive. I replaced it with another 20 gig out of a spare, unused server computer, and it booted Windows just fine. When it went to boot Aloha, however, it took me to a "looking for fileserver" screen with a "Make fileserver" button and would go no further.
After doing some searching on this website (which is a great source of info BTW), it sounds as though the security card (or HASP key as some call it?) does not match up with whatever file is stored in this new hard drive, and is therefore not allowing connectivity. I pulled the security key and looked it over for some sort of number or ID or something, but found nothing.
Anyhow, does it sound like im on the right track or barking up the wrong tree? Any suggestions for getting the key and the HD to match up? Thanks in advance, your help is greatly appreciated as the $300/hr tech support is a bit out of the budget in these tough economic times.
Steve
After doing some searching on this website (which is a great source of info BTW), it sounds as though the security card (or HASP key as some call it?) does not match up with whatever file is stored in this new hard drive, and is therefore not allowing connectivity. I pulled the security key and looked it over for some sort of number or ID or something, but found nothing.
Anyhow, does it sound like im on the right track or barking up the wrong tree? Any suggestions for getting the key and the HD to match up? Thanks in advance, your help is greatly appreciated as the $300/hr tech support is a bit out of the budget in these tough economic times.
Steve