|
Re: installation
|
|
Replies:
2
-
Pages:
1
-
Last Post:
Feb 9, 2006 2:41 PM
Last Post By: monkowsk
|
Threads:
[
Previous
|
Next
]
|
|
Posts:
2
Registered:
Feb 08, 2006 11:26:35 AM
|
|
|
|
Re: installation
Posted:
Feb 08, 2006 11:52:33 AM
|
|
|
|
Great alpha.
Two installation issues are reported in case they are of assistance to others, and a third which remains unresolved.
1. Current distribution of Apache binary for Windows is "Apache 2.x" and defaults into a subdir "Apache2" (under Apache Group). The Toolkit expects "Apache" as subdir. Resolved by using an earlier release of Apache 1.x which defaults into subdir "Apache". (Changing the install.bat file to use "Apache2" subdir for some reason did result in successful install - is there a hard-coded dependency to "Apache" somewhere in the compiled code?)
2. "Clips.bat" seemed to execute without complaint, but the swf file was not subsequently generated (similar to previous post). Debugging the problem, it appears to arise because the voice engine processes are persistent, and do not shut down when the GUI, after initial testing, is shut down and the self-extracting zip installation file executed. The required executables and dll's (ie: engine.exe and smapi.dll) accordingly do not copy over the originals, but copy into the appropriate directories under new names (with the zip file apparently not complaining during execution). Solution was to ensure processes are killed (kill them manually) prior to executing the zip file which installs the toolkit.
The third issue remains unresolved:
3. Could not get the real-time runtime faces to execute in a browser window. To debug ran the .sh commands directly in a bash shell with full path statements. The commands appear to execute, and binary output appears in the bash window in response to microphone input. The problem appears to be that the swf does not initialize in the browser window. Tried various browsers. Any solutions? Which version of Netscape did you use?
|
|
Posts:
2
Registered:
Feb 08, 2006 11:26:35 AM
|
|
|
|
Addendum
Posted:
Feb 08, 2006 04:41:28 PM
in response to: 's post
|
|
|
|
Re: item 3 above
The problem was a CGI permission problem. By removing control of CGI permissions from the Windows registry (ie: by placing the comment symbol back in front of "ScriptInterpreterSource registry" in the Apache config file httpd.conf) control of CGI execution was returned to Apache, and the permission problem was resolved.
Looks quite nice. Will post any further feedback after testing. Thank you.
|
|
Posts:
12
Registered:
Sep 16, 2005 09:42:25 AM
|
|
|
|
Re: Addendum
Posted:
Feb 09, 2006 02:41:01 PM
in response to: 's post
|
|
|
|
Re #1: The only dependence on Apache is in install.bat. I'm sorry that the installation script is so weak. I'm sure those \progra~1\apache~1\ could cause someone some trouble too if Apache was installed somewhere else. Apache 2 wasn't available for MS Windows when we put this together, but with changes to install.bat it should work fine.
Re #2: Sounds obvious when you mention it. Actually it's not the .zip file that puts the files into the bin directory; it's the install.bat file, which I admit again is weak.
Re #3: The reason for "ScriptInterpreterSource registry" is so that the the server knows to use bash to execute the .sh file. I'm not sure why this is causing problems, but then I haven't tried Apache 2 on MS Windows yet.
Thanks for your interest and for your perseverence.
Mike
|
|
|
|
|
