Total Commander VS WindowBlinds

Snowman · Post by *Snowman » 2004-09-15, 00:07 UTC

I have this annoying problem with TC when using WB:
TC randomly closes whenever WB is loaded. No error messages, no crash info, no nothing - it just closes. As soon as WB is unloaded, TC "behaves".

Is this happening to anyone else?!

(WinXP (clean install), no Service Packs, always the latest builds of WB)

I did search for a possible older thread on this topic, but the seach came up negative.

pdavit · Post by *pdavit » 2004-09-15, 15:24 UTC

I have been using WindowBlinds in cooperation with TC for almost three years now and have applied the combination on three MS OSs (Win98, WinME and now WinXP) and never experienced this type of problem.

It surprises me that your problem is there after a clean installation. Having said that a no SP operating system has definitely more bugs than an SP-ed one. Check also your graphics adapter drivers and your DirectX version since WindowBlinds is a graphically intensive software.

Snowman · Post by *Snowman » 2004-09-15, 23:22 UTC

I have never installed any Service Packs, gfxcard drivers are up-todate (as of a few weeks ago), DirectX version is also the latest.

But funny enough, it only started after TC got to v6. v5 and earlier version(s) have no problem - go figure..... Must be something else interferring, somehow. I might swing the problem by the WB coder, who i am in daily contact with (more or less) - it could all just be a local problem.

PS. WB isnt that demanding on the gfxcard, it's actually faster than the native XP MSStyle 'engine'

But still, it rather much depends on the skin in use, how much resources are used.

SanskritFritz · Post by *SanskritFritz » 2004-09-16, 07:19 UTC

Just a quick try: maybe the uncompressed version does the trick, who knows:
http://clubtotal.free.fr/index.php?dir=Releases/&file=tcmd603a_unpacked.exe.%2832bit%29.only.zip&PHPSESSID=1fc8198b509244331aa6216299923633

pdavit · Post by *pdavit » 2004-09-16, 13:43 UTC

Snowman wrote:PS. WB isnt that demanding on the gfxcard, it's actually faster than the native XP MSStyle 'engine'

This can easily be an advertising trick by Stardock. It may apply as you said based on the skin in use but certainly a native non skinned XP is faster than a skinned one whether it's internally skinned by XP itself or by external software like WindowBlinds.