D:\화일전송프로그램\Mix.bpr has been updated version5.3
For more information on the changes made click on the help button.

이라고 나오고요 help를 누르면

Compatibility issues concerning projects and their files:

Loading old projects
    Symbol files from previous versions
    Auto-created resource files
    STDVCL32.DLL versus STDVCL40.DLL
    Packages and units referencing non-units
    Auto-generated sentinels
    Packages and name changes

Loading old projects

When you load a project made in an earlier version of C++Builder into C++Builder 5, it is automatically updated to the new XML format. An informational message is displayed that tells you the project was updated. C++Builder then makes the following changes to your project:

The project options file (BPR or BPK) is converted to XML format. See .BPR file for more about the format of the project options file.
    References to LIBs, BPIs, and CSMs are updated from 40 to 50 (for example, Vclib40.lib is changed to Vclib50.lib).
    When upgrading from C++Builder 1.0, the .MAK file is automatically translated to and saved in the new XML format (in a .BPR file).

Symbol files from previous versions

C++Builder 4 symbol files are not compatible with C++Builder 5. If you see the message "Error reading symbol file" when opening a C++Builder 4 application, close the message box and rebuild the application.

Auto-created resource files

When you create a typical application, C++Builder creates a <project>.RES file which contains version info resources plus the application뭩 main icon. If a .RES file is not found for an application that requires one, C++Builder will create one automatically when you open the project.

STDVCL32.DLL versus STDVCL40.DLL

Projects created in C++Builder 3 and earlier require STDVCL32.DLL when upgrading to C++Builder 5.0. When the project is saved in C++Builder 5.0, it will use the new STDVCL40.DLL and the older library is no longer required.

Packages and units referencing non-units

When compiling packages, it is no longer possible to simply reference units from non-units. To do this, in the calling .CPP file use the directive:

#pragma package(smart_init)

This ensures that the called unit is properly initialized. This had not worked before, but the failure was poorly handled. This new step ensures the correct checks are in place to make the reference successfully.

Auto-generated sentinels

Header files automatically generated by COM wizards (including the Automation Object Wizard, the COM Object Wizard, and so on) in earlier versions of C++Builder used the sentinel form with the form

__Aunit_H

This is as opposed to the new sentinel form. As a result, these header files must be manually updated or they will not work correctly with the Type Library Editor (possibly even crashing the Type Library Editor).

Packages and name changes

Many Borland-supplied packages change names in different versions of C++Builder. For example, the C++Builder 4 package inet40.bpl is named inet50.bpl in version 5. This causes problems when working on an application created in an earlier version. The workaround is to open the make file and change the names of the packages.

Similarly, some packages are only available in certain editions of C++Builder. For instance, an application that was created in the Enterprise edition might use packages only available in that edition. If the application is then used under a later, but lesser editon of C++Builder (like the Professional edition), packages only available in the higher edition will not be found. In these cases, remove the packages from the make file.

라고 나옵니다.

[C++ Error] Config.cpp(28): E2451 Undefined symbol 'BROWSEINFO' 컴파일을 하면 이렇게

나오네요.

나머지 에러들도 컨피그 화일에서 나오는데요..좀 부탁드립니다.