AutoPatcher Forum

Coastie, on 20 June 2011 - 01:21 PM, said:

keeping it USB portable is no problem.

Adding more things to update is another matter. Its up to the people who manage modules for that. I can take work off there hands by making the creation of modules easier but, finding detection for update/installs still requires humans to find. They have to find registration entries, files, and md5s for those files.

I can make it easier to create the modules and md5 files and update the module. Even auto error reporting to a server if we get around to doing that. No more posting logs.

yay code conversion completed. Now I need to drag around the code for a while to make it OOP able and then get it ready for alpha testing.

[]s

close to alpha release... will be sometime within the this week.
Alpha release still uses curl while, beta release will probably use wget. There will be some advantages to using wget over the current curl such as
* Resume stopped downloads
* Date checking (don't download the file if the dates are the same. SUPER plus for use in module managing[Automatic downloading of changed files])
* supports wild cards and recursively mirror directories(will use this for module manager possibly)

I might even make one for the project depending on the needs.(I shiver at the thought of working with windows socks)

No need for alpha volunteers as I have some people already willing to test it. Beta release will be open to all however.

as a side note. I have heard that Current version of APUP doesn't work on linux wine. Mine "should".
Edited by ViroMan, 27 June 2011 - 12:42 AM.

[]s

Sounds like you're making real progress, I'm sure the users are itching to try out the new software.

well don't expect a miraculous improvement and all previous bugs fixed just yet. This is first a code conversion. Once this works it will only be slightly better then the previous one(during conversion I have modified/improved obvious issues in the code). Then from there I will make the major improvements.

I am ready - on my #1 system I have XP Pro w/SP3, XP Pro x64 w/SP2 and Win7 64-bit w/SP1; on my #2 system I also have XP Pro w/SP3 and Win7 32-bit w/SP1 so testing can be somewhat tedious and could take a while but, hopefully, the effort will be worth it.

delays delays... ran into a registry problem(XP x64 stores some things differently then any other version of windows(not talking x86 vs x64)) then an api problem(some api calls acted like they worked then failed afterwords(silly miss labeled variable)). both Fixed and continuing to work on stomping major bugs, probably won't make this weeks alpha release. The registry problem has given me an idea to make an external script to detect registry things instead of having them hard coded and recompiling the code if they ever change or there are newer versions. However that is for after the conversion. Not a good idea to pile up my todo list before I finish conversion. lol.
Edited by ViroMan, 02 July 2011 - 07:20 AM.

well of course I didn't do anything before and after 4th of July(American independence day)... When I got back to working on the code I got fed up with using an external downloading program... namely the way borland was handling them. So im implementing a downloader in a DLL. Then I will link it into the APUP. Future maintainers of the code can keep the link to DLL it if they like it or they can modify it or what ever. I decided on DLL form so that if they couldn't compile the code(uses INDY a free internet code) at least they could still use it.

Indy is great in how much flexibility it has... indy is bad in that the documentation on it is horrible but, what do you expect from open source?
Edited by ViroMan, 07 July 2011 - 02:17 PM.

that will help a lot. according to some things that i've read about, indy is promising

[]s

Hi ViroMan,

I just wanted to encourage you and cheer you on with creating a release that works with XP 64 bit, having just upgraded to it...your efforts are much appreciated!!

it will work with xp x64 but, it still requires someone to maintain that branch. currently there is no one to fill such a role. I dare not ask cristiano and I will severely brow beat anyone who does. That guy "quit" a while ago and is still doing lots of work here. I will endeavor to make managing the modules easier after finishing this of course.

xp x64 has another issue: so far i know, this one wasn't sold outside the US. i do have an install cd for it, but the version that i have has an time bomb and doesn't work for long term usage. so far i know, xp mode (the one that i'm running to take certain xp detections) also has an time bomb built inside. the only one computer that i had running xp was sold months ago, because i didn't had any usage for it anymore (in fact, since long before that, that one was an dvd player, not more than that). in fact, i us to deploy this one every single time that something from it is required, but it's unpractical do that every single month. due that, someone that runs that OS for real should be the one updating that script. i don't know for xp x64, but xp x86 right now only has critical updates that doesn't add any new features and soon, that will resume to mrt. due that, do an script for this one should be an simple task and easy to keep

oh yes, i'm acting as an collaborator only and that is the same thing than everybody could do. i don't have any ftp password, anything like that. i'm just fixing things and sending it to be checked and uploaded

[]s

it wasn't publicly advertised(as far as I know) to other nations but, it is available. You can still buy it and get an unlimited license(remember that means you can install on all(as many as you have) the computers in your family, not on other peoples computers).

wow.. I just did a price check for a xp x64 and its gone WAY up from when I bought it. I do see some cheaper ones out there for like $105 but I got mine for $89 a few years ago. at that price you might as well just get windows 7 x64 for $100 if your computer can handle it.
Edited by ViroMan, 10 July 2011 - 11:52 PM.

interesting. i was thinking that this one never was sold outside US because i didn't found any localized version for this one. but it's interesting to know that. by the way: certain schools has an program with microsoft that provides licenses free of charge of many of their products through msdn academic alliance, without any limitation about the number of the computers where you can run it (but of course, abuses grant blacklisting). an friend of mine has it and i've saw his account some time ago. he can download even developer tools (but of course, to learning purposes only)

[]s

lol I know I promised an alpha soon but, it seems I keep running into more code that I dislike and modifying it thus making other code break. APUP is in a semi ready state although it parses the modules incorrectly due to a previous change I made to the way it reads(which is a better way now). We shall see if I run into more issues from there. <crosses fingers>

Ok for sure im almost ready for alpha release now. lol so much code was completely replaced. It currently does almost everything properly, I just have some minor errors that need fixing up before I release to alpha.

I still have some more work to do on the download DLL but, I will leave that for the beta release. ATM it doesn't tell you the current speed you are downloading from properly and the code is in for the cancel download button but, because the download function is in the same thread as the button you can't cancel the download till it finishes the current file download. Easy fix if I put some time into it.

For your viewing pleasure there is a log file attached to this post. Do NOT expect the log to look the same when APUP enters BETA phase.
P.S. Open it with anything other then notepad. Window streams doesn't seem to generate proper CR LF compatible to dos.

Alright... Alpha is out! Alpha is available in the beta section for those of you who have access to it.