Member
On Sunday at home the meetinghouse communicator software worked fine.
I even did a test broadcast using still slides.
However when it came to the real event tonight I had problems.
Due to a hardware failure for the hardware meetinghouse communicator it had to go back.
So I took my windows 7 desktop which has the beta 3.0 version installed and attempted to connect it wirelessly.
When I started up the meetinghouse communicator software I got a message dialog box from windows that there was a problem with the programme and it would have to close and seek a solution.
I tried uninstalling and reinstalling.
After a reinstall i even got the message that it needed windows media encoder 9, which I had already installed.
Btw the message you get when you attempt to start the meetinghouse comm software beta 3.0 on start up "you need to install windows media encoder 9" click yes to install takes you to a defunct page.
However I had already installed encoder 9 and it still asked for it!
However again even when I had the programme installed normally windows still said there was a problem with the programme.
I wonder if it is because I attempted to connect using wireless?
I will try when I get home this morning (UK time) and if it works with the lan cable I will buy 50 metres of it and try it in the building.
Another thought is could it be the cisco firewall?
I even tried deleting the comm software of the registry, which I was a bit worried about, but that made no difference.
I think it is wrong that global services don't support official church software!
Worst of all I had two Area Seventies and a host of Stake presidents due to watch the broadcast.
I couldn't help the hardware failure, but the software failure nearly had me in tears!
Any suggestions and help would be much appreciated.
I even did a test broadcast using still slides.
However when it came to the real event tonight I had problems.
Due to a hardware failure for the hardware meetinghouse communicator it had to go back.
So I took my windows 7 desktop which has the beta 3.0 version installed and attempted to connect it wirelessly.
When I started up the meetinghouse communicator software I got a message dialog box from windows that there was a problem with the programme and it would have to close and seek a solution.
I tried uninstalling and reinstalling.
After a reinstall i even got the message that it needed windows media encoder 9, which I had already installed.
Btw the message you get when you attempt to start the meetinghouse comm software beta 3.0 on start up "you need to install windows media encoder 9" click yes to install takes you to a defunct page.
However I had already installed encoder 9 and it still asked for it!
However again even when I had the programme installed normally windows still said there was a problem with the programme.
I wonder if it is because I attempted to connect using wireless?
I will try when I get home this morning (UK time) and if it works with the lan cable I will buy 50 metres of it and try it in the building.
Another thought is could it be the cisco firewall?
I even tried deleting the comm software of the registry, which I was a bit worried about, but that made no difference.
I think it is wrong that global services don't support official church software!
Worst of all I had two Area Seventies and a host of Stake presidents due to watch the broadcast.
I couldn't help the hardware failure, but the software failure nearly had me in tears!
Any suggestions and help would be much appreciated.
