BoardBabe

Uh, okey and the relevance to topic is? As first post asks; how can I hide the tray icon? (Not how do I keep SetPoint from running on startup, I need SetPoint to run, but it's still possible to hide tray icon...)

Hehe ok, let's just terminate this topic. no one seems to understand what the topic is all about. I KNOW FINE HOW TO DELETE THE FILES! I'm just creating a list of left over files that you can ADD to your own cleanup if you please.

Where is the information stored wether systray icon should show or not. It's set default to show, and I'd like it to be hidden as default. Tried regshot with no luck.

Stick to the topic please.

Shouldn't that be OEAccess = Off

Is it possible to have windows NOT install outlook express?

Ok, let's make a list of files that can be deleted (during cleanup) after a fresh install of windows, such as *.tmp files *.log files etc. that are left behind by windows setup and are no longer needed after setup has completed (not including "Downloaded Installations" and %temp% dir nor regular cleanup stuff). Here's what I've got, please contribute: %WinDir%\*.log except WindowsUpdate.log %winDir%\*.bak %Windir%\system32\$winnt$.inf %WinDir%\setuplog.txt %winDir%\system32\wbem\Logs\*.log %winDir%\Debug\*.log %winDir%\security\logs\*.log %WinDir%\ntbtlog.txt %WinDir%\OEWABLog.txt %WinDir%\Debug\UserMode\userenv.log

Still show's up in wallpaper list.

I'm a bit annoyed that boot.bmp shows up at the list of desktop wallpapers at desktop properties. Is there anything I can do to prevent it from appearing on this list? Could eg. boot.bmp be moved away from %WinDir%? (PS. I delete all *.bmp from %WinDir% except boot.bmp atm.) -I'm very greatful for any solution to this topic...

No, you only need the .msi file. My method seems to work flawless. You do not need to click any icon, and MS AntiSpyware runs as normal as a background service, also with icon in systray after final reboot (or first boot after installing). Why make it more complicated than it needs to be? Only thing you might wan't to do is clean the shortcut's from start-menu an desktop, if you do not wish to keep those.

Uhm, okey Here's how I install it through WPI. cmd1[pn]=['"%cdrom%\\PROGRAMVARE\\MSANTISPYWARE\\Microsoft AntiSpyware.msi" /qn'] cmd2[pn]=['"%PROGRAMFILES%\\Microsoft AntiSpyware\\gcasDtServ.exe" /regserver'] Works flawless. -WinXP Pro SP2 NOR (all hotfixes)

Excactly, the code i provided skips the initial wizard too

Is there any way to get the KB895900 hotfix without the hassle of having to call M$? I believe I might need the norwegian version, as I run NOR xp.

Do you no longer have to run the %ProgramFiles%\Microsoft AntiSpyware\gcasDtServ.exe /regserver?

@fly2279: Excellent solution, but would'nt it be better to set the path to %temp% dir?

@Sonic: thank you. For all of you having the problem that some files and folders don't show up when browsing a computer on your LAN after installing the hotfix KB885250 here's the fix! If you don't care that WU/MU will nag you to install KB885250, then just don't install it and network browsing is fine. If you're like me and hate it when WU/MU nags about critical hotfixes integrate KB885250 to your UA media and replace mrxsmb.sys (%WinDir%\System32\drivers) with my modified version... download modified mrxsmb.sys here: http://rapidshare.de/files/7966320/mrxsmb.rar.html

KB885250 causing an error when browsing LAN computers (some folders are "hidden") The bug is in the latest mrxsmb.sys that this KB installs, I need to replace this with the old one from 13.4.2004 i believe. Can someone please post an mrxsmb.sys (system32\drivers) from a clean SP2 that DOES NOT have KB885250 integrated or installed? I need this "old" working mrxsmb.sys please...

Hehe that's pretty basic yeh. You ought to do some reading... This is one way to do it.... in a .cmd file. ofc you have to modify path and filename etc. @echo off for %%i in (C D E F G H I J K L M N O P Q R S T U V W X Y Z) do if exist %%i:\win51ip.SP2 set CDROM=%%i: copy /y "%cdrom%\path\to\registration.reg" "%ProgramFiles%\Bsplayer" exit If you also have to actually run the .reg file (implement to registry) then use the following: regedit /s "%ProgramFiles%\Bsplayer\registration.reg"

As I'm trying to say. I stronly believe there is something wrong with the isntaller, and NO SILENT SWITCH WORKING ATM.

gunsmokingman: that's a good point! But im guessing there's a reason it's in use? And should maybe not be deleted?

I'm not sure it's a bug no. But if you try run setup with /? it tells you /S is the silent switch. /S has worked fine up until now, so im guessing it's a bug. Guess the changes from 6.0.3 1.0.0.108 is not that important.

Aha, that's why theres two names Thank you, it's just what I need...!

By protected you mean write protected? I was thinking more like for /f "usebackq tokens=*" %%i in (`dir /b "%winDir%\*.log"`) do if %%i neq WindowsUpdate.log del /q "%WinDir%\%%i" Keeping the windows update log to see what's installed on MU/WU web, am I right? This would do the same as above vbs script I guess?

If you did a search you would find your answer in about 2 secounds (depending on your connection speed and hardware) as this has already been covered in previous posts... EDIT: Oh sorry! Did not see that you actually have posted in one of these previous posts... Then this would be a double post wich is against the rules. AGAIN that the latest DivxPlay/Create is bugged, and the /S switch (found as normal .exe /?) does not work. Wait for an update, use and old version or use AutoIt3 to install this version.

Seems theres a bunch of *.log files left after installation in %WinDir%, could all of these files be safely deleted at cleanup.cmd (I run cleanup after WPI), or is anyone needed or used later? Here's a list of .log files from %WinDir% right after install. 0.log chipset.log cmsetacl.log COM+.log comsetup.log DtcInstall.log FaxSetup.log GEARInstall.log iis6.log imsins.log KB834707.log KB867282.log KB873333.log KB873339.log KB883939.log KB885250.log KB885835.log KB885836.log KB886185.log KB887742.log KB887797.log KB888113.log KB888302.log KB888656.log KB890046.log KB890047.log KB890175.log KB890859.log KB890923.log KB891122.log KB891781.log KB893066.log KB893086.log KB893756.log KB893803v2.log KB894391.log KB896358.log KB896422.log KB896423.log KB896424.log KB896428.log KB896688.log KB896727.log KB898461.log KB899587.log KB899588.log KB899589.log KB899591.log KB900725.log KB900930.log KB901017.log KB901214.log KB902344.log KB902400.log KB903235.log KB904706.log KB905414.log KB905749.log KB906569.log MedCtrOC.log msgsocm.log msmqinst.log netfxocm.log ntdtcsetup.log ocgen.log ocmsn.log oobeact.log regopt.log sessmgr.setup.log setupact.log setupapi.log setuperr.log SetupWLD.log Sti_Trace.log SynInst.log tabletoc.log tsoc.log wiadebug.log wiaservc.log WindowsUpdate.log wmsetup.log