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.
Issue created on
Posted on
tadej wrote:
Hey Marc, I see that I (tadej from OpenDNS Forums) am the first poster here...
I am just reporting that today when I launched Marc's Updater I got a notice that a new version is available and it was downloaded "internally" (by some "update.exe" process launched in the TEMP directory, I assume started by "Marcs Updater.exe") and then on installation of this new version I the following error windows popped-up:
/EDIT: Oh and yes, here is all the code from this window:
Invalid memory access Code = -1073741819 Line = 277 File = Network.pbi OSV = 0x3C EIP = 0xFFFFFFFFDCDC43D0 ETP = 0xFFFFFFFFDCDC43D0 EAX = 0x14C0048 EBX = 0x0 ECX = 0x77F58EC1 EDX = 0x0 EBP = 0xFFFFFFFFDEDE43D0 ESI = 0x0 EDI = 0x0 ESP = 0x12BFFA4
And the same happened when I downloaded the "Marcs Updater.exe" installer from this link here on this forum.
Best regards, Tadej
Posted on
Marc wrote:
Hello, thanks for your report.
Please try build 203 and if that does not solve the problem, post more details about your internet connection at the time of crash, operating system, etc.
Posted on
tadej wrote:
Hello, thanks for your report.
Please try build 203 and if that does not solve the problem, post more details about your internet connection at the time of crash, operating system, etc.
Yeah, unfortunately it happens with build 203 too. Although this time (well this might've been the same before, but I just might haven't notice it) not during the installation but only after it (with procedure finished and service already being started/running for a few secs. in the background) when the system tray process is started.
I also "visually" checked the service (in Process Explorer and in DNSKong's logs) and it appears to be running just OK and doing it's thing. So this error-windows pops-up only when GUI (or more precisely tray process) is started.
And just as by the way; I noticed that the difference between builds 1.5.0.201 and 1.5.0.202/1.5.0.203 is that the latter ones ask for OpenDNS username and password during the installation procedure, while version 1.5.0.201 doesn't.
Anyway, I am just happily using version 1.5.0.201 (btw. what are the changes in latter two builds?? Are they major or only minor ones??) and am content with it.
Thanks for the reply, greetings!!
Posted on
RotBlitz wrote:
Hi Tadej,
I'm having exactly the same problem and have reported it via e-mail to Marc already too. I also went back to build 201 for the time being.
Cheers,
RotBlitz
Posted on
tadej wrote:
Oh and sorry, about the things that you also specifically asked about: the Internet connection was established at the time of crash, my operating system is Windows XP Professional (no Service Pack though), I still have an Internet Explorer 6 installed (an not IE8, I have many reasons for this but I won't go into details; I can explain it some day if you want to, but it's not relevant in this topic), while I use Firefox as my main and more or less only-used browser.
Although I don't know how these things (except from the OS maybe) could have anything to do with it. Of course I am not an expert (i.e. a real programmer etc.), but as I see it it must be something in "Marcs Updater.exe" executable that's causing this, especially since there was no such problem in build 1.5.0.201.
/EDIT:
I'm having exactly the same problem and have reported it via e-mail to Marc already too. I also went back to build 201 for the time being.
Ahhh I see, sorry RotBlitz, you know, I was editing (with Preview feature) my post so long before finally posting it that I missed yours that was posted in bwtween!!
Posted on
Marc wrote:
Ok, the crash happens at the end of the main DnsQuery method, that means that one of the internal string or main memory heaps got somehow screwed up, can you check with Wireshark or another tool what the last DNS query is right before the crash?
I have tested the build on XP, Vista, 7 and 7 64bit and can't reproduce the crash, so it has something to do with both, the new build and the enviroment it is running in. ;)
I have added a digital code signature in build 202, and I have fixed a bug that RotBlitz reported about the GUI closing for no reason in build 203.
Posted on
Marc wrote:
Found the problem, the nameserver array was not big enough to hold the nameserver count and the addresses at the same time.
http://msdn.microsoft.com/en-us/library ... 85%29.aspx
I just allocated memory for the AddrCount, and not for the data itself. Fix is on it's way.
Posted on
tadej wrote:
Found the problem, the nameserver array was not big enough to hold the nameserver count and the addresses at the same time.
http://msdn.microsoft.com/en-us/library ... 85%29.aspx
I just allocated memory for the AddrCount, and not for the data itself. Fix is on it's way.
That's good to hear, thanks Marc!! We are anxiously waiting for the new version/build -- :D ...
Posted on
tadej wrote:
Yeah, build 204 has it fixed, it's pretty stable. Thanks! :P
Just one more (not really related, but I didn't want to open a new thread just to ask this) question.
Is it OK to "trust" the internal updater to update the program (so update it through "There is a new version of Marcs Updater available, do you want to upgrade now?" dialog by clicking YES) or you (i.e. Marc, the program's author) rather recommend to download the installer-file and install it with it??
/EDIT: Well never mind, I just took a "risk" (please don't get me wrong though, I just tend to always do such things in as safest way possible) and installed/updated it through that window that pops-up and everything went OK. Oh and by the way, I managed to "catch" the "update.exe" process's command-line:
"http://dl.getdropbox.com/u/1358237/Updater/x86/Marcs Updater.exe" "C:Program Files\Updater\Marcs Updater.exe"
- ;) - :lol:
Posted on
Marc wrote:
It's ok to update through the internal updater, but the next version will be a major release which will require you to reinstall the application.