Not enough memory to load this application

We are currently having the error on MANY machines at work, and are unable
to fix the problem.

We also have to schedule a task to run every hour to fix time issues. The
time is constantly getting way behind, several
hours.

So we are having to constantly reboot out machines, which causes delays in
getting files processed, etc.

We are running Windows 98 SE, F-secure, and batch loops on start up. the
batch loops are constantly looping
checking directories for files, and processing them.

After awhile, you cannot run any DOS applications without getting the low
memory error, and the time gets behind.

Any ideas? I am at wits end on this issue.......

Thanks in advance.

Does time restore itself to correct values after restarting? If so, yours is a
classic case caused by real-mode, low-level processing. And the "looping" batch
files are most likely the direct cause. Also, you're probably not getting a "low
memory" error, you're probably getting a "low resources" error. They aren't the
same and, again, they are most likely due to real-mode, low-level processing.
Resources aren't being released, and the low-level interrupts are causing the
Windows timepiece (which counts CPU interrupts to keep time) to slow down, since
the low-level activity "steals" some of those interrupts.

All in all, I'd say that whatever it is that your file processing is intended to
accomplish needs to be accomplished in a different manner. But without having a
full knowledge of just what your systems are doing, I'd be hard pressed to offer
solutions. Of course, I'd probably be hard-pressed to offer the perfect
solutions, anyway. I know enough to have suggested the above as the most likely
explanations, but I'm not qualified to explain it in any manner more precise
than what I've already said, nor am I qualified to offer professional-grade
programming solutions (unless the goals are relatively simple and can be handled
by scripting, which I suspect is not the case.) In the end, you answered your
own question--the problems are caused by the very programming you can't seem to
keep alive. I hope this helps at least point you toward a solution.

(For an explanation of Resources, see
http://www.aumha.org/win4/a/resource.htm)

--
Gary S. Terhune
MS MVP for Win9x

"Michael J. Gregg" wrote in message
...
We are currently having the error on MANY machines at work, and are unable
to fix the problem.

We also have to schedule a task to run every hour to fix time issues. The
time is constantly getting way behind, several
hours.

So we are having to constantly reboot out machines, which causes delays in
getting files processed, etc.

We are running Windows 98 SE, F-secure, and batch loops on start up. the
batch loops are constantly looping
checking directories for files, and processing them.

After awhile, you cannot run any DOS applications without getting the low
memory error, and the time gets behind.

Any ideas? I am at wits end on this issue.......

Thanks in advance.

My apologies. Upon reconsidering, it's very possible your problems really are in
the way your programs handle memory, not just resources. But the issue is
otherwise the same--the programs you have running are the cause of your
problems, and it's most likely in the very nature of the looping batch files
you're running.

--
Gary S. Terhune
MS MVP for Win9x

"Michael J. Gregg" wrote in message
...
We are currently having the error on MANY machines at work, and are unable
to fix the problem.

We also have to schedule a task to run every hour to fix time issues. The
time is constantly getting way behind, several
hours.

So we are having to constantly reboot out machines, which causes delays in
getting files processed, etc.

We are running Windows 98 SE, F-secure, and batch loops on start up. the
batch loops are constantly looping
checking directories for files, and processing them.

After awhile, you cannot run any DOS applications without getting the low
memory error, and the time gets behind.

Any ideas? I am at wits end on this issue.......

Thanks in advance.

I do get a "Not enough memory to run the application" when I try to run
another DOS window or batch file.

Also, it's not the batch process, because the batch process is running on
many other servers without any problems.

It's just some machine, well, many machines, this occurs on.

It's also happenning on other programmers systems, and they have different
programs, batch files, etc running.

So it would tend to point to something to do with the system. Some setting,
or something.


"Gary S. Terhune" wrote in message
...
Does time restore itself to correct values after restarting? If so, yours
is a
classic case caused by real-mode, low-level processing. And the "looping"
batch
files are most likely the direct cause. Also, you're probably not getting
a "low
memory" error, you're probably getting a "low resources" error. They
aren't the
same and, again, they are most likely due to real-mode, low-level
processing.
Resources aren't being released, and the low-level interrupts are causing
the
Windows timepiece (which counts CPU interrupts to keep time) to slow down,
since
the low-level activity "steals" some of those interrupts.

All in all, I'd say that whatever it is that your file processing is
intended to
accomplish needs to be accomplished in a different manner. But without
having a
full knowledge of just what your systems are doing, I'd be hard pressed to
offer
solutions. Of course, I'd probably be hard-pressed to offer the perfect
solutions, anyway. I know enough to have suggested the above as the most
likely
explanations, but I'm not qualified to explain it in any manner more
precise
than what I've already said, nor am I qualified to offer
professional-grade
programming solutions (unless the goals are relatively simple and can be
handled
by scripting, which I suspect is not the case.) In the end, you answered
your
own question--the problems are caused by the very programming you can't
seem to
keep alive. I hope this helps at least point you toward a solution.

(For an explanation of Resources, see
http://www.aumha.org/win4/a/resource.htm)

--
Gary S. Terhune
MS MVP for Win9x

"Michael J. Gregg" wrote in message
...
We are currently having the error on MANY machines at work, and are
unable
to fix the problem.

We also have to schedule a task to run every hour to fix time issues.
The
time is constantly getting way behind, several
hours.

So we are having to constantly reboot out machines, which causes delays
in
getting files processed, etc.

We are running Windows 98 SE, F-secure, and batch loops on start up. the
batch loops are constantly looping
checking directories for files, and processing them.

After awhile, you cannot run any DOS applications without getting the low
memory error, and the time gets behind.

Any ideas? I am at wits end on this issue.......

Thanks in advance.

At the risk of upsetting you,
perhaps you should consider updating your OS , hardware and software. Win98
is fine for home use, but I haven't seen any business running it for years.
I know you might be attached to your particular DOS software, but really,
are you sure there is not another application which can do the same thing(or
better) on an up to date OS.
In the long run you will have to when the machines eventually break down and
nobody can repair them because its all obsolete.




Michael J. Gregg wrote:
We are currently having the error on MANY machines at work, and are
unable to fix the problem.

We also have to schedule a task to run every hour to fix time issues.
The time is constantly getting way behind, several
hours.

So we are having to constantly reboot out machines, which causes
delays in getting files processed, etc.

We are running Windows 98 SE, F-secure, and batch loops on start up.
the batch loops are constantly looping
checking directories for files, and processing them.

After awhile, you cannot run any DOS applications without getting the
low memory error, and the time gets behind.

Any ideas? I am at wits end on this issue.......

Thanks in advance.

That's the exact, verbatim error message? Because that's not a Microsoft error.
At least, it's not found in the KB. And it still may apply to a Resources issue,
since Resources are a small portion of the memory. Regardless, I'm fairly
certain it's not something that's fixed using Windows settings, it's something
that's fixed using proper programming. Yes, the routines might run fine on some
machines and not others--but are you certain that everything else about those
machines is the same? Same background load, same versions, same updates, etc.?

The issues I was talking about primarily apply to Win98/98SE and ME. It's the
way Virtual Mode is designed to function in the kernel of those versions. The
same issues wouldn't apply to NT servers. And even if the other programmers are
running different programs, batch files, etc., the same principles apply. Bottom
line, I'm nigh certain that there's no one magic pill and that the problem is
one that's endemic to the programs not being properly designed for use on
Windows 98. You're looking in the wrong place for the solution.

--
Gary S. Terhune
MS MVP for Win9x

"Michael J. Gregg" wrote in message
...
I do get a "Not enough memory to run the application" when I try to run
another DOS window or batch file.

Also, it's not the batch process, because the batch process is running on
many other servers without any problems.

It's just some machine, well, many machines, this occurs on.

It's also happenning on other programmers systems, and they have different
programs, batch files, etc running.

So it would tend to point to something to do with the system. Some setting,
or something.


"Gary S. Terhune" wrote in message
...
Does time restore itself to correct values after restarting? If so, yours
is a
classic case caused by real-mode, low-level processing. And the "looping"
batch
files are most likely the direct cause. Also, you're probably not getting
a "low
memory" error, you're probably getting a "low resources" error. They
aren't the
same and, again, they are most likely due to real-mode, low-level
processing.
Resources aren't being released, and the low-level interrupts are causing
the
Windows timepiece (which counts CPU interrupts to keep time) to slow down,
since
the low-level activity "steals" some of those interrupts.

All in all, I'd say that whatever it is that your file processing is
intended to
accomplish needs to be accomplished in a different manner. But without
having a
full knowledge of just what your systems are doing, I'd be hard pressed to
offer
solutions. Of course, I'd probably be hard-pressed to offer the perfect
solutions, anyway. I know enough to have suggested the above as the most
likely
explanations, but I'm not qualified to explain it in any manner more
precise
than what I've already said, nor am I qualified to offer
professional-grade
programming solutions (unless the goals are relatively simple and can be
handled
by scripting, which I suspect is not the case.) In the end, you answered
your
own question--the problems are caused by the very programming you can't
seem to
keep alive. I hope this helps at least point you toward a solution.

(For an explanation of Resources, see
http://www.aumha.org/win4/a/resource.htm)

--
Gary S. Terhune
MS MVP for Win9x

"Michael J. Gregg" wrote in message
...
We are currently having the error on MANY machines at work, and are
unable
to fix the problem.

We also have to schedule a task to run every hour to fix time issues.
The
time is constantly getting way behind, several
hours.

So we are having to constantly reboot out machines, which causes delays
in
getting files processed, etc.

We are running Windows 98 SE, F-secure, and batch loops on start up. the
batch loops are constantly looping
checking directories for files, and processing them.

After awhile, you cannot run any DOS applications without getting the low
memory error, and the time gets behind.

Any ideas? I am at wits end on this issue.......

Thanks in advance.

I replied to your identical post in another group. The fact that it does not occur
on every machine using the batch process is not relevant. This problem will not
occur on every machine. I have seen it on two machines at work but not two
others....all running identical software.

As I said in my reply:
I have seen these issues the clock problem -

Windows Clock on Taskbar and in Date/Time Tool Loses Time
http://support.microsoft.com?kbid=189706

The System Clock Slows If You Run a Program That Uses Sound Extensively
http://support.microsoft.com/?kbid=309296

Restart or Network Connection Changes Computer Date and Time
http://support.microsoft.com/?kbid=193912

"System clock loses time when using Norton AntiVirus 2000"
http://snipurl.com/7g7g

I have the same issue at work, and it appears to be related to a DOS app that we run
24/7
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"Michael J. Gregg" wrote in message
...
I do get a "Not enough memory to run the application" when I try to run
another DOS window or batch file.

Also, it's not the batch process, because the batch process is running on
many other servers without any problems.

It's just some machine, well, many machines, this occurs on.

It's also happenning on other programmers systems, and they have different
programs, batch files, etc running.

So it would tend to point to something to do with the system. Some setting,
or something.


"Gary S. Terhune" wrote in message
...
Does time restore itself to correct values after restarting? If so, yours
is a
classic case caused by real-mode, low-level processing. And the "looping"
batch
files are most likely the direct cause. Also, you're probably not getting
a "low
memory" error, you're probably getting a "low resources" error. They
aren't the
same and, again, they are most likely due to real-mode, low-level
processing.
Resources aren't being released, and the low-level interrupts are causing
the
Windows timepiece (which counts CPU interrupts to keep time) to slow down,
since
the low-level activity "steals" some of those interrupts.

All in all, I'd say that whatever it is that your file processing is
intended to
accomplish needs to be accomplished in a different manner. But without
having a
full knowledge of just what your systems are doing, I'd be hard pressed to
offer
solutions. Of course, I'd probably be hard-pressed to offer the perfect
solutions, anyway. I know enough to have suggested the above as the most
likely
explanations, but I'm not qualified to explain it in any manner more
precise
than what I've already said, nor am I qualified to offer
professional-grade
programming solutions (unless the goals are relatively simple and can be
handled
by scripting, which I suspect is not the case.) In the end, you answered
your
own question--the problems are caused by the very programming you can't
seem to
keep alive. I hope this helps at least point you toward a solution.

(For an explanation of Resources, see
http://www.aumha.org/win4/a/resource.htm)

--
Gary S. Terhune
MS MVP for Win9x

"Michael J. Gregg" wrote in message
...
We are currently having the error on MANY machines at work, and are
unable
to fix the problem.

We also have to schedule a task to run every hour to fix time issues.
The
time is constantly getting way behind, several
hours.

So we are having to constantly reboot out machines, which causes delays
in
getting files processed, etc.

We are running Windows 98 SE, F-secure, and batch loops on start up. the
batch loops are constantly looping
checking directories for files, and processing them.

After awhile, you cannot run any DOS applications without getting the low
memory error, and the time gets behind.

Any ideas? I am at wits end on this issue.......

Thanks in advance.

Believe me, I'd rather use Windows 2000 or XP, but my boss wants Windows 98
for some reason.

We've got a lot of legacy code, that will not work on Windows 2000/XP, so
that is probably the reason he's
wanting to stick with it.

We'll get him to change eventually. We are slowly updating machines to
Windows 2000/XP anyway.

"Dave B." wrote in message
om.au...
At the risk of upsetting you,
perhaps you should consider updating your OS , hardware and software.
Win98
is fine for home use, but I haven't seen any business running it for
years.
I know you might be attached to your particular DOS software, but really,
are you sure there is not another application which can do the same
thing(or
better) on an up to date OS.
In the long run you will have to when the machines eventually break down
and
nobody can repair them because its all obsolete.




Michael J. Gregg wrote:
We are currently having the error on MANY machines at work, and are
unable to fix the problem.

We also have to schedule a task to run every hour to fix time issues.
The time is constantly getting way behind, several
hours.

So we are having to constantly reboot out machines, which causes
delays in getting files processed, etc.

We are running Windows 98 SE, F-secure, and batch loops on start up.
the batch loops are constantly looping
checking directories for files, and processing them.

After awhile, you cannot run any DOS applications without getting the
low memory error, and the time gets behind.

Any ideas? I am at wits end on this issue.......

Thanks in advance.

I seem to have fixed the problem. Or so it seems for now.

We are using a lot of programs written in Clipper 5.2E and xBase 1.82, and apparently they do not use memory well.

Pardon the snapshot, but when we set Expanded and Extended memory to NONE as shown below, the problem has been running for almost 1 day
now without any further problems. Although, the time still looses time, and we have a simple batch in the task scheduler to run every hour.

I wish my boss would upgrade to Windows 2000 or XP... They handle memory, and everything else so much better.



"Michael J. Gregg" wrote in message ...
We are currently having the error on MANY machines at work, and are unable
to fix the problem.

We also have to schedule a task to run every hour to fix time issues. The
time is constantly getting way behind, several
hours.

So we are having to constantly reboot out machines, which causes delays in
getting files processed, etc.

We are running Windows 98 SE, F-secure, and batch loops on start up. the
batch loops are constantly looping
checking directories for files, and processing them.

After awhile, you cannot run any DOS applications without getting the low
memory error, and the time gets behind.

Any ideas? I am at wits end on this issue.......

Thanks in advance.

"Michael J. Gregg" wrote:

I seem to have fixed the problem. Or so it seems for now.

We are using a lot of programs written in Clipper 5.2E and xBase 1.82, and apparently they do not use memory well.

Pardon the snapshot, but when we set Expanded and Extended memory to NONE as shown below, the problem has been running for almost 1 day
now without any further problems. Although, the time still looses time, and we have a simple batch in the task scheduler to run every hour.

I wish my boss would upgrade to Windows 2000 or XP... They handle memory, and everything else so much better.


But one thing they do not always handle well is legacy MS-DOS apps.
This is especially true if the DOS apps are programmed so as to bypass
operating system function calls and work directly with the hardware.

Apps that do this will inevitably fail to operate under Windows 2000
or XP.

The more common instances of this would include:
- Games, where programmers have tried to tweak performance a bit by
writing direct to the video.
- Communications programs, where programmers often control the serial
port directly.
- Specialized application programs that use an external authorization
plug (e.g. a parallel port "dongle") where the application validates
the license by directly accessing the parallel port.

Good luck


Ron Martell Duncan B.C. Canada
--
Microsoft MVP
On-Line Help Computer Service
http://onlinehelp.bc.ca

"The reason computer chips are so small is computers don't eat much."