←  AutoPatcher for Windows XP SP3 (x86)

AutoPatcher Forum

»

KB895181 reports WMP10_NONCRITICAL_PARENT

Cristiano's Photo Cristiano 13 Sep 2010

i've finished the download of the office xp and seven x86. if some md5 check is required, please let me know it

in meantime, i will enjoy an nice and cold rain in here (and also the last days of our winter) :)

[]s
Quote

_def_x_'s Photo _def_x_ 14 Sep 2010

aleatorul said:

I'll keep your advice in mind for the next time.
Sadly, this is probably true.

aleatorul said:

but to what I had to do before finding out about your solution.
One idea is to not wait so long to update the releases, this is your responsibility. Depending on when you last ran APUP in May you very well could have missed 4 Patch Tuesdays - May thru August. The idea is to run APUP at least twice a month (not 4 times a year) to get new updates, remove old ones, maybe a script fix - this is common protocol regardless of what you use to update your system, AutoPatcher, MU or WU.

If you're not sure about how to do something ask before hand, "hey, I'm new to AutoPatcher, have any tips on how to best use the tool, keep it updated and Official?" There's the forum 'Search' feature that has a wealth of information, you might try using it as well. This is not unreasonable to expect of a new or inexperienced user.

aleatorul said:

Well, in the century of speed...
AutoPatcher is a very fast update process, maintaining the releases, especially when you have multiple releases all piled into one folder does take a bit more effort. That was my point about dialing in on the exact changes in your release when an error occurs. What would have taken maybe hours to find - a rogue file mixed in with 1000 others - by using simple comparison you can spot all changes in a few seconds.

aleatorul said:

'Cause I was raving and cursing and mouth foaming, right?
No raving, cursing, or foaming, just whining and complaining -> 'not fast enough', 'you insulted me'. I suppose I could accuse you of insulting, you use a free tool, get free support, don't know exactly how to use it, don't bother asking until after you have a problem. I simply say you need to be more pro-active and offer my opinion on how to quickly spot an issue and you have a tizzy.

aleatorul said:

It's what I believed to be an accusation from you, that I wasn't "pro-active" enough
Here's another tip: Many md5 tools like to rename files that don't pass hash, the tool may add '.old', '.bad' to the file, these files will get left behind because the scripts will expect to find the file it downloaded not one that was renamed. Many many many times a release has been Unofficial because a user doesn't pay attention to their md5 tool's preferences - don't make this mistake, check the tool you use now, have the tool alert you that a file is bad - not rename it otherwise you will have another Unofficial issue.

Also, it isn't impossible to have an error in a script, the release maintainer has no problem when they are alerted about an issue, nobody is expected to be perfect.

aleatorul said:

It's all clear then.
What's clear is this thread is mostly a waste of time. I don't think you really care about much more than getting what you feel you have a right to - someone else's time and attention, internet grifters operate this way.

One last thing, 'Patch Tuesday' is the second Tuesday of every month (hmm, today is?). You may think about updating your releases on time after the maintainers get the scripts updated. Btw, it may require running APUP a few times - the scripts get fixed when errors are found - this does happen.

My solution for this issue: aleatorul='Ignore'
Quote