25 replies to this topic

[Whatacrock]

I have been working on Windows XP SP3 script to make it the same layout that was done with the XP x64.
Have managed so far to just four folders each with a child folder holding all the update executables.
Once I got towards the end of the script arrived at the Tweaks section and got to thinking.
How many people still use this section in autopatcher....at a rough estimate only a few!!!!
I would therefore make a suggestion to remove this.
Your thoughts people, please

[ViroMan]

I don't think anyone uses them but, I do use tweakui... well the x64 version anyways.

[DesertJerry]

I'm assuming you mean: Registry Tweaks and the four sub-menus - I won't miss them. Agree about TweakUI though; 32 and 64 bit versions for XP.

[dkdk_it]

OK... so, can I remove all tweaks from XP release?

[Whatacrock]

I would therefore move a motion to remove the registry tweaks from Windows XP SP3 release.

BE GONE WITH THEM!!!!!!!!!!!!!!!!!!!!!!!

A slighty off subject request...small alteration to windows update agent as still shows as black with a checkmark in autopatcher.

Currently in apm is shown as

[DetectionFile]
FilePath=system:
FileName=wuapi.dll
FileVersion=7.6.7600.243

FilePath=system:
FileName=wuauclt.exe
FileVersion=7.6.7600.243

Change to

[DetectionFile]
FilePath=system:
FileName=wuapi.dll
FileVersion=>7.6.7600.243

FilePath=system:
FileName=wuauclt.exe
FileVersion=>7.6.7600.243

This should be also applied to the X64 apm also.....an observation that's all

Edited by Whatacrock, 08 August 2012 - 10:53 PM.

[click-click]

Be careful with =>. This does not always work on some modules. You are better off changing the version number to the newest version unless there is currently no direct download for the latest update agent.

[Whatacrock]

Thanks click-click, had tested in both x86 and x64 the greater than or equal to worked as I had lost the notes with actual version number and found it the posting by myself about the latest windowsupdate agent.
Therefore file version to each file to be changed to 7.6.7600.256
so
FilePath=system:
FileName=wuapi.dll
FileVersion=7.6.7600.256

FilePath=system:
FileName=wuauclt.exe
FileVersion=7.6.7600.256

[click-click]

Yes, but as far as I can tell APUP is still downloading the old windows update agent (243) so changing the version number will cause it to show up in black. The download needs to be updated too.

Edited by click-click, 09 August 2012 - 10:41 PM.

[Whatacrock]

As you are apparently aware there is no standalone installer available for .256 so as to my original suggestion to add the greater than to the lines will at this time be sufficient.
I have doubts that a standalone installer will ever be released for 256.....I could be wrong however

[click-click]

Then just use => with the old version as you suggested earlier until there is a new download link available.

[Whatacrock]

A couple of additions for suggestion of removal...this time from the Extras addons....they are quite old and I doubt than they are used by anybody.

Firstly DelMSJava...this thing is definitely ancient as Microsoft abandoned their Java project eons ago.
Secondly WinColorSetup.....not much to say on this one.

As usual thoughts on these would be appreciated

Edited by Whatacrock, 16 August 2012 - 03:12 PM.

[ViroMan]

They might have abandoned it long ago but, anyone using an xp disk will still get that junk installed.

[DesertJerry]

I just read the information available concerning the Control Panel > Color Control applet - all information indicates it is mainly for those publishing stuff - so that colors are consistent between printing, scanning, copying, etc - my suspicion is most of us have no possible use for this option - I vote: Go away.

Agree with ViroMan about Microsoft Java - as long as people continue to use XP the requiremnt to uninstall Microsoft Java runtimes will remain. Is there no way to not show this item if Sun Java or other is installed?

[ViroMan]

well yes there is a way but, it won't remove the bug ridden older ms java which any user who even remotely cares about security for his computer should do.

[DesertJerry]

 ViroMan, on 16 August 2012 - 09:54 PM, said:

well yes there is a way but, it won't remove the bug ridden older ms java which any user who even remotely cares about security for his computer should do.

OK - then is there any way to detect if Sun Java is installed and automatically uninstall Microsoft Java without any user input or notification?

[ViroMan]

Its possible to construct a batch file to do that and insert it into the script like the windows x64 and .net scripts do.
Using the REG command line you can look for specific registry strings and if you find it run the msjava remover.

Edit:
Also reading up on the MSJava from HERE It says that any XP disk that is SP1 or higher does not include MSjava. HOWEVER updating an existing pre sp1 to sp1 or higher will not remove the MSjava. I assume that slipstreaming an install disk will have the same effect.

Edit2:
So looking around... I can't seem to find any way to tell in the registry IF the MSJava is installed or not. the only thing I can think of is... installing an XP SP0, making an image, running the MSjava remove tool, then doing an image compare.

Edited by ViroMan, 17 August 2012 - 09:23 PM.

[ViroMan]

So I was looking around in the tweak area to see what might possibly be kept and or moved into other downloads... and this is what I came up with...

Move into MS security
DisableAdminShares
DisableLMHash (EVERYONE should use this. Prevents fast LM attacks on your password. They have to do it the harder way. P.S. ALWAYS use passwords over 8 characters long)
NoSharedDocs

Remove everything else.

Edited by ViroMan, 18 August 2012 - 07:04 PM.

[Whatacrock]

DAMN!!! I had a pc here just the other day that was installed with Windows XP SP0 and erased the drive to freash install with XP SP3.
I could have done a detection for MSJava for you.

[ViroMan]

Well if you upgraded that install disk from XP SP0 you still have MSJava on it. (Im pretty sure since adding SP's don't remove it.)

[Whatacrock]

VM I think you misunderstood the posting..the pc came to me as Winows XP SP0....was wiped clean and I reinstalled with Windows XP SP3.