From a linux machine, "man smbclient" shows the following:

       -M NetBIOS name
              This options allows you to send messages, using the
              "WinPopup" protocol, to another  computer.  Once  a
              connection  is  established you then type your mes-
              sage, pressing ^D (control-D) to end.

              If the receiving computer is running  WinPopup  the
              user  will receive the message and probably a beep.
              If they are not running WinPopup the  message  will
              be lost, and no error message will occur.

              The  message is also automatically truncated if the
              message is over 1600 bytes, as this is the limit of
              the protocol.

              One useful trick is to cat the message through smb-
              client.  For example:

              cat mymessage.txt | smbclient -M FRED

              will send the message in the file mymessage.txt  to
              the machine FRED.

              You  may also find the -U and -I options useful, as
              they allow you to control the FROM and TO parts  of
              the message.

              See  the  message command parameter in the smb.conf
              (5) for a description of  how  to  handle  incoming
              WinPopup messages in Samba.

              Note:  Copy WinPopup into the startup group on your
              WfWg PCs if you want them  to  always  be  able  to
              receive messages.

TRYING it out as follows "works"...
E:[TOM]/EMERSON/WORK>sh -L
########################################################################

               MPE/iX Shell and Utilities (A.50.02)
    COPYRIGHT (c) Hewlett-Packard Company 1992, All Rights Reserved.

########################################################################


shell/iX> cat SMBMSG | /SAMBA/PUB/bin/smbclient -M GURU2
Added interface ip=192.168.41.5 bcast=192.168.41.255 nmask=255.255.255.0
Connected. Type your message, ending it with a Control-D
sent 95 bytes (status was 0-0)

however, from the CI:

xeq /SAMBA/PUB/bin/smbclient;info="-M GURU2";stdin=SMBMSG

appears to work (in that it gives the same "sent 95 bytes" response), but
the message doesn't "pop-up"

dropping the "stdin=" parameter, the program does prompt for the
text-to-send, but doesn't take CONTROL-D as noted -- you need to type :EOD
instead... (however, this doesn't appear to work either)

Why this doesn't work when invoked from CI but does when invoked via the
shell remains a mystery, but, obviously, using the shell is one way to make
it work...


> -----Original Message-----
> From: Lars Appel [mailto:[log in to unmask]]
> Sent: Wednesday, November 15, 2000 2:48 PM
> To: [log in to unmask]
> Subject: Re: [HP3000-L] NET SEND on the e3000?
>
>
> Should be something in the line of...
>
>  :xeq /SAMBA/PUB/bin/smbclient "-M yourPC -I your.pc.ip.addr"
>  Type your message here or redirect input in above line.
>  :eod
>
> The "-I your.pc.ip.addr" should only be neccessary if your
> 3000 cannot resolve the nodename "yourPC" properly.
>
> All this is "by heart" only; haven't test-typed it right now.
>
> Lars.
>