I'm using Windows 2000 Server, SP3. Just installed my Dialogic D/41-EPCI board and its drivers (Intel's Release 5.1 and its Service Pack 1).
<br>
<br>I even ran some of the Intel's diagnoses and sample programs successfully (the hardware seems OK).
<br>
<br>Then installed the latest TeleFlow toolkit (fresh download), but the Server refuses to start: "The service is not responding to the control function" says the Server icon, "The Service did not respond to the start or control request in a timely fashion" says the Event Viewer...
<br>
<br>I ran TeleFlow Config: "Dialogic", path to a test of mine (that works under the Simulator), a log directory (with plenty of free space), "500" KB logfile, "200" log lines, auto-start checked (but failing)...
<br>
<br>The TFServer.log says:
<br>Oct 25 14:03:46.45: enGenic TeleFlow: Build 2004.0630
<br> (c) 1994 - 2002 enGenic
<br> All rights reserved.
<br>
<br>Oct 25 14:03:46.45: Dynamically loading board DLL at run-time.
<br>Oct 25 14:03:46.45: LoadBoardFunctions: Start
<br>Oct 25 14:03:46.70: LoadBoardFunctions: Success.
<br>Oct 25 14:03:46.70: Starting additional threads required by board DLL.
<br>Oct 25 14:03:46.70: Loading .TAL file into application list structure.
<br>Oct 25 14:03:46.70: This is an unlicensed or evaluation version of Teleflow.
<br>Oct 25 14:03:46.70: Port 1 is an unlicensed port
<br>Oct 25 14:03:46.70: Starting Monitor thread...
<br>Oct 25 14:03:46.70: Starting Engine threads...
<br>Oct 25 14:03:46.70: Waiting for events from threads.
<br>
<br>... and that's it! No errors... This is a development PC, not a production one, so the licensing issue should not affect, I guess. Or does it?
<br>
<br>Is there anything else I should check out to diagnose this?
|
<br>
<br>The TeleFlow\InstallCompletor.bat file is not doing its job correctly...
<br>
<br>If the %TFDIR% environment variable is not correctly set to the TeleFlow directory (or even if it's not defined at all, which was my case), the two services the batch file tries to install, are left with incorrect paths to the binary files that must be run as services.
<br>
<br>Besides, the "SERVICE" command-line parameter passed to the TFServer.exe application gets lost as well.
<br>
<br>I used the pserv.cpl freeware utility (http://p-nand-q.com/e/pserv.html) to edit the path to the files and correctly set the command-line parameter to TFServer, and then both services were able to start.
<br>
<br>Hope you can fix this for the next downloadable release of TeleFlow.