Recovering Vista ICM devices.tar.gz and style.tar.gz

September 22, 2012 07:32 by docbliny 

Several people reported that they had attempted to use the auto-update feature in the Vista ICM, and that doing that had removed the files required to display devices.

It seems the auto-update procedure is buggy and erases the flash storage before checking if it’s able to successfully load any available updates. Since the device has been discontinued and (I think) In2Networks has gone out of business (or at least has shut down the related servers). This means that the auto-update feature is now an “auto-destruct” feature.

My ICM was still intact (though I did have to factory reset it since it wasn’t responding), I did some hunting and pecking, and in the end I was able to pull out the files from flash file. I’ve attached them below. You can use the Advanced / File System page to upload and save them to flash under http://[ipaddress]/setup. As usual: Use at your own risk.

Thanks to Norman for agreeing to be the guinea pig to test these files out!


Now for some geeky stuff:

1. To download files from the device, you can create files in the /var/fusion/web folder. The other option is to create a symbolic link to an existing file. This is especially useful for larger files. You can then download the file(s) with a browser from http://[ipaddress]/web/[filename].

2. I wasn’t able to download all of the flash files. In any case they are in /dev/flash:

  • all
  • boot
  • bootarg
  • config
  • ethmac
  • image
  • settings
  • storage

The reason I couldn’t get some of the larger files out is that the embedded shell does not support IO redirection, so I couldn’t cat to gzip to minimize the size.

3. I pulled the devices.tar.gz and style.tar.gz out of a flash image located at /dev/flash/storage. Since they were combined in a flash image, I had to remove a few bytes of the header before the first gzip file, and then split it into two (one for styles and one for devices). A test with 7Zip on Windows said the files were valid. I was also able to use gunzip on the ICM to extract the contained tar. However, tar failed as it ran out of space about halfway through (normally they packages are on another disk so the extraction works when it happens on startup.

Yahoo! re-enables OAuth (at-your-own-risk)

April 24, 2009 15:38 by docbliny 

The plug got pulled on OAuth this week in several places, including Twitter and Yahoo!, with Twitter taking a lot of heat on the subject.

Yahoo! is now allowing users and developers to authorize applications, but with some additional messaging letting users know that their data may be at risk if they continue. The main idea here is obviously that developers can still continue their work while the protocol level problem is resolved.

Additional messaging

Additional information

Yahoo!’s OAuth Update #2

OAuth acknowledgement of issue

Details on the issue from the advisory

Converting D-Link D-ViewCam .DVF files to .AVI

February 14, 2009 14:10 by docbliny 

I ordered another HDHomeRun Thursday and was expecting it to arrive Friday. Well, after having some friends over for dinner I got around to checking the UPS order tracking and it stated “Delivered – Front door”. Well, I certainly couldn’t find it. So I started D-ViewCam to check the security footage from our front door and guess what? No UPS guy had ever walked past our front door Friday.

The software that comes with certain D-Link web cameras is pretty awful. It also creates proprietary files (MJPEG/MPEG4?) along with additional information such as motion detection details. This was the first time I wanted to actually get the video out in a format that I could actually forward on if needed which I didn’t end up needing. Amazon had placed a replacement order with free next day shipping about two hours after I emailed customer support. Of course, this didn't really help on a Friday (OK, OK… Saturday) past midnight.

Turns out that D-ViewCam doesn’t work all that well on a Windows Home Server, at least through Remote Desktop. I was able to set the start and end cue points only once for an export. Other times they were disabled making it impossible to actually export anything. And the one time I was able to export, I ended up with a zero length file.

Long story short (I’ll leave out having to install VS2008 in a virtual machine since D-ViewCam doesn’t work under 64-bit Vista either), a few hours later I had a custom utility that will take a .DVF file and convert it into an .AVI. Unfortunately, I have to use the libraries from D-ViewCam to do this, which means you’ll need to have that installed. In addition, the format (compression) doesn’t seem to work (It doesn’t have any effect. The same goes for exporting via D-ViewCam).

The story also has a happy ending, the person who received the package a few streets down was kind enough to bring it over this morning, so now I have 4 tuners in Vista MCE, but getting that to work is another post altogether.

Dvr Convert Screenshot

The utility is a quick hack. It will only convert the whole file, and this will take several hours. It doesn’t do batches, and you can’t cancel it (unless you kill the app with Task Manager). I didn’t want to spend the time writing these unless someone actually asks for these features.

It’s available on the downloads page. Just extract and run DvrConvert.exe. Let me know if you want the source.

I’ve only tested with D-ViewCam 2.03 (available here) which is listed to work with the following cameras:


Setting up an internal web site for mControl

October 16, 2008 13:10 by docbliny 

Embedded Automation's mControl for WHS currently installs an unsecured application under the Default Website in WHS. My recommendation is to immediately make sure that you've turned on requiring authentication for the mControl virtual folder. However, turning on authentication makes it harder to access the web version of mControl from within your local network, such as from an iPhone or UMPC. The solution is to create a second web site under IIS on the Windows Home Server.