vinifera

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 ?

has anoyne tried using ReactOS lately ? I personaly hate where vista and anything above went seeing only XP/srv2003 being last good OS-es come from MS I consider jump to ReactOS when XP's loses its support and by then I hope they will release the "everyday use" version

it could be some malware if your scanners can't find anything my recomendation would be repair (not format) of OS then again thats only my opinion usualy explorer.exe takes high resource if something of 3rd party is hooked to it and using it

problem is I can't regshot since .net I wish to "give" to XP would be from Longhorn build 3718 and I think its early .net version differs from final ones

and copying just folders won't do anything at all ? I mean, sometime when an app requires dll and user downloads it and puts it into same folder it will work...

bare with me in this situation if i didn't install .net (1.1 or 2, no matter), but just copied folders from \Windows\ directory (assembly, Microsoft.NET and WinSxS) from another installed XP that had .net installed what needs to be done, to "register" that components so windows can see them and use them ? and do i need to export/import some reg entries ?

could be ntkrnlpa.exe as its identical to boot screen

ok then thanks

yes i know the last SP is enough i was just worried as in past, i came across discussions (on net) that some people consider it is safer to do slipstream of SP3 ontop of XPSP2 rather than ontop of XP RTM dunno was it some security issue paranoia or did they had valid reasons so i asked here if it makes no difference or is there something init

sorry for sucky title i am just curious is it ok to slipstream XP's SP3 over XP SP0/RTM source or is it "wiser" to do it over XP SP2 or it doesn't make any difference ?

thanks

is this something serious ? will i have problems connecting to internet or LAN (i only test it in vmware)? or i can ignore this ?

in event viewer i have some weird events happening i slipstreamed XP RTM (SP0) and SP3 and added all hotfixes till this month this is what i am getting anyone have idea what it means ?

yea i have that already thanks for reply

got a question does FFDshow works in combination with XP's default WinMediaPlayer 9 or integrating it just with that player is useless ?

the only way i would do it, is to search dll or exe file that contains that icon (small shield) and replace it with blank icon, then icon would still be attached to UAC protected "icons" but it would be blank/invisible

oh this is nice thank you for answering