Scrumpmonkey said:
Definitions of download on the Web:
* transfer a file or program from a central computer to a smaller computer or to a computer at a remote location
* In computer networks, to download means to receive data to a local system from a remote system, or to initiate such a data transfer. Examples of a remote system from which a download might be performed include a webserver, FTP server, email server, or other similar systems. ...
*To receive digital information from a network. The term also refers to the process of saving retrieved information from digital information onto a hard drive, diskette or other electronic storage media.
Congratulations. You can use Wikipedia with the best of them. So can I [http://en.wikipedia.org/wiki/Installation_%28computer_programs%29]. My point is not that there is no downloading involved in the process but that the process is not strictly
just a simple download. If it were nothing more than "insert remote file A into local directory B", the result would not be a program that is registered as installed (and uninstallable) according to Windows, complete with registry entries and whatnot, without having run a separate installer or the game itself.
Yes, it does download the things it's installing. No, it's not exactly the same as downloading a JPEG image of a lolcat, other than that in both cases the data is coming from a remote source. Installation is a broader term and generally at least a slightly (and sometimes significantly) more involved process. Downloading is
only the transfer of remote data to a local system, while installation is a procedure involving the manipulation of data in a more complex way, and that data may or may not be local.
On some level, it doesn't actually matter where the data is, as long as access time/transfer rate is good enough for what you're doing with it. I can install software from a disk image on my hard drive to another location on that exact same hard drive. I can also do it from one hard drive to another in the same computer, or an optical drive to a hard drive, and it's still the same process on a basic level. I could do it from a drive in one computer to a second computer sitting next to it over an ethernet cable, and it's still the same. Put a router between them, and not much changes from the installer's point of view. Move one of them across the room or to the other end of the building, same thing. A completely separate arbitrary physical location? See above.
You can (and I do on a regular basis) mount a network share as a local volume, and programs will treat it like it's just another disk in your computer. They don't care (or even necessarily know) whether it really is, or it's on your local network, or it's hundreds or thousands of miles away. And yes, I also install things from (or sometimes to) non-local sources, or even a mixture of local and non-local, especially when package managers like the ones in Linux/BSD (or to a smaller extent other OSes) are involved. At some level, data is just data, and where it is doesn't matter and can be abstracted away from whatever's using it (e.g. an installer).