[Lvlug] Session 1 Presentation

[Brian Martin]

Scroll down to the sig block for an invitation...

Faber Fedor wrote:
> 
> On Fri, May 10, 2002 at 02:12:20PM -0400, Brian Martin wrote:
> > There's a great deal that can be done without VB.  There are several
> > tomes about NT* command line programming, and we use a great deal of it
> > here.
> 
> Can you forward some examples?  One of my presentations is a comparison
> of Windows and Linux and this would fit in very nicely.

Hmmm.  We add/delete users/groups, change group and security
associations, things like that.  The NT crew here uses it for processing
startup script options, like drive mappings and group memberships.  And
saying hello, but they can't fire phasers (that's Novell humor, for
those who haven't had the joy of working with the big red N).  We use it
to kick off more complex automation, like Autotester, and check exit
states and things.  Email us when bad things happen, or when the Quake
server goes down <wink>.

> Also, got names for those tomes or, better yet, online resources with
> real examples, or even keywords to search on?

Online I can't do, but the books they use are
1. Windows Scripting Host, 1-57870-139-2
2. Windows NT Shell Scripting
3. Windows Admin Scripting

#2 is probably what you're looking for, the others mostly help you
integrate with other pieces like WSH and VB.  Personally, I'd try perl
before anything else.  There are some really interesting extensions I've
seen on perlmonks but nothing I've tried myself yet, since I'm dealing
with a VB component here.

> > We also use Autotester, and WSH, but I don't like those.
> > Curiously, I *know* VB is more complicated and finicky than shell and
> > perl, yet I can do it.
> 
> Yes, but that's because you're studlier than the average geek!

You're just saying that so I'll show up with beer next time.

> > Strangely, my VB people are very resistant to
> > doing *nix.  They are too busy keeping up with changes in VB from year
> > to year,
> 
> I've never worked in a VB shop for more than a year, so I've never seen
> the chaos due to a new VB coming out.  What does it entail?  Do they
> actually have to recompile everything?

Not every time, but eventually it bites you in the tookus big time. 
I've seen entire libraries get hosed up in a single point release, but
that's not the norm.  Still, it is vastly more volatile
(onamonapeaonmybrain) than perl or sh or C.

> I remember back when ADO was introduced to replace DAO (or was it the
> reverse?).  My attitude at the time was to keep using DAO because it
> still worked; I saw no reason to change all the code to ADO.  That isn't
> feasible?

I dunno.  I speak Bourne and a smidgin of perl.  I have heard my #1
programmer bitching about that exact issue, not to mention things like
zero documentation on remote access to a SQL database, and other
Microtrocities.  But the UNIX boys are so quiet.  I mean, the last time
they changed something that really put a my knickers in a twist was when
they went from System 2 to System 3 and made the delete command the
rename command.  Like 1982.  I can't even remember which way it worked
out, but rm was a dangerous utility for a while there.  If anybody
remembers the exact details, please regale us with some better stories. 
I have managed to wash most of that period out of my brain.  Geez, the
clothes we wore and the hair styles.  Ick.


-- 
Wow!  Hey gang, note new CISSP designation below.  I actually passed
their hairy furball test.
More coin, and means more fun.  I'm gathering some bodies together next
Tuesday at 5pm at the SkyBox down here on Lehigh street.  Anyone in the
Lug, feel free to stop by and consume a couple with me or shoot some
pool.

Brian Martin, CISSP				610-402-1412
Manager, I/S Security				http://www.lvh.com
Lehigh Valley Health Network

Life is Noh drama.