Hi, Dave. I had the same problem with runtime packages some years ago. As I couldn't solve it, the installation ended with 30MB. The executables I managed to generate with runtime packages were about six times smaller than the linked ones. I diminished it a little bit by integrating some executables into the main one, which was done just for the sake of easing the download. Recently I started using executable compressors but they don't work with the protection scheme we use for internet. As our systems are very dynamic (users are always presenting "very needed" resources), sending smaller upgrades would be interesting. As I'm porting systems to Delphi 2007, I hope using the packages will be easier, even if I have to dismiss Jedi.
Thanks for not making me feel it only happens to me! :) Eduardo --- In [email protected], David Smith <djsmith_1...@...> wrote: > > >>The point of > using the runtime packages is when you are sending your clients more > than >>one program using the same packages. In this case, your > installation may end smaller >>than if you had linked whatever you needed > inside each executable. > > This is true. If you've got several executables all using run-time > packages, they will re-use the same package saving possibly lots of RAM. Same > deal for modularized apps. > > I had an app once that I couldn't convert to run-time packages by just > checking the box, I had inexplicable errors that I couldn't figure out... I > was eventually able to do it by re-creating the app from scratch and > re-compiling as I added each new component/package. Good luck, it can be a > challenge! > > Dave > > > > > > > [Non-text portions of this message have been removed] >
