Hi all,

On the Boxedapp packer please find some complement on what was embedded (35 Mb of code and runtime resources, dll-s and ocx-es):

- the VFP executable itself,
- VFP dlls and associated runtime resources,
- a host of legacy MS ocx (richtext.ocx, mscomct2.ocx...)
- an old copy of GDIplus (just in case... you never know),
- a couple of dbi ocx from their source and the associated required C++ runtime,
- the chilkat suite and the mapwingis ocx, a great but heavy GIS open-source ocx,
- a bunch of ocs and COM-registrable resource (plot-making, pdf-generation...)

output (see log below): a single 25 Mb executable that deploys easily and load fast (typically one or two secs.)!

Packers are becoming a standard pratice for python 3.x GUI applications. May I say that packing is indeed a fine solution for other interpreter-based development tools such our good old fox:-)

Cheers, Daniel,

********************************************************************************
Start building "C:\Myproject\executables\myVFPexe.exe" -> "C:\Myproject\executables\mydeployable.EXE"
Started calculating total size of embedded files...
Total size of embedded files is 36888392 bytes
Started calculating total count of registry keys and values...
Total count of registry keys and values is 16535
Opened splashscreen image "C:\HR descriptive deployment\splash_screen.jpg" successfully
Data read from splashscreen file "C:\HR descriptive deployment\splash_screen.jpg"
Going to write registry data
********************************************************************************