davilla Wrote:It's an .exe install that checks for an installed card before completing the install. Grrr. I just hate these types. ... If anyone running under windows can do this, I'd be interested in the firmware md5 checksum.
MD5 of bcmFilePlayFw.bin Version: 2.60.34.0 is:
358334f95b44079cb8492d30b36c261c
FYI, when you run an EXE or MSI installer, it usually extracts the contents to "Local Settings\Temp\"
This one put
another msi installer in that folder, so I had to copy the contents to my own folder, c:\broadcomdriver, before closing the installer.
I then used the command
Code:
msiexec /a "Broadcom CrystalHD Decoder.msi" /qb TARGETDIR=c:\BroadcomMSIContents
I don't have the card yet, but I think this worked fine.
This left me with a folder with a whole lot of stuff in it, but most importantly, in the
Code:
c:\BroadcomMSIContents\program files\Broadcom\Broadcom CrystalHD Decoder
folder, I have the following:
(all dated 8/14/2009)
Code:
# Broadcom WDM Driver for 7001X series Controller. (Version:2.36.0.0)
## brcmhd32.inf
## brcmhd32.sys
## brcmhd32.cat
# Driver Interface Library (bcmDIL.dll) - (Version:2.37.0)
# DirectShow Filter (bcmDFilter_ns.dll) - (Version:2.57.0)
# Firmware file (bcmFilePlayFw.bin) - (Version: 2.60.34.0)
... so there is a DirectShow filter
What does that mean for tiben20's
DS branch? If we use his DSPlayer with that filter, do we need to compile the CrystalHD branch at all on Windows?
-Wes
PS. now if I could just do that type of stuff in Linux, I would be much more useful