>1) BORLNDMM.DLL
>2) DELPHIMM.DLL

>So if you upgrade your Delphi from 3 or 4 To 5 the go into the Delphi 5
>CD and to RunImage Directory ... Copy These Two Files to your
><Windows>/System Directory and Voila! ... The Most IDE
>Access Violation are gone!

>Hope this tip to help some people having problems with delphi 5.

> >A friend of mine got Delphi 5. He had Delphi 4 Prof on his machine.
> >So he did the Upgrade from Delphi 4 To Delphi 5... After using it
> >with his project When he tried to close the Delphi IDE he got
> >Error messages for "BorlndMM.DLL" File.... After a lot of
> >looking we found that the Delphi Installer Doesn't Replace 2 Dlls
> >with the newer versions.These Are :

> >1) BORLNDMM.DLL
> >2) DELPHIMM.DLL

> >So if you upgrade your Delphi from 3 or 4 To 5 the go into the Delphi 5
> >CD and to RunImage Directory ... Copy These Two Files to your
> ><Windows>/System Directory and Voila! ... The Most IDE
> >Access Violation are gone!

> >Hope this tip to help some people having problems with delphi 5.

> If those two files are in your Windows system directory, it's because
> _you_ put them there. No Delphi installation program--any
> version--puts them there.

> If you installed Delphi 5.0 on top of an existing Delphi 4.0
> installation, then you didn't heed the warning in the INSTALL.TXT
> file: "If you install to a different location, be sure you do not
> install over any previous Delphi release."

> -Steve

> What's the oversight? It's clearly documented when you need to
> deploy this DLL. The Delphi installer puts it in Delphi5/Bin. Nowhere
> else.

> /Anders

> ??? If you are deploying a Delphi application that uses BORLNDMM.DLL,
> and you neglect to properly install it along with your application,
> then that is certainly YOUR oversight, not Borland's. If you are
> saying that it was an oversight by Borland to not install those DLLs
> to the Windows system directory, the answer is no, it was a conscious
> decision to install them exactly where they are.

> -Steve

>The solution is simple:
>...
>2) Install BORLNDMM.DLL and DELPHIMM.DLL to the Windows system
>directory, but ensure that your application setup script explicitly
>includes those files, and checks that they are up to date (if not, it
>should replace them with the current version). This is exactly the
>same process that must occur whenever a Windows application that uses
>DLLs is installed.

>I can see the point you are trying to make, Steve, but I think the original
>poster is correct in calling this a Delphi problem.  If the DLLs are
>incompatible, they should have changed the name.  If they ARE downward
>compatible, they should have checked \windows\system.