nlite - RyanVM Integrator

[skinner36]

I am really new at all this and I am trying to digest all the information there is about integrating hot fixes etc. my question is, what is the difference between nlite and RyanVM's integrator?

Are they two competing products? Are they used in conjunction with one another?

Any help is appreciated

John

[ElSid]

Ryan's integrator is designed specifically to add/update/integrate/slipstream the base Windows XP CD

nLite is originally designed to tweak and remove unwanted XP components.

The confusing part is that nLite can also add/update/integrate/slipstream; however, if you are using RyanVM's update pack, it is recomeded to use the integrator, as RyanVM and the community can assist you in trouble shooting your disk, assuming you have not tweaked and/or removed unwanted XP components with nLite.

[skinner36]

many thanks for the repy

[nuhi]

Well I disagree, IF you are already using nLite then it is recommended to use it for the RVM pack integration as well. That way it will take care of sequencing and there won't be any room for mistakes.

[Madhits45]

I've always wondered do they both apply the updates the same way?

There must be a slight difference between them. When you use ryans with the integrator then nlite you get different size results then when you use nlite for the whole thing.

[bledd]

the way i do it is

use nlite to only integrate rvm pack, close nlite, re open, then do removals (otherwise you get a few languages left over)

[nuhi]

Madhits45, thing is with the CAB compression, if you don't remove any drivers and keep it big then that difference is visible. They do some sorting for better compression.

[RyanVM]

nuhi said it well. If you're going to use nLite on your CD anyway, just integrate the pack with it too (honestly, I don't know why even MaximumPC thinks otherwise). Just be advised that you're not likely to get much help from me or my forum if something doesn't work right since component removal adds another layer of complexity that I'm not qualified to troubleshoot.

[JoeGons]

Hi,

Will nLite and/or RyanVM sort out the mess here?

I am trying to Slipstream (Intergrate) SP2 onto my Gateway OS install CD. I can do a clean XP SP1

install with it now.

BUT,

I tried it the Microsoft way AND,

I get this error:

This Service Pack cannot be integrated into a destination that also has integrated Software Updates.

Consult the Service Pack documentation for more details about supported integration scenarios.

Microsoft says (but no solution):

You receive an error message when you try to integrate Windows XP Service Pack 2 (SP2) files into an

existing Windows XP distribution share

View products that this article applies to.

This Service Pack cannot be integrated into a destination that also has integrated Software Updates.

Consult the Service Pack documentation for more details about supported integration scenarios

If there are already some of the Fixes from SP1 which SP2 will duplicate, will there be a problem?

Thanks,

Joe

[bledd]

you only need to slipstream SP2, it includes all SP1 updates

[Gcentrex]

Look in your I386 folder and you proberly have a folder called "svcpack" and also look for svcpack.inf if you dont find that look for svcpack.in_ if it has svcpack.inf delete it and also the folder svcpack, then look for svcpack,in_ if its their. If not make a new file called svcpack.inf and add this text to it

[Version]
Signature="$Windows NT$"

[SetupData]
CatalogSubDir="i386\hotfixes"

[ProductCatalogsToInstall]

[SetupHotfixesToRun]

Save it compress it as a cab file and make sure its named SVCPACK.IN_ place it into your I386 folder then do integration, some OEM's add in service packs into their disks it was the same for my old HP laptop they integrated the CPU fix for laptops to use less power and some other ones I first has to remove those before integrating updating into the source.

[JoeGons]

Thank you.

I see the Files you mention.

I will try what you suggest and post the results.

How do I compress a "CAB" file?

Thanks,

This is what the .inf has now:

[Version]

Signature="$Windows NT$"

BuildNumber=2600

MajorVersion=5

MinorVersion=1

[setupData]

CatalogSubDir="i386\svcpack"

[ProductCatalogsToInstall]

q323255.cat

q327979.cat

q329115.cat

q329834.cat

q810243.cat

Q810400.cat

q810577.cat

q810833.cat

q814696.cat

q816509.cat

q816843.cat

q816982.cat

q331958.cat

q814995.cat

q816048.cat

KB282010.cat

Q329441.cat

KB821557.cat

KB823559.cat

KB824146.cat

Q328310.cat

Q329048.cat

Q329170.cat

Q329390.cat

Q331958.cat

Q810565.cat

Q811493.cat

Q811630.cat

Q814033.cat

Q815021.cat

Q817287.cat

Q817606.cat

Q819636.cat

Q819696.cat

kb821187.cat

KB822603.cat

dx9w2k.cat

dxnetsrv.cat

dxxp.cat

[setupHotfixesToRun]

q323255.exe /q /n /z

q327979.exe /q /n /z

q329115.exe /q /n /z

q329834.exe /q /n /z

q810243.exe /q /n /z

Q810400.exe /q /n /z

q810577.exe /q /n /z

q810833.exe /q /n /z

q814696.exe /q /n /z

Q816509.exe /q /n /z

Q816843.exe /q /n /z

Q816982.exe /q /n /z

Q331958.exe /q /n /z

Q814995.exe /q /n /z

Q816048.exe /q /n /z

KB282010.exe /q /n /z

KB329441.exe /q /n /z

KB821557.exe /q /n /z

KB823559.exe /q /n /z

KB824146.exe /q /n /z

Q328310.exe /q /n /z

Q329048.exe /q /n /z

Q329170.exe /q /n /z

Q329390.exe /q /n /z

Q331958.exe /q /n /z

Q810565.exe /q /n /z

Q811493.exe /q /n /z

Q811630.exe /q /n /z

Q814033.exe /q /n /z

Q815021.exe /q /n /z

Q817287.exe /q /n /z

Q817606.exe /q /n /z

Q819636.exe /q /n /z

Q819696.exe /q /n /z

KB822603.exe /q /n /z

kb821187.exe /q /n /z

DX9NTopk.exe

js56nen.exe /q:a

q330994.exe /q:a

q822925.exe /q:a /r:n

vbs56nen.exe /q:a

dotnetfx.exe /q:a /c:â€install /qâ€

WMP9_MM2.exe

SunJava.exe

KB819639.exe /q:a

Q820771.EXE /q:a

;Q823718.exe /q:a /r:n

Joe

Edited May 23, 2007 by JoeGons

[Gcentrex]

Seems perfectly fine to me, but I integrate the Ryan update packs instead of doing it the MS way as Ryan's method installs quicker and keeps the disk at about the same size, it good for my basic base disk.

Just be sure your extra addons are able to be run from the svcpack folder some are not able to just so you know.

As for making cab files that easy windows has a built in tool for doing that. It's called makecab a command line utility but easy to use none the less or you can make a cmd file like this and copy makecab.exe into the same folder as it.

@echo off
echo ================
echo Set File to compress
echo ================
set /P file=
makecab.exe %file%
echo ================
echo Compressing File
echo ================
echo.
echo ===============
echo File Compressed
echo ===============
pause

So with that you put the file into the same folder as makecad.exe and this cmd run the cmd and type in the file including extension you wish to compress and it will do it, simple really.

[JoeGons]

I'll try this

J

[JoeGons]

Gcentrex

All is working well.

Is there a way to create the Files in a different Folder?

Thanks

Joe

Edited May 28, 2007 by JoeGons