RTLINK cannont find .LNK script file 1

[DeadIslets]

Seems like this forum is all but dead, but I'll post this anyway. After several years of being away from clipper, I'm back to supporting an old app. My problem is RTLINK cannot find my link script file, even though I'm compiling out of the same directory. The compiler finds all the files and produces object files but RTLINK says 'Path not found'.

I'm running this on an XP system and as you know the .lnk extension is used for Windows shortcuts as well. Something in my gut makes me think there is a conflict although I cannot prove it. I've even changed the reference to specify the absolute pathname, i.e. @C:\DEV\MMPROG.LNK and RTLINK still cannot find it.

I'm not sure where to go next. Any and all help is appreciated.

Thanks,

-Keith

 

[DeadIslets]

Just wanted to add this used to work fine, but something has changed. I think when windows cleans up unused shortcuts in can remove an old RTLINK script file too, as I had to find my script file on an old system, because it had disappeared on the development box.

 

[JockMullin]

Hi Keith

Oh boy, haven't used RTLINK in about 15 years.
However, I am pretty sure the .lnk is just the default extension for the link file, you can use any extension you want as long as you specify it explicitly in the command that invokes RTLink.

It would help a lot if you were to post your compile script which is invoking RTLink and the contents of your link file.

Also, are you sure you have set your lib environment variable? RTLink will want to look there for the list of libraries referenced in the LIB parameter.

Jock

 

[GriffMG]

Keith

Jock is right, it's not necessarily the .lnk file that it can't find - and yest the .lnk is just a convention I use .lk5 for some reason.

An yes, again, this forum is rather quiet these days... cue sound of tumble weed blown across the set...

Regards

Griff
Keep [Smile]ing

There are 10 kinds of people in the world, those who understand binary and those who don't.

 

[TonHu]

You'd better use .lk5 (or something else ofcourse) over .lnk, as the .lnk file-extension is used by Windows for shortcuts. It's even impossible to have the extension displayed in Windows Explorer! You may have accidentally deleted them when cleaning up your project directory using Windows Explorer.

 

[DeadIslets]

Hey guys,

Thanks so much for the responses. Griff and TonHu I did not realize .lnk was only a convention, but will definitely be using the .lk5 extension from now on. I was able to get around this the other night, but the solution was incredibly dirty. I went into the registry and eliminated the value for
HKEY_CLASSES_ROOT\lnkfile\shellex\IconHandler. While it allowed
RTLINK to find the file, it totally eliminated all icon functionality...bummer. Needless to say I will be restoring this registry value soon!

Thanks again everyone for the feedback. Even though this is old stuff I've enjoyed working with it again and quite frankly glad to see the Clipper community is only quiet, not dead.

-Keith

 

[TonHu]

glad to see the Clipper community is only quiet, not dead.

I suppose most of us have switched either to another development environment/language, like Java or C# et al, or are using the Harbour-Project or xHarbour compilers, that have their own support groups.
I can not even run my Clipper compiler & compiled apps on my x64 Windows 7 any more...

 

[JockMullin]

Yes, clipper is fading into history, though I still maintain systems for 3 or 4 customers running Clipper Summer '87 and Clipper 5 systems - they still do the job.

I now use xharbour for what little new clipper programming I do, and use XP mode under Win 7 64 bit to run the older 16 bit compilers and their output. Still works well.

Haven't done any Cobol programming lately, though

Jock

 

[jlcca]

Quote: [highlight]I can not even run my Clipper compiler & compiled apps on my x64 Windows 7 any more...[/highlight]

I use DOSBox, available from

http://www.dosbox.com/

to run my old Clipper programs.

As DOSBox works on both Windows and Ubuntu (Linux), my old Clipper programs can be used on both OSes.

Joe

 

[JockMullin]

Hi Joe

I did not know DOSBox was available for Linus - must give that a try. Thanks.

Jock