The "Total Commander 6.50 affair" is solved, but for educational purposes
:
...Stopping the services and killing ashDisp is rather a "big" action...
Simply stopping resident providers did not helped - I had to stop (rather gently
via services.msc) all Avast ! services. Killing "Blueball" was "just in case"
...he should write avast! Home Edition, especially because we are talking about both products...
Yes, You are right, I should be more precise, especially when "reporting bugs". I apologise - it will never happen again
Have you tried downloading Total Commander 6.50 from some other source ?
Yes, I tried all links from
www.gishler.com download section
Are you logged in Windows under account with administrator rights ?
Yes
...The Total Commander lockup was repeatable with the previous VPS? How many times did you try?
I didn't try to install TC 6.50 with previous VPS because I've noticed and downloaded newest version of TC yesterday (20.01.2005) - just after AVAST! automatically updated VPSto 0503-1.
To sum it up: if it wasn't avast, then I don't know what was that
- clean (no virusers and other "guest") and fresh (few days) installation of XPSP2 Prof
- no unusual and unneeded services and backgruod processes (only Zone Alarm Pro and services needed for running Win XP connected to internet via ADSL0
- previous TC (6.03) instance uninstalled (in fact first backed up to another partition and then uninstalled)
- installer downloaded several times from diffrent locations (no download manager, just Firefox 1.0). All identical, thesame CRC strings
- no NTFS privileges mess-up - I've checked it carefully
- Avast! - except this infelicitous TC and some false alarm with "..\FlyakiteOSX\misc\utilities\DeleteSource.exe" file - but this is for another topic
(this time
I asked some of my friends
)seems to work OK
- 0503-2 - my problems dissapeared...
So, what was that - WFM or "S*it happens"
Anyway - this topic may be closed, thanks all for Your help