Author Topic: LATEST VERSION INFO THREAD - DcUpdater - 1.32.01 - May 9, 2017 (Read 263,188 times)

cranioscopical · « **Reply #25 on:** July 11, 2007, 11:55 PM »

Quote

What version of farr are you using?

2.00.126 Thanks for the response. I missed the "FindAndRunRobot.dcupdate" file, it is there.

lanux128 · « **Reply #26 on:** July 12, 2007, 12:44 AM »

mouser, in the version 1.15.02, the exe has been renamed to DcUppdater.exe. is this intentional?

mouser · « **Reply #27 on:** July 12, 2007, 12:48 AM »

yes it was intentional. the reason is quite crazy.

when testing on vista, the updater was freaking out and causing all kinds of UAC alerts.

it turns out (as Taichimaster discovered) that the reason for this was that vista tries to be clever about handling setup/install programs specially with their new account elevation stuff, and when vista was seeing the word update in the program name, this was triggered. so i had to rename to uppdater to avoid this

Tekzel · « **Reply #28 on:** July 12, 2007, 01:45 PM »

Quote from: mouser on July 12, 2007, 12:48 AM

yes it was intentional. the reason is quite crazy.

when testing on vista, the updater was freaking out and causing all kinds of UAC alerts.

it turns out (as Taichimaster discovered) that the reason for this was that vista tries to be clever about handling setup/install programs specially with their new account elevation stuff, and when vista was seeing the word update in the program name, this was triggered. so i had to rename to uppdater to avoid this

Well, I think we should come up with a completely new name then. I wouldn't want people to see that and think you are a horrible speller. And, you know they will.

Edit: I saw someone refer to it as "DCU" in another thread, how about retaining the name DCUpdater and just change the exe to dcu.exe?

tinjaw · « **Reply #29 on:** July 12, 2007, 03:52 PM »

DC Appdater - the application updater

cranioscopical · « **Reply #30 on:** July 14, 2007, 05:58 AM »

Mouser, here's a small thing to consider.

Using DC Updater (1.16.01) with my system heavily burdened by other online tasks:

DC Updater found several updates, including itself.
It takes a long time to grab the updates (due to other system activity here).
DC Updater updates itself first, creating the need to restart other update downloads.

Should Updater hold off on updating itself until its tasks are finished?

mouser · « **Reply #31 on:** July 14, 2007, 06:03 AM »

Quote

Should Updater hold off on updating itself until its tasks are finished?

this came up today in another thread (http://www.donationcoder.com/forum/index.php?topic=9206.0)
and the answer is yes, it's on my todo list, definitely is needed

Tekzel · « **Reply #32 on:** July 16, 2007, 04:49 PM »

Quote from: mouser on July 14, 2007, 06:03 AM

Quote
Should Updater hold off on updating itself until its tasks are finished?
this came up today in another thread (http://www.donationcoder.com/forum/index.php?topic=9206.0)
and the answer is yes, it's on my todo list, definitely is needed

Actually, I think it should go the other way. If DCUpdater sees that there are several updates, including itself, I think it should hold all other updates until IT is updated. That just seems more logical to me.

tinjaw · « **Reply #33 on:** July 16, 2007, 04:54 PM »

I agree with DcUpdater updating itself first. This way, if the new update has any new functionality, it can be utilized immediately. For example, there may be a bug in DcUpdater that prevents some other app from updating. That bug could be fixed in the newly available version of DcUpdater.

steeladept · « **Reply #34 on:** July 18, 2007, 08:59 PM »

Mouser - While waiting for the http: proxy, I need to download the software manually, but on the download page it is still the June 30th release, version 1.12.05. Will you be updating this too soon?

Thanks

mouser · « **Reply #35 on:** July 18, 2007, 09:23 PM »

yes i will at the end of the month when FARR 2 goes public.
from the updater if you drag up the bottom of the panel, youll be able to see the download url.

Deozaan · « **Reply #36 on:** July 18, 2007, 11:42 PM »

Quote from: tinjaw on July 12, 2007, 03:52 PM

DC Appdater - the application updater

I second the vote for program to be renamed the Appdater! the Uppdater looks retarded and it broke it's own start menu shortcuts when it changed to that name. Ha!

cranioscopical · « **Reply #37 on:** July 19, 2007, 02:48 AM »

Just ran 1.17.01 and it's lost all entries other than itself.
Tried dragging the FARR folder onto it but it doesn't arrive on the updates tab.
(XP SP2)

wreckedcarzz · « **Reply #38 on:** July 20, 2007, 07:52 AM »

I just found this via a search, can't believe I hadn't seen this yet. Seems to work well (even on Vista)- can't wait for all DC programs to be supported

Edit: I don't use Vista's User Annoyance Creator, though

superboyac · « **Reply #39 on:** July 23, 2007, 08:30 PM »

I just tried this program, great idea! But I don't have any .dcupdate files except for the program itself. Not even for FARR. Where can I get these files, or how else can I include them in the list?

mouser · « **Reply #40 on:** July 23, 2007, 08:35 PM »

superboy, when you install the newer versions of FARR, the dcupdater will have entries for it. Also when you launch the updater from FARR itself.

other DC apps are not built with support for the updater yet, that will come starting in august.

superboyac · « **Reply #41 on:** July 23, 2007, 08:55 PM »

Quote from: mouser on July 23, 2007, 08:35 PM

superboy, when you install the newer versions of FARR, the dcupdater will have entries for it. Also when you launch the updater from FARR itself.

other DC apps are not built with support for the updater yet, that will come starting in august.

Ah! Very cool! Works like a charm. You know, there was a pretty cool plugin for Total COmmander that I almost used diligently that would check for updates for software. but it was more like website-watcher than a true update checker, because you would point it to the text on the website that indicated the version number, and when it changed, it would notify you. Not quite as slick as this.

Tekzel · « **Reply #42 on:** July 24, 2007, 02:10 PM »

Heeeey Mouser. Just something I was wondering, and you may have addressed in the PAD file discussion. But, I will ask it anyway as I like being redundant. Will we be able to add an entry to point to a 3rd party program's PAD file entry, hopefully put in an update frequency individually (maybe have a "default" frequency that is used if not specified otherwise) and have it check for programs with no .dcupdate file? Or we can use one of the existing .dcupdate files and make our own for a program we use frequently that isn't from DC.

mouser · « **Reply #43 on:** July 24, 2007, 07:13 PM »

Quote

Will we be able to add an entry to point to a 3rd party program's PAD file entry, hopefully put in an update frequency individually (maybe have a "default" frequency that is used if not specified otherwise) and have it check for programs with no .dcupdate file?

The basic idea is this:
The .dcupdate file is a local file, it tells dcupdater what file on the web to check for version info, how to install a new version, and miscelaneous information about the program.

In the ideal case of a dcupdate-supported program, the author of the program does the following:

Creates a .dcupdate file in the program's directory, which is installed with the program and always specifies the current installed version of the program.
Creates a version.xml file which is a tiny file placed on the server which only holds version # of the program. This is the file normally checked by the dcupdater, and the fact that its so small is good because it minimies bandwidth when thousands of people are constantly checking it every day.

To support a program that is not "made for dcupdater", then dcupdater will have to do something like this:

Let the user ask to create a new entry, which will result in a new .dcupdate file being created on their pc (or they can download a dcupdate file from a friend or forum). If the user has the url of a pad file, nearly all information dcupdater needs to make a new dcupdate file can be found in the pad file.
This dcupdate file will describe the program and where the PAD FILE of the program is located (or it might even have a regular expression designed to parse version number from a program web page). The point is the dcupdate file will have instructions on how to figure out the current web version of the program. Dcupdater will be able to parse a pad file to get the web version and download url and webpage, etc, so a pad file is ideal for this. But I may add code that minimizes bandwidth by checking http headers, etc.
The dcupdate file will also contain information on how to locate the locally installed version of the program. Since the program isnt made for dcupdate, it won't have a dcupdate file in its directory which is kept up to date. So dcupdater will have to get the version # from the exe file, OR by having dcupdater manually update it on install of new version.

Tekzel · « **Reply #44 on:** July 25, 2007, 06:45 PM »

It sounds like you have really thought this thing out! The hardest part will be supporting non-dcupdate programs, but your scheme sounds like it would work. I think for situations where you are checking PAD files for version info, it might be a good idea to make it so it will only check those once per day at the most frequent. You really don't need to check more frequently than that anyway. There are a number of very important programs for me that I would like to use DCUpdater to keep an eye on for me. I could approach the authors about including DCUpdate support since it would ridiculously easy to do, but would like an alternate way to do it if they wont or cant for some reason.

mouser · « **Reply #45 on:** July 31, 2007, 04:50 AM »

I've uploaded a new version (1.18.01) but im not going to upload the file that would make everyone's updater update itself, since i expect to have to release minor fixes in the next day or so.

This new version has major changes to the look and feel, but i haven't added any pad file stuff yet. You will notice however that there is a new tab for programs not yet installed but available for installation.

[attachthumb]

Tekzel · « **Reply #46 on:** July 31, 2007, 02:28 PM »

Hey mouser, looking sharp! Couple of issues to report, and a possible bug.

Issue#1 - Using Vista, the prefs dialog is too big for the frame so it puts in scroll bars. Image attached.

Spoiler (click to show/hide)

[attach]

mouser · « **Reply #47 on:** July 31, 2007, 02:37 PM »

all good ideas and bugs, thank you.. will be working on them, especially the couple of show stoppers.
treeview for plugins is a good idea.

mouser · « **Reply #48 on:** August 05, 2007, 11:25 AM »

Ok major new version released..

The big work here under the hood (and above the hood as well), is lots of support for installing new packages, not just updating existing packages.

For example, one idea is that you should now be able to download a plugin .zip file and drag+drop it onto the dcupdater window, which will report about its contents and know where to install it and install it (or check web for update).

You could do the same with simply a plain .dcupdate file which is not yet installed.

--

This new system will be used with FARR 2 release, which will no longer come with all plugins pre-installed. Instead, the updater for FARR will know about the available plugins, and you will be able to quickly install any plugin you want simply by choosing it in the updater.

mouser · « **Reply #49 on:** August 05, 2007, 11:49 AM »

Another feature added is more support for manual stuff. You can now right click and tell the updater to just download the new file for you.

[attachthumb]