Desktop Shuttle & WiDi, Push2TV3000

riggy77

Honorable
Jul 24, 2013
7
0
10,510
Hello

At the beginning of this year I purchased a Shuttle SZ77R5, a desktop machine with an Intel i7 3770 3.4Ghz Socket 1155 CPU which I bought to take advantage of the WiDi technology.

After doing some research, I eventually got an Intel Centrino Ultimate-N 6300 (a Mini PCIe card with 3 UF.L sockets) from amazon.co.uk along with 2x Internal 3G/4G WWAN / WLAN Wireless Antenna. This allowed me to connect the wires from one of the antenna to sockets 1 and 2, then I connected one of the wires from the other antenna to socket 3. The remaining wire I strapped up inside the case along with any excess wire so that there was no chance of anything shorting out whilst moving the shuttle around. Having tested the wireless I was pleased to find it picked up both the 2.4Ghz and 5Ghz signals from my DGND4000 dual–band router without any problem.

The next step was to wait as the Netgear Push2TV3000 did not arrive in the UK until the end of June. Trying to get it to work was even harder and I soon ended up chatting to several Netgear operators over several hours. For reasons that I wont bore you with now, I ended up sending the PTV3000 back to the outlet I bought it from as I figured there must have been something wrong with it.

Now the replacement has arrived and I still can’t quite get it to work properly. I have wiped the hard disk clean and re-installed Windows 7 Pro 64-Bit. I carefully installed the software in exactly the right order 1. Graphics 2. Wireless adaptor 3. Intel WiDi 4. WiDi Widget (optional). The WiDi software doesn’t generally have a problem finding the PTV3000, (unless it gets confused in which case I just remove the power for about 10 seconds.) When I click connect it then says that it is connecting and both the TV and the monitor flash a blank display as if it were successful but unfortunately the TV display just stays blank (black screen.) Other errors that I have experienced are “HDCP authentication failed” (on TV screen) which I thought I had resolved by buying a HDCP compliant HDMI cable, “RTSP closed by the source” (also on TV screen) – not sure what that means and "One or more of the required Intel ® WiDi audio devices has been disabled or removed. Intel ® WiDi cannot stream without these audio devices. Please enable these audio devices or reinstall Intel ® WiDi." (as shown on the PC monitor.)

I am now convinced that there is no compatibility issue here because of the way it tries to connect. My gut feeling is a configuration problem with the software or possibly the order in which Intel are insisting it is installed in. In fact I'd say the question of an audio configuration problem is where my best bet lies (in my opinion.)

At the moment I am trying to configure the machine to work with a Samsung Smart TV UE32D6530 but previously I have also been trying out an Acer Touchscreen T231H Monitor. Technically it shouldn't work because it isn't a smart TV but it is reacting exactly the same as the TV so causing me to believe that it is also WiDi compatible - if it is then great, but if it isn't then I am going to have to rethink my entire strategy. The only slightly ambiguous part is that the monitor is in the room below my bedroom (where the router is) and receives a near perfect signal. The TV on the other hand is in the living room where there is a large dead spot. Consequently I have plugged in my old DG834G (Version 4) Netgear router in order to broadcast a wireless network, with no internet access, but I presume there is no need for the PTV3000 to require internet access, surely it only needs a wireless network to get it going, right??

Has anybody had any success with solving WiDi problems – especially those with desktop machines? Any suggestions will be gratefully received!!

Thanks for your time.

Rich
 

riggy77

Honorable
Jul 24, 2013
7
0
10,510
Hello

Thank you for reading this thread. It would seem that I am not the only person interested in getting WiDi technology in a desktop machine after all!! There are in fact many people who want to enable this feature as I found out when I posted a similar thread to this one on the Intel Support Community forum which you can read here:

https://communities.intel.com/message/201152#201152


In that thread a user called joe_intel was less than confident about solving my issues. There had been other users who were “testing the water” by posting comments such as “Desktop WiDi” as recently as just a few weeks ago. I don’t know how I missed them – they must’ve been hidden away where I couldn’t spot them. In those cases, joe_intel told them the same as he told me (paraphrased):

The system is custom built, WiDi was not preinstalled, the wireless adapter integration has not be validated or certified. The wireless adapters are meant to be professionally installed by OEM technicians. And finally that the wrong adapters are being used (Intel recommend one from the “For Desktop” range! I did not want one that would have an antenna suspended in mid-air outside of the machine.)

At the bottom of Joe’s comment you will see that his only other solution is to roll back the driver. He directed me to http://communities.intel.com/message/198908#198908 where some people who had got WiDi working went on to describe a blank (black) screen after the graphics driver was updated. They got it working again by rolling the driver back. So I went to the download center and installed the following graphics file (for Desktop machines): Version 15.31.3.64.3071 (9.17.10.3071) for 3rd generation CPU. I wasn’t sure if I would need to reinstall the Wireless PROSet and WiDi software to maintain the order that Intel are requiring but I decided to give it a go anyway. The Acer Touchscreen T231H (not the Samsung Smart TV) started displaying the desktop before the WiDi software finished verifying the adapter!

There is however a problem in that the screen keeps disconnecting itself in much the same way that other users of these forums have described. I am hoping that this temperamental nature is just a teething problem and will go away but I have my doubts. Can anybody point me in the direction of an answer to this next hurdle?

(Maybe this post will help someone else get their equipment working too!)

Many thanks for your time once again.

Rich