BBS: Inland Empire Archive
Date: 05-06-92 (15:15)             Number: 193
From: RICHARD VANNOY               Refer#: NONE
  To: SCOTT WUNSCH                  Recvd: NO  
Subj: Hmm                            Conf: (2) Quik_Bas
SW>  While I must admit this is a crazy thread, I think you've given
SW>me an idea.  When you compile a program as an EXE, it stores the
SW>file size in the header.  This means DOS knows how big it should
SW>be, and ignores the rest of the file.  So... if you stick some data
SW>onto the end of an EXE, it just sits there.  Latest idea for a
SW>timelock <g>.  Sorry to bother you with this big long "thought",
SW>but I just wanted to thank you for the idea.

True.  Take a really short EXE file, tack a HUGE text file
on to the end of it.  When you run the EXE, it loads and
runs the EXE immediately (proving it didn't take the time
to load the text file).  This is kinda how PKLITE type
compressor programs work.  The prepended unzipper is loaded,
it goes to the "attached" compressed file, unpacks it on the
fly to memory and then executes a goto to the starting address
in memory of the "real" program when it is unpacked.

And yes, you can do some strange things with this "extra"
file storage area.

> MegaMail 2.1b #0:Time flies when you don't know what yur doing!

--- WM v2.01/91-0012
 * Origin: Com-Dat BBS  Hillsboro, OR.  HST (503) 681-0543 (1:105/314)
Outer Court
Echo Basic Postings

Books at Amazon:

Back to BASIC: The History, Corruption, and Future of the Language

Hackers: Heroes of the Computer Revolution (including Tiny BASIC)

Go to: The Story of the Math Majors, Bridge Players, Engineers, Chess Wizards, Scientists and Iconoclasts who were the Hero Programmers of the Software Revolution

The Advent of the Algorithm: The Idea that Rules the World

Moths in the Machine: The Power and Perils of Programming

Mastering Visual Basic .NET