Help with Aloha 6.7.16 on Windows 7 Pro

[justadoode]

Hello POS Gurus-

Power surge fried the Aloha File server despite being on a surge protector (supposedly). Long story short, the owners want to save money and bought a computer from a local Frys with Windows 7 Pro on it. I followed the instructions from Coors man in faq693-7418 and successfully installed Aloha 6.7.16 on this computer.

I was able to migrate the spooling files from the master terminal back to EDC, successfully process and batch out the credit cards, which is good. However, I cannot execute a successful file server recovery and I cannot get Aloha manager to work correctly. I keep getting the error message ctlsvr disconnected try to reconnect?
Let me mention that the new server did not have an LPT1 port so i had to purchase a USB key from the local reseller and change the SEC codes in the Aloha.ini file. Anyway, in looking at the debout.txt file I show this:
Oct 31, 15:09:21, [16924], [STATUS],,"AlohaMgr starting... version 6.7.16.2036.1 "
Oct 31, 15:09:21, [16924], [INFO],," MODE SETTINGS"
Oct 31, 15:09:21, [16924], [INFO],,"***** Version: 6.7.16.2036.1 "
Oct 31, 15:09:44, [16924], [INFO],,"LoadIberStrings() - Loaded version 6.7.16.0, C:\BootDrv\Aloha\bin\IBERSTR.DLL"
Oct 31, 15:09:44, [16924], [INFO],,"***** Workstation: ALOHABOH"
Oct 31, 15:09:44, [16924], [INFO],,"***** TableService Only"
Oct 31, 15:09:44, [16924], [INFO],,"***** Labor Scheduler enabled."
Oct 31, 15:09:44, [16924], [INFO],,"***** Site Id: 1"
Oct 31, 15:09:44, [16924], [INFO],,"*****Start of WORK in InitInstance"
Oct 31, 15:09:50, [16924], [INFO],,"*****Before AlohaMgr create"
Oct 31, 15:09:50, [16924], [INFO],,"*****Before AlohaMgr RequestCtlSvr"
Oct 31, 15:09:50, [16924], [INFO],,"CAlohaMgrApp::RequestCtlSvr() called..."
Oct 31, 15:09:50, [16924], [INFO],,"WaitForCtlSvrStartupComplete()..."
Oct 31, 15:09:50, [15724], [INFO],,"ACtlSvrConnect: (thread) - Begin Run()"
Oct 31, 15:10:43, [15724], [INFO],,"ACtlSvrConnect: (ICtlSvrCom::AreYouAlive failed (0x4))"
Oct 31, 15:10:43, [15724], [INFO],,"ACtlSvrConnect: Connection to CtlSvr lost. Prompting for reconnect..."

when I look at debout.svr I show this:
ct 31, 15:09:51, [15044], [STATUS],,"CTLSVR: Started CtlServiceThread... version 6.7.16.2036.1 "
Oct 31, 15:09:51, [15044], [INFO],,"CTLSVR 6.7.16.2036.1 is running on workstation ALOHABOH"
Oct 31, 15:09:51, [15044], [INFO],,"CTLSVR: IBERDIR is C:\BootDrv\Aloha"
Oct 31, 15:09:51, [15044], [INFO],,"Operating system is Windows 7 (BuildNumber 7601, Platform 2, Version 6.1, Service Pack 1)"
Oct 31, 15:09:51, [15044], [INFO],,"Hasp driver for Windows NT has not been installed."
Oct 31, 15:09:51, [15376], [INFO],,"[Run] SpawnRadiantHeartBeatCheckerThread... "
Oct 31, 15:10:12, [15044], [INFO],,"LoadIberStrings() - Loaded version 6.7.16.0, C:\BootDrv\Aloha\bin\IBERSTR.DLL"
Oct 31, 15:10:12, [15044], [INFO],,"CTLSVR: Serial Number not Found as no Security key found"
Oct 31, 15:10:13, [15044], [INFO],,"CtlSvr - Refresh - RFS Not in use"
Oct 31, 15:10:14, [15044], [INFO],,"TIMEZONE=INTL - using time zone information from the BOH computer"
Oct 31, 15:10:14, [15044], [INFO],,"TIMEZONE: Reading C:\BootDrv\Aloha\data\timezone.ini"
Oct 31, 15:10:14, [15044], [INFO],,"TIMEZONE: Standard Name = Central Standard Time"
Oct 31, 15:10:14, [15044], [INFO],,"TIMEZONE: Daylight Name = Central Daylight Time"
Oct 31, 15:10:14, [15044], [INFO],,"TIMEZONE: Successfully read the Timezone.ini contents"
Oct 31, 15:10:14, [15044], [INFO],,"TIMEZONE: operating system time zone settings match values in TIMEZONE.INI"
Oct 31, 15:10:14, [15044], [INFO],,"CTLSVR: Is NOT running in SQLMODE."
Oct 31, 15:10:14, [15044], [INFO],,"CTLSVR: bRobust = TRUE"
Oct 31, 15:10:14, [15044], [INFO],,"CTLSVR: Begin initializing network..."
Oct 31, 15:10:14, [15044], [INFO],,"Initializing network..."
Oct 31, 15:10:14, [15044], [INFO],,"Node = 15006 String = 'BFAAG'"
Oct 31, 15:10:14, [15044], [INFO],,"NBInit()-> Before NBAddName()-> StationName = "IBERBFAAG ""
Oct 31, 15:10:17, [15044], [INFO],,"NBInit()-> After NBAddName()-> StationNumber = 2"
Oct 31, 15:10:17, [15044], [INFO],,"NBInit()-> Before NBAddGroupName()-> SessionName = "IBERLINK""
Oct 31, 15:10:20, [15044], [INFO],,"NBInit()-> After NBAddGroupName()-> SessionNumber = 3"
Oct 31, 15:10:20, [15044], [INFO],,"Station number 2, session 3"
Oct 31, 15:10:20, [15044], [INFO],,"Network initialization complete."
Oct 31, 15:10:20, [15044], [INFO],,"TIMEOUT ALERT!!! NBInit took 6.021000 seconds our threshold is 5.000000"
Oct 31, 15:10:20, [15044], [INFO],,"CTLSVR: Done initializing network."
Oct 31, 15:10:20, [15044], [INFO],,"Failed to open C:\BootDrv\Aloha\SQL\SQL.INI: No such file or directory"
Oct 31, 15:10:21, [15044], [INFO],,"** AKS License file not found."
Oct 31, 15:10:43, [15044], [INFO],,"CTLSVR: Waited 23 seconds for HASP driver to make security key available."
Oct 31, 15:10:43, [15044], [INFO],,"CTLSVR: Security key not found."
Oct 31, 15:10:43, [15044], [INFO],,"CTLSVR: Initialization failed before main."
Oct 31, 15:10:43, [15044], [INFO],,"CTLSVR: Start background processing..."
Oct 31, 15:10:43, [15044], [INFO],,""
Oct 31, 15:10:43, [15044], [INFO],,"CTLSVR: CtlServiceThread - Stopping background processing..."
Oct 31, 15:10:43, [15044], [INFO],,"net shutdown!"
Oct 31, 15:10:43, [15044], [INFO],,"Canceling datagrams..."
Oct 31, 15:10:43, [15044], [INFO],,"Canceling datagrams second time..."
Oct 31, 15:10:43, [15044], [INFO],,"Dropping names..."
Oct 31, 15:10:49, [15044], [INFO],,"Net shutdown complete"
Oct 31, 15:10:49, [15044], [INFO],,"CTLSVR: CtlServiceThread Terminated."
Oct 31, 15:10:51, [3636], [INFO],,"purgeDays=14 : Try to delete all aged zipped debout files..."

Am I missing a HASP driver? If so, does anyone know where I can get it? The local reseller, as many tend to be, will not offer any assistance with this. They basically hand you whatever hard ware and say, "You're on your own, unless you want to pay our $1500 set up fee."

Hopefully it's just a driver that someone here can point me in the right direction.

Thank you very much-

Charles aka Justadoode

 

[justadoode]

Unfortunately, even though I followed the instructions to the T. It did not work...

 

[posrescue]

I checked with a dealer guy and supposedly Aloha 6.7 is listed as compat with Win7. I always buy 7 Pro and downgrade to XPP so I have little insight.

I install a new HD and install XP using a valid XP license that is already in use on another computer. The validation will fail. Call the number given on the license error screen and explain downgrade. If you give them your valid Win 7 license info they can generate a XP license that you can enter and away you go.

 

[justadoode]

So here's how I finally got it all to work. I went in to Win 7 Pro and
1. I shrunk the hard drive space
2. Created a separate partion (called it XP Partition)
3. Ran a COMPLETE format (because a quick one didn't work)
4. Rebooted the computer and went into the BIOS where I changed the drive type to IDE (SUPER SUPER SUPER IMPORTANT OR ELSE IT WILL FAIL)
5. Booted from the XP PRO install disc and installed XP Pro

(hooray)

Then I went in and
1. Installed the hasp key drivers from Aladdin FIRST
2. Rebooted
3. Plugged in the hasp key and let the drivers install themselves
4. Rebooted
5. Installed a wireless NIC card to get network access
6. Downloaded the XP hardware drivers (nic card, etc.)
7. Installed C+++ redistributable package
8. Installed Aloha
9. Installed EDC
7. Installed lanacfg
8. Changed lana paths
10. Made myself a stiff libation

It worked. Now the only problem I'm having is that the terms cannot map a drive back to the Alohaboh server. This is usually the easiest part, but only 14% of my brain works at this point, so there must be SOMETHING simple I'm missing. BOOTDRV is shared and I have it set so that network users can change files, but each time I map, regardless of user credentials it says access is denied. So close... so very close....

The bar is ok though because the cc transactions have been processing and batching so no money is lost and all the dated sub-directories are back where they belong.

 

[justadoode]

I'm retarded... I figured out why I wasn't seeing from the FOH to the BOH.... *whew*... Glad to finally put this all behind me!!!

Thanks for all of the insight GURUS!!!!


Charles a.k.a. Justadoode

 

[eburks]

@ posrescue and @ justadoode

!!I am good but no expert and could be wrong here!!

Seems a lot of people throw around the phrase Win 7 Pro

As far as I know most console based (cmd.exe) based stuff will run just fine on Windows 7's (any flavor) 32bit
(32bit being the key)

Recently Dell for instance only ships desktops with 64 bit windows 7's. You CAN buy an Inspiron mini with 32 bit windows 7
(I even got one last week with windows 7 home ultimate 32bit)
For a little longer you can probably find some 32 bit Dells on Buy.com. Not much help... I know

The 64 bit flavors of Windows 7 (probably XP and 2008 too)do not have the NTDVM needed to run these apps. (Do not confuse NTDVM with the "Virtual PC"/Vmware virtual machine guests that can be run they are not the same thing)

I believe (and I would really like someone out there to confirm) that when Aloha says their software will run on windows 7 they are only talking about 32 bit windows 7 or possibly the XP mode of Windows 7 Pro and Enterprise which are virtual pc based.
I could never see someone wanting to run a terminal in any of the virtual guest configurations.

You can run "Virtual PC" with DOS, Windows 3.11, 98SE XP linux etc etc guest op systems on 64 bit windows 7 and more. (vmware which is the only "virtual" I work with right now, can do it too)

It is possible for someone to say you can run program XYZ on windows 7 64bit and they mean in one of these guests but I would call that misleading. If I am wrong, I'm sure someone will school us before too long

 

[coorsman]

It's jot aloha as Mitch as it is aladdin hasp key won't recognize in 64 bit mode. Even
Using a virtual machine the key is plugged into the hardware and won't work.

Cheers,
Coorsman

 

[justadoode]

Yes, eburks. I contacted the local Aloha reseller and they also said Aloha will not function and is not certified on 64 bit systems. That's why I did what I did. I will say, it was one heck of a learning experience. .

Charles/Justadoode

 

[ltso]

I've been trying for months to get a straight answer from Radiant as to when they will FINALLY enter the current century of 64 bit OS. It seems the day will not arrive til next summer when 7.0 is due to arrive with haspless licensing. Until then, we must downgrade all OS's to 32 bit.