I haven't provided the specific services you mention because I don't see a need for them, but over the years I've done everything you propose here. Sockets, remote pings, and outside (bi-directional) messaging and requests for information are at the core of most of what I've been doing for the last decade. My private toolkit has the base code for all of this functionality. It's not a "trick", it's the air I breathe. I just wish there was as much interest for communications in the Pick market as everywhere else.
Or to put it another way - if you do come up with something communication-wise that might "be worth having", let me know because I might already have it in a junk drawer somewhere.
How's this for a stupid pet trick: Character-screen programs that do animation. I wrote two favorites. One had two dogs humping - yeah, in 80x24 ASCII. Another had a Romulan warbird flying on the screen, and the USS Enterprise coming up from the bottom. The Enterprise shoots a torpedo at the warbird which then explodes, and the Enterprise retreats back down through the bottom of the screen. Use the TCL command to send these to another port and listen for the reaction. I don't have the source for these anymore but they didn't take long to whip up.
T
Tiny Bear's Wild Bird Store
"Everything For The Backyard Bird Enthusiast, Except For The
Birds"
http://www.TinyBearWildBirdStore.com
Toll Free: 1-855-TinyBear (855-846-9232)
At least in D3, really fixing a GFE requires knowledge of specific bits and bytes in data groups and in the File Control Block (FCB). The FCB didn't exist in R83 and some of the structures are different from R83. And there are many different kinds of GFEs, each one requiring understanding and specific knowledge. I believe TL would offer a class on this with enough demand, maybe at Spectrum, or in one of their marketing/conference tours. I have no idea - can't hurt to ask.
I haven't seen a GFE in years. Is it worth the time to acquire that knowledge - and then forget it before getting a chance to use it?
T
Why is basic system administration called a "stupid pet trick"? We have the source code for a file-save program and account-save program, both wrapped around a simple and well-documented Save verb. Why is it not SOP for every "value-add reseller" or system administrator to copy and distribute site-specific versions of these programs which are designed to address common specific needs? Why isn't there a FOSS page where people post simple utilities to save select pieces of a production system at specific times, thus reducing file-save and related downtime?
Want a search-system2? I have one that displays across a wide 132-column screen, searches IDs and/or within items. (I offered it to TL who either lost it or decided not to include the extra features - go figure.) Anyone else here have a custom search-system utility? The source is there - go for it. It's not a stupid pet trick when you're using the tools that are available.
T
--
1 2595 mds > DAILY.PSL > FPSINVENTORY.MORE
1 2596 mds > DAILY.PSL > FPSINVENTORY.MORE > FPSINVENTORY.MORE
File Inconsistency Encountered - Incorrect Links
Q=Quit/O=Logoff/S=Skip/F=Fix/T=Truncate/<CR>=Debug?
I wrote a BASIC program that completely rebuilt trashed AP/Pro systems, including all files, links, and the overflow table. This was for systems that ran out of overflow and used up the reserve frames, and for people who hit X to restore without having a verified backup. It was one of the coolest proggies I ever wrote. It was deployed from a floppy which I transferred to Support when I became QA Manager at Pick Systems - we weren't allowed to save programs on the production system. The floppy was lost soon after. I almost cried, both at the loss, and at my stupidity for not getting more copies.
Now THAT was a stupid pet trick, and a testament to the power of BASIC. Kudos to your colleague, Neil - I didn't know anyone else had written something like this.
T
Why is basic system administration called a "stupid pet trick"?