Ben's Bits

Once upon a time batch files were king in the PC world. Hardly a magazine issue, BBS discussion or user group meeting would go by without one of these handy scripts to add some functionality or usability to systems. Since the reign of Windows batch file programming has been on the decline. Of course shell scripting remains popular and extremely popular in Linux where most settings on the system are still controlled by text configuration files and command line utilities but in Microsoft land the script has been largely supplanted.

Even though the NT based operating systems (NT, 2000, XP, etc.) have actually made significantly more configuration available from the command line and there was a push for a new 'Windows Scripting' language these things have become largely forgotten and there are now an extremely limited number of users comparable to the Windows operating population which are comfortable writing scripts to automate things in Windows. Even among large corporate IT departments where there is perhaps the most to be gained by writing these sort of mini-utilities scripting is a dying art. One of the reasons for this is that most magazines and technical publications no longer regularly mention scripting or command line configuration utilities so there is a limited opportunity to learn about these tools.

Nevertheless these tools exist and when you find them they can be extremely useful. Take the "netsh" program for example. This handy little tool allows you to set and manipulate many of the Windows network settings from the command line and when combined with scripting it is possible to create scripts which will completely reconfigure your network interfaces (say from DHCP to a static address to another static address) for various network configurations all with the simple execution of a script.

You can learn more about this powerful tool from a few different Microsoft sites but while these provide some syntax and information perhaps the best place to get started is at one of the third party sites which covers it. Or now that you know about the utility you could just start experimenting with things.

For example running the "netsh -c interface dump" command will dump all kinds of interesting information about how your interfaces are currently configured to the prompt. It's possible to capture this information to a text file and then 'replay' the data to reconfigure things as they currently are using something like "netsh -f netsettings.txt"

Keep the art alive!

One of the many misconceptions about the D-STAR digital amateur radio protocol is that it is closed and will prevent tinkering by hobbyists. This turns out to be far from the truth indeed. Last year at the Dayton Hamvention there were several exhibits by D-STAR enthusiasts which included an entirely home brewed D-STAR radio and a home brewed D-STAR repeater controller. Well now someone has built a DV interface adapter which can provide a D-STAR digital voice interface on many existing transceivers. Of course some functionality is missing as there is no ability to change various DV settings from the minimal interface but it proves yet again that there is the possibility for much experimentation with this new digital mode.

On other fronts the OpenDSTAR group has released several software tools which build on existing commercially available repeaters and Internet gateways to extend functionality. Still in the pipe from that group is a USB dongle called the DV Dongle which will allow end users to encode audio in the AMBE format used by D-STAR digital voice for later playback through the repeater or, ostensibly, for live PC to repeater communications. Indeed the home brew spirit of amateur radio is alive and well in the world of digital communications, it just looks different than it has in the past.

A few months ago I learned of an interesting website called myNetWatchman. This is a very interesting and free website which aggregates firewall logs from various sources around the Net (you are free to contribute your logs as well) and analyzes them for trends and potential infections by IP address. System administrators are then able to enter IP addresses of servers they manage into the site and see whether those servers have been exhibiting any malicious behavior towards the monitored firewalls. This is just one additional useful tool for sysadmins to monitor the behavior of their servers.