Discussion:
trimming down BCB2006
(too old to reply)
Robert G. Hoover
2007-10-01 11:53:07 UTC
Permalink
Hi All,

My BCB2006 installation takes way too long to do just about everything.
Is there a way to trim it down so that it doesn't load the modules that
I don't use? I'd like to make it lean and mean... ;) I see "Component ->
Install Packages". Will that do the trick? Are there other shortcuts and
optimizations for this tool?

Many thanks,

Rob
Craig Farrell
2007-10-02 19:25:00 UTC
Permalink
Hi,
Post by Robert G. Hoover
Is there a way to trim it down so that it doesn't load the modules that
I don't use? I'd like to make it lean and mean... ;) I see "Component ->
Install Packages". Will that do the trick? Are there other shortcuts and
IMO, the bds.exe switch, -r, is perfect for that. It
is documented as a debugger aide, so that you can create
one IDE registry launch that does not have the packages
loaded that you want to debug in another IDE registry
launch, but it is perfect for creating an alternate
(lighter weight) launch of the IDE. To use it:
1) Copy a Windows shortcut of the installed shortcut
from Windows Start menu, Programs.
2) Edit the target property of the new shortcut, e.g.
"C:\Program Files\Borland\BDS\4.0\Bin\bds.exe" -rMyTrimmedIDE
3) Launch the IDE via this short and close the IDE
4) Open the registry and go to
HKEY_CURRENT_USER\Software\Borland\MyTrimmedIDE\4.0
5) Under Known Assemblies, Known IDE Packages, and Known Packages,
start deleting things. (it is usually possible to tell what
the package is by name or description, e.g. if you use
no modeling or refactoring remove all the things that
sound like Together, e.g. TGIDE100.bpl). Generallly the worse
that can happen is that you will a load error if you remove
a dependent package but not the package that needs. But an
error like that simpply serves to point out the relationship
of the packages/dlls/assemblies used by the IDE.
The nice thing about this is, if you go too far, or decide
you do want something loaded, simply delete
HKEY_CURRENT_USER\Software\Borland\MyTrimmedIDE\4.0
and go back to step 3.
-r can be used with the other command line switches, e.g.
"C:\Program Files\Borland\BDS\4.0\Bin\bds.exe" -rMyTrimmedIDE -pCBuilder


--Craig
Robert G. Hoover
2007-10-02 20:39:26 UTC
Permalink
Hi Craig,


Wow.... scary..... but sounds just like what I'm looking for...

Thanks!

Rob
Post by Craig Farrell
Hi,
IMO, the bds.exe switch, -r, is perfect for that. It
is documented as a debugger aide, so that you can create
one IDE registry launch that does not have the packages
loaded that you want to debug in another IDE registry
launch, but it is perfect for creating an alternate
1) Copy a Windows shortcut of the installed shortcut
from Windows Start menu, Programs.
2) Edit the target property of the new shortcut, e.g.
"C:\Program Files\Borland\BDS\4.0\Bin\bds.exe" -rMyTrimmedIDE
3) Launch the IDE via this short and close the IDE
4) Open the registry and go to
HKEY_CURRENT_USER\Software\Borland\MyTrimmedIDE\4.0
5) Under Known Assemblies, Known IDE Packages, and Known Packages,
start deleting things. (it is usually possible to tell what
the package is by name or description, e.g. if you use
no modeling or refactoring remove all the things that
sound like Together, e.g. TGIDE100.bpl). Generallly the worse
that can happen is that you will a load error if you remove
a dependent package but not the package that needs. But an
error like that simpply serves to point out the relationship
of the packages/dlls/assemblies used by the IDE.
The nice thing about this is, if you go too far, or decide
you do want something loaded, simply delete
HKEY_CURRENT_USER\Software\Borland\MyTrimmedIDE\4.0
and go back to step 3.
-r can be used with the other command line switches, e.g.
"C:\Program Files\Borland\BDS\4.0\Bin\bds.exe" -rMyTrimmedIDE -pCBuilder
--Craig
Loading...