CONVETIONAL MEMORY EXAUSTED - Clipper

On Sat, 17 Nov 2007 15:16:38 +0200, UNION ÅÐÅ wrote:

> application

Use Blinker to link your application in protected mode (blinker executable
extended)

Regards
Mike Evans

Actually I use Blinker extended as You suggested. The truth is that the
program was working alright and from one moment to the next I could not enter
in to the program again becaue of that error.

regards
Avraam

--------------------------------------------------------------------------------------

Mike Evans wrote:

> On Sat, 17 Nov 2007 15:16:38 +0200, UNION ÅÐÅ wrote:
>
> > application
>
> Use Blinker to link your application in protected mode (blinker executable
> extended)
>
> Regards
> Mike Evans

Dear UNION ÅÐÅ:

"UNION ÅÐÅ" <union1@otenet.gr> wrote in message
news:473EE9B6.205890EA@otenet.gr...
>
> When working with a clipper program on windows 2000
> operating and to ener the application with no success.
> It cannot also do reidexing. When try to use DBU in a
> certain file I get the message "unrecoverable error
> 5304 convetional memory exausted.
>
> Ay IDEAS? I have buffers=40, files=60 or 80 or 220

Easiest will be to switch to xharbour.org now, and get rid of the
need to dance on the head of a pin. Depending on the third party
libs you have used, of course.

Have you tried creating a PIF for these executables, tweaking the
PIF so they run right (the Memory tab), and always executing via
the PIF?

David A. Smith

"UNION ÅÐÅ" <union1@otenet.gr> wrote in message
news:473EE9B6.205890EA@otenet.gr...
>
> When working with a clipper program on windows 2000 operating and to
> ener the application with no success. It cannot also do reidexing. When
> try to use DBU in a certain file I get the message "unrecoverable error
> 5304 convetional memory exausted.
>
> Ay IDEAS? I have buffers=40, files=60 or 80 or 220
>
> faithfully yours
>
> Avraam Avramopoylos
>
Conventional memory is mostly unrelated to the setting of buffers, files,
etc. although increasing them will decrease conventional memory available by
a small amount. Microsoft has some tips, but they are poorly organized.
Here's a starting link http://support.microsoft.com/kb/134399 . Usually, you
have to remove some memory resident programs. If you are running windows XP,
go into the \windows\system32 and look at your autoexec.nt and config.nt
settings. Experiment with removing some devices that you don't need or at
least remove some so that you can run the program. David'sdvice to move you
progam to (x)Harbour is better as a long term solution.

hi,

> Actually I use Blinker extended as You suggested. The truth is that the
> program was working alright and from one moment to the next I could not
> enter
> in to the program again becaue of that error.

show us your *.LNK file.

use MEM /P to see if you have EMS or XMS Memory

if you use XMS memory you need only 256KB conventional
Memory (< 640kb) to run Blinker in protect mode.

greetings by OHR
Jimmy

Avraam

> When working with a clipper program on windows 2000 operating and to
> ener the application with no success. It cannot also do reidexing. When
> try to use DBU in a certain file I get the message "unrecoverable error
> 5304 convetional memory exausted.

If the problem is only with 1 DBF causing this error then the DBF may be corrupt and no amount of configuration settings
will fix it.
The corruption could also be causing your indexing endeavour with DBU to fail as well.

Have you tried just deleting the index files and having a look at your data file to see if there is any corruption??

--
CYA
Steve

Hi!

"UNION ÅÐÅ" <union1@otenet.gr> escribio en el mensaje
news:473EE9B6.205890EA@otenet.gr...
>
> When working with a clipper program on windows 2000 operating and to
> ener the application with no success. It cannot also do reidexing. When
> try to use DBU in a certain file I get the message "unrecoverable error
> 5304 convetional memory exausted.
>
> Ay IDEAS? I have buffers=40, files=60 or 80 or 220
>
> faithfully yours
>
> Avraam Avramopoylos
>

Which compiler version are you using?
If it is 5.2x, go to 5.3b; the 5.2 version has some memory problems when
dealing with indexes on large databases (that could be the problem in your
case).
I'm having that problem now (an index on a dbf with 3.1 million records),
and I'm going to the xharbour way, as suggested by David.
If you could tweak the index reducing its length, then you can -maybe-
create the index; but changing to clip5.3 cures the problem (or
"xharbouring").

HTH
--
Claudio Voskian
ICQ#: 18122595 - Aol/Msn/Skype/Y!: cvoskian
Buenos Aires - Argentina