Well that was something that worked in the DOS days, and that works even better since the Vista release, because the new way windows is actually upgraded. Once the old files were overwritten. Now a new whole installation is made in a different folder, and the old documents and settings are imported at the end of the install process
Yes, I am using the Shared Ceton feature from my Ceton PCIe tuner on Windows 7. I am using 8.1 drivers on Windows 10 with out problems. I share them on my Window 7 base HTPC, and my Office machine uses WIndows 10 pro, that I use WMC on to watch tv, etc using the shared tuner over the network. From the early versions of WMC 10, I have been using 8.1 drivers with no issues.
5 RDP Sessions in Actual Multiple Monitors... Dual Monitor Setup So I have 5 RDP Sessions with 5 different instances of WMC running. I am connecting to Win10/WMCv12 using Microsoft Remote Desktop Connection (RDC). Also using Actual Multiple Monitors (AMM), the MDL RDP Patch, and RdpWrapper. I am able to snap WMC to a full screen monitor. So far, I have been unable to snap WMC into any of the 4 small windows on the left. What I would like to end up with is 4 mini versions and one full version. The question is....How do I get rid of the scroll bars on the 4 screens to the left?
Ok. I tested it briefly. With just one local and one remote session. I tried with the chrome enabled and, while the local one will fit exactly in one of the squares, the remote one does not. If you think... it's easy to understand why: the remote app (and its window) is managed by the remote machine while AMM is installed locally, so has no effect on the Remote APP window. Likely I should configure AMM on the remote machine, and assuming the remote monitor is sized the same as the local one, possibly it will work. That using a windows with the full border. In chromeless mode I doubt would be possible to center exactly the widows unless using some precooked registry files. Alternatively you may want to try editing the *.rdp file with the notepad, setting the remote resolution sized exactly as one local free rectangle, that may work, because the remote desktop client is actually a local program, unlike a remote app. Hence iit should follow the rules of the local windows manager.
BIG THANK YOU TO ALL THOSE THAT MADE MCE POSSIBLE IN WIN10 I was apprehensive about switching from Win7 on my 5 year old HTPC with a Ceton InfiniTV tuner, but Win7 was running like crapola lately, and I decided to take the plunge. I ran the Win10 upgrade so my HTPC gets free Win10 registration, then did a clean install. I downloaded the MCE package (v12) linked in the first post of this thread, and followed the instructions. The installation was as easy as if it was run in Win7 itself. The one problem I had, was not realizing there were Win8.1 drivers available for the Ceton Infini Tuner, and I installed the Win7 drivers. Windows MCE installed fine with the Ceton Win7 drivers, but when I put MCE in window mode, it flickered to the point it went to a blank screen leaving me to task kill MCE and restart. I then found out about the 8.1 Ceton drivers, and uninstalled the Win7 drivers, ran CC Cleaners registry clean, rebooted, and installed the 8.1 driver. Now MCE works perfect in window mode. I also bought a new copy of MyChannelsLogo XL, which works well in Win10. My original copy of MyChannelsLogo was version 2, which kept crashing in Win10. I can't give an in-depth examination of MCE on Win 10, since I basically only use it for recorded and live TV, but so far, it's been stellar. I can't believe MCE has been discontinued since 2009, and still there's absolutely ZERO viable alternatives. That's either a testament to how well written MCE was, or creating such an application is a behemoth of an undertaking. MCE still has fantastic features to this day, but it's showing its age. One thing MCE DESPERATELY needs, is an option whereby if you tune to an SD channel, it can automatically go to it's HD channel if available. Modern cable DVR's offer this option, and it would save from having two sets of channels in my favorites menu, one SD and one HD. Thanks again to all that made this possible!
GuideTool Zap the SD channels I use GuideTool and uncheck all the SD's Search GuideTool in the Search Thread window. 12 Hits. Net 2.5 may or may not not be necessary.
Still trying to get my 360 extender going. Upgraded a fully working 8.1 system. Followed meluvalli's steps, pretty sure I got them all correct. Still craps out on "Searching for your extender". Then I get "Configuration error". Could it be my Windows build version? I am on 10586.420. Or, could it be an installed Windows Update? [01]: KB3135173 [02]: KB3136561 [03]: KB3142588 [04]: KB3149135 [05]: KB3167685 [06]: KB3163018
after upgrading to v12, im getting smartscreen errors at boot on application ehtray. error states an issue connecting to te smartscreen server. any ideas how to fix this?
What errors do you get (related to extender) in Event Viewer/Applications and Services Logs/Media Center Check out post 4257 for GarethNorths Version ImCokeMan has had some success too.
I've seen problems like this in the past, turned out it was bad ram in the machine, it didn't corrupt uncompressed files but if you tried to decompress a file the result was almost always corruption.
Sure. The bad RAM is an obvious way to corrupt a file. Those cases were pretty common once. Now are rarer but definitely possible.
Just look at it a on a 1440 x 900 display those values to get the full screen covered would be the 0,0,1440,900 (in decimal, obviously), sometimes 0 won't work for the origins, just try 1
I've not been able to get DRM working despite following these directions. Using wmc12.7 and followed the directions to the tee. Have an hdhomerun prime. The other strange behavior I get it when I first launch WMC and go to live tv, it won't play, tosses an error about monitor support for hdcp. I have to minimize WMC and then expand it again and it works. Been spending way too much time troubleshooting to no avail. Help is so greatly appreciated.