WinBatch Tech Support Home

Database Search

If you can't find the information using the categories below, post a question over in our WinBatch Tech Support Forum.

TechHome

Winbatch Studio
plus

Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.

WinBatch Studio Choppy and Slow


Question:

Anyone else noticed this behaviour? Occasionally, while working in WBStudio, it starts to act choppy when moving the cursor from line to line or when editing text. I've been monitoring the processes and there's nothing sitting there churning up any extra processor cycles...I've got no other WB scripts running or anything...so I can't quite figure it out. Any thoughts? Sometimes a reboot fixes it, sometimes it doesn't. A stop/restart of WBStudio never fixes it.

Answer:

Where are the files you are editing. I think Floppyies or having lots of files open on slow network connectsions might do this. Slow networks and lots of files open (more than one?) lead to choppiness.

User reply:

3 files open, all referencing UNC paths on the network. OK, so even if this is a known behaviour, why does my moving from one line to another in an already opened file have to be affected by any network slowdown? Isn't the file cached locally? It's not like it has to go back to the server for each line like an AS400 terminal session or anything.

Answer:

Apparently the original developers had, before even starting the code for WinBatch Studio, certain "issues" with other programs modifying files outside of the editor they were working in.

For exapmple some compilers (Not the WinBatch compiler) produce listing files ouf the output run. It is common to view these files in an editor.

What happens is that you can edit the program in the editor, compile the program to get the listing file, then also view the file in the editor.

Then you can fix some code and rerun the compiler that updates the listing file.

Unless you remember to close and reopen the listing file in the editor, then you may be viewing an older, out of date listing file, which, considering the original programmers, led to great confusion.

Thus WinBatch studio *constantly* monitors al the files it has open, checking to see if any of them were modified by some outside process. This works fine on local hard drives and zippy network connections (I've had 100 file open on a network with only monor degradation). How ever son a slow network connection this process can make it "choppy". --


Article ID:   W16264
File Created: 2005:08:10:10:35:50
Last Updated: 2005:08:10:10:35:50