Thanks for the clarification. So I guess you are controlling virtualisation from ‘sandbox settings’ when ‘running a program in the sandbox’?
Well running limited unvirtualised helps a bit as at least you don’t have to deal with data files being in the wrong place!
This is likely as far as we can go without an update, unless anyone can find a program that allows you to inhibit specific global hooks for specific programs. Something like CIS, but not CIS, as you don’t appear to be able to do this for guard32.dll in CIS, as you might expect. I have tried :).
I think this may be as far as we can go without an update. I have PM’d the developers and drawn their attention to this thread. No reply as yet.
I am really pleased my clarification is clear and yes I am controlling virtualisation from the sandbox settings, I could not find any other way to do it and then of course running in the sandbox as you say.
I fully agree this is as far as we can go now, I really appreciate that it has gone so far with other peoples input.
So I will just carry on running it either in the sandbox or with guard disabled until we have an update that works.
Thanks also for PM’ing the developers and all your assistance with this problem.
Well I have always believed if you want help and people are prepared to assist then you should at least be prepared to put in some effort and try to give them the required information and at the very least show some appreciation.
I am going to sign off on this one too for now. But as you say the Developers are now asking for more information which is great ;D, it may well be that they will need me to contribute and of course I will do anything I can.
So although I have signed off on this post I will keep an eye on it from time to time just in case my input is needed.
Hi Guys this CIS 4.1.149672.916. version has not helped this problem at all. Just exactly the same symptoms. Tried excluding the exe from event hooks but that did not work either.
Thanks again for all your efforts, it really is appreciated that you are putting time to this and I think the devs are probably trying really hard as well, they have so much to acheive just now (we only just have to look at the list of bugs to be resolved :() we can’t all expect immediate solutions, although some may not appreciate that.
My point in the last post was just to really to hightlight that this particular latest release had not resolved the problem.
Not sure I fully understand the solution you propose, it’s the bit about “‘Run a’ defaults to the same directory each time” I don’t understand. I did not initially understand the reference to Endymion but having re read you PM and the last post I do now, I’m easily confused sometimes.
As I understand it you can run TXR using ‘Run a program in the sandbox’. But this is inconvenient probably in part because it means navigating to a directory then choosing the executable from among a large number of files. Happily ‘Run a program in the sandbox’ defaults to the directory last used. So I was merely suggesting you create an empty directory and put just the shortcut to TXR in it. You have probably done this already.
Getting confused in the absence of information is the mark of a logical mind
I have now found at least one more unfixed guard32 issue, so hopefully the devs will fix, but I cannot promise.
Thanks for the update and explanation which I now understand but have not done, didn’t occur to me to try that. See, despite your compliment I’m still easily confused ;D. But seriously thanks a lot.
Tried that and yep it works but still a bit cumbersome, not to worry wait for further updates, Rev920 seems to have sorted a few other nigglies but it still does not recognise winword.exe so have submitted it.