vinifera

then what if I do all manualy without using nlite just extract from RTM ISO contents into a folder, then manualy integrate SP3 with its switches, and do the same with hotfixes, and then whole folder just repack back to ISO and make it bootable ?

may I ask why its not good idea ? I mean, I wouldn't remove anything of any component, just add SP3 and hotfixes

yeh screwed topic anyways my question is, since soon is year 2011 and if I just nlite XP RTM + SP3 + all hotfixes untill 2011 is it smarter then later to use that "XP 2011" as nliting foundation, so I don't have to bother with keeping SP3 and all those hotfixes on disk or not ?

I call it bul*****, pardon my French

lately vlite starts to act weird on me I'm vliting win7 RTM and in folder where files are dumped BOOTMGR exists but as soon I make ISO with vlite, vmware starts with error any idea what causes this ? -------------------- edit: yep vlite doesn't copy half things anymore manual insert in ISO fixes issue

Intel for me got MoBos dying over the years, dropping down like flies only Intel outlived them all

Disktrix UltimateDefrag here been using it for 5 years, still the best in my eyes tho I dislike how their team makes crappy UI

thank you very much

I just wan't to know for this part <InputLocale>en-US</InputLocale> <SystemLocale>en-US</SystemLocale> <UserLocale>en-US</UserLocale> what to change for Croatian keyboard/sys locale and/or where to find this list for countries to change any info apreciated

just to add to sillyness of MS (this will look like advertising but is not , I always intend to recommend better soft that I know of) example of UltraSearch app, its free, but my main point is that it reads directly from $MFT, no indexing, no nothing one has to wonder why MS never did such thing, after all they were the ones that wanted instant search with Longhorn and then reverted to slow indexing again... also, sorry if this was not replies you wanted

just use alternatives Everything UltraSearch ... whatever they are all fast MS ones are slow, resource hungry and quite stupid

I'm trying to slim down PDC build 6801 but whenever I try, install is always broken on this point with this message: now, I don't care what will work when OS is installed, I just want it slimmed to be installed this is my session, if someone can see it (its not big at all), and tell me what is so **** sensitive there (had to use pastebin, attachment not working for me) http://pastebin.com/wV7dvxXv

thats bollocks they use "sample proof" image of Flight simulator for which has already been proved gizillion times it was fake closest thing to DX 10 on XP you will come if you find compatible DirectX 9L for Longhorn that is actualy compatible with srv2003 which I even doubt it can be

do you know if it resets only HKLM or some others too ?

you missed the whole point of my question

my question goes for Repair option when booted from CD except clearing whole Windows directory and putting original files back to it what else does it do ?

so this means that user actualy needs full bloat of 2, 3, 3.5 and 4 afterall ?

hehe believe it or not I did some sniffing and found that exact answer here on MSFN () btw quotes are necessary around %'s, ive noticed on PDF file it doesn't load in PDF viewer without them still thanks for answer, apreciate it

I get same result with just %1 and with %1 %* (no quotes on both cases)

for some reason when used unattended installation with $OEM$ batch file for T-13 time setting propper file associations fail simple example: for irfanview to open GIF file ASSOC .GIF=GIF.FILE FTYPE GIF.FILE="%PROGRAMFILES%\IrfanView\i_view32.exe" "%1" or PDF Xchange to open PDF's ASSOC .PDF=PDF.File FTYPE PDF.File="%PROGRAMFILES%\PDFXChange\PDFXCView.exe" "%1" if I do it manualy (type it in cmd window) it will work but why doesn't it do right with T-13 batch file ? i noticed in output window that "%1" doesn't get applied but just "" is added which I guess screws things up anyone know how to fix this things ?

remove winsxs and you have FUBAR OS

PDF XChange gets my vote

i've noticed that 2005 has some... issues... MS offers 3 versions to download redist 2005 redist 2005 SP1 and redist 2005 SP1 update but they seem to clash? with each other, the newer removes older while in 2008 case, both 2008 and SP1 co-exists bit odd

I'd like to add to my nlited installation Visual C++ redist's is it enough to just add 2005 SP1 and 2008 SP1 or ALL 2005, 2005 SP1, 2005 SP1 ATL security update, 2008, 2008 SP1 ?

some people say that 1.1 and 4 are enough since supposedly 4 covers CLR2 this true or all 1,2,3,4 are a must ?