Problem connecting to an Access database on x64

April 26, 2009 22:11 by docbliny 

I know I’ve seen the solution to this one somewhere, but if you’re getting the following error on a 64-bit platform, the solution is to set your application to compile as “x86” and not “Any CPU”:

ERROR: 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine.

image


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:

DCS-900
DCS-900W
DCS-G900
DCS-910
DCS-920
DCS-950
DCS-950G
DCS-1110
DCS-2000
DCS-2100
DCS-2100+
DCS-2100G
DCS-2120
DCS-3110
DCS-3220
DCS-3220G
DCS-3410
DCS-3415
DCS-3420
DCS-5220
DCS-5300
DCS-5300G
DCS-5300W
DCS-5610
DCS-6620
DCS-6620G
DCS-6110


Getting mControl build 2.1.3257.3 working on 64-bit Vista

January 16, 2009 18:01 by docbliny 

The current latest beta build of mControl doesn’t work under Vista. I tracked the issue down to the DLLS being compiled for 32-bit, but the main application for “anycpu”.

If you have the .NET Framework SDK, you can create a workaround as follows:

  1. Open an administrative command prompt. The Visual Studio 2008 command prompt is a good candidate, since it has the required paths pointing to "corflags.exe" (It’s in C:\Program Files\Microsoft SDKs\Windows\v6.1\Bin or similar).
  2. Go to the mControl binary folder:
    CD C:\Program Files (x86)\Embedded Automation\mControl\bin
  3. Turn on the 32-bit flag for mControlEditorForm.exe:
    corflags mControlEditorForm.exe /32bit+ /force

UPDATE: This issue has been fixed in build 2.1.3306.3