migration to dos extended mode

[babak1341]

Hi everybody
I have an application with clipper 5.2e which is linked by blinker 3.2. And I want to migrate to dos extended mode. beacaus of a peace of C code in my application that has became a problem for me. When I run the application an error happens when any of my C functions is be called.
Can anybody tell me what can I do?
The error isn't handled by error handling system. when it happens the contents of registers of system are be showed in monitor.
excuse for my bad english

 

[bjolly64]

try creating a small C program to test you modual first and then present it to clipper.



bobby

 

[circes9]

has this application run successfully before? If so, what has changed? new OS? new compile/link?

 

[Elkari]

You really should get a newer version of Blinker that has better abilityies using extended mode. Check out this web site for more information.

http://www.blinkinc.com

 

[babak1341]

application is ranning properly in real mode. when I link it in extended mode the error ocures.

 

[Elkari]

What does your link script look like?

 

[babak1341]

Like a link script ;-)

blinker output ...
blinker inceremental off
blinker executable extended
blinker executable clipper f:55

file ...
.
.
.
lib signega
lib ct
.
.
.

 

[Elkari]

Try changing your EXECUTABLE CLIPPER line to this -

BLINKER EXECUTABLE CLIPPER //VMSIZE:16384 F:127;E2048;DYNF:0;SWAPK:65535;TEMPPATH:'.\';SWAPPATH:'.\'

All on one line of course. I use this with Blinker 5 on serveral projects without any problem. I do not know if it is compatible with your version.

 

[TonHu]

Your C-function(s) is probably using some technique not allowed by protected mode.
This was 1st to be solved on all 3th party libs I used, before I could switch to 286 Protected Mode with ExoSpace (Later switched to Blinker because of speed/performance). It's 'all' in the Norton Guide of ExoSpace how to avoid/use those techniques right. I guess Blinker guide also has this info (now checking...hold on) Hey, it's there!!! In the NG for Blinker 3.2 there is some error so the chapter on 'DOS Extender/Coding for protected mode' is not available, but in the Bli3.3 guide it's all there. Quite tough to read/understand but it's mostly there. Blinker 3.3 should be available as a free upgrade to your Bli3.2 version, from

http://www.blinkinc.com

HTH, TonHu

 

[BlueCorsa]

You should also get and use the protected mode versions of clipper tools, since you are linking with the CT lib, you should link with CTP52.lib. This could also be causing some problems.