Supportnet / Forum / Windows98

hi,kann mir jemand sagen, zu was diese datei gut sein soll? beim starten zeigt es mir immer an, dass die datei fehlt. im papierkorb habe ich sie zwar gefunden, aber er akzeptiert sie nicht mehr, obwohl ich die löschung rückgängig gemacht habe. wäre nett, wenn der/die eine odere andere sie mal in seinem/ihrem pc suchen lässt und mir dann mitteilt, wofür die überhaupt zuständig ist und in welches programm sie gehört. danke für die mühe. fiscro

Ich habe zwar kein Win98 auf meinem Rechner, meine Arbeit damit sagt mir allerdings, dass es keine Original-Win98-Datei ist. Wurde also durch irgendein Proggi angelegt. Was nun ?
Checke alle Programme auf korrekte Lauffähigkeit! Wenn alle Programme korrekt laufen, kannst Du den entsprechenden Eintrag in der Registrierung löschen. Bitte vorher aber die Registry sichern, falls doch was schief geht.
Löschen :
Über Ausführen "regedit" aufrufen und mit <F3> nach genau diesem Dateinamen suchen. Alle vorhanden Einträge löschen. Aber wie gesagt, Sicherung nicht vergessen !!!
Nach dem Löschen sollte Dein Rechner fehlerfrei hochfahren, wenn nicht, noch mal in der System.ini suchen und entfernen (auch hier gilt, vorher sichern !)

Gruss Andreas

hi andreas,
das problem ist, dass mehrere programme nicht laufen. und deshalb würde ich gerne wissen, für welches prog dieser treiber ist. wenn verschiedene leute mal in ihrem pc danach suchen lassen würden, wäre es einfacher und ich müsste das programm nicht löschen. das löschen wäre die alternative, falls sich nichts ergibt. aber ich hoffe halt immer noch. gruss fiscro

Working with packages and components

A package is a special dynamic-link library used by C++Builder applications, the IDE, or both. Runtime packages provide functionality when a user runs an application. Design-time packages are used to install components in the IDE and to create special property editors for custom components. A single package can function at both design time and runtime, and design-time packages frequently work by calling runtime packages. To distinguish them from other DLLs, package libraries are stored in files that end with the .BPL (Borland package library) extension.

Like other runtime libraries, packages contain code that can be shared among applications. For example, the most frequently used C++Builder components reside in a package called VCL50. Each time you create an application, you can specify that it uses VCL50. When you compile an application created this way, the applications executable image contains only the code and data unique to it; the common code is in VCL50.BPL. A computer with several package-enabled applications installed on it needs only a single copy of VCL50.BPL, which is shared by all the applications and the IDE itself.

C++Builder ships with several precompiled runtime packages, including VCL50, that encapsulate VCL components. C++Builder also uses design-time packages to manipulate components in the IDE.

You can build applications with or without packages. However, if you want to add custom components to the IDE, you must install them as design-time packages.

You can create your own runtime packages to share among applications. If you write C++Builder components, you can compile your components into design-time packages before installing them.

Why use packages?

Design-time packages simplify the tasks of distributing and installing custom components. Runtime packages, which are optional, offer several advantages over conventional programming. By compiling reused code into a runtime library, you can share it among applications. For example, all of your applications--including C++Builder itself--can access standard components through packages. Since the applications dont have separate copies of the component library bound into their executables, the executables are much smaller--saving both system resources and hard disk storage. Moreover, packages allow faster compilation because only code unique to the application is compiled with each build.

Packages and standard DLLs

Create a package when you want to make a custom component thats available through the IDE. Create a standard DLL when you want to build a library that can be called from any Windows application, regardless of the development tool used to build the application.

Note: Packages share their global data with other modules in an application.

Runtime packages

Runtime packages are deployed with C++Builder applications. They provide functionality when a user runs the application.

To run an application that uses packages, a computer must have both the applications .EXE file and all the packages (.BPL files) that the application uses. The .BPL files must be on the system path for an application to use them. When you deploy an application, you must make sure that users have correct versions of any required .BPLs.

Using packages in an application

To use packages in an application,

Load or create a project in the IDE.
Choose Project|Options.
Choose the Packages tab.
Select the "Build with Runtime Packages" check box, and enter one or more package names in the edit box underneath. (Runtime packages associated with installed design-time packages are already listed in the edit box.) To add a package to an existing list, click the Add button and enter the name of the new package in the Add Runtime Package dialog. To browse from a list of available packages, click the Add button, then click the Browse button next to the Package Name edit box in the Add Runtime Package dialog.

If you edit the Search Path edit box in the Add Runtime Package dialog, you will be changing C++Builders global Library Path.

You do not need to include file extensions with package names. If you type directly into the Runtime Packages edit box, be sure to separate multiple names with semicolons. For example:

VCL50;VCLDB50;VCLDBX50


Packages listed in the Runtime Packages edit box are automatically linked to your application when you compile. Duplicate package names are ignored, and if the edit box is empty the application is compiled without packages.

Runtime packages are selected for the current project only. To make the current choices into automatic defaults for new projects, select the "Defaults" check box at the bottom of the dialog.

An application built with packages still must include header files for the packaged units that it uses. For example, an application that uses database controls needs the

#include "vcldb.h"


statement, even if it uses the VCLDB40 package. In generated source files, C++Builder creates these #include statements automatically.

Dynamically loading packages

To load a package at runtime, call the LoadPackage function. For example, the following code could be executed when a file is chosen in a file-selection dialog.

if (OpenDialog1->Execute())
  PackageList->Items->AddObject(FileName, Pointer(LoadPackage(Filename)));


To unload a package dynamically, call UnloadPackage. Be careful to destroy any instances of classes defined in the package and to unregister classes that were registered by it.

Deciding which runtime packages to use

C++Builder ships with several precompiled runtime packages, including VCL50, which supply basic language and component support.

The VCL50 package contains the most commonly used components, system functions, and Windows interface elements. It does not include database or Windows 3.1 components, which are available in separate packages.

For a list of the other runtime packages shipped with C++Builder, see "runtime packages, precompiled" in your online Help index.

To create a client/server database application that uses packages, you need at least two runtime packages: VCL50 and VCLDB50. If you want to use Outline components in your application, you also need VCLX50. To use these packages, choose Project|Options, select the Packages tab, and enter the following list in the Runtime Packages edit box.

VCL50;VCLDB50;VCLX50


Actually, you dont have to include VCL50, because VCL50 is referenced in the Requires list of VCLDB50. (See "The Requires list".) Your application will compile just the same whether or not VCL50 is included in the Runtime Packages edit box.

Custom packages

A custom package is either a BPL you code and compile yourself, or a precompiled package from a third-party vendor. To use a custom runtime package with an application, choose Project|Options and add the name of the package to the Runtime Packages edit box on the Packages page. For example, suppose you have a statistical package called STATS.BPL. To use it in an application, the line you enter in the Runtime Packages edit box might look like this:

VCL50;VCLDB50;STATS


If you create your own packages, you can add them to the list as needed.

Design-time packages

Design-time packages are used to install components on the IDEs Component palette and to create special property editors for custom components.

C++Builder ships with the following design-time component packages preinstalled in the IDE.



Table 10.1 Design-time packages

Package
Component palette pages

DCLSTD50.BPL
Standard, Additional, System, Win32, Dialogs

DCLTEE50.BPL
Additional (TChart component)

DCLDB50.BPL
Data Access, Data Controls

DCLMID50.BPL
Data Access (MIDAS)

DCL31W50.BPL
Win 3.1

DCLNET50.BPL
NMFAST50.BPL
Internet

BCBSMP50.BPL
Samples

DCLOCX50.BPL
ActiveX

DCLQRT50.BPL
QReport

DCLDSS50.BPL
Decision Cube

IBSMP50.BPL
Samples (IBEventAlerter component)

DCLINT50.BPL
(International Tools--Resource DLL wizard)

RCEXPERT.BPL
(Resource Expert)

DBWEBXPRT.BPL
(Web Wizard)

MFCWIZARD.BPL
(MFC Wizard)

These design-time packages work by calling runtime packages, which they reference in their Requires lists. (See "The Requires list".) For example, DCLSTD50 references VCL50. DCLSTD50 itself contains additional functionality that makes most of the standard components available on the Component palette.

In addition to preinstalled packages, you can install your own component packages, or component packages from third-party developers, in the IDE. The DCLUSR50 design-time package is provided as a default container for new components.

hi 123,
da ich kein englisch kann, nutzt mir die antwort leider nichts. ich danke dir aber für deine mühe trotzdem recht herzlich. fiscro

• Fehlermeldung beim Hochfahren
• Was bedeutet diese Fehlermeldung