Originally Posted by caesar1
Any clue as to why I couldn't do HDMI update, but I could do main firmware update?
Hey all, just caught back up on the thread since my last post in September.
Someone else has PM'd me about the HDMI update as well. I'm not sure yet why it is more picky... but I'm thinking it's the ocx file coupled with the 64bit os.
I did my HDMI update in September, used a usb-to-serial adapter, on a laptop with XP (32 bit). Went just fine.
So the likely sticking points for the HDMI update are
1) 64bit os and the ocx file being registered properly. And also possibly:
2) the 64bit compatibility of the usb-to-serial adapter. Make sure it has 64 bit drivers before buying.
So the work arounds would be to either try again using a 32bit os, or try registering the ocx in syswow64 manually.
The file is a 32bit ocx, so copy it to c:\\Windows\\syswow64, then Right-click it or double click it. You will likely get a dialog box:
"You are attempting to open a file of type 'ActiveX Control' (.ocx)
..." with an "Open With..." button. Click the Open With button.
The next dialog is:
"Windows cannot open this file:
... What do you want to do?"
"Select a program from a list of installed programs"
On the bottom of the next window, UNCHECK the box "Always use this program to open this kind of file", then click "Browse..."
Now this is where someone might go wrong, there are 2 versions of regsvr32.exe on a 64bit os. A 32bit version (In C:\\Windows\\SysWOW64) and a 64bit version (In C:\\Windows\\System32). yes the names are backwards intuitive. Since we are trying to register a 32bit ocx, lets err on the side of caution and use the 32bit version of regsvr32.exe, which is is C:\\Windows\\syswow64. So browse to that folder, find "regsvr32.exe", then click "Open". You should immediately get a pop-up stating that "mscomm32.ocx was registered successfully" This is why I uncheck the box, which would have made a permanent association. Since its possible that 32bit and 64bit dlls need the seperate versions, I don't want to make a permanent assocation to the 32bit regsvr32 on a 64bit os. Again, just err'ing on the side of caution.
It might not matter, and either version of regsvr32 may work for any dll. But I'm not sure. For more information registering dll's and ocx's, see: http://support.microsoft.com/kb/249873
My unit is all up to date, so you other end users get to iron out all these little details for the HDMI update. It's a relatively new section of the update directions, and I wrote the directions with a 32bit os computer in mind. the OCX is 32bit (from 1998 no less), and my laptop is 32bit XP. We may be able to get it working on a 64 bit os, but I cannot try it or troubleshoot it myself.
Perhaps ceaser1 can try these steps and let us know how it went? Maybe you registered it using the 64bit regsvr32.exe file?
If you make no headway after re-registering the ocx, you might need to find a friend with a 32bit laptop and try it once from there. For me it went very easily and simply, the same as the MAIN fw updates went. But I used Windows XP.