Finally tried WMC with Server 2022. All good so far but I can't find a Microsoft WMC remote receiver driver. Anyone got it working with Server?
Never used a WMC remote in my life, so I need to guess. What do you mean for I can't find a drive? You have a question mark in i dev manager, you see it as generic hid or what?
Exclamation mark. eHome Infrared Transceiver. USB\VID_0471&PID_0815&REV_0000 I tried all the drivers I found, but those were quite old. Does anyone have Windows 10 drivers for it?
Well if you tested it in W10 and it works, the ISO of win 10 has it. Edit: I just checked. Yours it's a Philips device, the driver is usbcir, and is from 2006, the driver in Server 22000 seem identical to the one from win 10, albeit is labeled as 20348 So if it works in win10 but not in 2022 could be a missing parent driver or a kernel policy. But before getting crazy is mandatory to understand if it works in win 10, if you havent already tested it just do a quick parallel installation using a native vhdx and see what happens in W10 Alternatively get a cheap MX3 on amzn/ebay, it's plug and play, it works via radio, it can work both as traditional remote, as a mouse driven by a giroscope, and as a small keyboard, it's backlit, it can learn four infrared codes to turn use it seamlessly to control the TV, and I got mine for 11€
It works on Win10/11. I've tried over ten different drivers that have the same VID&PID but no luck. This is strange, when I right click the device in device manager and then pick the driver by specifying the folder it does not even recognize that the driver is for this device. It just says Windows didn't find any drivers. Same with the Microsoft XBOX one USB receiver. Everything else was fine when I manually installed drivers, it just complained that driver might not work, but with these two devices it does not even try.
It's the same driver so don't get crazy trying variations of the same old driver. Probably there is a missing intermediate HID driver in the server room there was people who had a similar problem with a track pad. Try (on W10) to look about the driver details for a clue, maybe there is something more than usbcir (and its coinstaller dll)
@abbodi1406 Great! About the W8 version is the original 9200 + new patches or is it the 9600 version backported? I tried the second option, but no matter what I did I got it working for 30/40 seconds then it closed itself, w/o any error or any clue coming from process explorer. Second question, is it supposed to install also on WES8 ?
@acer-5100 It's totally 9200 files different patching approach, using redirected slc.dll (although i could patch the files themselves instead) what second option? i have no idea, i just tested it briefly on Win8 Enterprise
Ok, thanks! I'll test it when free time allow, and report back. But I'm afraid I have ready to go only x86 machines do you plan to make a x86 version as well?
Woo, very nice! I never took the time to do it, but there was a real demand for a x86 8.8.x package. It's great these folks now have a working solution! Any chance you could share additional details about these changes? Note: it's undoubtedly a false positive, but the x64 .7z archive was flagged as a "Trojan:Script/Wacatac.B!ml" malware by Windows Defender on my test VM.
Those are great news! I haven't had much time to experiment WMC-related stuff lately but I tried a slightly different approach for transcoding: instead of doing it at the Tvheadend level, I wrote a tiny .NET HTTP server that acts as a proxy between the TV source (Tvheadend in my case) and HDHRProxyIPTV. The principle is very simple: each time HDHRProxyIPTV requests a channel, the proxy server retrieves the live stream from the source server, dynamically spawns a ffmpeg instance and returns the transcoded stream to HDHRProxyIPTV. It's as fast as doing it with Tvheadend, but it can be installed as a Windows service on each WMC machine (I experimented this approach because I have a machine connected via PLC with limited bandwidth, so doing the MPEG2 transcoding on the final machine itself is way more efficient).
As always everithing has pros and cons, the VM approach has the big advantage of being something that you can configure once, then reuse forever. I tried even a VMware x86 one that can even run in a old OS like Win 8 x64 concurrently with Hyper-V. You need vmware 12 to do so. Something that is officially possible only starting from 19041.2xx + VMware 15.5.5. In that way the x86 VM runs in binary translation mode, w/o HW assistance (which is seized by Hyper-V) and still perfectly usable. Also the VM approach has the advantage of being usable in multiple boot taking a single GB of space, even if you have 10 OSes relying on it. Obviously the proxy approach is very interesting, please let me/us informed on how it evolve.... ...but if I was a coder I would consider to fork the HdhrProxy source and mod it to do the job in one step, that would be a really elegant solution...
it's just for the decoder licenesing check (don't matter if current SKU already allow them) for ehReplay.dll / Mcx2Filter.dll / mcmde.dll i noticed the previous patch only bypass msmpeg2vdec-MPEG2VideoDecoder, but not msmpeg2adec-DolbyDigitalDecoder for ehtray.exe, previous patch bypass IsMCEAllowedOnThisMachine result, i update it to even suppress IsMCEAllowedOnThisMachine check --- probably superuser64.exe although, WD seems to flag most unsigned exes as Trojan:Script/Wacatac.B!ml
Great! I'm testing right now, the 9200 version on Server 2012 (standard). No luck for now, it installed properly and clearly it tries to start but it crashes instantaneously with the error System.BadImageFormatException. Even ehtray.exe crashes. with a different error. Maybe it's something broken in that specific installation that is old and may have some tweak I don't remember, but everything else seem working OK. (it's not updated, aside .net 4.7.2, and has just the tv and streaming packages added, taken from 2012 essentials)
Is WOW64 feature disabled? check C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.log for unusual errors