Posted on Fri, February 19th, 2010 in HDX 1000, Tips 'n Tricks - Michiel -
1 comment »
One of the nastiest things about upgrading your OS is probably driver support. A videocard or other device that you’ve gotten so used to, that you can’t get to work when updating your OS. This same problem is here when upgrading to Windows 7 when connecting the HDX-1000 to your PC using the USB slave cable.
Fortunately there is a fix. The obvious driver install doesn’t seem to work, but Windows 7 has a thing called Compatibility Mode, even for installation of drivers. First thing you need to do is read through this list. It explains how to connect to your HDX-1000/Popcorn Hour A-110 using the USB slave cable and installing the driver. If you, like me, are on Windows 7 and are having trouble installing the driver, read on.
To install the driver, save the file (download it here) to some location where you can easily find it. I’ve used my desktop. See the screenshots below.

Right click the file and select "Troubleshoot compatibility".

In the popup window that appears, select "Troubleshoot program".

Now, the next step is very important. Since the drivers are said to work on Windows Vista but not on Windows 7, select the top most option, "The program worked in earlier versions of Windows but won't install or run now".

Since the driver works with Windows Vista, select the latest version of Windows Vista in the list, "Windows Vista (Service Pack 2)".

Final step: click "Start the program...". Done!
I hope this tutorial has been helpful to you. Anyway, please feel free to leave a comment with your thoughts. And remember, if you’ve completed the steps above to install the driver, continue on with the great tutorial on NetworkedMediaTank.com.
Thanks and good luck!
Posted on Fri, February 19th, 2010 in ColdFusion, Flex, MySQL, Work, jQuery - Michiel -
No comments »
Yesterday was quite a joyful day. Jilster, a project we’ve been working on for the past months, was officially launched. Jilster is an online tool with which you can create your very own magazine and was built using Adobe’s ColdFusion and Flex, running on a MySQL database.
Curious? Check www.jilster.nl (it’s all Dutch).

Cake to celebrate, always a pleasure!
Posted on Thu, February 4th, 2010 in Tips 'n Tricks - Michiel -
2 comments »
If you’re experiencing a weird red line through your screen in Windows Media Player on Windows 7, it can be quite a struggle to find the solution. Believe it or not, the problem lies within the latest ATI Catalyst Control Center (CCC). To fix it, follow these easy steps:

Step 1: Open the Catalyst Control Center, click on "Graphics" and go to "Avivo Video".

Step 2: Click on "All Settings".

Step 3: Scroll all the way down to "Video Demo Mode" and uncheck "Enable Demo Mode". Then press "OK".
If you’re done with the above steps, your problem should be fixed!
Posted on Fri, January 15th, 2010 in Webdevelopment, jQuery - Michiel -
1 comment »
The long awaited jQuery 1.4 has been released. The jQuery team chose a special day for this event because the number 14 is very special: January 14th is the birthdate of jQuery.
Version 1.4 contains some very promising and long awaited features. For a full list of these features, check jQuery’s special website dedicated to the release of jQuery 1.4: The 14 Days of jQuery.
Posted on Thu, January 7th, 2010 in Flex - Michiel -
No comments »
If you are having problems getting a new SDK installation to work with Flex Builder 3 (e.g. if you’re trying to compile a Flex project as AIR application using Flash Player 10) and get the following error:
Process terminated without establishing connection to debugger.
Command:
“C:\Program Files (x86)\Adobe\Flex Builder 3\sdks\3.5\bin\adl.exe” “projectPath” “bin-debug location“
Output from command:
error while loading initial content
Process terminated without establishing connection to debugger.
Command:
“C:\Program Files (x86)\Adobe\Flex Builder 3\sdks\3.5\bin\adl.exe” “projectPath” “bin-debug location”
Output from command:
error while loading initial content
here is the solution, thanks to Jim Hayes.
In your project, there’s a file called <yourApplicationName>-app.xml. Open it and change the following:
<?xml version="1.0" encoding="UTF-8"?>
<application xmlns="http://ns.adobe.com/air/application/x.x">
to:
<?xml version="1.0" encoding="UTF-8"?>
<application xmlns="http://ns.adobe.com/air/application/1.5">
That should solve your problem.