David Moisan's Blog

Starting tomorrow, SATV will go off the air for an upgrade.  We will get shiny new equipment, and I'm blogging the whole thing!  Our first step is to demolish the old console.  I expect we'll find surprises like this:

This cable formerly powered one of the PC's in Cablecast.  It went down one day, and this is what I found!   

Paul Thurrott (“Forget About XP- Let's Save Windows for Workgroups 3.11!”) and numerous others have written about Microsoft’s retirement of Windows For Workgroups, which has had quite an afterlife in embedded systems.

(This is not new:  The 1800-series Red Line trains on Boston’s MBTA are reported to have an “A>” prompt on a console in the driver’s cabin;  DOS 6.22 has been seen in embedded systems, and probably in those trains.)

Paul made a nice banner:

Windows 3.11 is special for me;  it was the first Windows version I ever used.

It made me think of another “special” persona at Microsoft, Clippy!  He had a retirement party a few years back.  He made the rounds to various Microsoft events around the country.  He happened to ask me for career directions and I obliged:

I hope he’s having a good life.

One thing that is very important to any IT shop is environmental monitoring.  There are too many instances of overheated or soggy servers these days, especially as more servers are outside traditional datacenter spaces as in them.    We wanted our cablecast area, and other critical areas like our server room to be monitored for temperature and water detection.

We went with an inexpensive box from ITWatchdogs.com:

This is the SuperGoose.  It can accept 16 digital sensors and three analog inputs.  In practice, we use digital temperature sensors and analog water sensors.  It is web-based and allows alerts to be sent based on conditions.  As you can see, it also has a digital display and an alarm.

To avoid running more wire throughout the building, I built some breakout boxes from common network components from Home Depot and Radio Shack so I could use an unused network drop to run both the digital and analog sensors to remote locations and permit expansion in the future.

This is the master breakout box that goes to remote sensors in the Control Room and Engineering.  I’ve made the wiring diagram available [PDF].

One thing you need to know if you do your own sensor wiring with this system:  The documentation is wrong! Documents on the ITWatchdogs site give two different pinouts for the digital sensors.  Neither one is correct. 

The digital sensors need conductors 2, 3 and 4 passed straight-through to the Goose—no crossover cables!  You’ll probably run into this when you reuse old RJ11 phone cables for your sensors;  almost all of them are crossed.  MilesTek sells straight-through RJ11 cables cheap—use them!

The analog sensors are straightforward;  just one contact and ground.

The SuperGoose works fine;  the only thing I wish for is a web page on the Goose that indicated active alarms at a glance.  The Goose makes the data and log available so it’s possible I could write an app or a Vista gadget to indicate alarms. 

It’s an inexpensive solution that I highly recommend for small shops. 

We’ve been talking for years about upgrading our cablecast plant.  I’ve described it in an earlier post, Information Technology and Coping with the Second Energy Crisis.  You may also remember the problems I had in there a few months ago, mentioned in passing, Why Johnny is not a Tech, and also our problems ensuring access for the visually impaired, Future of SATV's Audible Bulletin Board on my other blog.

We’re purchasing a system from Tightrope Media Systems, our current vendor.  I’m sure their tech support staff (Hi, Jeremy!) will be so happy!

The installation will start around August 20th, and I will blog the whole process with pictures.

Notice the ghosted text in the upper center.  It was caused by Movie Maker crashing the night before.  The artifact persisted until the system was rebooted. 

Mind Of Root is spreading a meme!  What was one’s first job as a sysadmin and when did they learn scripting?

How old were you when you started using computers?

I was, um, 16, and a freshman at Salem High.  We had a PDP-11/60 and a computer lab.  I loved it.

What was my first machine?

My brother bought a TRS-80 Color Computer in my junior year of HS, and I used it through college, eventually buying enough parts for it that I had half ownership.  The first computer I owned personally was a 286 PC clone in 1991.

What was the first real script you wrote?

In high-school, I and my brother and several of our friends took turns being sysadmin for the PDP-11.  It ran RSTS, which was a BASIC-based timeshare system for educational use.  Its scripting language was BASIC!  I wrote a script to backup files from our system disk (a large removable disk pack) to our secondary disk (another pack).  The backup system on RSTS, like most all minicomputers at the time, was made to use tape as the backup media, like the (now old-style) NTBackup, and we didn’t have any tape drives.

What scripting languages have you used?

BASIC (!!), VBScript, CMD, Perl and now PowerShell.

What was your first professional sysadmin gig?

That would be the job I hold now at Salem Access Television, the first job I’ve had in a while where I get to be sysadmin, though of course I have much deeper responsibilities there.

If you knew then what you know now, would have started in IT?

When I got out of college, I felt a little disillusioned and considered technical writing.  I never seriously considered a non-technical career (like management), but I wasn’t going to be a coder as I had originally trained for.  After going through the “Parachute” job book too many times.  I now believe IT was the right thing for me after all.  It’s a craft of sorts.

If there is one thing you learned along the way that you would tell new sysadmins, what would it be?

Get involved with community;  it’s much easier to stay connected than it was when I was an intimidated freshman in college.  I was alone for too much of my college life.  Don’t be afraid to look at the big picture;  as you get more experience, you won’t see your world only through a shell prompt.  Also don’t forget the larger community—at SATV I am making a difference for us in how we serve our community.  Keeping things smooth can be its own reward. 

What’s the most fun you’ve ever had scripting?

I have fun just learning scripting, though I admit I haven’t had the time or energy to get into the real esoteric stuff that’s in PowerShell CTP 2, though I do run it and do tinker from time to time.

Who am I calling out?

SBS 2008 has PowerShell built in.  It will be the first exposure to PowerShell for many SBS admins, so I want to call out people in the SBS community:

• SBS Diva
• David Overton
• Reload Nuggets
• Knight-time Ramblings
• Bill's Bit Bucket

Microsoft has filed a very scary patent.  The original purpose seems benign, according to Unwired View:

In addition to many benefits brought to us by mobile phones, there have been a few drawbacks as well. Especially, related to ethics/culture/social issues of the mobile phone use.

Don’t you just hate it, when during an engaging presentation, show or movie, a mobile phone of some as#$%^&&, sorry, forgetful person, begins to ring? What about someone taking out his high end cameraphone and doing something with it in the locker room? Can you be sure he’s not taking your nude pictures in the shower? What about someone secretly recording confidential conversation on his mobile phone?

Microsoft seems to have an idea how to solve all these problems at once. By creating device manners policy DMP [sic]), to which all mobile devices will have to comply to. And they even want to patent it

[From the Microsoft patent:]

Such policy may be used to communicate to various mobile and other devices the “manners” with which compliance is expected or required. Similar to some of the social manners honored among people, such as with “no smoking” or “employees only” zones, “no swimming” or “no flash photography” areas, and scenarios for “please wash your hands” or “no talking out loud”, devices may recognize and comply with analogous “device manners” policy.

This won't stop there.  I can anticipate lots of potential "no photography" zones:

• Schools:  "Behind Every Camera is a Pedo!"
• Government buildings:  I guess I can't film public hearings anymore like I used to.
• Public places:  Remember, papparazzi!
• Workplaces:  Maybe you'll be allowed to take pictures of the office party...if you're good with the boss!  You're a whistleblower?  Siberia might be safer.
• Anywhere where someone in power is scared of their own people.

That last is the scariest place of them all, for it is everywhere in America.  Everywhere in our country, people take pictures of things the powers-that-be would rather not have seen.

Youtube has video on atrocities in Myanmar.  Perhaps in a few years there'll be smuggled videos and photos from America.

I live in the “tourist town” of Salem.  What if the Peabody Essex Museum wanted exclusive photo rights for the whole city? 

Original:  Microsoft wants to teach manners to you mobile device » Unwired View

Update:  Boing Boing Gadgets posted about this.  DCulbertson writes in the comments:

Suppose it was implemented. I wonder how many public places would eventually have the "no pictures" flag set? Meaning even if it's legal to take photos, you couldn't... Then how many police cars and federal agents would have DMP boxes with "no photos / no video / no audio recording" flags set. No more individuals documenting arrests or police action.

Someone, somewhere in the Department of Homeland Security, is smiling.

Update:  Bruce Schneier as usual has an excellent take.  Also see his column in Wired, “I’ve Seen the Future and it has a Kill Switch”.