clip5.2d and blinker 7 problem with vm integrity failure

[teering]

i have recently re-complied a very large program with
clipper 5.2d and blinker 7
when i attempt to run a reindex routine or browse thru
the database the program crashes with a vm integrity failure error
does anyone know how to fix this? i am running the program
on a windows xp computer and windows 98 with the same problem
thanks
teresa pickering

Teresa Pickering
Professional Computer Services

 

[rob444]

update your 5.2d to 5.2e which is much more stable.
This update is for free at CA.COM

Rob.

 

[teering]

i upgraded to 5.2e and still have the vm problem
does anyone have a sample link script for blinker7
that works with windows xp computers?
thanks
teresa pickering


Teresa Pickering
Professional Computer Services

 

[rob444]

Show the script you're using...

Rob.

 

[rob444]

Or.. perhaps you should consider switching to xharbour.

You can download xharbour for free at

http://www.xharbour.org

and there is enough support on that site to get you going.

There is not much that should be taken care of when using xharbour and it generates 32 bit executables...
Have a look there.

Rob.

 

[teering]

here is my link script:
blinker incremental off
blinker executable dual
blinker executable clipper //f:200
blinker overlay opsize 64
blinker overlay umb on
blinker overlay pageframe on
blinker procedure depth 30
blinker executable nodelete
blinker cache ems 100%
blinker message wink
output main
file main
beginarea
...list of files here (total of 85)
endarea
search blxclp52
@cl520mid
map a,s

i have downloaded the xharbour. do you think my problem
is with the complier and not my blinker7 linking script?
thanks
teresa pickering


Teresa Pickering
Professional Computer Services

 

[rob444]

Blinker 7 was especially ment to be a problem solver for the specific XP VM problems with the clipper- and other 16 bits apps.
As far as I can see there is nothing wrong with this script.
Perhaps you can have somw trial and error testing with the following settings:
blinker executable clipper //f:200
blinker overlay umb on
blinker procedure depth 30
blinker cache ems 100%

I think the good old clipper compiler is getting out of sinc with today's operating systems.
If you put some efford in migrating to xharbour you'll find that many problems disappear AND that you'll have real 32 bit real executables (no interpreter in the exe).
And you'll love the speed.

Good luck!
Rob.

 

[metron9]

Make a test program that simply reindexes the database and see if you get the error. I just opened the Blinker 7.0 box a few minutes ago. My program is small compared to yours but with exospace the MEMORY() function gives me only 94 on my opening menu. With the following script I get 64993. The other benifit is my processor usage is back to 2% using blinker 7.0 and the command BLICPUREL(). Normally useing any other linker it's maxed out at 100% in the windows xp Task manager when any of my clipper 5.3 / DOS programs are running in a window.

I don't use reindex, I just delete the old index and "index on" to create a new one. You could try that. I am still usinf the NTX index files and you did not say what type of index files you are using but the threads on corrupt databases and reindexing NTX files are hear for the dearching.

My link file for one program that works on XP using clipper 5.3. Not sure if its 5.3b or what as executing clipper on the command line says "5.3"

Still unsure if I am using a DOS window if the file MPAR from Blinker should be linked or not.


BLINKER EXECUTABLE EXTENDED
BLINKER INCREMENTAL OFF
FILE CCQT04
FILE MPAR
SEARCH BLXCLP53