[error] 2 updates not applying

[craighackl]

Hi i am using the latest autopatcher 2005, on a new xp sp2 build, but two updates don't apply.

the updates that don't apply are

security update for windows xp (kb885836)

.net framework 1.1 service pack 1

both of these updates are listed in windows update as not being applied

in my modules folder it appears that i have them

dotnet11sp1.xxx

and kb885836.xxx

when i run autopatcher it shows everything in blue

when i check add/remove programs i show 885836 installed, and it only says .net framework 1.1

checking the resistry it looks like 1.1 sp1 is installed.

any thoughts, my problem is, i run a windows update server, and it will force the updates down for these, and the .net one

Edited April 8, 2005 by nw_raptor

[gandolas]

I have the same problem with the ".net framework 1.1 service pack 1"... I can't install it using AutoPatcher... It starts decompressing, and then exits. :(

[+M2Ys4U Subscriber¹]

Have you tried running the installation multiple times? I think it might be a reboot issue...

[gandolas]

Yes, and in the second run, the AutoPatcher thinks that the ".net framework 1.1 service pack 1" is installed (appears in blue). I choose to install it again and nothing...

[pacifica]

check your change\remove programs and enable the "show updates" and see if it's installed.

i don't use autopatcher but i have my updates set to automatically install. when i go to the windows upate site it shows that .net framework 1.1 service pack 1 didn't install on one date, but on another date it shows it installed successfully.

go to windows update and check to see if this is the case.

[gandolas]

My problem is than it doesn't appear in the Add/remove programs, but does appear in the windows update... And AutoPatcher thinks that it has installed it... :(

And with the kb885836, it appears in windowsupdate and in add/remove...

[gandolas]

The problem with .net framework 1.1 service pack 1 was solved doing a slipstream version of .net framework 1.1 + .net framework 1.1 SP 1 + KB886903.

Now the only problem is with KB885836...

[PsiMoon314]

Hi Guys,

You might like to check out the .NET Framework Installer here at:

http://ryanvm.msfn.org/

This is a self-extracting switchless installer which already has Service Pack 1 and the KB886903 hotfix integrated into it. Also includes other unofficial hotfixes as of February 22nd.

I would imagine this would work well with APXP 5.0 if the module is re-written to use it.

Kind Regards

Simon

[gandolas]

Thanks for the info PsiMoon314, but it's already done. ;) I've slipstreamed it, using a ".bat".

The hotfix isn't slipstreamed because the installation of the .NET package would give some problems if the .NET Framework 1.1 SP1 was already installed. So, to avoid it, nw_raptor suggested to have them in two modules (instead of the original 3). So, who only needs the hotfix, just has to install it and not the hole package.

[PsiMoon314]

Hi gandolas,

I see you point :)

Perhaps there needs to be an addition to the APXP Module Code such that one patch or fix cannot be installed until another is installed and detected as such.

This might mean several passes though APXP to get everthing installed, but might be safer in the long term.

This would be useful for installing packages such as .NET Framework and even Service Packs for Windows or Office Applications.

Kind Regards

Simon

[akaladis Veteran]

PsiMoon314, a step towards this, will be done in the next AutoPatcher engine, 5.1 (or 5.01). Here's a changelog for what's coming:

[*] Support for modules in subfolders (module groups).

[*] UniqueID property has been removed.

[*] Prerequisites property has been added.

[*] Extended Registry support (i.e DWORD values).

[*] Backwards compatible with 5.0 modules.

I still haven't decided yet on the piracy blocker. The code is already in 5.0, just not activated.

[rtk]

I still haven't decided yet on the piracy blocker. The code is already in 5.0, just not activated.

585801100[/snapback]

Piracy blocker? Did a search but this is the only post I see reference to this functionality... what's the scoop there?

[akaladis Veteran]

Well, I didn't really say it correctly. It's a pirated-Windows blocker. As you may be aware XP SP2 blocks certain (illegal) copies of Windows. This functionality (as in the code) was added in AutoPatcher 5.0 ever since it came out. It was just not triggered. In 5.1, It will probably be.

[PsiMoon314]

Hi nw_raptor,

[*] Support for modules in subfolders (module groups).

[*] UniqueID property has been removed.

[*] Prerequisites property has been added.

[*] Extended Registry support (i.e DWORD values).

[*] Backwards compatible with 5.0 modules.

Good set of updates :) Don't forget my colour changes for unofficial items! ;)

You might want to ensure that when an item which is referenced as a Prerequisite (by something else which needs it) that the "NeedsRestart=True" flag on the Prerequisite will mean that a reboot is needed before the dependent items can be installed.

This could mean that the dependent items are simply greyed out and unselectable until the Prerequisite is installed.

How will your piracy code work?

Will you block every installation which is deemed to have an illegal PID or go beyond what MS currently does with this and block all keys which are generated by the well known keygens for XP (including those for XP SP2 Corp).

Kind Regards

Simon

[+M2Ys4U Subscriber¹]

heh, why the validation?

[akaladis Veteran]

I'll block the PIDs blocked by SP2.

[+theblazingangel MVC]

I'll block the PIDs blocked by SP2.

585803614[/snapback]

im not sure if i see any point in it

to make proper use of AP youd have to have installed a service pack before hand which means youd have to pass the list already.

theres no need to then check it again is there? :huh:

[+M2Ys4U Subscriber¹]

exactly :s

[akaladis Veteran]

Some people are still running it on XP SP1 or even RTM.

[+theblazingangel MVC]

Some people are still running it on XP SP1 or even RTM.

585806794[/snapback]

but then they only get a very small number of updates to install...

they can make there own sp0/1 modules, but there still not secure without the latest service pack, so why go to all that trouble of creating the modules and not simply installing a service pack?

im sure they'd rather forget AP and use Windows Update!

[akaladis Veteran]

I'm only going to activate this feature if/when Microsoft activates it on windows update and other downloads.

[+theblazingangel MVC]

ok :)

[Cardinal]

Raptor, you are coinciding with Microsoft to help stop piracy. Is that what you really intend to do? What a pointless feature if you enable it. Are you trying to get brownie points here? You will lose a lot of support from the community if you enable this feature.

While I'm at it, you should include a list of what registry 'hacks' your autopatcher does so they can be undone if the situation occurs. I personally think you have made some errors in your registry settings.

- Cardinal

[+theblazingangel MVC]

Raptor, you are coinciding with Microsoft to help stop piracy. Is that what you really intend to do? What a pointless feature if you enable it. Are you trying to get brownie points here? You will lose a lot of support from the community if you enable this feature.

While I'm at it, you should include a list of what registry 'hacks' your autopatcher does so they can be undone if the situation occurs. I personally think you have made some errors in your registry settings.

- Cardinal

585860181[/snapback]

first, i dont think raptor will loose any (or very much) support, and he definately wont loose mine. the only reason i question it is because i dont understand the use of it.

second, although theres no official list like there is for updates and addons, you can find them all under the tweaks section from within AutoPatcher.

You can undo tweaks by using the tweak undo tool in AutoPatchers \tools directory.

I personally transfered the tweaks from AutoPatcher 4.6 to 5.0, and spent a lot of time fixing problems with them.

If you feel theres anything still wrong with any of them, i welcome your comments.

[akaladis Veteran]

Cardinal,

Maybe you didn't quite understand; Microsoft will probably add piracy-check on their downloads. Adding the same checks in AutoPatcher is I think the way to go if we don't want to have trouble. Why would we loose community support? People who use pirated copies of Windows would not support this decision, but I don't see why someone who has paid for his operating system like you (?) and me would object. If Microsoft doesn't add piracy checks, neither will I. Is it clear now?