[RELEASE] Boooggy's WMP 11 direct integration solution

Chrysalis · Post by **Chrysalis** » Mon May 19, 2008 11:39 pm

[quote="roirraW "edor""]

Chrysalis wrote:good app I used it on my recent sp3 test cd. Seems to have all worked but the hotfixes which I integrated after it using nlite do not show as installed hotfixes does anyone know if thats how its supposed to be?

Hotfixes for WMP11 or just in general - for SP3??? I would assume you mean for WMP11, however, you should have the WMP11 Slipstreamer integrating both WMP11 and all of it's current hotfixes listed on the WMP11 Slipstreamer home page, so there wouldn't be any need to integrate them separately using nLite.

Chrysalis wrote:Also as some feedback I got confused by the instructions for nlite, they say to add the installer inside nlite which I did and caused an error it meant the wmp11 exe file. Not the wmp11 slipstreamer.

Someone else may have to answer this as I use the WMP11 Slipstreamer as a separate application.

What I do know is that you have to have the WMP11 Slipstreamer installed, but I would think that you had done that. That's why I alleviate all confusion on my part and just use the WMP11 Slipstreamer separately, but I've just been too lazy to learn how to use it properly through nLite.[/quote]

Well the instructions dont say, the hotfixes are simply listed, nlite provides basic (very basic) instructions saying add wmp11 as a hotfix and nlite itself runs the slipstreamer to do the integration. Then it integrates the hotfixes itself after.

Chrysalis · Post by **Chrysalis** » Mon May 19, 2008 11:42 pm

[quote="roirraW "edor""]

n7Epsilon wrote:- For WMP11 hotfixes, we do not add registry entries to show Windows that the hotfixes have been installed because (Thankfully) Windows Update is smart enough to check the actual file version, so if no wmp fixes show on windows update, the fixes were integrated correctly.

[/quote]

Ok thanks but I prefer them to be listed as its peace of mind they installed.

anonim1979 · Post by **anonim1979** » Tue May 20, 2008 12:14 am

Bug info in 1.2 if you aren't dev you can skip reading this post.

From
http://www.ryanvm.net/forum/viewtopic.php?p=76404
(I'm posting it in 3 places so it won't be overlooked)

anonim1979 wrote:I dont think that second instance of:
napclientprov.mof
napclientschema.mof
should be modified like the first

I think that this part should stay as it is:
[WBEM.SYSTEMMOFS]
....
CmdEvTgProv.mof
dgnet.mof
whqlprov.mof ; wmi provider for whql to get driver signing info. a-kjaw
ieinfo5.mof
rsop.mof
rsop.mfl
wscenter.mof
napclientprov.mof
napclientschema.mof
The first is in COPY files section and is indeed missing 8.3 filename. So the instaler dont know from what 8.3 file copy that long filename files.

But second is in section that doesn't copy files and there are other not 8.3 names:
CmdEvTgProv.mof
there is no need to add references for source files in this section.

checked:
c:\WINDOWS\system32\wbem\Logs\setup.log
c:\WINDOWS\system32\wbem\Logs\mofcomp.log

Modified 2 instances (like 1.2 slipstreamer do)

(Tue May 20 05:34:31 2008): Beginning Wbemupgd.dll Registration
(Tue May 20 05:34:31 2008): Current build of wbemupgd.dll is 5.1.2600.5512 (xpsp.080413-2108)
(Tue May 20 05:34:31 2008): Beginning Core Upgrade
(Tue May 20 05:34:31 2008): ERROR: GetStandardMofs failed to locate file C:\WINDOWS\system32\WBEM\napclientprov.mof,napprov.mof.
(Tue May 20 05:34:31 2008): ERROR: GetStandardMofs failed to locate file C:\WINDOWS\system32\WBEM\napclientschema.mof,napschem.mof.
(Tue May 20 05:34:31 2008): Beginning MOF load
(Tue May 20 05:34:31 2008): Processing C:\WINDOWS\system32\WBEM\cimwin32.mof

One (like I recomended)

(Tue May 20 03:48:43 2008): Beginning Wbemupgd.dll Registration
(Tue May 20 03:48:43 2008): Current build of wbemupgd.dll is 5.1.2600.5512 (xpsp.080413-2108)
(Tue May 20 03:48:43 2008): Beginning Core Upgrade
(Tue May 20 03:48:43 2008): Beginning MOF load
(Tue May 20 03:48:43 2008): Processing C:\WINDOWS\system32\WBEM\cimwin32.mof

And they show properly in
c:\WINDOWS\system32\wbem\Logs\mofcomp.log

C:\WINDOWS\system32\WBEM\napclientprov.mof
(Tue May 20 03:49:25 2008.1242797) : Finished compiling file:C:\WINDOWS\system32\WBEM\napclientprov.mof
(Tue May 20 03:49:25 2008.1242807) : Przetwarzanie pliku MOF: C:\WINDOWS\system32\WBEM\napclientschema.mof
(Tue May 20 03:49:25 2008.1242857) : Finished compiling file:C:\WINDOWS\system32\WBEM\napclientschema.mof

kontini · Post by **kontini** » Wed May 21, 2008 4:44 am

New fix kb945381. It should replace kb942264. Bye

Stimpy · Post by **Stimpy** » Wed May 21, 2008 5:37 am

Thanks Kontini

rootworm · Post by **rootworm** » Wed May 21, 2008 6:14 am

First off, I'd like to report that after slipstreaming WMP11 on a clean disc with .991 I'm no longer having issues with Media Sharing. I must have figured out a way to screw it up on many many discs. Thanks to crashfly for also testing.

But I have a more serious issue to report. 1.2 of the slipstreamer is broken for me. When I use 1.2 on a clean source the resulting disc is missing Windows Media Player Network Sharing Service. Other than that WMP11 does function.

When I use .991 on the same exact source, with the same exact installer and hotfixes and the same options (Tweaked version, keep cats) I end up with a perfect result. (only difference is I patched SFC on this disc)

Host OS: XP SP3
Target source: XP Corp SP3 (clean) clean means all I did was throw winnt.sif on there after slipstreaming, that's it.

I made 6 different test images with 1.2, one of which was completely rebuilt from Gold. All results were the same. At first I blamed other addons so I did WMP11 only. Then I thought the problem was slipstreaming from a SP3 host so I tried in SP2 VM, no change. Then I thought maybe slipstreaming SP3 onto gold from a SP3 host had problems like doing it from Vista so I slipstreamed SP3 from a SP2 VM. No change. Lastly I tried WMP11 only with no hotfixes, but that didn't fix it either.

<File compare snipped>

n7Epsilon · Post by **n7Epsilon** » Wed May 21, 2008 8:23 am

I have identified the issue, it is due to a small bug in the IniParser that causes it to parse the key (which was stripped from quotes during processing) instead of the entire line with quotes as a CSV, so it was taking the value of the first quoted entity (in one of the INFs, this is the Network sharing service install line) and dropping the rest of the command line (which is the "install" parameter).

The end result was that the service was being launched without parameters and not installing.

I have fixed the issue in an internal build, and I am working on preventing it from happening again without notice (by having the CSV parser throw a warning when it encounters a malformed entity).

The fix will go in the next release (maybe later today), along with the fix for the Wbem issue.

Thank you for reporting it.

boooggy · Post by **boooggy** » Wed May 21, 2008 9:24 am

thx kontini
i will update the site just after we will release the new version.

Sanjay · Post by **Sanjay** » Fri May 23, 2008 12:48 pm

5. Removal of embedded uxtheme.dll and msobmain.dll hotfixes. Slipstreamer will break unattended and display a warning if it finds that uxtheme or msobmain need updating, integrate those fixes before running the slipstreamer to avoid this.

Now that the slipstreamer no longer contains KB908536 or KB894871, where can one find these hotfixes, since Microsoft no longer has them listed for download and one has to specially request them from Microsoft. Also, how exactly does one integrate them? Can they be integrated with the slipstreamer itself? Quite honestly it was a lot easier and simpler when the slipstreamer integrated these by default.

Thanks.

n7Epsilon · Post by **n7Epsilon** » Fri May 23, 2008 1:44 pm

You can find them on Xable's hotfix share. You can integrate either using nLite, or by integrating an update pack that contains these 2 fixes.

Also, note that this only applies to XP Service Pack 2 32-bit and MCE 2005 32-bit. XP SP3 32-bit already includes versions of these files that do not have any problems with wmp11.

We decided to do this for 3 reasons:
1. We used to embed the english versions of these fixes, and there are users out there with non-english XP and non-english WMP that need the version correct for their languages.
2. We are moving away from embedding any kind of MS file inside WMP11Slip, we are also looking to remove embedding KB913800 which is needed (and currently still automatically integrated) on MCE 2005 sources.
3. Most people now are using XP SP3 sources (you should too) so this would not impact a great number of users.

Currently RyanVM Update Pack (Post SP2) 2.2.2 contains the minimum allowed version of uxtheme.dll, but it doesn't contain the newest msobmain.dll, so integrate KB894871 with nLite before running the slipstreamer on your XP SP2 source.

Again I will say, if you are using XP SP3, then no need for them.

boooggy · Post by **boooggy** » Fri May 23, 2008 1:52 pm

new version out 1.2.3.0

changelog
fixed wbemoc.inf editing (thx to anonim1979)
fixed iniparser to parse an entire line with quotes as a CSV

also site updated
it contains latest wmp 11 hotfixes (up2date).

Gorki · Post by **Gorki** » Fri May 23, 2008 2:11 pm

Thanks boooggy!

Stimpy · Post by **Stimpy** » Fri May 23, 2008 3:06 pm

Thanks for all your hard work keeping this updated.

Botus · Post by **Botus** » Fri May 23, 2008 4:16 pm

boooggy wrote:new version out 1.2.3.0

thanks Boooggy, one question. The Link on your site gives a file to download called 1.2i ? is that the previous version?

runningfool87 · Post by **runningfool87** » Fri May 23, 2008 4:20 pm

n7Epsilon wrote:You can find them on Xable's hotfix share. You can integrate either using nLite, or by integrating an update pack that contains these 2 fixes.

Also, note that this only applies to XP Service Pack 2 and MCE 2005. XP SP3 already includes the newest files.

We decided to do this for 2 reasons:
1. We used to embed the english versions of these fixes, and there are users out there with non-english XP and non-english WMP that need the version correct for their languages.
2. We are moving away from embedding any kind of MS file inside WMP11Slip, we are also looking to remove embedding KB913800 which is needed (and currently still automatically integrated) on MCE 2005 sources.
3. Most people now are using XP SP3 sources (you should too) so this would not impact a great number of users.

Currently RyanVM Update Pack (Post SP2) 2.2.2 contains the minimum allowed version of uxtheme.dll, but it doesn't contain the newest msobmain.dll, so integrate KB894871 with nLite before running the slipstreamer on your XP SP2 source.

Again I will say, if you are using XP SP3, then no need for them.

how does this affect xp x64 users?

n7Epsilon · Post by **n7Epsilon** » Fri May 23, 2008 4:24 pm

It doesn't, the change only affects XP SP2 32-bit and MCE 2005 32-bit.

(We don't make any breaking changes without announcements, don't worry

).

ChiefZeke · Post by **ChiefZeke** » Fri May 23, 2008 6:04 pm

Botus wrote:
boooggy wrote:new version out 1.2.3.0
thanks Boooggy, one question. The Link on your site gives a file to download called 1.2i ? is that the previous version?

I just downloaded it and when run it shows as version 1.2.3.0

roirraWedorehT · Post by **roirraWedorehT** » Fri May 23, 2008 6:52 pm

ChiefZeke wrote:I just downloaded it and when run it shows as version 1.2.3.0

Movie Quote:

"...1...2...3...4...5"

"That's amazing, that's the same combination I have on my luggage!"

crashfly · Post by **crashfly** » Fri May 23, 2008 6:55 pm

[quote="roirraW "edor""]

ChiefZeke wrote:I just downloaded it and when run it shows as version 1.2.3.0

Movie Quote:

"...1...2...3...4...5"

"That's amazing, that's the same combination I have on my luggage!"[/quote]
It has been a while since I have seen Spaceballs. But even *I* remember *that* line.

roirraWedorehT · Post by **roirraWedorehT** » Fri May 23, 2008 7:04 pm

crashfly wrote:It has been a while since I have seen Spaceballs. But even *I* remember *that* line.

Then I'm glad because I was tempted to add as a hint:

"I see that your schwartz is as big as mine!"

TechnoHunter · Post by **TechnoHunter** » Fri May 23, 2008 7:07 pm

or the ever popular "We've been Jammed!"

-evil grin-

roirraWedorehT · Post by **roirraWedorehT** » Fri May 23, 2008 7:14 pm

LOL

Raspberry!

"We've got the bleeps, the sweeps and the creeps!"

P.S. Sorry, boooggy!

anonim1979 · Post by **anonim1979** » Fri May 23, 2008 11:04 pm

Bugs?
After 1.2.3.0

wbemoc.inf:

11,wbem,wbemprox.dll,"1 ; this needs to be the last core dll registered" ; this needs to be the last core dll registered

CmdEvTgProv.mof
dgnet.mof
"whqlprov.mof ; wmi provider for whql to get driver signing info. a-kjaw" ; wmi provider for whql to get driver signing info. a-kjaw
ieinfo5.mof
rsop.mof
rsop.mfl
wscenter.mof
napclientprov.mof
napclientschema.mof

and few more " put in unusual places (use compare in Total Commander for example)

----
EDIT:
(fixed my mistake)
And one more question
wmp.inf
1.2.0
[Run.PUI]
"%11%\rundll32.exe %11%\wpd_ci.dll","DoCmd remove rescan"

in 1.2.3
[Run.PUI]
"%11%\rundll32.exe %11%\wpd_ci.dll,DoCmd remove rescan"

(the other line with WMPNetwk is fixed properly)

Isn't it now (1.2.3.0) incorect? Or it WAS incorect and now is fixed?
It's ok in 1.2.3

ENU_user · Post by **ENU_user** » Fri May 23, 2008 11:23 pm

:txtsetup is changed with (removing spaces around "=")
so, i guess slipstreamer can be used last. due! to an incompatibility with nlite/RVMI & some newer or older addons that are using txtsetup edits....

though the only thing that should get parsed is the feed against the source as well as filtering changed or duplicate lines
but really! this shouldnt concern slipstreamer.

n7Epsilon · Post by **n7Epsilon** » Sat May 24, 2008 4:52 am

@anonim1979: Yes I know where this got broken, sorry about that, I sent boooggy the new release that fixes this and he will release it shortly.

@enu_user:
I think nLite can handle the edits I make correctly because it uses a very good parser that can handle these changes. The only thing that will be incompatible is addons that try to use extrafileedits and edit txtsetup.sif directly.

From the beginning that method is very fragile, and should not be used at all. Addons should use more robust methods (like obsolete_files) for example.

boooggy · Post by **boooggy** » Sat May 24, 2008 5:34 am

new version out 1.2.4.0

Changelog:
Fix for broken IniParser CSV line normalization. The bug affected a case where a non-quoted CSV line that had an inline comment that caused the last entity (including the comment) to be treated as part of the last entity found. (thx anonim1979 for found the buggie).

ENU_user · Post by **ENU_user** » Sat May 24, 2008 10:35 am

im not sure if consigning changes to txtsetup with one tool automatically brings others to adapt that quick... especially when they will need to add better code to maintain compatibility with this one that is already breaking some addons if used priorly ...

of course, if both nlite & rvmi adapt some of the same parsing spreading into other sections of txtsetup, this issue will be mostly gone but then addons in entries.ini should be parsed first not to have spaces around "=" between values (regardless).. before changes are merged .which I'm more for that anyways ...

thanks.

chiners_68 · Post by **chiners_68** » Mon May 26, 2008 12:43 pm

getting this error.

WMP11Slipstreamer v1.2.4.0
Detected source: Windows™ XP Professional SP3

Hotfixes:
windowsmedia11-kb928788-x86-intl.exe
windowsmedia11-kb929399-v2-x86-intl.exe
windowsmedia11-kb929773-x86-intl.exe
windowsmedia11-kb932390-x86-intl.exe
windowsmedia11-kb933547-x86-intl.exe
windowsmedia11-kb935551-x86-intl.exe
windowsmedia11-kb935552-x86-intl.exe
windowsmedia11-kb939209-x86-intl.exe
WindowsMedia11-KB939683-x86-ENU.exe
windowsmedia11-kb944110-x86-intl.exe
windowsmedia11-kb944882-x86-intl.exe
windowsmedia11-kb945381-x86-intl.exe
windowsmedia11-kb946665-x86-intl.exe

System.ComponentModel.Win32Exception: %1 is not a valid Win32 application
at WMP11Slipstreamer.Backend.StandardHotfixApply(String fixesFolder, Dictionary`2 hotfixFileDictionary)
at WMP11Slipstreamer.Backend.ApplyFixes()
at WMP11Slipstreamer.Backend.SlipstreamWMP11()
at WMP11Slipstreamer.MainForm.WorkerMethod(Object workerParam)

Extra error information:
Offending hotfix: windowsmedia11-kb946665-x86-intl.exe

Deleting "C:\AutoImageTmp\i386\wmp11temp"... Done!

The source being modified has not been damaged.
All changes have been successfully reverted.

n7Epsilon · Post by **n7Epsilon** » Mon May 26, 2008 12:47 pm

Please read the first post, this has already been answered many times.

Look at the error message you copied and pasted:

....
%1 is not a valid Win32 application
...
Extra error information:
Offending hotfix: windowsmedia11-kb946665-x86-intl.exe

chiners_68 · Post by **chiners_68** » Mon May 26, 2008 1:20 pm

Re downloaded from home it & works. easiest way to check is to open exe file with 7zip. if it opens its ok if not download from another location.
Tried about 5 times from work & it kept downloadin but wouldnt open.

download · Post by **download** » Tue May 27, 2008 7:59 am

n7Epsilon wrote:You can find them on Xable's hotfix share. You can integrate either using nLite, or by integrating an update pack that contains these 2 fixes.

Also, note that this only applies to XP Service Pack 2 32-bit and MCE 2005 32-bit. XP SP3 32-bit already includes versions of these files that do not have any problems with wmp11.

We decided to do this for 3 reasons:
1. We used to embed the english versions of these fixes, and there are users out there with non-english XP and non-english WMP that need the version correct for their languages.
2. We are moving away from embedding any kind of MS file inside WMP11Slip, we are also looking to remove embedding KB913800 which is needed (and currently still automatically integrated) on MCE 2005 sources.
3. Most people now are using XP SP3 sources (you should too) so this would not impact a great number of users.

Currently RyanVM Update Pack (Post SP2) 2.2.2 contains the minimum allowed version of uxtheme.dll, but it doesn't contain the newest msobmain.dll, so integrate KB894871 with nLite before running the slipstreamer on your XP SP2 source.

Again I will say, if you are using XP SP3, then no need for them.

I see where you going with this because SP3 dont need the hotfixes that errors out if you try and integrate them with SP2, but SP3 is'nt finalized 100% is it ?

boooggy · Post by **boooggy** » Tue May 27, 2008 8:09 am

sp3 is finalised..and it was released by microsoft on all thier services....

download · Post by **download** » Tue May 27, 2008 8:22 am

boooggy wrote:sp3 is finalised..and it was released by microsoft on all thier services....

Thanks for your fast reply

but why it's not on automatic update services?

Can you tell me what order i should do these..this is how i do it but pls correct me...

1. WMP11
2. Nlite Editing + Custom Addons including IE7
3. Driverpacks
4. Burn CD

roirraWedorehT · Post by **roirraWedorehT** » Tue May 27, 2008 10:45 am

As with Vista SP1, Microsoft has been releasing their Service Packs in a gradual way. If you manually go to Windows Update or Microsoft Update, you'll see Service Pack 3 listed. I don't know what date MS plans on putting it on Automatic Updates. I downloaded the redistributable copy of SP3 final more than a month ago.

FYI that's the order I do things. I also use the XP Post-SP3 Update Pack. Just one note. If you slipstream SP3, DON'T integrate IE7 as updates for IE7 won't work with integration under SP3. Instead, install IE7 after XP is up and running, then it will work as normal.

mr_smartepants · Post by **mr_smartepants** » Tue May 27, 2008 11:16 pm

[quote="roirraW "edor""]If you slipstream SP3, DON'T integrate IE7 as updates for IE7 won't work with integration under SP3. [/quote]

Really?

I've been integrating IE7 with nlite along with the new cumulative update (KB947864 released 6 May) and everything is fine here. Maybe I'm missing something. What are the symptoms?

BTW, Thanks Boooggy and n7epsilon! Your slipstreamer is awesome! And it just keeps getting better.

roirraWedorehT · Post by **roirraWedorehT** » Tue May 27, 2008 11:35 pm

Are you saying that you integrated IE7 and the new cumulative update? That's not the problem. The problem is that when more IE7 updates come out, they won't successfully install unless you reinstall IE7 from a standalone installer.

At least that is what the experience was that I had and some others I then read about on the internet if I used nLite to integrate the official MS standalone IE7 installer (no IE7 addon).

The symptom was that once the cumulative update came out, it would download and attempt to install, but each time installation would fail whether through Automatic, Windows, or Microsoft Update.

If you're saying that you integrated IE7 and that the new cumulative update successfully installed through AU/WU/MU after XP was installed, then what method are you using to integrate IE7?

pen25jf · Post by **pen25jf** » Wed May 28, 2008 9:36 am

Hi boooggy (or anyone that can answer),

sorry for a n00b question, but I always used your old add-on pack and ran the updates via SVCPACK. With the integrator, do I need to be online for it to work, i.e. get the updates? I do I just use it in nLite and it does it's thing offline?

Yeah, I know

hah

boooggy · Post by **boooggy** » Wed May 28, 2008 10:26 am

no...u dont have to be online.....
and slipstreamer works with files found on your pc...not online

pen25jf · Post by **pen25jf** » Wed May 28, 2008 10:34 am

great, thanks for the response booogy!

bober101 · Post by **bober101** » Sat May 31, 2008 9:36 pm

boooggy i have a question;does the new version of the slipstreamer fix the issues of the missing files when integrating on an sp3 source?i couldint find any change logs...thx.

boooggy · Post by **boooggy** » Sun Jun 01, 2008 3:12 am

bober what missing files?

if u talk about .mof files yes it is fixed....

bober101 · Post by **bober101** » Sun Jun 01, 2008 12:13 pm

yup thats what i was talking about.thx

rootworm · Post by **rootworm** » Mon Jun 02, 2008 12:53 am

download wrote:Can you tell me what order i should do these..this is how i do it but pls correct me...

1. WMP11
2. Nlite Editing + Custom Addons including IE7
3. Driverpacks
4. Burn CD

Personally I do not get a perfect WMP11 install unless I do it very last. I've been using this addon for a long time and I only now figured that out. (It was working fine but media sharing and DRM was messed up unless I added WMP11 last)

This slipstreamer is a brilliant piece of work, but from what I understand it's entries are very vulnerable to corruption by nLite and/or Integrator. (never figured out which one or if it was both)

boooggy · Post by **boooggy** » Mon Jun 02, 2008 3:07 am

i never had issues with nlite...and belive me i tested a lot.

chiners_68 · Post by **chiners_68** » Mon Jun 02, 2008 4:59 am

Hi Booogy,
on your forum you mention all the compatible OS's but you didnt mention XP Tablet? I presume its compatible..

roirraWedorehT · Post by **roirraWedorehT** » Mon Jun 02, 2008 5:18 am

rootworm wrote:
download wrote:Can you tell me what order i should do these..this is how i do it but pls correct me...

1. WMP11
2. Nlite Editing + Custom Addons including IE7
3. Driverpacks
4. Burn CD
Personally I do not get a perfect WMP11 install unless I do it very last. I've been using this addon for a long time and I only now figured that out. (It was working fine but media sharing and DRM was messed up unless I added WMP11 last)

This slipstreamer is a brilliant piece of work, but from what I understand it's entries are very vulnerable to corruption by nLite and/or Integrator. (never figured out which one or if it was both)

Glad you got that figured out. One question, were you able to do the WMP11 Slipstreamer even after DriverPacks, or do you not use DriverPacks?

twig123 · Post by **twig123** » Mon Jun 02, 2008 8:12 am

@boooggy - Could you please enlighten us as to the proper order that these steps should be done? I created a slip last night and upon completion trying to launch WMP I got an error that it was not installed correctly and to reinstall from the web.

is the correct order:
WMP
RyanVM Updates
nlite custom addons
DriverPacks

Thank you in advance for you time and effort towards this great project!

crashfly · Post by **crashfly** » Mon Jun 02, 2008 8:24 am

twig123 wrote:@boooggy - Could you please enlighten us as to the proper order that these steps should be done? I created a slip last night and upon completion trying to launch WMP I got an error that it was not installed correctly and to reinstall from the web.

is the correct order:
WMP
RyanVM Updates
nlite custom addons
DriverPacks

Thank you in advance for you time and effort towards this great project!

I am curious, if you are using nlite for custom addons, why do you not also use nlite it integrate drivers in with it? It would save a step or two (except for the step of uncompressing the drivers). Plus, except for the actual integration of WMP itself, the RyanVM updates can be included with nlite also.

twig123 · Post by **twig123** » Mon Jun 02, 2008 8:28 am

I use BTS DriverPacks Base for all of my drivers, instead of manually specifying the drivers to install with nlite, hence the extra step. Also, I have only a few addons that are supported by Integrator only... so I use both Integrator and nlite.

So is the above mentioned the correct order?

ccl0 · Post by **ccl0** » Mon Jun 02, 2008 10:30 am

twig123 wrote:
is the correct order:
WMP
RyanVM Updates
nlite custom addons
DriverPacks

my 2 cents:
i'd integrate rvm updates first. driver packs always last. stuff in between is kind of flexible