11 replies to this topic

[hlarsen]

I'm seeing an error with the APUP2 (version 1.05.13) getting .NET framework for x64, and I have to laugh at the error. The title is "Oh sh*t there is an Error". The body of the error is "Permission denied."

So, I reverted to the original APUP and tried again. That one seems to be working.

[hlarsen]

Whoops, I could be wrong. I'm getting "One or more files has failed verification." during the fetch for office 2007 sp3. Specifically 20120313. Not sure what I'm doing wrong.

[hlarsen]

okay... it just worked...

[ViroMan]

wow... I didn't even know that error string was still in there.
The permission denied is due to not having admin rights to read/write something.

That's funny, I can't seem to find that string. Figures as soon as I say that I find it.

Yep it has to do with executing dos commands. Both apup and apup2 use the same method to execute dos commands. They create a temp batch file, stuff the command into it, and then execute it. The error string you got only happens if it can not create the temp batch file or for some reason there is one with that exact name there already that it can't remove to make a new one. This still comes back to needing proper access rights.

Changed it to say "Command Execution Error" As I thought I already did. Although you won't see the change until I post a newer version.

Edited by ViroMan, 06 June 2012 - 09:57 PM.

[hlarsen]

Thanks, Viroman, although I like the first error better.

Can you tell me the location where the batch files are created? It's just strange because I'm not only the local machine admin, I'm the domain admin. I should be able to go anywhere.

It is entirely possible I had two apup update tasks going at the same time, which may be the reason why it was erroring out, if the batch file names are generic. I also might have started the update task too quickly if the one that errored out had yet to clear out the temp files. I'll have to watch that.

Nice work on APUP2 btw.

You have any need for a guy heavily into autoit scripting?

Edited by hlarsen, 06 June 2012 - 11:27 PM.

[ViroMan]

The batch files are created in a directory called temp_bin that is created and removed for both apups. That directory is created in the same directory that apup is run from. I believe apup uses a time stamp method on its name for its batch files. Apup2 just uses the same file. It creates/opens, truncates the file if opened, and then fills it in. The apup2's batch name is modulecode.bat.

hmm I was having lots of problems with it before. It used to set the file to read only for some damn reason. I fixed it but, perhaps it is still doing that for you. If you get that error leave apup on and navigate to the temp_bin and look for the batch file. See if its read only attribute is set.

Quote

You have any need for a guy heavily into autoit scripting?

Well we could defiantly use someone to help sort and clean up the current scripts. If you have noticed Click-Click's .NET download beautifully sorts out all the downloads, we want the others to do the same. WhatACrock is currently working on the XP x64 script. This is a benefit to yourself as well as others. Imagine no longer needing to have an APUP folder for each OS or having a gigantic DVD full of OS's. You would be able to just select the OS folder from apup and then copy it over.

Quote

Nice work on APUP2 btw.

Thanks but, props also go out to my alpha testers too, Cristiano and Domenico without which would have taken much longer to get to this point.

Edited by ViroMan, 07 June 2012 - 12:21 AM.

[hlarsen]

No offense intended, Cristiano and Domenico, as well as anyone I'm not aware of on the APUP team, I certainly didn't mean to exclude. I'm a fan, guys.

I understand where you are going. How do I get started? You want to take this out of the forum?

[ViroMan]

Public is better. Less questions if someone else wants to help as well. It would help to first know what OS(s) you have. Then we can recommend a script that would suite you since you are likely to already have the updates downloaded.

[hlarsen]

I'm still here

System installed to the machine I use is Windows 7 64, although I also administer a load of XP 32.

[ViroMan]

ohh well then the either script is fine. point your browser to
www.autopatcher.com/releases.list
to get the list of scripts from there you can switch to the one you want to fix up windows 7 or XP. Make sure you select the English ones if you only understand English. If you can do the other languages even better since they don't get any love.

OHH and before you even get started I recommend taking a look at the Documents page. That can help get you started in understanding how the scripts work and what does what.

Edited by ViroMan, 12 June 2012 - 12:42 AM.

[hlarsen]

Hey ViroMan, I think I'll actually start with Office 2007, as it seems some love is needed in those particular products, as opposed to the OS releases, which seem to have maintainers. I've actually been studying the documentation for a while now, and experimenting a bit. Thank you.

A couple questions, is there a general document/guideline for which products as a whole AP is targetting?

I'm not familiar with RTI. Can you expound on what it is, if I need to generate it, and if so, how?

When I've completed an update, what do I do with it?

Edited by hlarsen, 12 June 2012 - 03:07 PM.

[ViroMan]

someone is actually already working on Office already.

In general the project is targeting Windows and Microsoft products as they both get updates from the same update servers and don't let you keep them unless you do the downloads manually(tons of work). There are extras like Java(temporarily suspended again) and several Adobe products(everyone uses them). In short... if it is popular and you can spare the time to keep the script up to date we are willing to consider adding it.

RTI is a file that we use to verify the script downloads are where they should be and if the downloads are not corrupt or different(newer version) then what it should be. You do not have to generate one unless you are a release manager. We will do that for you once you give us the script and apm files.

The BEST way to test the scripts yourself is to use dropbox. Upload your files and a faux release.list there. The list should point to your script. the script should point to the direct downloads(the servers they are on) and your zipped apms(on your dropbox). Then point apup (or if you still have apup2) to the dropbox list. Use the attached batch file to point apup1 to your dropbox. You will have to edit it with the location of the dropbox release.list though. Remove the "pause" if you don't want it. For apup2 just give it the link to your faux list in options.

Attached Files

•  Release2.zip   230bytes   6 downloads