Problems and Solutions

cFPcom_proxy eats almost all available CPU

For some reason, the cFPcom_proxy will use all CPU resources if it has been started before ZEUS is started and initialized. To avoid this, the cFPcom_proxy should be started after ZEUS. One solution could be a batch file starting ZEUS and proxy:

"C:\Documents and Settings\All Users\Start Menu\Programs\ZEUS\ZEUS.lnk"
ping 1.1.1.1 -n 1 -w 60000 >NUL
"C:\Documents and Settings\All Users\Start Menu\Programs\ZEUS\cfpcom_proxy.lnk"

However, this batch file can't be directly auto-started. Otherwise all commands in batch file will run simultaneously (don't ask me why, it is Windows). Therefore, it can be started with

cmd.exe /c c:\zeus.bat

Another problem: if German Windows is used, the path to ZEUS.lnk and cfpcom_proxy.lnk is different and include umlauts. cmd.exe does nto support umlauts in path names (or some mystic encoding should be used). The best would be to copy .lnk files to some directory without umlauts in path name and executed them from there.

If there is still problems while running from autostart menu, the ​nncron application can be used to run zeus.bat at startup (lite version is not enough). The crontab should look like this:

#( zeus
 Time: START-TIME
 Action:
 StartIn: "C:\"
 ShowNormal   NormalPriority
 START-APPW: C:\zeus.bat
)#