noxmetus

Was the issue solved? I do not use WindowBlinds since February, despite I paid for it.

When using WindowBlinds Total Commander's lister doesn't show the vertical scroll bar. Instead of it there is a just one big vertical white rectangle, which is not responsive to the mouse at all and actually paints above non-client area of the window. Normal lister: With WindowBlinds: <img src="http://pix.academ.org/img/2010/03/01/b92df93e7736120e0b143d093161d6f7.jpg"

[quote who="Neil Banfield" reply="11" id="2552500"]We know exactly what the issue is, but unfortunately it requires an update to a file thats got some very special signing requirements which is why the latest WB release did not resolve the problem. There is something about TakeCommand thats causing a deadlock in the process load when WB loads up some other dlls (note that this isn't being called from DllMain which obviously could cause such issues). No other app has ever show

[quote who="Hankers" reply="10" id="2552452"]noxmetus - Do you have a trouble ticket number from support? If so, please post that number here.[/quote]I haven't created a ticket for this particular issue, since the support showed itself sometimes useless. I posted the issue directly here. There is another issue I've submitted a ticket for and I had no response from the support other than check the installation. Are you interested in its number?

Why it is always like this with not free software? Whenever you offer your help to solve a problem with their software, tech guys just silently dissappear. It seems like they are never interested in solving problems. As strange as it may sound it is very often much easier to get real help with free and open source sofware. I found several bugs in WindowBlinds, beginning from visual artifacts, ending up with compatibility problems. All that the support could offer is an advice to check my inst

[quote who="Neil Banfield" reply="7" id="2529782"]Unfortunately the logs attached to that post require forum access and they appear to have manual procedures for accepting new accounts so right now I cannot access any of the files.[/quote]Neil, if you really want to investigate the issue, I can send you whatever logs you want, help with debugging, tracing and nailing down the problem. [quote who="Neil Banfield" reply="7" id="2529782"]What OS are you using?[/quote]I am using Windows

[quote who="DrJBHL" reply="5" id="2529305"]My error. I thought it determined boot sequence. Perhaps if you alter your boot sequence to have WB start and fully finish booting before Take Command boots (or just not have it in your startup programs but rather open only when you need it) the problem will be resolved.[/quote]As far as I understood, the word "startup" not necessarily means startup of Windows or PC. I am sorry if I was wrong. I meant the launch of Take Command. It has nothing to do

[quote who="DrJBHL" reply="2" id="2528925"]I might be asking a stupid question, but might you also be having too much starting at once.[/quote]What do you mean? [quote who="DrJBHL" reply="2" id="2528925"]Seems to me that perhaps Take Command could delay the start of other programs until after WB is fully loaded.[/quote]It knows nothing about WB, which is right, how possibly it can delay anything until WB load? [quote who="DrJBHL" reply="2" id="2528925"]If you opt to start

[quote who="Neil Banfield" reply="1" id="2528893"]If the app hangs on startup and it is excluded then chances are the problem is in Take Command not WindowBlinds.[/quote]But it works absolutely fine without WindowBlinds. And even those times when it doesn't hang, it works several times faster without WindowBlinds! That's for sure. I checked it several times. I analized the stack trace of the hanged threads. They indicate that the hang occurs during CreateWindowEx call. I adres

There is a nice and powerful command line processor called Take Command, written by JPSoftware (the successor of famous 4dos and 4nt). With WindowBlinds installed it sometimes hangs on startup. Excluding it from skinning doesn't help. I finally had to uninstall WindowBlinds completely. It is already 7th version of WindowBlinds and it still has a lot of compatibility problems. Maybe it is worth to stop issuing new versions and try at last to debug the old ones?