Internal error 19

[gmalavrazic]

I try to move from Windows/DOS platform to Linux/DOSEmu. Some applications work but some have problems.

And here is the problem:
Under Windows/DOS this application work, but under Linux/DOSEmu crashes with: Internal error 19.

problematic part of the code is:

...
if OBRACUN->sifra=="0999"
OBRACUN->(GMCopyRec("COPY&quot)
if !OBRACTMP->(dbseek(space(len(OBRACUN->mbr))))
OBRACTMP->(GMAddRec())
endif
...

Colored row is the point of CRASH with message: internal error 19.

Maybe is the problem with memory management, or...

Any ideas?

 

[JockMullin]

Hi, GMAlavrazic

Well, in my experience internal error 19 can have a lot of basic causes and memory management or memory problems can be the culprit. Basically I think it means there is or has been a problem in accessing an index file (corrupted index). It is not necessarily one associated with the file on which the actual crash occurs, but could be any index previously opened, and not necessarily even accessed. This index has corrupted memory areas used for file buffering or control.

I usually rebuild all indexes and try again.

However I have no experience with your environment, so it could be something else which is causing corruption of the
file buffers such as memory management or linking problems or database drivers.

Try disabling expanded memory usage and see if that helps.

Best regards
Jock Mullin

 

[gmalavrazic]

>>Try disabling expanded memory usage and see if that helps.
>>

Thanks!!!
It works.
There was a combination of this and something that I described in my thread "INDEX ON vs dbcreateindex()"

 

[fbizzell]

I have a small Clipper application that I need to send to someone that is using Linux. Where do I start to get my Clipper application ready to run on a Linux Box. Is there something I have to do to my application or is here something that is run on the Linux box to make it possible.

 

[ZoDra]

Hi Gmalavrazic!

In my expirience internal eror 19 has to do something with corrupt indexes mainly; or in some cases with corrupt database. Try:
1. rebuild index that is in use
2. if that doesn't help try packing the database and dbt file if it exists. Use dbu or dbx for this NOT DBASE.