Every time I restart magicJack I get the darn upgrade sequence, like it does not KNOW / Remember that it has already upgraded on a previous start of magicJack. What's up with that? Any solution.
I have used the option of not starting using magicJackLoader.exe but on occassion after a startup, I was not able to hear a dial tone or here the remote party. (e.g. the call would go out with know tones audible - the other party would pick up and I could hear them but they could not hear me!). After going back to the standard startup that problem disappeared - but now I have to deal with an upgrade (3-5 minute delay to startup) everytime on restarts.
Jack
Every restart results in "Lucky You - Upgrade"
Moderators: Bill Smith, Pilot
-
stroths
- Dan isn't smart enough to hire me
- Posts: 470
- Joined: Wed Apr 02, 2008 11:45 pm
- Location: Dallas, TX
Two thoughts come to mind on this issue.
1. If you are running MJ on a thin client then make sure you "commit" after any changes or they will be lost after a reboot. If you don't know what a thin client is then you are not running one and ignore this.
2. If you are running MJ as a service or as a different user than currently logged in as? If so, running upgrade will make the upgrade to the current user logged into Windows. In other words, the upgrade files will go to the user's profile who is logged on. When you reboot, it will load the old version from the other user's profile and trigger an upgrade again. If you are running this configuration then make sure you upgrade the correct user.
If neither of these apply, then I am not sure what would cause this off the top of my head.
1. If you are running MJ on a thin client then make sure you "commit" after any changes or they will be lost after a reboot. If you don't know what a thin client is then you are not running one and ignore this.
2. If you are running MJ as a service or as a different user than currently logged in as? If so, running upgrade will make the upgrade to the current user logged into Windows. In other words, the upgrade files will go to the user's profile who is logged on. When you reboot, it will load the old version from the other user's profile and trigger an upgrade again. If you are running this configuration then make sure you upgrade the correct user.
If neither of these apply, then I am not sure what would cause this off the top of my head.
Not the problem.
stroths,
Thanks for the ideas, but neither of those items are my problem. I installed originally and upgrade using my own login. But good information to have - maybe that will help others.
Jack
Thanks for the ideas, but neither of those items are my problem. I installed originally and upgrade using my own login. But good information to have - maybe that will help others.
Jack