Marcs Updater
There have been some reports about issues with the Updater not updating anymore. Please try the latest beta version and switch to another IP Check provider instead of the previous default dnsomatic.com. For some reason they are rate-limiting the number of requests to their service. The new IP Check provider selection allows you to choose another provider in such cases. You can test the functionality with the new "Test" panel.
If you want to add a custom provider to the unstable testing version, store a JSON file like the following under %PROGRAMDATA%\Marcs Updater\ServiceProviders\dyndns.json:
{
"name": "DynDNS.org (Test)",
"endpoint": "https://members.dyndns.org/nic/update",
"method": "GET",
"queryString": "hostname={HOSTNAME}&myip={MYIP}",
"dataPayload": "",
"defaults": {
"username": "test",
"password": "test",
"hostname": "test1.customtest.dyndns.org"
}
}Supported query and payload tags are {USERNAME}, {PASSWORD}, {HOSTNAME} and {MYIP}. Restart the background service and foreground application to apply any changes.
Discussion created on
Posted on
Marc wrote:
Released version 1.5.2.294
- Fixed stack corruption in network state detection
I finally found the reason for the service crashing in rare cases during network state changes. I was investigating this bug since months and would like to ask you to update as soon as possible and test the new version.
Thanks and sorry for the trouble!
1
Posted on
tayiper wrote:
Though I haven't yet seen the service *crashing* (as in process closing etc.), I do/did have experiences (must yet see with the latest a few minutes ago installed version 1.5.2.294) with service behaving erratically, but not in a way of crashing the "usual way", but so that it was becoming "dead", meaning that Stop and Pause buttons became unclickable (see example in the screenshot below from Process Explorer for "services.exe", which is designed that way though) and the only way to shut it down was to kill the process.
The strangest thing was that this (service in that "crippled" state) also seemed to somehow affect my ability to be able to connect to Internet; until the service process was not closed and started again (by GUI process for instance), I was not able to connector in other words, the Vodafone Mobile Broadband program that I use (it comes together with 3G USB modem) was not working properly.
Posted on
tayiper wrote:
Ups sorry all, I forgot to add that screenshot of Properties - Services tab of for "services.exe" process in Sysinternals Process Explorer (actually, there's two separate services "running in it", Event Log and Plug and Play, and both cannot be stopped or paused) where you can see how it looked like in "Marcs Updater.exe" service's case. While also I need to mention that I have so many problems with the mentioned Vodafone program (or USB modem, or my ISP's 3G network itself, or...) that I didn't even consider this as a major problem since this one was always solved instantly (just just need to kill one processs), compare to other problems that I experience from time to time (some more, some less often) with Vodafone software and/or Huawei USB Modem.
Best regards, Tadej from Slovenia
Posted on
Marc wrote:
This could also be related to the fixed issue. Stack corruptions can cause all kinds of trouble and since the service is multi-threaded, everything is possible once the stack or heap is corrupt.
1