WinBatch Debugger Slow to Start

 Keywords: WinBatch Studio Debugger Context File Menu FileMenu Slow Lag Start

Question:

Our team is experiencing delays when running the debugger in WinBatch Studio and when right-clicking to bring up the context menu in Windows Explorer. We believe the latter issue also to be WinBatch related because 1) using shell diagnostic tools to deactivate the WinBatch context menu resolves the delay and 2) after uninstalling WinBatch the problem goes away and after re-installing WinBatch the issue returns.
I see about a 10 second lag between the time Debug is run and the time the first statement is reached. Also I see about a 10 second lag between the time a file is right-clicked and the time the context menu appears.
As for the context menu issue:

It only occurs when right-clicking files, not folders.
It occurs when right-clicking on any file type.
If one right-clicks with the next minute or two, the opening of the context menu is instantaneous. After waiting a minute or two to do so again, however, the lag reappears. And, if one closes and reopens Windows Explorer, the lag also occurs right away.

Our Environment:
WinBatch + Compiler 2011B. OS: Windows 7 Enterprise, Service Pack 1, 64 bit. (We previously had XP machines running 2011B, but no lag issues there.) Processor: Intel Core i5-3470 3.20 GHz. RAM: 4 GB We have admin rights to our computer. UAC is turned off (set to 'Never Notify')
Could you help us determine why WinBatch is exhibiting a lag when starting debugging and also appears to be impacting the loading of the context menu?

Answer:

I just wanted to let you know that I believe I figured out what was going on with the slow WinBatch response time when running the debugger or when opening the context menu�.

My computer had an incredibly long environmental path statement. I noticed that "C:\Program Files (x86)\WinBatch\System" was not in this path statement. However, one element in the path statement, placed by another installed application, referenced a non-local path, e.g. \\server\share\blah. I suspect that when calling any WinBatch component, the OS was searching first through all the path elements, including the share path, and that the delay in reading the share path was creating the delay. In any event, moving "C:\Program Files (x86)\WinBatch\System" to the front of the environmental path statement resolved the issue.

Article ID:   W17971

Filename:   WinBatch Debugger Slow to Start.txt

File Created: 2014:01:13:10:23:26

Last Updated: 2014:01:13:10:23:26

Database Search

TechHome