After starwdaemon starting the next string appers: _____Stripchart Server ver. 10.0.5-04/29/99 is operational on port 14360________

although file /etc/services contents string: 'star-chartd tcp/6200 '.

At the same time port-scanning program detects that port 6200 is open.

And after all, executable Star program can't work starwatch daemon. Does anybody know how to force starwatch work?

Which OS are working at? Windows or Linux? I have exactly the same problem with Linux, but with Windows everything fine.

How can you make it work in windows??

I meen Windows version of Star-CD.

Dear Anton.... Of couse I mean Linux version of StarCD. Have Your resolve the abouve problem?

To get starwatch to work you have to (1) start the starwdaemon (you already did this), (2) /etc/services register the port (this looks like you did this also), (3) when running Star executable, have starwatch opened up and ready to connect to the starwdaemon server. As soon as the solver starts to report residuals, click on connect and select the server available (usually your NT user account name) and it will tell you what process is available to monitor. Select it and you should be able to watch your residuals as a graph plot.

how do you run starwatch and the daemon on linux then?

If you have STARDIR in your path, type starwatch at an xterm window to start starwatch. Type starwdaemon at an xterm window to start the daemon.

Also, when you run interactively from the Star Guide, starwatch will automatically be opened up. At this point just connect to the server and select the active service.

ive tried that but i get the message ERROR - the residuals charting daemon is not registered. any ideas?

i have the same problem under Linux Red Hat 7.1

i have succeded in it only one time when two tcp port have been in use.

As I remember, you need to start starwdaemon before you run a star job, otherwise starwdaemon won't register the charts. You can start starwatch at any time, but I also remember if you terminate the starwatch process by command "kill", consequently you also terminate the daemon. In this case, you won't be able to monitor the running star jobs any more unless next round restart.

Never try to run starwdaemon and starwatch via different user accounts, though. Probably that will prevent starwatch terminate starwdaemon?

Good luck.

JY