AutoPatcher Forum

In the Components, there are the following errors:

1 - .Net1.1 requires restart and it is NOT set to restart!
It caused .Net2.0SP1 to fail on installation
(I didn't notice the message because "hidden" behind the other window)

2 - KB928366 is only listed under Portuguese. Why not English? It is a legitimate fix!

3 - .Net2.0SP1 is good for XP (and others) and doesn't show.
It lists only for W2Ksp3 and sp4, NOT all the others.
In addition, a PreRequisite needs to be in place for W2K.

4 - .Net3.5 is good for XP (and others) and doesn't show.
Also it includes .Net2.0SP1 and .Net3.0SP1.

Search Microsoft.Com for items 2 thru 4 and you'll see what I mean!

I hope this is the appropriate place. I don't see a Forum for Net Framework. If I'm incorrect about this, please move this topic.

Quote

- The dotnet 1.1 module is set to reboot after AutoPatcher has completed it's updates:

[Behavior]
ParentID=DOTNET_PARENT
UniqueID=DOTNET1.1
Critical=False
AutoExpand=True
Depends=
TimeToInstall=90
TimeToRemove=90
RequiresReboot=True
ModuleFolder=dotnet1.1_files

Quote

KB928366 is a language specific update. Renato went ahead and created a dotnet package solely for Portuguese which is why he included it. If you download any of the English update packs for Vista/XP/2K3/2K, KB928366 is included but only displays after you install dotnet 1.1

Quote

You're right, .Net2.0Sp1 is good for any OS. I decided not to included the tags though since dotnet 3.5 already includes this. Once AP has the support to deselect updates based upon what you choose, this probably will be updated.

Quote

Not sure why this one isn't showing on your rig. Run autopatcher.exe with a /log flag and post the autopatcher.log file located in your windows system directory here

1 - Uh-uh... the problem is that after install the DotNet installation isn't silent and the "Do you want to reboot" box appears, thus defeating "RequiresReboot=True". The box was "hidden" because of other screens overlaying it so I never noticed. My bad maybe?

2 - Yep, it's there... Probably didn't show as "needed" since I installed it separately.

3 - Ok, but maybe some folks don't want Net3.5 ( ? like me)... And just as a note to anyone interested - ".NET Runtime Optimization Service" (usually the first entry in "Services") will clobber your CPU with high utilization unless it's first Stopped then Disabled. Found out the hard way... The rationale behind exposing it in this package is built for an older rig (450mhz, 10gb HDD, 196mb-RAM) so it can't be clobbered. Having enough trouble finding AV and Firewall with small footprint...

4 - Clueless... Just doesn't show. 1.1 and 1.1sp1 show as installed. Naturally 2.0 doesn't show (installed manually). No time to get a log right now since busy battling A-V/Firewall crap.

x - On a side note, installed everything before any .NET components (did them last). XP Updates and Net Updates built separately then "merged" in another folder and placed on CD...

Thank you for your support... Will try this beast on another rig later and report back...

Just a warning that doing this:

submix8c, on Jul 26 2008, 11:57 PM, said:

is a seriously, seriously bad idea.

Don't misunderstand what I'm saying here: 100% CPU will happen, but don't disable the service.

The .NET Runtime Optimization Service (which is mscorsvw.exe) is required every time a service pack or an update comes along.

Immediately after installing an SP/Update this service will run in the background to (re-)precompile .NET assemblies. There is usually a high-priority element and a low-priority element to its work. Once all work is done the service will automatically reconfigure itself and will not run again until the next SP/update.

So, unless you want .NET to grind to a halt - let it do its job!

If you are totally impatient, type:
[indent]ngen.exe executequeueditems[/indent]at a command prompt and go and have a coffee.

--