anonim1979

I NEVER had it in my files - I dont like to have something I know nothing about. And I haven't any problems with this setting missing. Who knows maybe a gross of errors is because of this setting Nah couldnt be ... It's only because it was in your driverpack cmd file I wanted to look at it closer.

@muiz Search Wow! What a briliant solution ! Did you try it by yourself before answering ? Because I DID *BEFORE* asking! ref.chm [help file] from Deploy.cab [for sp2] - NOTHING http://www.msfn.org/ - 63 posts and NO ANSWER - most people have it set but explanation what is it for exacly and if it even works .... http://unattended.msfn.org - nothing http://support.microsoft.com/default.aspx?...kb;en-us;293335 - nothing http://support.microsoft.com - NOTHING http://search.microsoft.com/search/results...b&c=4&s=1&swc=4 !!NOTHING!!! NOT A WORD on microsoft pages So maybe you ,my all knowing friend, will give my answer?

In slipstream_DPM.cmd You first remove alide REM ### Removing to be overwritten entries. ### REM ### [sourceDisksFiles] ### SET T1=nircmd.exe inidelval I386\txtsetup.sif "SourceDisksFiles" %T1% adpu160m.sys %T1% aliide.sys %T1% dac2w2k.sys But you dont add it again! REM ___[sourceDisksFiles]___ SET T1=nircmd.exe inisetval I386\txtsetup.sif "SourceDisksFiles" SET T12="~x201,,,,,,4_,4,1,,,1,4" REM ALI/ULI REM BUSEXTENDER %T1% "aliide.sys~x20" %T12% ^^^^^^^^^^^^ shouldnt it be removed? 1,,,,,,3_,4,1,,,1,4 1,,,,,,4_,4,1,,,1,4 What is the diference - 3_ disc 3rd 4_ disc 4th. Will this matter on computer which have ali controler [on computer without one there is no difference?]?

@Bâshrat After my aliide error with 5049 I started analysing your .com files step by step I found an error in run_me.cmd [not connected to aliide error] REM ### Edits the winnt.sif to set the DriverSigningPolicy. ### nircmd.exe inidelval I386\winnt.sif "Unattended" "~tDriverSigningPolicy" nircmd.exe inidelval I386\winnt.sif "Unattended" "~tNonDriverSigningPolicy" This lines do nothing due to ~t inisetval accepts ~t without problems but inidelval seems to have problems. Make test file: nircmd.exe inisetval .\test.txt "Unattended" "~tDriverSigningPolicy" "Ignore" nircmd.exe inisetval .\test.txt "Unattended" "~tNonDriverSigningPolicy" "Ignore" nircmd.exe inidelval .\test.txt "Unattended" "~tDriverSigningPolicy" nircmd.exe inidelval .\test.txt "Unattended" "NonDriverSigningPolicy" The result should be (if ~t worked OK) file without those lines but DriverSigningPolicy will stay. If you wanted to make sure that user have those valuses set to ignore you can probably use this: nircmd.exe inidelval I386\winnt.sif "Unattended" "DriverSigningPolicy" nircmd.exe inidelval I386\winnt.sif "Unattended" "NonDriverSigningPolicy" nircmd.exe inisetval I386\winnt.sif "Unattended" "~tDriverSigningPolicy" "Ignore" nircmd.exe inisetval I386\winnt.sif "Unattended" "~tNonDriverSigningPolicy" "Ignore" BTW anyone what exacly NonDriverSigningPolicy is for? For what kind of files it is used?

I have error with newest 5049 version aliide.sys entry damaged/missing under [sourceDisksFiles] during TEXT setup. I added one line aliide.sys = 1,,,,,,3_,4,1,,,1,4 and problem solved. - xp instaled without problems. System I have been using - laptop without any sata. I'm attaching 3 txtsetup files. Unmodified (clean XP SP2 no nlite etc.) file I'v got after using BASE 5049 and modified one. Those files are from polish win xp pro sp2! So some names are localised! txtsetup.rar

You could test what happend when you use bootvis after install with BTS driverpacks. Maybe some drivers are loaded in bad priority ? If bootvis change something post your results here. Of course if bootvis works with Win 2003.[i dont know for sure]

One more thing. I have a question to people who are using English WIN XP and dutch/portugese etc keyboard. You are setting your keyboard preferences in winnt.sif ? Nvidia drivers get instaled with langauge (not english) but of the choice of keyboard. Why not set english keyboard in your english windows CD/DVD. Let drivers install Change keybord AFTER silent instalation of drivers [using runonceex or something appropriate] by .reg[?] file Problem solved.? I think [i didnt check] it would be easiest way. So the only thing speaking for lite version would be spared place [not important on DVD but MAYBE usefull on CD]. SO I AM ASKING HOW MUCH WOULD BE GAINED? Bashrat can you answer this question ? How many MB [approximately] it would be in most lite version [ie. no language except english in ALL driver pack]?

NO. Waste of time for what few MB? How much smaller it will be 10MB less ? I would rather see Bâshrat fixing bugs / adding new drivers than wasting time/support/server space for lite version.

I posted it in diff topic. And haven't tested myself yet but you can try it. @bashrat maybe problem is because RD /S /Q %SystemDrive%\DP - if executed from .bat or .cmd file works ok - if you try runing this comand from RUN menu in Windows you will get RD file not found. cmd.exe /c "RD /S /Q %SystemDrive%\DP" - this comand works both from .cmd .bat and RUN menu I'm fairly sure error is because .SIF is traing to execute something like this rd.EXE /S /Q %SystemDrive%\DP - And this WONT WORK because there is no rd.exe using my line it would be cmd.exe /c "RD /S /Q %SystemDrive%\DP" - and this work - cmd.exe is present

@bashrat maybe problem is because RD /S /Q %SystemDrive%\DP - if executed from .bat or .cmd file works ok - if you try runing this comand from RUN menu in Windows you will get RD file not found. cmd.exe /c "RD /S /Q %SystemDrive%\DP" - this comand works both from .cmd .bat and RUN menu I'm fairly sure error is because .SIF is traing to execute something like this rd.EXE /S /Q %SystemDrive%\DP - And this WONT WORK because there is no rd.exe using my line it would be cmd.exe /c "RD /S /Q %SystemDrive%\DP" - and this work - cmd.exe is present

Type in you config Mamβ in start "Adding Mamβ to Power Users" /wait net.exe localgroup "Power Users" Mamβ /add Now check if you get Mamá account created Something like this worked for me in my local cmd files in deleting localised names. Different code pages are used.

Next conflict WindowsXP-KB886716-x86 and KB885894 sysmain.sdb is common, and there is no teling which one is newer (unlike dll no version number. Probably the one from KB886716 (since the fix is from february and the other one from 2004)

Waraxx method with Integrating kbxxxx35 mrxsmb.sys to mrxsmb.sys.SOMETHING Integrating kbxxxx50 mrxsmb.sys.SOMETHING to mrxsmb.sys Works the best and it takes ~10 sec - Move it on 1st page! The method described now on 1st page is