operating system not responding for 2 minutes when closing T

[arndt]

TC: version 7.03, 23.4.2008, registered
OS: WinXP64 sp2, US version set to AU local
TC installed to OS harddisk in C:\bin\wincmd\ (not on a USB stick)

repeatability of problem: 9 out of 10 cases

I always logon as a normal, non-administrative user.

Sometimes I need a shell with admin priviliges, hence I start TC via RunAs selecting the only administrative user (note: the name of the Administrator is not the default name but I don't think this matters).

I normally have a second copy of TC running as the normal user. It does not matter in which order I start these 2 copies as different users.

I then usually "do" stuff - if in the admin shell I do file operations such as editing, installing software, run anti-malware applications, or run regedit - pretty much anything more than just looking at things without write operations - then the OS will stop responding for about 1 minute and then be very very very slow for another minute when I close the LAST copy of TC running.

All copies of TC share the same ini file:
C:\WINDOWS\WINCMD.INI
File permissions on that file are set such that the normal user can also modify it.

Disabling all plugins does not make any difference.

Obviously this is very inconvenient - older versions of TC (6.50?) never had a problem with this scenario.

Any ideas?!
Thanks,
Arndt

[sqa_wizard]

Strange, never had this kind of stop responding.

You may disable your Antivirus for testing, before closing TC.

If this helps, you can exclude at least the WINCMD.INI from access scan (This is always accessed on close).
You may exclude TOTALCMD.EXE too. This is save, because TC has his own CRC check against modifications.

[Hacker]

arndt,
You can also check if it happens with a fresh.ini

Code: Select all

totalcmd.exe /I=c:\writable_dir\fresh.ini

HTH
Roman

[arndt]

Thanks for the suggestions!
I'll give it a try and report back.

Cheers,
Arndt

[ghisler(Author)]

Try using FileMon from www.sysinternals.com to find out what happens during these 2 minutes. I would also check first whether it's the virus scanner.