HP3000-L Archives

June 2000, Week 5

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
ChipDorm <[log in to unmask]>
Reply To:
Date:
Fri, 30 Jun 2000 16:43:29 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (51 lines)
Hi y'all,

Well, ah, actually no...

At least not without some VERY serious network programming which
might border on passing out a trojan horse.  In ancient times, there
were "hard" connections between terminal and machine.  This allowed
programs on the 3k to actually "open" and "write" to logged-off  terminals.
This is how I use to broadcast "system is up" messages to available terminals.

*sigh* You could do lots of fun things with FCOPY...

Ok, I'll go back to my rockin' chair now,
Chip "oh-nurse" Dorman
Greenfield Industries/Kennametal
>Tom asks:
>
>>Back in the "old days" - when all terminals were connected via DTC
>>ports, it was straightforward to send messages to all DTC ports.  This
>>is the method we used to notify users that a planned shutdown was over,
>>etc.
>>
>>Now that most connections are from a network using terminal emulators,
>>it's not so easy.  Naturally, we can use Novell broadcasts or Winpopup
>>messages, but we'd like to be able to do it {perhaps automatically]
>>from the 3000.
>>
>>Does anyone have ideas on how this could be done to a static IP
>>address? How about DHCP-based addresses?
>
>The "tell all" command still works just fine, regardless of how the sessions
>are connected. For example:
>
>  :tell @;Please note that you have 1 minute to log off.
>
>See on-line help for more options.
>
>Wirt Atmar
>
>
>
>
>
>
>
>



Take the second star to the right and on until morning.

ATOM RSS1 RSS2