35 replies to this topic

[Cristiano]

My friends, i'm proud to announce that reached one major milestone about AutoPatcher Updater: our download mechanism was completely replaced by cURL. This new engine allow us deal with an ancient flaw: the ability to deal with proxies. Yes, we are not joking, APUP has now the ability to deal with proxies, including those that require authentication. Even more, now you have the ability and the control to do an autorun feature: if you wish, apup can remember your script selections and download those script without any question. Also we already said, there's an serious job being done and I believe that yours will like it

As for those that are downloading apup for the first time, the new version can be reached in our downloads page

Again, a lot of thanks to Antony and bigjoe714 for join the Team and do those awaited improvements. If you think that can help too, even with comments, please feel free to do it. Your opinion is important and we need it in order to do an better software.

edit: some screenshots:



[]s

Edited by Cristiano, 04 November 2009 - 10:11 AM.

[click-click]

Thanks for the new release. I mentioned this before, but I find it easier to see what has been updated if the release name entries were sorted by date from the most current update to the oldest. Now that there is a new options tab, maybe sort on date could be added there or even better make all columns sortable.

Sorry I should have posted in http://www.autopatch...ture-requests/U
Please feel free to move this post.

Thanks

Edited by click-click, 04 November 2009 - 10:04 AM.

[Cristiano]

no problem, my friend. the developers will look in here too

[]s

[cymicro]

Dear Christiano, first let me thank u & the other developers for providing this wonderful tool.
I've been using it fairly recently since v1.04 or .05. A few questions, when I ran apup yesterday (v1.06), it d'loaded the latest v1.1, but kept on d'loading the same files over & over again. So, for a major update ( such as this one ), do we have to delete all files & folders in apup, & start from scratch ( which is what I'm doing now ) or can we keep the d'loaded folders (XPSP3 etc) & just overwrite the 2 files & 1 folder from the new release. I really don't want to keep d'loading all the files every time.
Thanks.

[_def_x_]

-> it d'loaded the latest v1.1, but kept on d'loading the same files over & over again.

Yes, this is a bug in v1.1 and will be fixed but for now you should do the following:

Download apup_exe_1006.7z and extract apup.exe (v1.0.0.6), you will want to run apup.exe (v1.0.0.6) instead of apup.exe (v1.1)

Note: To prevent APUP from constantly overwritting v1.0.0.6 with v1.1 you will need to rename v1.0.0.6 - to something like apup_v1006.exe, create a shortcut to v1.0.0.6.

This way APUP will see apup.exe (v1.1) and ignore apup_v1006.exe. The shortcut is so you don't have to constantly go to the folder and find v1006, just launch the
shortcut from wherever you move it to.

If you're unsure about creating the shortcut:

...Look in your AutoPatcher / APUP folder - you should (for now) have 2 apup executables "apup.exe" and "apup_v1006.exe"
...Right-Click on "apup_v1006.exe" and scroll down to Create Shortcut - when you select it a shortcut will appear.
...Right-Click on the new shortcut and scroll down to Properties - the Properties window will appear.
...With the Shortcut tab selected look for Target (this is the path to your file) -> C:\apup\apup_v1006.exe
...Edit the Target by adding /log to your file - the new target -> C:\apup\apup_v1006.exe /log - Click Apply - Click OK

Note: This will run APUP with logging activated, also, your path may be different but the important part is "\apup_v1006.exe /log"

You can rename and move the shortcut wherever you like - maybe the desktop, and when launched will run apup.exe (v1.0.0.6) with logging, the log can be
found in your AutoPatcher / APUP directory.

When the bugs are fixed in v1.1 or v1.0.0.6 will once again download using APUP this is the fix I would recommend.

[BrainDedd]

Thanks Guitar_Mike. Was about to go crazy with that. Though my issues were with the errors saying the files already exist.
Will stick with v1.0.0.6 until the new one is stable.

[cymicro]

Many thanks, guitar_mike. I hope the bugs are fixed soon, coz, this is a wonderful program.

[startrek]

Apup v1006 or apup v11 make in KIS 2009 in firewall application list, every time I try to update over 40 entries wit same name MODULECODE -time.two numbers.BAT

Attached Files

•  ap.jpg   152.93K   14 downloads

[Antony]

Yes, that's expected behavior of APUP tool. And KIS too. And this is no a bug.
more over - this should not be a firewall list)) Applications control - yes.
You may or delete these entries or to create an exlusion rule for not controling of APUP tool and its child processes

[kmcheng]

so when will windows 7 be included in the list?

[_def_x_]

kmcheng said:

so when will windows 7 be included in the list?

Not for some time (months) - there is lots of work ahead to get both AutoPatcher and APUP ready for Windows 7.

[_def_x_]

Update to post #5:

Nothing has changed rather I thought you should know...so you don't think I'm loosing my marbles !

For now (this is a good thing) AutoPatcher Updater 1.1 has been #commented out of the script - the line of code is ignored and v1.1 wont be seen in APUP,
when the bugs are fixed you will once again see it as a selection.

So, when you run APUP you will have (for the moment) 2 selections made for you - AutoPatcher Engine 5.6.81 and your native OS.

I would keep the shortcut to "apup_v1006.exe", you could (if you want) save to a .txt file 2 links, 1 to the stable version of APUP and 1 to the most recent apup.exe.
This is just a precaution - we have 2 great people updating code but a bug here and there may pop up so an alternative may be necessary. We do need as many
people doing beta testing so don't look at discovering errors as all bad - this is part of the process and the more people using the beta programs the more likely
the bugs will occur. If I'm the only one complaining about something do you think it will matter as much as 20 or 30 people - with that said?

Example:

The most recent APUP will (for now) be apup.exe - and so the link:
Target: -> C:\apup\apup.exe /log

In the event a bug is making it impossible to use "apup.exe" you may need to have a backup that wont get deleted - thus the name change (anything - be simple):
Target: -> C:\apup\apup_v1006.exe /log

As long as the Start in folder is the same ie: C:\apup\ - just copy and paste the necessary link to the Target section of the shortcut Properties.

Again, this may seem like a lot of work but it really takes only seconds to perform and it can make using APUP and AutoPatcher easier, by setting up useful
pre-configured shortcuts or running with switches that make the applications operate more feature rich and so on.

Just Wait, it will take time (and if no unforeseen problems arise) when the guys are done both AutoPatcher and APUP will be much more feature rich and functional.

If you haven't seen some of the available switches for AutoPatcher - Look Here!

[click-click]

It might be a good idea to mention whether a new release is Beta or not. It will help people that want to test to take precautions such as saving there old setup. My 2 cents worth

[Cristiano]

my friend, issues happen. in the beta tests, it didn't showed up. besides, it seems to be an minor bug only. when tracking it, it happens only with the files that has to be extracted. if you don't select the extras package, that will means that apup will download the .apm files again, just that. otherwise, it will download again about 11MB and, if the user has patience enough to wait until it ends, it will download and extract everything ok. besides, this issue doesn't happen to everybody and we are still looking to know why

[]s

[click-click]

I only said that because Mike mentioned beta testing in his previous reply. I understand now that 1.1 was planned as an RTM release and yes, issues do happen. If I can help identify what is causing the problem, let me know. I ran some tests without java and extra checked and 1.1 still felt it needed to download files that were current.

Edited by click-click, 06 November 2009 - 10:36 AM.

[Cristiano]

we was beta testing before it goes public and mike was one of those that was beta testing it. a few things was changed between the beta and the final one. one of those issues was related to proxy authentication (added) and a few minor glitches with minimize/maximize. oh yes, curl wasn't closing when exiting apup in the middle of an download too. all those issues was fixed. then, no one had reported any issue and then this happen. for sure, this was an flaw from the beta testers, that didn't noticed or reported this until it was too late. and, by the way, i've asked if the current version could be already released. as any issue was reported, then the file was released. but the developers will fix it, don't worry. also, apup will be fully re-written with some other major changes

> d 1.1 still felt it needed to download files that were current
yes, compressed files only. the compressed 7z files and something else. if you let checked ap engine, then an file from win9xnt folder will be re-downloaded too. i did that test a dozen of times yesterday, just to be sure of it. so, i've toke an sample list of files that are re-downloaded (and those files are always the same) and the developers are already aware of that. right now, i'm thinking that this has something to do with the extraction of the modules, because apup 1.1 is asking to overwrite files and this wasn't supposed to happen.

[]s

Edited by Cristiano, 06 November 2009 - 10:40 AM.

[_def_x_]

Thank you click-click for making me have to come back and elaborate on what I was getting at...

Know this, the team wouldn't release an application that was an obvious candidate for beta designation.

The facts: The AutoPatcher Team doesn't have access to an exhaustive group of people working within a variety of situations so,

We have 2 people offering their coding experience updating the software - there's 2 beta testers available, Cristiano, myself and maybe a few
more offer to test said update - what is this 5 maybe 6 people now (not a consensus) - we all test said application 5 or 6 times - all seems
fine, so the update gets released. We hope our test - maybe 50 total within 5 or 6 environments is a sufficient test bed but it can't be for an
application that gets downloaded and used worldwide - my point: In my view until enough people have used and have not reported problems
technically said application might honestly be looked at as still beta (for a time).

If the new proxy features have only been used in 2 or 3 proxy settings do you really think that honestly an application is proxy ready, we could
wait and hold off on a release until 10 or 20 users with proxy support needs offer to test but we would be waiting months, so try to understand
my comment was an attempt to be honest - until enough time has passed and enough people have used and not reported problems it may be
fair to say - the application may not be bug free - technically beta - meaning untested to a sufficient degree.

The larger point - we sure could use more people using the application bugs and all to guarantee the bugs have been fully worked out, the reality,
most users sit back and wait for the so-called stable release - and so the cycle goes. That's all I meant.

Have you ever had one of those days were you wished you'd kept your mouth shut?

[Cristiano]

just to clarify: apup 1.1 wasn't beta tested only by 5 people. yes, a few people are in that meeting, but only that. i've sent that beta to an dozen of users that had serious issues related to proxies and apup usage. just one of them reported an issue like the one presented in here, after the release goes public.

and, by the way, i've tested the betas with:
- dial-up;
- radio;
- public wireless;
- dsl;
- with an restrictive proxy that requires proxy authentication (the screen of the first post was taken from that machine)

also, the reports about apup 1.1 was only stating that apup was finally working into their ICs. and, by the way, the present issue doesn't happen in a first run, only when updating an existing folder. and no one had noticed that and still, there's reports that this didn't happened at all. and still, this issue doesn't damage anyone, except those that don't wait until the end of the download. so, surely this isn't an major bug. an glitch, for sure, but not an major bug

[]s

[_def_x_]

FOR GODS SAKE - DELETE MY DAMN POST - IM GOING BACK INTO HIDING

[click-click]

Don't do that. We would all miss you
Anyway, if the team needs another beta tester, let me know. I don't mind helping.

Edited by click-click, 06 November 2009 - 12:28 PM.