Unrecoverable error 667: Eval stack fault

[karweng]

Hello everyone,

I've been getting the above error message recently with propriety clipper software for which I'm not familiar with. Is there anyway that I can tweak my pc to make this work?

 

[TonHu]

A few options:
- Probably an error not caught or caused by ErrorSys. If you have a 'local' errorhandler, disable it and see what the real problem is, or else it's an error inside the errorhandler, that gets to call itself, etc. until the stack overflows
- Are you updating the software so it gets bigger? Then temporarily remove some functions, so it gets smaller and see if the problem goes away
- When executing macro's (&) change the code so there is no more bug(s) inside it

My bet goes for the 3rd option ;-)

HTH
TonHu

 

[karweng]

Hi TonHu,

It's an off the shelve software which we do not have the source code. Recently the records has increased dramatically I guess the program was not cater for it.

 

[GriffMG]

Does the program have a re-index utility?

If so, try that first.

Which OS are you running on, it *might* be a memory issue.

Martin

Regards

Griff
Keep [Smile]ing

 

[karweng]

Hi,

The clipper program does have an reindex fuction and which I did reindexed all the dbf and ntx files.

The program is running on a Win98 machine and I tried tweaking the config.sys to free up as much memory but I'm still unable to run it.

 

[GriffMG]

A Clipper program should run very well on an Win98 machine.

I'm stretching to remember any problems to be honest, if I were sat in your place I'd probably do the following:

1) Disconnect from any network, remove (disable) any ant-virus and try.

2) Get as clean a config.sys and autoexec.bat as possible and try that.

3) Check on another machine

Questions:
Is your data local or on a network?
What anti-virus are you using?
Do you have any other apps running?

Sorry, I suspect we're in 'change and play' territory

Regards

Griff
Keep [Smile]ing

 

[GriffMG]

Just one other thought, Win98 is DOS based. DOS had 'stacks' as a command in either the autoexec or the config.sys - does yours?

Regards

Griff
Keep [Smile]ing

 

[karweng]

Hi Griff,

The program i m running is on my local harddisk and it's the same problem when running off a network drive too.

I've tried booting into full dos mode and it's still the same problem.

This is my current config.sys settings

device=c:\windows\himem.sys
buffershigh=150
fileshigh=100
stacks=9,256
dos=high,umb
device=c:\windows\emm386.exe noems
lastdrive=z

 

[GriffMG]

Hi again,

Unfortunately, I have no more Windows 95/98 machines left - my two Windows Me ones both have completely empty config.sys files (which probably is not an option with W98).

I have found one or two references to similar errors on the 'net. My suggestion du jour is to edit your autoexec.bat and put the following on a line that is certain to be executed:

SET CLIPPER F100;E00

That should read E Zero Zero NOT E Oh Oh if you follow me.

You need this line early on, before any batch or shell programs are executed. Also watch out for other SET CLIPPER statements after it.

Good luck.




Regards

Griff
Keep [Smile]ing

 

[mbinfo]

Programs in Clipper use EMS memory type. If your EMM386 states NOEMS you are in trouble with performance.
If you don't have EMS all the processing and memory usage is done below 1Mb (in fact below 640k) and DISK.

You can change NOEMS to RAM in order to have EMS memory available to Clipper. Also check the memory type in the properties screen of your PIF just to see how it is set.

Using EMS you possibly will relieve the low memory usage and (who knows) reduce the problem with Unrecoverable Error 667.

Ulisses

 

[TonHu]

BUT:

As EMS implementation of DBFNTX (at least. may be up to the VM) is _very_ buggy, and whole table to be indexed has to fit fully in EMS (or something strange like that, I'm not exactly sure) it is strongly dis-advised to use EMS with Clipper. This has been true for over 10 years now, and the flaws have never been (or will be) fixed.

Don't waste time on any investigation on this subject, tried and proven wrong.

If the memory-usage of a Clipper app is over low memory capacity, recompile with (x)Harbour (to be using 32 bit model with (nearly) unlimited memory capacity), or at least use a protected mode linker like ExoSpace or Blinker 3 and up, or use Blinker to create a more efficient and automatic Overlay system.

HTH
TonHu