I had a similar situation; all our workstations involved are still Windows XP and the service is still there, but is disabled by a service pack or security patch or something, I forget the details.
In order to allow the old fashioned and insecure "net send" command I created a Group Policy Object similar to the one here: http://www.eggheadcafe.com/software/aspnet/31323861/create-policy-for-allowre.aspx Microsoft has an article here that describes the "Net Send" command and search on "AllowRemoteRPC" to learn more! http://msdn.microsoft.com/en-us/library/aa383842%28VS.85%29.aspx On Mon, Jan 18, 2010 at 2:16 PM, Evan Brastow <[email protected]>wrote: > Hi all, > > > > I have a legacy application I wrote in PowerBuilder about 10 years ago that > uses the syntax NET SEND (username) (message) to send messages to users > (they pick the messages from a drop-down box for speed). However, since a > certain service pack in XP as well as in Vista, this functionality no longer > available and the service itself it gone. > > > > What I’m wondering is, is there anything out there that will essentially > install a replica of the Windows Messenger service so that the same API can > be used to send/receive popup messages? I don’t need a full-fledged > messaging app as the messages must come from my legacy app, not be > user-typed. > > > > I found something called LanTalk XP which seems like it could have worked, > but not quite. > > > > Anyone have any ideas? > > > > Thanks so much.. > > > > Evan** > > > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
