xable.net

Darren

(aka xable)

Re: SP2 Update Pack January Edition Support

No worrys YikxX - If your haveing trouble with nLite though you should make sure it`s not just a one off and then report it to nuhi with steps to reproduce it. nuhi has to know about bugs to be able to fix them.

maly

Member

Re: SP2 Update Pack January Edition Support

Hi, im just wondering as i'm a non-trust person why does your pack need .sys and other unecasary windows files eg. Explorer.exe?

Im not being rude or ignorant i just usually use my own imported updates as i said i dont really trust that many people with all this new terrorist software like (pro-rootkits, trojans, malware and every malicous thing known to a computer)

thanks pls reply

Darren

(aka xable)

Re: SP2 Update Pack January Edition Support

lol you must be haveing a laugh.. if your not I appologise but you are being quite ignorant. Why wouldn`t my pack include the files which update windows? Seen as that is it`s exact purpose.

maly

Member

Re: SP2 Update Pack January Edition Support

OK, thanks sorry for any inconvenience.

Darren

(aka xable)

Re: SP2 Update Pack January Edition Support

No trouble at all. and your right to be wary of anything other than an update pack that includes core system files.

odellkevin

Member

Re: SP2 Update Pack January Edition Support

Hi, just did a fresh install of XP Pro Corp with SP2 UDP slipped with nLite, the only things windows update shows is IE7 (don't want it), WGAN (don't want it), and KB936357 - an Intel reliability update. Anybody know what this is? Why it's not in the pack? And do I need it? Also, (this probably belongs in another post, but) can anyone recommend a good & recent DirectX addon? Cause normally, when I build a disc, I just add in drivers, UDP, and DirectX. Thanks.

Darren

(aka xable)

Re: SP2 Update Pack January Edition Support

936357 is a hardware specific update and doesn`t show on windows update for me. That`s why it`s not in my pack. It addresses specific hardware related issues, read it`s KB article to decide whether you need it or not. Also, updateing your BIOS may negate the need for this update.

ITinerant

Member

Re: SP2 Update Pack January Edition Support

xable; You da Man!

gn!uz

Member

Re: SP2 Update Pack January Edition Support

Thanks a lot for this updatepack.
Having some questions..
When I click on Add/Remove Windows Components I receive an application error with a reference to xudpack.inf file... Please explain what process uses this inf and why it has a reference to add/remove windows components...
It appears the xudpack.inf does not exist in the INF folder. So is the reference in the txtsetup.sif correct?

Are there any other 'tags' that refer to you (Xable) other than the one in udpack.inf?

Can you share the source for xhelper.exe? What does it do precisely?

Once again, many thanks for making this as smooth as possible. It's just that I'm extremely cautious when it comes to implementing this on a larger scale. I have to know what's happening under the hood.

I've done several tests on a clean XP SP2 image. After installation I still get some required updates. After installing these I get more updates to install. A couple of which should already be part of your collection. Weird.. HAve to dig into this a little more though!

WindowsXP-KB896344-v2-x86-ENU.exe
WindowsXP-KB900485-v2-x86-ENU.exe
WindowsXP-KB904942-v2-x86-ENU.exe
WindowsXP-KB920342-x86-ENU.exe
WindowsXP-KB920872-x86-ENU.exe
WindowsXP-KB920872-x86-NLD.exe
WindowsXP-KB925720-x86-ENU.exe
WindowsXP-KB925876-x86-ENU.exe
WindowsXP-KB936357-v2-x86-ENU.exe
WindowsXP-KB942763-x86-ENU.exe

Once again, thanks for your hard work.. Slipstreaming all post-sp2 hotfixes manually is a bitch and you make it so easy for us. I hope you understand my point of view!~:)

Last edited by gn!uz (01-02-08 04:13)

Darren

(aka xable)

Re: SP2 Update Pack January Edition Support

Many questions many answers...

XUDPack.inf adds all the registry entries for the updates.

XHelper.exe is an autoit script, all it does is remove XUDPack.inf as the inf is useless after it`s done it`s job adding the registry entries. You can decompile XUDPack.exe with the decompiler included with autoit, it`s not pass protected and is really easy to do. Just point the decompiler at the script and choose where to save the output.

Removing XUDPack.inf (as you can see when you decompile the script) involves deleting it and it`s pnf  from the inf directory and removeing the referance to the inf from sysoc.inf.

If XUDPack.inf has been deleted but sysoc.inf referaces it, you will get that error when opening Add/Remove Windows Components.

Something is not right if the inf has been deleted but not the referance to it in sysoc.

So, you say you`ve been using a clean XP SP2 image. Make absolute sure it`s virgin and just add the pack, nothing else, then test it. If you have more than expected show on windows update and/or you get that application error, post nLite`s ini from that session and the contents of sysoc.inf from the install after setup, not from the CD.