User Bill Gribble (email@example.com) posted:
I'm not altogether certain this is a problem with Robot. In fact, I'm
pretty convinced it's either an issue with the application I'm testing
or the operating system. But I'd be grateful for advice.
I need to automate an application that runs in Windows (in this case
Windows 98). It is, to all intents and purposes, a fancy calculator. I'm
using Robot v.2002.05.00 - or at least trying to.
The application in question is somewhat resource hungry in terms of RAM.
But it will run quite happily on a PC with 256mb. However, if I try to
invoke it using a script (and thus having Robot already running in the
background), the application crashes, giving all the signs and error
messages consistent with it not finding enough memory on the system to
If I load the application first, then load Robot, they sit side by side
quite happily. The scripts even run, to a point. However, the first time
the script invokes an object data VP, the application crashes. Again,
all the error messages point to insufficient RAM. Besides which, it is
imperative to the task in hand that the Robot scripts be able to invoke
and shut down the application a number of times across the course of
Being a simple soul, fond of simple solutions, I thought to up the RAM
in the PC to 512mb. This worked in the past, when automating a similar
job on a related but separate application developed by the same people.
In that case, we started with the host PC running on 128mb of RAM, hit
the same error messages that I'm hitting now, and upped the RAM to
256mb, which resolved the issue.
Any ideas? I could increase the RAM further (and probably will today).
Though I'm baffled by the fact that the application will run with 256mb,
but when another 256mb of RAM is added, the problem persists.
There is, incidentally, plenty of drive space on the PC for Windows to
handle its virtual memory. Which doesn't seem to help at all
I'm beginning to wonder if it isn't just a simple matter of RAM, but
some more arcane and indecipherable conflict between Robot and the
At this point, I'm beginning to miss the days of DOS, its conventional
memory limitations, QEMM and Automator QA . . .
I'd appreciate any suggestions.
Re: Robot Amnesia
User (firstname.lastname@example.org) posted:
Bill, here are a few ideas to try:
I haven't tried running Robot 2002 on Windows 98. I did have success
running version 2000.02.10 on Windows 95, 98 SE, NT4, 2000 and an XP
If you have version 2000.02.10, you might want to try it on Win98.
What language and tools is this app built with? How does it allocate
memory? Some languages (especially FORTRAN) are infamous for
memory-related problems (static memory allocation + programmer goofs).
Is this by any chance a 16-bit Windows application? I've seen similar
behavior with 16-bit apps before. Under Win95, a 16-bit app can violate
32-bit address space (not true under NT4). This may be the case for Win98
as well. What I'm trying to say is that your application may have memory
Can you create and run a debug version of the app (under Win98, of
This could be really helpful if it's your app that's the problem.
Does this app use a lot of Resource Memory (window handles and a variety
of actions use this)? Windows 9.x has precious little resource memory,
and is prone to hang/crash when it runs low.
Re: Robot Amnesia
User MArk B. (email@example.com) posted:
Might try to get the dev environment installed on the test machine to find
out where in the program it's barfing after it fails. You know, where it
asks if you want to debug the program. Also try to run it on NT, Win2k, or
XP. (Or maybe CEMENT too. snicker)
And you might ask why the stupid thing needs so much memory. Does it really
need that much or are the programmers misbehaving?
"Bill Gribble" <firstname.lastname@example.org> wrote in message
Re: Robot Amnesia
User DAVID MARSH (DAVID.MARSH@thales-cs.com.nospam) posted:
I think that Win 9x has a maximum of 512Mb if I remember right, but as other
said, it don't look like that sort of memory problem.