- Easyworship 6 keeps crashing pro#
- Easyworship 6 keeps crashing software#
- Easyworship 6 keeps crashing mac#
I'm happy to try to help out, especially since i'm new here. There could be a bug in the web interface (and I'm sure EW would love to find it and fix it), but the rest of your post doesn't help anyone help you (or them) get to the actual solution.
Easyworship 6 keeps crashing software#
You seem to have made quite a few yourself about the cause of the negative experience you're having, going to the extent of criticizing the design of the software before you really have much solid info about your problem. Have you tried to access the easyworship site from this same machine outside of EW 6? Did you have any SSL issues? I don't believe the web request would stay live for 20 minutes so you may have something else going on.Īlso, you mention assumptions in your original post. Is your church using any Big Brother-type monitoring software? Sometimes they act as a man-in-the-middle and screw things up. If that's the case, your IE engine is making a request for the site and not liking what it's receiving. You can hide IE's shortcuts, but if you truly try to remove the software from your computer, you've gone to some serious effort (that would destabilize other parts of Windows) to remove something you can simply choose not to use.Īdditionally, your first post suggests that you're having difficulty reconciling the SSL cert, which is more likely your problem. I think that Terry is trying to let you know that if you alter your operating system at that level, no software, including EW 6, that uses a web-view-type control will work in Windows.
Easyworship 6 keeps crashing mac#
As far as software goes, the standard method of using embedded web controls in Windows and on Mac both use the native browser engine, which is IE's and Safari's respectively. EW6.2.1 does work on it on all seven monitors and projector including powerpoint and videos on foldback but I didn't test the web interface on it.Īre you sure you've uninstalled IE? Choosing a default browser such as Chrome or Firefox is not equal to removing/uninstalling Internet Explorer.
Easyworship 6 keeps crashing pro#
Our church PC which at the moment we are still using EW2009 until we think EW6 is working well enough to go live is an Intel i5 2.8GB with 8GB Ram and Sapphire HD 5770 GPU running Windows 7 Pro SP1. Don't have any problems with any other software on any of the attached PCs. PC is connected to a network via cat5 cable directly via a Netgear Gigabit Switch then cat5 to Fibre Modem which all works perfectly. As I said in the previous message we don't have Internet Explorer installed but use Mozilla Firefox which is at 38.0.1 at the moment. PC is only used for EW6 testing and hopefully schedules once we can transfer them to our church PC which will hopefully be soon. I'm running EW6.2.1 on Windows 7 Ultimate SP1 64-bit OS, CPU Intel Core2Quad 2.4GB with 4GB Ram and NVidia GT630 GPU on my Home PC where I've noticed the issue. Any software that uses the web has to be compatible with other vendors but I suspect that isn't the case here as we use Mozilla Firefox as I'm sure millions of others do too. We don't all use MS Internet Explorer or Media Player or iTunes or indeed have Quicktime installed on our systems and we, ourselves have ran EasyWorship since the early days of EW2007 with no problems. I think a lot of assumption has gone into the designing of EW6. I was only trying to view Support from within EW6 but have had to give up as it keeps freezing similarly with each button pressed. It has finally come up after about 20 minutes with MSN / Bing Search Engine and a message with a Security Alert saying 'The Name of the Security Certificate is Invalid or Does Not Match the Name of the Site.' Proceed Yes or No or View Certificate. It does this on any tab or button that I select. Then when I clicked on Media tab again it froze out with the same results and long wait. I think there is a bug with the web interface in that it took over 10 minutes for the busy icon to disappear and the (Not Responding) at the top also took the same time as well.
0 kommentar(er)
