Hi Fritz,

>> Anyway, here's the solution: use the Windows search function
>> (case-insensitively) to find any files within your IBO tree that
>> contain the string "copkg32". Open those files (probably just one)
>> in a text editor, find the occurrences, and change the letter o/O
>> to digit 0. (...)

> I did so, but there where no results using Windows search for
> contents. Searching for "c0pkg32.obj" - no results too. Crazy! In
> the end I got the idea and looked around for any tool for search of
> contents: Ampersand File Tool - quick and dirty, but the grep works
> well. Gave me 222 lines with "c0pkg32.obj", but none with
> "copkg.obj" ... Thinking about ...

> In addition I did check both tools with "version" and "projects".
> Must say, that my(!) Windows search dosn*t work well searching for
> contents. Seems to filter for files extention - could not find a way
> to adjust it (same on two different installations of XP).

Wonderful World of Windows... ;-)

> Fix: There is a special version in the IBO40EDT_C5.bpl's
> project/options/paths, pointing to "..\.\lib".

I think you mean "..\..\lib". But this too is a problem that pops up
from time to time: project files containing relative paths that work
on Jason's computer but not necessarily on ours. E.g. in my setup I
have the IBO projects in D:\Firebird\IBO\IBO_<version>. The path
..\..\lib would therefore point to D:\Firebird\lib, which doesn't
exist. But if it does exist and it contains other versions of
libraries with the same name, it's even worse.

I suppose Jason has the IBO projects under $(BCB)\Projects, so that
..\..\lib points to $(BCB)\lib


Greetings,
Paul Vinkenoog