Anyway, loading the program into RAM means making a copy.

When you open an application, it is loaded into RAM.

These connected via the parallel interface allowing applications to be quickly loaded into RAM.

That's written into nonvolatile RAM and kept there.

During this period it composed the book that you see there and loaded it into RAM.

Applications are installed directly into RAM and executed in place.

Some systems use demand paging-waiting until a page is actually requested before loading it into RAM.

It needs to get into RAM, and then it sort of self-decrypts itself.

Is there no 500-megahertz weight-reduction machine that translates fat into RAM, for instance?

This allows for less use of disk space, as well as making them faster to load into RAM.