Like flash says, problem solved as far as I’m concerned too, so this will probably be the end of this thread for me.
Thanks for all your views and ideas.
Wouldn’t say no to a link to that thread you found though flash (avast.ini)
I’m happy now to allow RPCSS to run, but still without the Rpcltscm.dll. (It DOES work for me lol)
VLK is right when he says it’s required for the virus chest, with RPCSS disabled you are unable to move a file to the chest, so if you wanna use that function, or if any other program needs RPCSS, leave it running.
I think it’s clear now that avast does not need to start this server to function, VLK backs this up, but IS wrong about RPCSS being enabled as default.
As pcb pointed out, your program STARTS the RPCSS process on our OS.
If I disable your software, RPCSS does NOT start on my machine.
Avast may not use the networking side of things, but when RPCSS starts, it also then kicks off a load of other services, including the dll I mentioned which STARTS THE SERVER which DEFFO LISTENS ON PORT 135 (trust me! lol).
By the way, I’ve now blocked all incoming blue bitmaps from passing through the firewall just to be sure (I AM that paranoid lol)
Anyway, if you think think this thread is long, check this out!
http://computing.net/windows95/wwwboard/forum/3943.html.
Gives a lot of theories including a conspiracy theory that suggests 135 is opened so Microsoft can check on piracy!
(Woooooahhh, now I really AM worried! lol)
A far more productive and extremley informative page can be found at http://www.cexx.org/rpcss.htm
C’y’all soon.