Quantcast
Channel: Intel Communities: Message List
Viewing all articles
Browse latest Browse all 20046

Intel WiDi on Desktop PC with Multiple Monitors on Windows 8.1 update 1

$
0
0

Hello all,

 

I've been looking to sort out an issue I've been tracking for some time and thought I'd create my own thread since it appears to be a non-standard setup compared to what others have described. I have a custom-built desktop equipped with an Intel Core i7-3770 CPU, Intel AC 7260 Dual-band wireless PCI-E card + Bluetooth, Intel HD Graphics 4000 built into the motherboard which is an Asrock Z68 Extreme3 Gen3, and an NVIDIA GeForce GTX 660 discrete graphics card for gaming. I have two 22 in. Dell monitors attached via DVI to the NVIDIA card running 1920x1080 resolutions and a third of the same size and resolutuion via HDMI to the integrated graphics on the motherboard. The three monitors work together with no issues, but in the same room where the setup is located I have a 40 inch Samsung TV. It sits a good 15 feet from my setup across a den and I'd like to use it as a 4th display for media or displaying other content to a wider viewing area.

 

Unfortunately the layout of the room does not make running an HDMI cable from the NVIDIA card a feasible option, so I attached a Netgear P2TV3000 with the latest firmware to the TV and added the AC7260 to my system to run it as a wireless display on demand. For whatever reason, Windows 8.1 with the latest update installed does not give me the option to add a wireless display under the project menu within Charms (Win+P). Any changes I make there (Duplicate, Extend, etc) only impacts my main three monitors and the "Add Wireless Display" option is no where to be found. Interestingly, I can go into the traditional Devices and Printers screen within the legacy control panel and add the P2TV there; it comes up when I go to Add Device and lets me pair with the code provided on the TV display, so I know they can communicate. That's as far as I can get though as once added as a device the P2TV goes grey after a minute as though it's offline even though everything is up. It's like they just decide to stop communicating for no apparent reason.

 

I am wondering if there is a buffer restriction for the amount of pixels this would create. It doesn't seem impossible a separate, discrete display profile could not exist for this wireless setup that does not take the other three monitors into account. The WiDi update utility also renders any legacy software meant for Windows 7 inert I try to install, so I am unable to use it as an option. At one point I did actually have it working before additional updates to the software, driver, Windows, or some combination broke my ability to use the legacy WiDi utility. If that restriction was lifted so it would work with Windows 8.1 I believe this would alleviate a lot of headaches expressed on this forum, as the TV would just show up as a 4th monitor I could drag windows over to. Another viable option would be the ability to mirror a monitor of my choosing over to the P2TV as well so I still just have three displays, but with one of the three mirrored.

 

I'm able to work around this failure with a Chromecast and apps like Plex for accessing my media on the desktop, but it would be nice to have the additional capability and be able to use the card for the reason I purchased it beyond traditional wireless networking. Another goal I have, latency permitting is the ability to use the wireless display with my PC so I can have it as a wireless streaming Steambox of sorts (imagining running Steam in big picture mode with the TV as a 4th display or mirrored from one of the others.

 

Thanks for any assistance or feedback anyone can provide regarding this setup. I would consider confirmation that my setup is not compatible sufficient, though I did do my research and ensured all my components were certified and compatible before making the purchases.


Viewing all articles
Browse latest Browse all 20046

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>