[submix8c]

BWAHAHAHAH!!!! You manually slipstream'd SP3 onto a pre-SP3 XP, right? Wonder how many other duplicates you have (compressed vs uncompressed)? nLite when SLIPSTREAMING A SERVICE PACK ONLY would have "cleaned up" for you...

edit - or... maybe not.
I will say that XP SP2 is 5.1.2600.2180. Better check your SOURCE!!! Something is not right...

edit2 - see this as well - TWO of you with same problem?
http://www.msfn.org/...view=getnewpost

I'm now bowing out... -X- this is your baby from now on...

This post has been edited by submix8c: 22 June 2012 - 02:16 PM

[O0o0O0O0o]

submix8c, on 22 June 2012 - 02:02 PM, said:

BWAHAHAHAH!!!! You manually slipstream'd SP3 onto a pre-SP3 XP, right? Wonder how many other duplicates you have (compressed vs uncompressed)? nLite when SLIPSTREAMING A SERVICE PACK ONLY would have "cleaned up" for you...

Impossible action. I have SP2 Home OEM. No Duplicate -






Please make no doubt with -X-, this is one time mistake as I do things very thorough. I believe I hit 'next' button after sp3 integration done but before the number changed.Either that or forgot to slip SP3 but doubtful,Im sure I remember it extracting and installing.

EDIT:

Quote

edit2 - see this as well - TWO of you with same problem?
http://www.msfn.org/...view=getnewpost

I read thread but seen no solution.

Edit again: I see solution now but don't like solution.

This post has been edited by O0o0O0O0o: 22 June 2012 - 04:35 PM

[-X-]

OK, now start again with a fresh source but this time, after sorting the updates by date move, with the up and down arrows on the right, KB978338 below KB2509553. Once done, tell me the version of tcpip6.

This post has been edited by -X-: 22 June 2012 - 04:55 PM

[O0o0O0O0o]

Ok I do as you say and this time In source there was tcpip6.sys file and it say version 5.1.2600.5935....

(Last time it say 5.1.2600.5625)

This post has been edited by O0o0O0O0o: 22 June 2012 - 08:45 PM

[-X-]

OK. You can take that nLited source and burn it and you should have a clean Windows Update. And you now know what to do in the future...put KB978338 below KB2509553.

The problem is your nLite is "broken". It should automatically use the higher version sys file without resorting to sorting. What version of nLite are you using?

It is also very strange that tcpip6.sys was expanded.

[O0o0O0O0o]

-X-, on 22 June 2012 - 09:45 PM, said:

OK. You can take that nLited source and burn it and you should have a clean Windows Update. And you now know what to do in the future...put KB978338 below KB2509553.

The problem is your nLite is "broken". It should automatically use the higher version sys file without resorting to sorting. What version of nLite are you using?

It is also very strange that tcpip6.sys was expanded.

Thank you -X-, for knowledge and patients.


Im using nLite v1.4.9.1 | Installer | 2.54 MB from nuhi's website.

I didn't sort updates before so Im going to have to go with "broken" theory .. No idea how that could happen but would explain how my SP3 didn't slip properly last session.



.

This post has been edited by O0o0O0O0o: 22 June 2012 - 10:19 PM

[-X-]

I doubt this will work but you could try installing nLite again over your installed one and then run some experiments with just those 2 updates. Put one before the other and see what version of tcpip6 is used. Then invert the sort and check again.

[O0o0O0O0o]

I uninstall nLite and reinstalled .

I Start with Fresh source,slipstream SP3,Done.
I go into source and TCPIP6.SY_ was there. I extracted and was tcpip6.sys file version: 5.1.2600.5512

(copy and pasted to desktop/ do not mess up source)



1.) I goto hotfix section and integrate "KB978338 below KB2509553" and TCPIP6.SY_ dissappeared and left behind tcpip6.sys file version: 5.1.2600.5935 ...

I Start with Fresh source again,slipstream SP3,Done.

2.) I try this other way around, KB2509553 below KB978338 and same TCPIP6.SY_ dissappeared and left behind tcpip6.sys file version: 5.1.2600.5625


I also integrated everything (fresh source) and didn't arange any updates except for "KB978338 below KB2509553" and that turned out correct. Is it possible that XP pro is different than Home when it comes to integrating ? I see you run pro 32.

[-X-]

Very strange. I'm at a loss to explain it. There's another member having the same problem. I seriously doubt that it's a XP Home problem.

[-X-]

I forgot I had a copy of XP home and did some experiments.

I was wrong. You were right. It's because it's XP Home. KB2509553 has system.adm. A file used for group policy. XP Home does not come with group policy so nLite uses the /integrate switch on that update..



I'll add a footnote for those 2 updates saying that KB978338 must be put below KB2509553 when the target source is XP Home.

This post has been edited by -X-: 23 June 2012 - 10:35 AM

[O0o0O0O0o]

Very good research and good find -X-, you do great work.

EDIT: Do You use vmare player ? I try installing one for 32 and 64 bit systems but still not able to install.

I'll research and see if a version I can use,unless better recommend ?

This post has been edited by O0o0O0O0o: 23 June 2012 - 11:56 AM

[submix8c]

O0o0O0O0o, on 23 June 2012 - 11:19 AM, said:

EDIT: Do You use vmare player ? I try installing one for 32 and 64 bit systems but still not able to install.

Maybe -X- does, I don't I use MS' VPC2007 (I said that). Again, your Integrated Drivers will ONLY install if the Hardware is There/Defined (else they are ignored). Alternatively, go the the Website I gave for VMware Player "Documentation" and Get-Those-Drivers and integrate them ADDITIONALLY (they interface to your REAL HOST OS Hardware+Drivers). Additionally, you can ONLY install an X64 system on X64 Hardware REGARDLESS of whether you "define" the Machine as X64 (unless VMWare "emulates" one). VPC2007 does NOT do X64 Machine at all! My CD's install XP 32-bit just fine in VPC2007... There is absolutely NO reason that XP 32-bit will be "not able to install"... you MUST be doing something wrong!!!

edit - OHHHH! Sorry, you are referring to being unable to install VMWare Player on your Host!!! Here are the PDF docs. It SHOULD install... Err-maybe not (see the "Getting Started With" PDF). Your Dimension 4600 is 32-bit only... It APPEARS that v2.5 will install/run...

v2.5.5 and drivers (documents for v2.5 in above link).

This post has been edited by submix8c: 23 June 2012 - 12:29 PM

[O0o0O0O0o]

I make mistake as it read "Run 32- and 64-bit virtual machines," not for 32 and 64 bit machines. ooops

Thank you to submix8c, I install v 2.5 as you say,very good .

This post has been edited by O0o0O0O0o: 23 June 2012 - 12:51 PM

[-X-]

I use VirtualBox portable. http://www.vbox.me/

[O0o0O0O0o]

-X-, on 23 June 2012 - 03:51 PM, said:

I use VirtualBox portable. http://www.vbox.me/

Oh I wish I would have used this before 5-6 installs.. haha Very excellent application.

(by the way,CD turn out great)

[O0o0O0O0o]

When integrating drivers with nLite,I know intel chipset go first but I read somewhere that network come second (maybe nuhi's guide can't remember) is this matter of fact or not matter a way that the rest of drivers integrate ?

Is there an optimal preference ?

[-X-]

Order doesn't matter.

[O0o0O0O0o]

I just got a WU update today 'KB2699988' but I know this didn't show up on this install when first integrated,check and double check,etc... nothing show up but until today.

I use registry ccleaner everytime I uninstall a few programs. Is this possibly a cause ? I know update integrated and was proper as I also test on VM.

[-X-]

KB2699988 contains some registry entries but I doubt a cleaner would have touched those. I don't recommend running registry cleaners. They can cause problems.

If it wasn't in fact cleaning the registry, I'm at a loss to explain why it showed up. That is if you haven't already applied it. Then we can check file versions.

[O0o0O0O0o]

-X-, on 27 June 2012 - 09:42 AM, said:

KB2699988 contains some registry entries but I doubt a cleaner would have touched those. I don't recommend running registry cleaners. They can cause problems.

If it wasn't in fact cleaning the registry, I'm at a loss to explain why it showed up. That is if you haven't already applied it. Then we can check file versions.

Err.. I do same thing and install because it was on pop up balloon and didn't think to check first,but no big deal, this cd perfect and first time it happen. I wait till next install but don't expect again.

I will stop using regcleaner but I thought ccleaner 'reg' section was less problem than others,such as reg mechanic,etc..... Anything that find 350 errors first time can't be good..

edit:

This post has been edited by O0o0O0O0o: 27 June 2012 - 12:31 PM