🚀 go-pugleaf

Hans,

>> I am trying to set up a simple client-server system on our LAN.
>> Basically, I want to build a restricted remote user interface (client)
>> to a machine that is controlled by a PC (server) on our LAN.
>
>Would you use the naming client/server for 'remotely controlled'/controller ?

In the first round, the machine is actually a pulse generator
connected to a serial port on the server, sitting in a lab.  Detailed
operating parameters will have to be set up on the server, but then
basically the turning on and off and selection of channels in case of
a multi-channel generator shall be possible from the client, e.g., my
office PC.

>> I think I have one solution that works with Windows 2000, using named
>> pipes.  However, this does apparently not work on/with Windows 98SE,
>> which is where I have a good candidate for the server.  Are there
>> alternative methods to accommodate Win98SE  short of Internet style
>> ones?  I'd like a lean solution ...
>
>The way to do that is using sockets. You will be done for LAN and internet
>at once. You can use components f.i. TServerSocket/TClientSocket.

Thanks for the suggestion.  I'll look into that.

Cheers,                     Jochen

hjtrost at microfab dot com


Nil nimium studeo, Caesar, tibi velle placere,
nec scire ut an sis albus an ater homo.
                                          Catullus