Thank you, for all your answers!
We have one employee who has worked a lot with Windows, and same with OPC. So I can provide same answers.
* Mike Hearn - OPC is mostly used for data collection, and to a lesser degree to control industrial machines.
* Juan Lang AND Robert Shearman - OPC doesn't use named pipes. OPC uses Dcom over TCP.
* Mike Hearn - OPC doesn't need any new Windows (2000, XP) parts, and should work on Win 98 with the added Dcom support (not tested).
* Mike Hearn - Price of OPC for Linux was when I looked at it for about a year ago 3000 - 4000$ per project you used their API in. And it only supported one of the OPC versions. Now I guess that the prices has been going down...
Now I also got some questions from your answers:
* Did I understand correctly. Wine doesn't have a built in support for DCom, to be abel to use Dcom I have to add the DCom support from Windows 98 to the Linux system? And the problem with that is the MS License, it stops me from distribute those XXX.dll with a Linux product (hardware and software in this case.)
* We want to make a OPC server, because other computers want to get information from our system. Is there a problem in make a DCOM server, is it the "no user can acsas port under 1024 on a Linux system" problem.
* What I have heard I thought DCom uset RPC??? But Juan Lang wrote that Wine doesn't have support for RPC
/Rickard