Home > Archive > Clipper > July 2007 > Memory Errors
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Ryan Ford 2007-07-25, 6:55 pm |
| We have been experiencing many issues with memory while running dbase
iii / clipper apps. Users continue to receive either "out of memory"
or "memory low" errors. We have modified the config.nt file to
reflect 'files=120' as well as modify the shortcuts for the apps to
set conventional memory total and initial to 'auto', ems to none, xms
to auto and to use hma, and dpmi to auto. This seems to resolve most
of the memory errors and seems to be the best settings for maximum
memory allocation, but some users continue to receive the memory
errors. Most of these, but not all, seem to be happening on
'indexing' a db. All users run the same version of the app and all
index on an identical db.
Any and all suggestions comments are greatly appreciated.
Regards,
Ryan
| |
|
| Dear Ryan Ford:
On Jul 25, 9:36 am, Ryan Ford <rfor...@gmail.com> wrote:
> We have been experiencing many issues with
> memory while running dbase iii / clipper apps.
....
> Any and all suggestions comments are greatly
> appreciated.
Switch to xHarbour.org. Depending on which version of Clipper you are
running (and 3rd party libraries), you will have little or no code
modifications. And this version is free, is 32-bits, and runs as a
native Windows application.
David A. Smith
| |
| Stephen Quinn 2007-07-25, 6:55 pm |
| Ryan
We'll have to assume the app is a real mode app.
Have you tried linking in exended mode??
That would be the best option but it depends on which 3rd party libraries (if any) are used, they
need to be extended mode compatable.
The above also assumes you have the source to compile the app<bg>
If you don't have the source then you'll really need to talk the the developer of the app.
If you do hve the source then post the make file and link script here, also tell us which version
of the compiler (S'87, C5.2, C5.3) and which linker & version your using.
--
CYA
Steve
| |
| Ryan Ford 2007-07-25, 6:55 pm |
| I wish I could answer your inquirey on real mode vs. extended mode. I
do not know. I do not believe that there are any 3rd party librarys.
I believe that the app and all associated prg's are home brewed. I do
have all of the sorce (prg's). We are using DBaseIII+ v.S'87, Clipper
v.S'87, and Blinker 5.1. Here is the compile script I use for this
particular program. The program uses about 70 +/- prg files. Let me
know what, if any, of the files referenced in the script below, you
would like to see in text.
==========BEGIN==========
:: start in M:\SOURCE\MXRMAIN
:: create !FZLINK.LNK
echo BLINKER INCREMENTAL OFF > !FZLINK.LNK
echo BLINKER EXECUTABLE CLIPPER R020;E000;F050 >> !FZLINK.LNK
echo OUTPUT %1 >> !FZLINK.LNK
echo FILE M:\SOURCE\CLIPPER\%1.OBJ >> !FZLINK.LNK
echo FILE M:\SOURCE\CLIPPER\EPOCH.OBJ >> !FZLINK.LNK
echo FILE M:\SOURCE\CLIPPER\__WAIT_B.OBJ >> !FZLINK.LNK
echo LIB M:\SOURCE\CLIPPER\CLIPPER.LIB >> !FZLINK.LNK
echo LIB M:\SOURCE\CLIPPER\EXTEND.LIB >> !FZLINK.LNK
:: change directory and run clipper
CD\SOURCE\CLIPPER
CLIPPER M:\SOURCE\MXRMAIN\%1
pause
:: change directory and run blinker
CD\SOURCE\BLINKER\BIN
BLINKER @M:\SOURCE\MXRMAIN\!fzlink
pause
:: move the exe and erase the temp files
COPY %1.EXE M:\SOURCE\MXRMAIN
ERASE M:\SOURCE\CLIPPER\%1.OBJ
ERASE M:\SOURCE\BLINKER\BIN\%1.EXE
ERASE M:\SOURCE\MXRMAIN\!FZLINK.LNK
:: return to the starting directory and run the exe
CD\SOURCE\MXRMAIN
%1
==========END==========
| |
| Ryan Ford 2007-07-25, 6:55 pm |
| I wish I could answer your inquiry on real mode vs. extended mode. I
do not know. I do not believe that there are any 3rd party
libraries.
I believe that the app and all associated prg's are home brewed. I
do
have all of the source (prg's). We are using DBaseIII+ v.S'87,
Clipper
v.S'87, and Blinker 5.1. Here is the compile script I use for this
particular program. The program uses about 70 +/- prg files. Let me
know what, if any, of the files referenced in the script below, you
would like to see in text.
==========BEGIN==========
:: start in M:\SOURCE\MXRMAIN
:: create !FZLINK.LNK
echo BLINKER INCREMENTAL OFF > !FZLINK.LNK
echo BLINKER EXECUTABLE CLIPPER R020;E000;F050 >> !FZLINK.LNK
echo OUTPUT %1 >> !FZLINK.LNK
echo FILE M:\SOURCE\CLIPPER\%1.OBJ >> !FZLINK.LNK
echo FILE M:\SOURCE\CLIPPER\EPOCH.OBJ >> !FZLINK.LNK
echo FILE M:\SOURCE\CLIPPER\__WAIT_B.OBJ >> !FZLINK.LNK
echo LIB M:\SOURCE\CLIPPER\CLIPPER.LIB >> !FZLINK.LNK
echo LIB M:\SOURCE\CLIPPER\EXTEND.LIB >> !FZLINK.LNK
:: change directory and run clipper
CD\SOURCE\CLIPPER
CLIPPER M:\SOURCE\MXRMAIN\%1
pause
:: change directory and run blinker
CD\SOURCE\BLINKER\BIN
BLINKER @M:\SOURCE\MXRMAIN\!fzlink
pause
:: move the exe and erase the temp files
COPY %1.EXE M:\SOURCE\MXRMAIN
ERASE M:\SOURCE\CLIPPER\%1.OBJ
ERASE M:\SOURCE\BLINKER\BIN\%1.EXE
ERASE M:\SOURCE\MXRMAIN\!FZLINK.LNK
:: return to the starting directory and run the exe
CD\SOURCE\MXRMAIN
%1
==========END==========
______________________________________
Ryan D Ford
Mobile: (619) 847-9876
rford75@gmail.com
______________________________________
| |
| Ryan Ford 2007-07-25, 6:55 pm |
| I wish I could answer your inquiry on real mode vs. extended mode. I
do not know. I do not believe that there are any 3rd party
libraries.
I believe that the app and all associated prg's are home brewed. I
do
have all of the source (prg's). We are using DBaseIII+ v.S'87,
Clipper
v.S'87, and Blinker 5.1. Here is the compile script I use for this
particular program. The program uses about 70 +/- prg files. Let me
know what, if any, of the files referenced in the script below, you
would like to see in text.
==========BEGIN==========
:: start in M:\SOURCE\MXRMAIN
:: create !FZLINK.LNK
echo BLINKER INCREMENTAL OFF > !FZLINK.LNK
echo BLINKER EXECUTABLE CLIPPER R020;E000;F050 >> !FZLINK.LNK
echo OUTPUT %1 >> !FZLINK.LNK
echo FILE M:\SOURCE\CLIPPER\%1.OBJ >> !FZLINK.LNK
echo FILE M:\SOURCE\CLIPPER\EPOCH.OBJ >> !FZLINK.LNK
echo FILE M:\SOURCE\CLIPPER\__WAIT_B.OBJ >> !FZLINK.LNK
echo LIB M:\SOURCE\CLIPPER\CLIPPER.LIB >> !FZLINK.LNK
echo LIB M:\SOURCE\CLIPPER\EXTEND.LIB >> !FZLINK.LNK
:: change directory and run clipper
CD\SOURCE\CLIPPER
CLIPPER M:\SOURCE\MXRMAIN\%1
pause
:: change directory and run blinker
CD\SOURCE\BLINKER\BIN
BLINKER @M:\SOURCE\MXRMAIN\!fzlink
pause
:: move the exe and erase the temp files
COPY %1.EXE M:\SOURCE\MXRMAIN
ERASE M:\SOURCE\CLIPPER\%1.OBJ
ERASE M:\SOURCE\BLINKER\BIN\%1.EXE
ERASE M:\SOURCE\MXRMAIN\!FZLINK.LNK
:: return to the starting directory and run the exe
CD\SOURCE\MXRMAIN
%1
==========END==========
______________________________________
Ryan D Ford
Manager I.T. Services
Office: (858) 565-4472
Mobile: (619) 847-9876
ryan.ford@merryxray.com
www.merryxray.com
______________________________________
| |
| Stephen Quinn 2007-07-25, 9:55 pm |
| Ryan
> have all of the sorce (prg's). We are using DBaseIII+ v.S'87, Clipper
> v.S'87, and Blinker 5.1. Here is the compile script I use for this
Are you sure it's S'87 your using??
I only ask because AFAIK the __WAIT_B.obj file is for Clipper 5 not S'87.
> echo FILE M:\SOURCE\CLIPPER\__WAIT_B.OBJ >> !FZLINK.LNK
What parameter do you pass into that .bat file??
What's this file??
> CLIPPER M:\SOURCE\MXRMAIN\%1
--
CYA
Steve
| |
| Rene Flores 2007-07-25, 9:55 pm |
| Ryan:
If you are working with summer 87 there's nothing you can do, you are
using real mode not extended memory mode, not even with Blinker you can
access extended memory mode with summer 87 unless you switch to Clipper
5.3 at least.
My best advice, get the rid off clipper summer 87, go to
www.xharbour.org, download the open source compiler, it will "eat" all
your summer 87 code and will turn it into a powerful 32 bits - extended
mode application ready to run in all the Windows enviroments.
Regards
Rene Flores
http://www.ciber-tec.com
Ford escribió:
> We have been experiencing many issues with memory while running dbase
> iii / clipper apps. Users continue to receive either "out of memory"
> or "memory low" errors. We have modified the config.nt file to
> reflect 'files=120' as well as modify the shortcuts for the apps to
> set conventional memory total and initial to 'auto', ems to none, xms
> to auto and to use hma, and dpmi to auto. This seems to resolve most
> of the memory errors and seems to be the best settings for maximum
> memory allocation, but some users continue to receive the memory
> errors. Most of these, but not all, seem to be happening on
> 'indexing' a db. All users run the same version of the app and all
> index on an identical db.
>
> Any and all suggestions comments are greatly appreciated.
>
> Regards,
> Ryan
>
| |
| pete@nospam.demon.co.uk 2007-07-26, 3:55 am |
| In article <1185392647.083626.195960@i13g2000prf.googlegroups.com>
rford75@gmail.com " Ryan Ford" writes:
> I wish I could answer your inquiry on real mode vs. extended mode. I
> do not know. I do not believe that there are any 3rd party
> libraries.
> I believe that the app and all associated prg's are home brewed. I
> do
> have all of the source (prg's). We are using DBaseIII+ v.S'87,
> Clipper
> v.S'87, and Blinker 5.1. Here is the compile script I use for this
> particular program. The program uses about 70 +/- prg files. Let me
> know what, if any, of the files referenced in the script below, you
> would like to see in text.
> ==========BEGIN==========
> :: start in M:\SOURCE\MXRMAIN
> :: create !FZLINK.LNK
> echo BLINKER INCREMENTAL OFF > !FZLINK.LNK
> echo BLINKER EXECUTABLE CLIPPER R020;E000;F050 >> !FZLINK.LNK
Do you need to reserve 20K for extermal programs? If not, try
leaving out the R020. You might also be able to squeeze a few
more K by reducing the amount of mem Clipper sets aside for
variables -- the V parameter. I forget what the default is,
something like 16?, so you could try reducing this to e.g. V008
but obviously only if your app doesn't use all the variable space
allocation already.
> echo OUTPUT %1 >> !FZLINK.LNK
> echo FILE M:\SOURCE\CLIPPER\%1.OBJ >> !FZLINK.LNK
What is %1? -- It looks like it might be a CLP file? If so,
compile and specify each prg/obj separately. I've not used
Blinker, but perhaps it can organise its dynamic overlaying
better like this? And if dynamic overlaying isn't working
properly, maybe you can "help" it by specifying some SECTION
commands in your link script? This is what I used to have to
do using Plink86 (ahh, happy days...)
> echo FILE M:\SOURCE\CLIPPER\EPOCH.OBJ >> !FZLINK.LNK
> echo FILE M:\SOURCE\CLIPPER\__WAIT_B.OBJ >> !FZLINK.LNK
> echo LIB M:\SOURCE\CLIPPER\CLIPPER.LIB >> !FZLINK.LNK
> echo LIB M:\SOURCE\CLIPPER\EXTEND.LIB >> !FZLINK.LNK
> :: change directory and run clipper
> CD\SOURCE\CLIPPER
> CLIPPER M:\SOURCE\MXRMAIN\%1
> pause
> :: change directory and run blinker
> CD\SOURCE\BLINKER\BIN
> BLINKER @M:\SOURCE\MXRMAIN\!fzlink
> pause
> :: move the exe and erase the temp files
> COPY %1.EXE M:\SOURCE\MXRMAIN
> ERASE M:\SOURCE\CLIPPER\%1.OBJ
> ERASE M:\SOURCE\BLINKER\BIN\%1.EXE
> ERASE M:\SOURCE\MXRMAIN\!FZLINK.LNK
> :: return to the starting directory and run the exe
> CD\SOURCE\MXRMAIN
> %1
> ==========END==========
No doubt the Blinker experts will be along soon to help. I'm
sure there's a lot you can do to fix your problem!
Pete
--
"We have not inherited the earth from our ancestors,
we have borrowed it from our descendants."
|
|
|
|
|