Windows 7 Network Bridging

When setting up my SageTV server, I needed to move the server from the office to a spare room to get better over the air reception. In doing so I had to alter my network layout, so I had my Ethernet over power link running from the server to the HD300, and then a wifi link from the server to the rest of my network.

I was having all sorts of problems getting the routing correct, when I noticed Windows 7 has a bridge device option.

(shown turn off above as this image was captured on my work laptop)

When I click this option it said something like: ‘You need to select two devices to bridge’, good point. So I selected the Ethernet and Wifi at the same time, right clicked, and bridged them.

Now the HD300 can see the internet, and it all just works (this was done months ago) and it is still just work.

So Windows 7 earns a “just works” point, well done to the OS team there.

Odd Spam

Deleting spam today I noticed many just like these:

The words talk about Nike football boots (soccer cleats) yet the URL’s points to Adidas f50 boots. Which by it’s self is boring, but in the weekend Jacob and I were looking for new football boots for him, and were going to get the f10 boot from the f50 range, but they didn’t have the colour he liked in his size.


WES 2009 Error “An error occurred while getting the vendors list section name”

When trying to import the ‘Intel(R) Chipset Device Software‘ inf files into Component Designer for Windows Embedded Standard 2009, I have been getting the error “An error occurred while getting the vendors list section name”.

My solution is to open the .inf files and change this section:


; =================== Intel ==================


to this:


; =================== Intel ==================


The problem is the Manufacturer section lists Intel as the base section, with a NT.5.1 (Vista) and NTamd64 (64bit) driver section, but does not list the x86 option. Also the section [Intel] acts as a catch all section, but Component Designer is looking for each [base].[sub] section. The normal Windows driver install handles the Intel scripts, but Component Designer does not.

WinCE development without Active Sync on Win 7

At the start of the year I was given a device to do trial Windows CE development against. I was also given a zip file with the SDK and some instructions.

Step 1: Install Active Sync 4.5 on your Windows XP machine (this will not work on Vista or Win 7)

So my Win 7 lappy is shafted. Luckily some work colleagues had been doing WinCE development ‘differently’ on an earlier product, and they mentioned using ‘CMaccept.exe’.

Search for ‘CMaccept.exe’ leads you to the advice you want: How to: Connect to Windows CE Device Without ActiveSync

Luckily for me my device has working Ethernet, so this worked nicely.

I mention this because today another engineer asked me how I got Active Sync working on the device, as he’s having problems under XP, thus I suggested the above method.