Here is mine.

/* BOOT FRAMES
* Each @"<text>" marks single frame, add as many as you want each will be displayed for one second
* @"" is multiline string so you can write multiple lines */
@"
Kernel: Initializing..."
,
@"
Kernel: Initialized.
Data Network: Scanning..."
,
@"
Kernel: Initialized.
Data Network: Scanned.
Display Nodes: Configuring..."
,
@"
Kernel: Initialized.
Data Network: Scanned.
Display Nodes: Configured.
Display Nodes: Booting..."
/* END OF BOOT FRAMES */

Another simple boot frame sequence..

/* BOOT FRAMES
* Each @"<text>" marks single frame, add as many as you want each will be displayed for one second
* @"" is multiline string so you can write multiple lines */
@"
Kernel: Initializing..."
,
@"
Kernel: Initialized.
Network: Connecting..."
,
@"
Kernel: Initialized.
Network: Online.
Displays: Initializing..."
/* END OF BOOT FRAMES */

Just a thought, could it be possible to move the boot frame definitions into the custom data of the autoLCD's programmable block?
For instance, boot frames in PB custom data might look like:

BF1="Kernel: Initializing..."
BF2="Kernel: Initialized.\nNetwork: Connecting..."
BF3="Kernel: Initialized.\nNetwork: Online.\nDisplays: Initializing..."

A loop to read the custom data might take up less space in the code than the currently hard coded boot frames. :-)