#StackBounty: #windows #windows-10 #google-chrome #autohotkey Disabling the WS_CAPTION flag does not work for chrome apps opened as win…

Bounty: 50

For years I’ve been using the ahk script below to disable the WS_CAPTION (long 0x00C00000) flag on Windows 10 applications windows in order to make their title bars invisible. The most common case of usage is for chrome apps opened as window.

LWIN & MButton::
MouseGetPos,,, WinUMID
WinSet, Style, -0xC00000, ahk_id %WinUMID%

I’m not sure if it’s because of my Windows update or Chrome update, but this does not work for chrome apps opened as windows anymore. It still does work for other applications, though. I’m pretty sure there is no problem with my script, because I never change it. Also, my AutoHotKey didn’t update, so I guess there is no problem with it as well. I’ve filled a bug report for chrome (I think they don’t provide reporters an url), even though I’m not sure it’s their problem. Does anyone also have this issue or know what could cause it?

As asked by 3D1T0R, here’s a screenshot of a current window that this script used to work on.
screenshot of a current window that this script used to work on

Thank you very much.


Get this bounty!!!

#StackBounty: #windows #cache Transparent Caching on Windows – expiry time

Bounty: 50

I tried to use Transparent Caching on Windows for accessing large (100s MB) files from Network drives. First tests are very promising. It can reduce reading all tested files from 3.5s to 0.3s.

The problem is that the cache is invalidated very quickly. From what I’ve tested, after ~10 seconds.

Is it possible to control how long the cache persists? How the system knows the cache needs to be reevaluated? Maybe it can be caused by SMB setup.


Get this bounty!!!

#StackBounty: #windows #svn #tortoise-svn Why can't I execute a client-side hook script when committing a switched path?

Bounty: 50

I have got an SVN repository (version 1.9.2), and I am using a TortoiseSVN client (version 1.9.2) on a Windows 7 (x64) machine. There are client-side hook scripts (start-commit, pre-commit and post-commit), which are stored within the repository and of course available in the local working copy. They scripts are installed by using the special properties tsvn:startcommithook, tsvn:precommithook and tsvn:postcommithook, each pointing to the respective script file using the %REPOROOT% variable to avoid having to specify the absolute working copy path.

When I commit changes to the repository, the hook scripts (batch files, .bat) all work fine.

However, when I try to commit changes to files in a switched path, the following error appears:

And the commit cannot be done after confirming the message, the commit dialog does not appear.

I believe this error is not triggered by the hook scripts (because there is no change when I write exit 0 or exit 1 into the scripts as the only command), but by TortoiseSVN when trying to execute them, which, for some reason, seems not to be able to find the respective script any more.

So how can I use hook scripts that are located in the repository and hence in the working copy?


Replacing the variable %REPOROOT% by full absolute paths does not change the behaviour at all.

When I replace variable %REPOROOT% by %REPOROOT+% in the tsvn:*commithook properties, nothing changes for switched paths (so the aforementioned error message appears), but for standard paths, no hook script is executed and there is no error message after all.


Just as a side note: to verify whether or not a hook script is attempted to be fired, I rely on appearance of the approval/reject dialog of TortoiseSVN:
Approve or reject client-side hook script


Get this bounty!!!

#StackBounty: #windows #svn #tortoise-svn Why can't I execute a client-side hook script when committing a switched path?

Bounty: 50

I have got an SVN repository (version 1.9.2), and I am using a TortoiseSVN client (version 1.9.2) on a Windows 7 (x64) machine. There are client-side hook scripts (start-commit, pre-commit and post-commit), which are stored within the repository and of course available in the local working copy. They scripts are installed by using the special properties tsvn:startcommithook, tsvn:precommithook and tsvn:postcommithook, each pointing to the respective script file using the %REPOROOT% variable to avoid having to specify the absolute working copy path.

When I commit changes to the repository, the hook scripts (batch files, .bat) all work fine.

However, when I try to commit changes to files in a switched path, the following error appears:

And the commit cannot be done after confirming the message, the commit dialog does not appear.

I believe this error is not triggered by the hook scripts (because there is no change when I write exit 0 or exit 1 into the scripts as the only command), but by TortoiseSVN when trying to execute them, which, for some reason, seems not to be able to find the respective script any more.

So how can I use hook scripts that are located in the repository and hence in the working copy?


Replacing the variable %REPOROOT% by full absolute paths does not change the behaviour at all.

When I replace variable %REPOROOT% by %REPOROOT+% in the tsvn:*commithook properties, nothing changes for switched paths (so the aforementioned error message appears), but for standard paths, no hook script is executed and there is no error message after all.


Just as a side note: to verify whether or not a hook script is attempted to be fired, I rely on appearance of the approval/reject dialog of TortoiseSVN:
Approve or reject client-side hook script


Get this bounty!!!

#StackBounty: #windows #svn #tortoise-svn Why can't I execute a client-side hook script when committing a switched path?

Bounty: 50

I have got an SVN repository (version 1.9.2), and I am using a TortoiseSVN client (version 1.9.2) on a Windows 7 (x64) machine. There are client-side hook scripts (start-commit, pre-commit and post-commit), which are stored within the repository and of course available in the local working copy. They scripts are installed by using the special properties tsvn:startcommithook, tsvn:precommithook and tsvn:postcommithook, each pointing to the respective script file using the %REPOROOT% variable to avoid having to specify the absolute working copy path.

When I commit changes to the repository, the hook scripts (batch files, .bat) all work fine.

However, when I try to commit changes to files in a switched path, the following error appears:

And the commit cannot be done after confirming the message, the commit dialog does not appear.

I believe this error is not triggered by the hook scripts (because there is no change when I write exit 0 or exit 1 into the scripts as the only command), but by TortoiseSVN when trying to execute them, which, for some reason, seems not to be able to find the respective script any more.

So how can I use hook scripts that are located in the repository and hence in the working copy?


Replacing the variable %REPOROOT% by full absolute paths does not change the behaviour at all.

When I replace variable %REPOROOT% by %REPOROOT+% in the tsvn:*commithook properties, nothing changes for switched paths (so the aforementioned error message appears), but for standard paths, no hook script is executed and there is no error message after all.


Just as a side note: to verify whether or not a hook script is attempted to be fired, I rely on appearance of the approval/reject dialog of TortoiseSVN:
Approve or reject client-side hook script


Get this bounty!!!

#StackBounty: #windows #svn #tortoise-svn Why can't I execute a client-side hook script when committing a switched path?

Bounty: 50

I have got an SVN repository (version 1.9.2), and I am using a TortoiseSVN client (version 1.9.2) on a Windows 7 (x64) machine. There are client-side hook scripts (start-commit, pre-commit and post-commit), which are stored within the repository and of course available in the local working copy. They scripts are installed by using the special properties tsvn:startcommithook, tsvn:precommithook and tsvn:postcommithook, each pointing to the respective script file using the %REPOROOT% variable to avoid having to specify the absolute working copy path.

When I commit changes to the repository, the hook scripts (batch files, .bat) all work fine.

However, when I try to commit changes to files in a switched path, the following error appears:

And the commit cannot be done after confirming the message, the commit dialog does not appear.

I believe this error is not triggered by the hook scripts (because there is no change when I write exit 0 or exit 1 into the scripts as the only command), but by TortoiseSVN when trying to execute them, which, for some reason, seems not to be able to find the respective script any more.

So how can I use hook scripts that are located in the repository and hence in the working copy?


Replacing the variable %REPOROOT% by full absolute paths does not change the behaviour at all.

When I replace variable %REPOROOT% by %REPOROOT+% in the tsvn:*commithook properties, nothing changes for switched paths (so the aforementioned error message appears), but for standard paths, no hook script is executed and there is no error message after all.


Just as a side note: to verify whether or not a hook script is attempted to be fired, I rely on appearance of the approval/reject dialog of TortoiseSVN:
Approve or reject client-side hook script


Get this bounty!!!

#StackBounty: #windows #svn #tortoise-svn Why can't I execute a client-side hook script when committing a switched path?

Bounty: 50

I have got an SVN repository (version 1.9.2), and I am using a TortoiseSVN client (version 1.9.2) on a Windows 7 (x64) machine. There are client-side hook scripts (start-commit, pre-commit and post-commit), which are stored within the repository and of course available in the local working copy. They scripts are installed by using the special properties tsvn:startcommithook, tsvn:precommithook and tsvn:postcommithook, each pointing to the respective script file using the %REPOROOT% variable to avoid having to specify the absolute working copy path.

When I commit changes to the repository, the hook scripts (batch files, .bat) all work fine.

However, when I try to commit changes to files in a switched path, the following error appears:

And the commit cannot be done after confirming the message, the commit dialog does not appear.

I believe this error is not triggered by the hook scripts (because there is no change when I write exit 0 or exit 1 into the scripts as the only command), but by TortoiseSVN when trying to execute them, which, for some reason, seems not to be able to find the respective script any more.

So how can I use hook scripts that are located in the repository and hence in the working copy?


Replacing the variable %REPOROOT% by full absolute paths does not change the behaviour at all.

When I replace variable %REPOROOT% by %REPOROOT+% in the tsvn:*commithook properties, nothing changes for switched paths (so the aforementioned error message appears), but for standard paths, no hook script is executed and there is no error message after all.


Just as a side note: to verify whether or not a hook script is attempted to be fired, I rely on appearance of the approval/reject dialog of TortoiseSVN:
Approve or reject client-side hook script


Get this bounty!!!

#StackBounty: #windows #svn #tortoise-svn Why can't I execute a client-side hook script when committing a switched path?

Bounty: 50

I have got an SVN repository (version 1.9.2), and I am using a TortoiseSVN client (version 1.9.2) on a Windows 7 (x64) machine. There are client-side hook scripts (start-commit, pre-commit and post-commit), which are stored within the repository and of course available in the local working copy. They scripts are installed by using the special properties tsvn:startcommithook, tsvn:precommithook and tsvn:postcommithook, each pointing to the respective script file using the %REPOROOT% variable to avoid having to specify the absolute working copy path.

When I commit changes to the repository, the hook scripts (batch files, .bat) all work fine.

However, when I try to commit changes to files in a switched path, the following error appears:

And the commit cannot be done after confirming the message, the commit dialog does not appear.

I believe this error is not triggered by the hook scripts (because there is no change when I write exit 0 or exit 1 into the scripts as the only command), but by TortoiseSVN when trying to execute them, which, for some reason, seems not to be able to find the respective script any more.

So how can I use hook scripts that are located in the repository and hence in the working copy?


Replacing the variable %REPOROOT% by full absolute paths does not change the behaviour at all.

When I replace variable %REPOROOT% by %REPOROOT+% in the tsvn:*commithook properties, nothing changes for switched paths (so the aforementioned error message appears), but for standard paths, no hook script is executed and there is no error message after all.


Just as a side note: to verify whether or not a hook script is attempted to be fired, I rely on appearance of the approval/reject dialog of TortoiseSVN:
Approve or reject client-side hook script


Get this bounty!!!

#StackBounty: #windows #svn #tortoise-svn Why can't I execute a client-side hook script when committing a switched path?

Bounty: 50

I have got an SVN repository (version 1.9.2), and I am using a TortoiseSVN client (version 1.9.2) on a Windows 7 (x64) machine. There are client-side hook scripts (start-commit, pre-commit and post-commit), which are stored within the repository and of course available in the local working copy. They scripts are installed by using the special properties tsvn:startcommithook, tsvn:precommithook and tsvn:postcommithook, each pointing to the respective script file using the %REPOROOT% variable to avoid having to specify the absolute working copy path.

When I commit changes to the repository, the hook scripts (batch files, .bat) all work fine.

However, when I try to commit changes to files in a switched path, the following error appears:

And the commit cannot be done after confirming the message, the commit dialog does not appear.

I believe this error is not triggered by the hook scripts (because there is no change when I write exit 0 or exit 1 into the scripts as the only command), but by TortoiseSVN when trying to execute them, which, for some reason, seems not to be able to find the respective script any more.

So how can I use hook scripts that are located in the repository and hence in the working copy?


Replacing the variable %REPOROOT% by full absolute paths does not change the behaviour at all.

When I replace variable %REPOROOT% by %REPOROOT+% in the tsvn:*commithook properties, nothing changes for switched paths (so the aforementioned error message appears), but for standard paths, no hook script is executed and there is no error message after all.


Just as a side note: to verify whether or not a hook script is attempted to be fired, I rely on appearance of the approval/reject dialog of TortoiseSVN:
Approve or reject client-side hook script


Get this bounty!!!

#StackBounty: #windows #svn #tortoise-svn Why can't I execute a client-side hook script when committing a switched path?

Bounty: 50

I have got an SVN repository (version 1.9.2), and I am using a TortoiseSVN client (version 1.9.2) on a Windows 7 (x64) machine. There are client-side hook scripts (start-commit, pre-commit and post-commit), which are stored within the repository and of course available in the local working copy. They scripts are installed by using the special properties tsvn:startcommithook, tsvn:precommithook and tsvn:postcommithook, each pointing to the respective script file using the %REPOROOT% variable to avoid having to specify the absolute working copy path.

When I commit changes to the repository, the hook scripts (batch files, .bat) all work fine.

However, when I try to commit changes to files in a switched path, the following error appears:

And the commit cannot be done after confirming the message, the commit dialog does not appear.

I believe this error is not triggered by the hook scripts (because there is no change when I write exit 0 or exit 1 into the scripts as the only command), but by TortoiseSVN when trying to execute them, which, for some reason, seems not to be able to find the respective script any more.

So how can I use hook scripts that are located in the repository and hence in the working copy?


Replacing the variable %REPOROOT% by full absolute paths does not change the behaviour at all.

When I replace variable %REPOROOT% by %REPOROOT+% in the tsvn:*commithook properties, nothing changes for switched paths (so the aforementioned error message appears), but for standard paths, no hook script is executed and there is no error message after all.


Just as a side note: to verify whether or not a hook script is attempted to be fired, I rely on appearance of the approval/reject dialog of TortoiseSVN:
Approve or reject client-side hook script


Get this bounty!!!