Thanks for your comments. I haven't done anything yet to diagnose it. I'll run it through the debugger and see what happens when I get a chance. I am running several things in parallel and the box has a quad core CPU: so I thought allocating two cores to the VM may help. I was actually going to run ...

We have a macro that works fine on an XP virtual machine on VMWare Workstation. However, if I switch the virtual machine image from a single CPU to dual CPU the macro crashes ("msched.exe has encountered an error and needs to close"). Very strange problem and not sure if this is a VMWare issue or a ...

Thanks for this - very helpful. My problem was with the way I was starting up the scripts. The long running script was started via the run arrow on the Macro Scheduler GUI. This meant that when the second macro was started (using the msnet remote controller) it seemed to hang/pause. I have now got t...

I'm trying to do the following: Computer 1 is running a long running macro doing some GUI processing. Sometimes user input is required so it sends data to a second PC where a real user has a simple interface, say a yes/no dialogue. When the user clicks a button on Computer 2, what I'm trying to do i...

On a machine I plan to have several VMs each running some proprietary software which I wish to automate with MS. It may help to ignore the fact they are VMs and just consider them separate machines on a private network as I don't think it makes any difference. The situation I have is: - VM1 is essen...

Couldn't agree more!

In fact you helped me out with an issue many months ago... it was so long ago that I had forgotten what the solution was and still having the thread available was most helpful in refreshing my memory!

Yes, this is an option. However, the macro I have was in Vista and I'm trying to move it to XP (not my requirement!) If the worst comes to the worst then I can always just step through it and tweak the positions and have one macro that works in Vista and one that works in XP. I was just curious to s...

Thank you for this, very useful. However, I may be missing something obvious (or probably going about this in completely the wrong way!) The application that I'm dealing with seems to position its controls and other items depending on the size of the "working area" available to it. Previously I was ...

I have had an issue moving a macro from Vista to XP. This macro extensively uses GetPixelColor, WaitPixelColor and MouseMove/LClick to control an application. The macro has positioned the window at known co-ordinates on the screen and has resized the window to a specified size. Everything works fine...

Wow - our last messages crossed... didn't expect you to have solved it so quickly!

Everything seems to work fine now and I can see the memory constantly varying as it is allocated and then freed.

Thanks very much for this. Great job and superb turn around time!

Ken

Thanks very much for this. Hope you manage to find it easily... I know how problematic getting to the bottom of a leak can be from first hand experience!!!

Thanks again.

Ken

Sorry - problem is still there.

Prior to running:
354208 k free Physical Memory (I think I need to reboot to recover the memory lost in earlier tests I should have 4 times this!)

After 10,000 iterations:
306640 k free Physical Memory

Thanks for the swift response. Most appreciated.

Ken

Hi all, My main requirement is to take 5 small images (around 10x10 pixels) that are displayed on the screen (in different locations) and match these to a bank of 60 "known" images. There will always be a match. I then must repeat the process every few seconds indefintiely. I previously raised anoth...

Further to my email above, I can now confirm: Version 9.1.03 running on Windows XP Standard does not take the position of the image within the screen into account. The checksum is the same regardless of where the image is actually positioned - presumably some sort of algorithm working on the colours...

Thank you for your quick and helpful response. I'm a little confused though as I've previously seen the exact same checksum being generated for a particular image regardless of where it is actually positioned on the screen. Has this perhaps changed in version 10? I will try to find my old code and r...