nlite 147, just turn off/on components not remove them?

[mikesw]

I realize that Nlite 1.4.7 can delete components from the slipped OS; however,

the MSFNunattended pdf manual specifies a section where one can modify the

[Components] section of the SVCPACK.INF to turn on or off various components.

It also gives a list of things that can be turned on/off.

So,

[Components]

msmsgs=off

will allow me to disable installing MSoft messenger 4.2.x when I install the OS.

I don't want to delete the component, but just prevent it from installing.

Is it posible to add this functionality to Nlite so one gets presented a list of items that one

could check to turn "on" or "off" that functionality?

For another case, if I go to the delete Components list of Nlite, I see that I get presented a list

whereby one item is called "MSXML 2.0 (old version) that I could delete. However, I thought

with Win XP OS SP3, that it integrated in MSXML v6.0 and that MSoft had removed this old version by

overwriting the files that pertained to MSXML. Hence, shouldn't this message really be MSXML 6.0

and not 2.0? If 2.0 doesn't exist anymore, shouldn't Nlite not display this as a component to delete from

the OS slipped build?

A third case is, I tried to integrate the "rootcert_upd.exe" into the OS. It is a win32 cab. The switches

are /Q /T:<directory> /C . During the integration, NLite complained that the typical switches for win32 cabs

didn't work. This is true, but is it possible that when an error conditon is detected, that it would display a

popup to ask me if I wanted to enter the correct switches for a given piece of software, such that when

I select "yes", a data field entry is displayed next to the filename I'm trying to integrate so that I can enter them?

In this case, a "/q" or "/Q", or just let it default to nothing - just do it by entering the file without switches.

If "no", or if the list of entered switches is wrong (which then displays the yes/no popup

box), that it will just then continue on with the integration. If the switches are correct, then the filename along with

the switches I entered will then be written to the SVCPACK.INF file with the file put in the SVCPACK directory. This will

save me time of manually entering them by hand. Yes I know of the Runonce, batch file methods and the

others, but I want to use the SVCPACK.INF file for all MSoft software that deals with updating the OS

only (not apps). This would apply to windows script v5.6, future mdacs, mmc too which aren't part of the new SP3.

This could also be used in the case of MSoft Media Player 9.x or 10.x (if one doesn't use the WMP 11 slipper) which

wouldn't have any switches. These older Mplayers are needed on older Win OS' than xp.

A forth case is, anybody know or think about writing a slipping application like Windows Media Player 11 to slip

MovieMaker, Mplayer 9.x (i.e. win 2K), mmc, windows script, driectx9c, communicator (by replacing messenger) into the

windows OS directly by replacing the old files? Yes, I know about the Ryanvm packs, SVCPACK.INF way, but I'd

like something like what the WMP11 slipping tool does, but direct integration.

Edited July 14, 2008 by mikesw

[mikesw]

A forth case is, anybody know or think about writing a slipping application like Windows Media Player 11 to slip

MovieMaker, Mplayer 9.x (i.e. win 2K), mmc, windows script, communicator (by replacing messenger) into the

windows OS directly by replacing the old files? Yes, I know about the Ryanvm packs, SVCPACK.INF way, but I'd

like something like what the WMP11 slipping tool does, but direct integration.

For the fourth case dealing with directx 9c and all the monthly updates (the same steps apply when reupdating

older directx 9c updates, I came across this from 2003 on msfn although some of the disabling or deleting of wmp player and sfc could be removed from the steps if one wants.

Perhaps this direct integration can be added to Nlite instead of current method. Here are the links:

http://www.msfn.org/board/Replace-DX8-inst...all-t10665.html The original steps

Note: Directx 9 came with Win XP SP2, but the above steps can repeat for directx 9 monthly updates.

http://www.msfn.org/board/Replace-DX8-inst...aded#entry79070

This provides a zip file whereby the contents are already setup per the readme.txt file. Maybe nlite can

do this without having predefined files ready to go though.

Hmmmm, will any of these steps apply to Win 2000 also?

What about with directx10, any difference in the steps?

instead of using the ".reg" files to load the registry, the steps could convert it to directx.inf instead.

Edited July 14, 2008 by mikesw