Hi Mathais,
Probably nothing to do with ME, but I thought you might have some ideas.
=============================================
....And on another machie it's different. If I start D5 with an empty project I get:
Cannot load package 'IndySystem50'. It contains unit 'filectrl', which is also contained in package 'Vclx50'
then when I drop an Indy component onto the form, I get the Assertion failure and the component doesn't appear.
If I then compile and run the app runs fine.
When I close the app I get several MS error report dialogs, then a fewof the the little run-time error 216 snags.
I'm running MadExcept 3, which is installed but disabled at runtime. If I disable ME IDE exception handling, I get: the same messages but from the IDE, not ME.
And all of the Indy components are gone.
Any thoughts? (Madshi also?)
<universe@NOSPAMnetcabo.pt> wrote in message news:2B73562D14E0E240universe@NOSPAMnetcabo.pt...
> Ross McMillan wrote:
>> I recenly installed D9/2005 and removed the bundled version of Indy. I have
>> installed the snapshot and my app compiles OK and seems to run, but when D9
>> starts up I get three snag messages:
>>
>> Failed to load c:\program files\borland\bds\3.0\Bin\dclIndyCore.dll.
>> File or assembly name dclIndyCore.dll, or one of its dependencies, was not
>> found.
>>
>> followed by:
>>
>> Failed to load c:\program files\borland\bds\3.0\Bin\dclIndyProtocols.dll.
>> File or assembly name dclIndyProtocols.dll, or one of its dependencies,
>> was not found.
>>
>
> Did you forget to remove the design packages from the IDE before
> removing the files? Those messages only appear for packages in the
> design packages list. You should always uncheck and remove the Indy
> packages before updating.
>
>>
>> The reason it can't find the DLL files is because I renamed them to keep
>> them out of trouble, but shouldn't the package installation regenerate them?
>>
>
> Yes, but not where you think: they're probably in "My Documents\Borland
> Studio Projects\Bpl".
>