[-X-]

OK, here's my findings...

KB2686509 fails with disable Windows key
KB2686509 fails with removed keyboards.
KB2686509 does it's thing perfectly if neither of the above is done.

Time to write that footnote.

Thanks for bringing this up.

[PinkFreud]

You're welcome.

This post has been edited by PinkFreud: 19 November 2012 - 07:24 PM

[PinkFreud]

Confirmed, KB log attached...



Do I substitute the CAB "Faker" file for the real one? Or do I slipstream both?

This post has been edited by PinkFreud: 19 November 2012 - 07:25 PM

[-X-]

Substitute.

[PinkFreud]

-X-, on 24 June 2012 - 04:40 AM, said:

Substitute.

Thanks

This post has been edited by PinkFreud: 19 November 2012 - 07:26 PM

[PinkFreud]

Nope...CAB faker didn't get it done Last INI att'd...

This post has been edited by PinkFreud: 19 November 2012 - 07:26 PM

[-X-]

The faker is supposed to hide the update..that's all. Did you not remove it from the update list?

[PinkFreud]

-X-, on 24 June 2012 - 07:59 AM, said:

The faker is supposed to hide the update..that's all. Did you not remove it from the update list?

Please explain in more detail what EXACTLY the Faker cab does/doesn't do when you have the time.

Thanks & much gratitude,
"Pink"

This post has been edited by PinkFreud: 19 November 2012 - 07:27 PM

[-X-]

EDIT: The it is KB2686509


So after you setup Windows, you tried to install it? That's what I get from your image of the log file.... c:\152.............................\update\update.exe.

KB2686509 is a weird update. It does not install any files or reg entries (except those indicating that the update has been applied).
I'm not a MS update engineer but it appears to me that WindowsXP-KB2686509-x86-ENU\update\kblChecker.dll does some magic as far as checking things. Now on a fresh install everything should be OK if it's just a scancode map reg entry (disable or remap a key). So the faker will just tell WU that, hey I've done my magic because all it looks for is "has this update been run?". The faker does not run the update, it just tricks WU into thinking it has been run. Remember this update only runs and does not add things to the system.

Here is the faker....

[general]
builddate=2012/04/19
description=Security Update faker
language=English
title=KB2686509 faker
website=http://support.microsoft.com/?kbid=2686509



[registry_addreg]
HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\KB2686509,"Installed",0x10001,1
HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\KB2686509,"Comments",0,"Security Update for Windows XP (KB2686509)"
HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\KB2686509,"Backup Dir",0,""
HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\KB2686509,"Fix Description",0,"Security Update for Windows XP (KB2686509)"
HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\KB2686509,"Installed By",0,""
HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\KB2686509,"Installed On",0,""
HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\KB2686509,"Service Pack",0x10001,"4"
HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\KB2686509,"Valid",0x10001,1
HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\KB2686509\File 1\,"Flags",0,""
HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\KB2686509\File 1\,"New File",0,""
HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\KB2686509\File 1\,"New Link Date",0,""
HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\KB2686509\File 1\,"Old Link Date",0,""
HKLM,SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB2686509,"Description",,"Security Update for Windows XP (KB2686509)"
HKLM,SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB2686509

As you can see it just add entries into the section of the registry that keeps track of what has been "installed".

To expect the faker to make the update ignore the errors with keyboards is unrealistic. I don't know what the effects are of having those keyboard errors. I truly don't understand fully what this security vulnerability does. The vulnerability is pretty minor as all it affects is a logged in limited users being able to run administrator commands. They would need physical access to the machine. If you don't add limited users like your kids or something that are hackers then this update is kinda meaningless. Hence the faker.

This post has been edited by -X-: 24 June 2012 - 09:38 AM

[tomasz86]

@-X-
I think your "faker" could be simplified to this:

[general]
builddate=2012/04/19
description=Security Update faker
language=English
title=KB2686509 faker
website=http://support.microsoft.com/?kbid=2686509



[registry_addreg]
HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\KB2686509,"Installed",0x10001,1

[-X-]

Probably

[PinkFreud]

-X-, on 24 June 2012 - 09:20 AM, said:

EDIT: The it is KB2686509....

...If you don't add limited users like your kids or something that are hackers then this update is kinda meaningless. Hence the faker.

Thank you -X- much appreciated

This post has been edited by PinkFreud: 19 November 2012 - 07:28 PM

[O0o0O0O0o]

I would like to ask you ,'PinkFreud' what is size of your final integrated cd/dvd ?

I see Im barely making it without application addons so I too must cut out 'lang' (99mb) folder,and few others as mentioned on unattended site "slimming down cd ."

[PinkFreud]

>>>I would like to ask you ,'PinkFreud' what is size of your final integrated cd/dvd ?<<<

I haven't burned a CD yet but original "clean" SP3 source was 591 MB, final nLited ISO is 319 MB.

This post has been edited by PinkFreud: 19 November 2012 - 07:29 PM

[O0o0O0O0o]

PinkFreud, on 24 June 2012 - 08:45 PM, said:

>>>I would like to ask you ,'PinkFreud' what is size of your final integrated cd/dvd ?<<<

I haven't burned a CD yet but original "clean" SP3 source was 591 MB, final nLited ISO is 319 MB.

Does this extensive "slimming" make your OS run better/faster ?

Or to some atvantage ?

[PinkFreud]

O0o0O0O0o, on 26 June 2012 - 08:53 AM, said:

Does this extensive "slimming" make your OS run better/faster ?

Or to some atvantage ?

I only use extreme slimming like the one above for use in VM, much different than "live" XP. I'm really not that technically proficient (above average user) to diagnose effect (good/bad/faster/slower/broken components...etc) of such slimmed versions. I know it runs fine for me in VM, (test software, run apps incompatible with Win 7, etc) I create a new CD every 4-6 months...mostly because I have a lot of free time & as an educational tool.

This post has been edited by PinkFreud: 17 August 2012 - 08:29 AM

[PinkFreud]

self-delete

This post has been edited by PinkFreud: 27 June 2012 - 08:59 PM