Configuring a virtual WiFi access point with my netbook in Windows 7 turned out to be easier than I expected. I boot into LINUX and tether the netbook to the internet over a bluetooth connection to my Blackberry regularly, but I’ve not tried it under Windows 7. This hasn’t been required, until now.

Occasionally, when we travel abroad we rent USB cellular data cards to track the weather and keep in touch. I’ve yet to find a card or service that works predictably with my LINUX kernel of choice. Sadly, this drives me into Windows 7.

You can do this from the command-line. Open a command line with administrative privileges and type:

	netsh wlan set hostednetwork mode=allow ssid=NAME key=PASSWORD

Replace ‘NAME’ and ‘PASSWORD’ with something that makes sense to you and your users will remember. Start the access point with this line:

	netsh wlan start hostednetwork

Stop the access point with this line:

	netsh wlan stop hostednetwork

You can share an existing connection to this interface by going to the ‘Properties’ of a connection, select the sharing tab and enable ICS by choosing the corresponding virtual WiFi adapter.

While this has a certain stark elegance, it is a bit involved and requires more steps than you might want to do on a daily basis. There is an Open Source option that simplifies this considerably.

Virtual Router is a free, open source software based router for PCs running Windows 7 or Windows Server 2008 R2. Users wirelessly share any internet connection (Wifi, LAN, Cable Modem, Dial-up, Cellular, etc.) with any Wifi device (laptop, smart phone, iPod Touch, iPhone, iPad, etc.) Devices connect just like any other access point using WPA2 encryption.

I’ve found this to be pretty handy. What do you use?

(See also: virtual router)

I’m collaborating with a very small team to develop business process tools for an energy risk management company. One of the developers was not as comfortable with the UNIX command-line interface and wanted to know if I could set up a GUI.

It turns out, you can. Assuming you have shell access to the instance, this is the easy way to do it. Log into your instance and load the following packages:

sudo apt-get install ubuntu-desktop
sudo apt-get install vnc4server
vncserver :1

Launching VNCserver will prompt you for a password. When your VNC client of choice (I use Chicken, based on Chicken of the VNC by Jason Harris) connects, you see a terminal window in the desktop. Type the following command to start your gnome desktop:

nohup gnome-session &

This will launch the gnome desktop session manager and bring you to an UBUNTU desktop you might recognize. Most of the base configurations are exceptionally small machines. Launching a desktop is pretty taxing, launching a browser is paralyzing.

You should know there are more efficient ways to an UBUNTU windowing system. Installing the entire ubuntu-desktop will create a collection of tools that you may never use, making your storage footprint quite a bit larger. If you do not want all the desktop tools you can install only what you need.

There are also a range of remote desktop servers and clients available. I chose the Chicken fork of VNC. You might like to investigate FreeNX, or any of the other flavors of the VNC family.

Once the correct EC2 tools are installed, the proper keys are generated, in the right directories, the instance behaves like any other remote server.

I’m interested to learn what our burn rate will be for the services we’re developing. What I see so far is encouraging.

MinneWebCon 2011 – Timothy Kunau from TECHdotMN on Vimeo.

After my session about interactive graphics titled More than 1000 Words: Scripts and Techniques for Interactive Graphics, I was interviewed by Mike Bollinger from tech.mn.

(See also: tech.mn)
(See also: More than 1000 Words: Scripts and Techniques for Interactive Graphics)
(See also: tech.mn: MinneWebCon 2011)

(See also: tech.mn: MinneWebCon 2011)

I spent the afternoon testing internal cabling looking for a transient error. It now looks like we have the bit error rate (BER) under control, BER both pre and post test are now 1.0E-9. The FEC reference in the image refers to forward error correction (FEC) first introduced by American mathematician Richard Hamming who pioneered this field in the 1940′s.

According to wikipedia and what I remember from the Tanenbaum and Stevens books: FEC gives the receiver an ability to correct errors without needing a reverse channel to request retransmission of data, but this advantage is at the cost of a fixed higher forward channel bandwidth. FEC is therefore applied in situations where retransmissions are relatively costly, or impossible such as when broadcasting to multiple receivers. This is the case with cable data connections.

What was old is new again.

(See also: Richard Hamming)