Clipper - Rescued Clipper S87 recompilation problems

Author

Rescued Clipper S87 recompilation problems

Chriz

2005-12-05, 7:55 am

Hi there,

I have to update an old clipper s87 program for one of my head and I do
not really know how it works.
The exe was decompiled with Valkyrie. All the restored code was renamed
with a .prg extension.

My problem comes when I recompile the code (using novlib and blinker).
I can compile my file without problem, but when I run it, nothing
happens. My program has three databases and is "linked" to an ini file.

Any idea or clue about what I am doing wrong ?

Thanks

Chiz

pete@nospam.demon.co.uk

2005-12-05, 6:55 pm

In article <1133786204.555895.208340@g14g2000cwa.googlegroups.com>
cmauron@infomaniak.ch "Chriz" writes:

> Hi there,
>
> I have to update an old clipper s87 program for one of my head and I do
> not really know how it works.

That is not a good start :-(

> The exe was decompiled with Valkyrie. All the restored code was renamed
> with a .prg extension.
>
> My problem comes when I recompile the code (using novlib and blinker).
> I can compile my file without problem, but when I run it, nothing
> happens. My program has three databases and is "linked" to an ini file.
>
> Any idea or clue about what I am doing wrong ?

I think you need to provide some more details:

1. does the original .exe "work"?
2. did you make any changes to the decompiled source before
recompiling it?
3. are the "databases" and "ini" file in the location that the
program expects to find them?
4. some details of the OS you're using, and the commands you're
using to link would be useful.

Help us to help you...

Pete
--
"We have not inherited the earth from our ancestors,
we have borrowed it from our descendants."

Chen Kedem

2005-12-06, 3:55 am

Chriz,

> I can compile my file without problem,
> but when I run it, nothing happens.

Try to compile your program with or without
the /n switch.

If this does not work, please show us your
compile and link scripts.

Chen.

Chriz

2005-12-06, 7:55 am

1. does the original .exe "work"?
Yes, it works fine

2. did you make any changes to the decompiled source before
recompiling it?
Yes, I renamed a function (createdir into FSdirADD)

3. are the "databases" and "ini" file in the location that the
program expects to find them?
In fact it is a "sys" file instead of "ini" file. Yes, they
are, if they are not, the program display an error message

4. some details of the OS you're using, and the commands you're
using to link would be useful.
I am compiling the software on a WXP SP2 Workstation.
I have only Clipper S87, Blinker 7.0 and Novlib 3.30.
When I compile I type : clipper @myfile.clp (in this case :
@adr.clp)
Then under Blinker, I type : blinker File adr,novlib87 Lib
extend,novlib,novdos,novlibcl
and the prog compiled.
In my adr.clp file I have got the following prg files :
adraffi, adrcimp, adrclie, adrconf, adrfunc, adrhelp, adrmain,
adrmkdb, adrmenu,
adrmsgs, adrnovo, adrtrim, adrutil, blcalprg, blerrprg, errorsys,
examplep

pete@nospam.demon.co.uk

2005-12-07, 3:55 am

In article <1133865059.279760.214110@g43g2000cwa.googlegroups.com>
cmauron@infomaniak.ch "Chriz" writes:

Hi Chriz,

> 1. does the original .exe "work"?
> Yes, it works fine
>
> 2. did you make any changes to the decompiled source before
> recompiling it?
> Yes, I renamed a function (createdir into FSdirADD)

Hmmm -- the first thing that one would usually do here would be
to "rebuild the kit" with the original pieces and to check that
the .exes are identical (or as identical as one might expect).
But I'm intrigued as to why one would want to rename a function;
as well as having to also rename all the calls to it in the code
there could be problems if the original name is buried away in a
lib or more. I'm not saying that this is your problem, but it
would be one thing to eliminate by rebuilding the original source
first to check that that works OK.

> 3. are the "databases" and "ini" file in the location that the
> program expects to find them?
> In fact it is a "sys" file instead of "ini" file. Yes, they
> are, if they are not, the program display an error message

Fair enough.

> 4. some details of the OS you're using, and the commands you're
> using to link would be useful.
> I am compiling the software on a WXP SP2 Workstation.
> I have only Clipper S87, Blinker 7.0 and Novlib 3.30.
> When I compile I type : clipper @myfile.clp (in this case :
> @adr.clp)
> Then under Blinker, I type : blinker File adr,novlib87 Lib
> extend,novlib,novdos,novlibcl
> and the prog compiled.

I've no experience of novlib, but would suggest playing around
with the order in which you specify those .lib files; also, I
normally specify clipper.lib explicitly. However, if you
inherited the .clp file and the link script, one can only assume
that they worked OK before...

> In my adr.clp file I have got the following prg files :
> adraffi, adrcimp, adrclie, adrconf, adrfunc, adrhelp, adrmain,
> adrmkdb, adrmenu,
> adrmsgs, adrnovo, adrtrim, adrutil, blcalprg, blerrprg, errorsys,
> examplep
>

Maybe a Blinker user (I'm not) can spot something amiss with the
linkage?

Pete
--
"We have not inherited the earth from our ancestors,
we have borrowed it from our descendants."

ReIncarnated

2005-12-07, 3:55 am

With Novlib and Blinker, the order should be:

LIB clipper, novlibcl, novlib, extend

On Wed, 07 Dec 2005 06:06:31 +0000 (UTC), pete@nospam.demon.co.uk
wrote:

>
>I've no experience of novlib, but would suggest playing around
>with the order in which you specify those .lib files; also, I
>normally specify clipper.lib explicitly. However, if you
>inherited the .clp file and the link script, one can only assume
>that they worked OK before...
John.

Chriz

2005-12-07, 7:55 am

Thanks for all.

I found the clue.

It was the order of my prg files in the clp file that was causing the
error.

Hope this leason might help some others newbies.

Chiz.

Sponsored Links