QUOTE(Chancer @ Feb 4 2009, 02:58 PM)
![View Post](http://forums.xboxscene.org/public/style_images/master/snapback.png)
Check your facts. Some of the updates do restart the 360 and install. All download and verify before installing. The fact you only see one progress bar does not indicate that the update is installing on the fly. this would be a very dangerous thing to do as a dropped packet means a corrupt update.
I'm speculatin' here by extrapolating from the black one to the white one, but the way it used to work was that the update was downloaded in place, and then every time the title was started up, it would verify the update before running it. All title updates restart the game (at which point it verifies and executes).
Dashboard updates restart the console (and therefore the dashboard), at which point it will verify the update and flash it (see the NXE on a memory stick hack).
Doing the verify at download time is pretty pointless, because it doesn't protect you from the user modifying the content once it's installed (See the Wii's homebrew channels).
In any case, all this stuff misses the point: all three consoles are complete dogs when it comes to downloading stuff. What they should be comparing them with is a PC downloading from akamai or similar. The 360 downloads multi-gigabye games over UDP, for fuck's sake. UDP! Quakeworld demonstrated that that was a slow, inefficient way to roll-out files. The content's all signed anyway; what's wrong with HTTP?
Arguments that PS3, 360 and Wii connect to different servers are dumb: LIVE+360, PSN+PS3 and WFC+Wii are all platforms; obviously we're interested in how the platform as a whole performs. The abilities of the end-user hardware in isolation is not really very interesting.
QUOTE(MrFish @ Feb 4 2009, 08:04 PM)
![View Post](http://forums.xboxscene.org/public/style_images/master/snapback.png)
the way it used to work was that the update was downloaded in place, and then every time the title was started up, it would verify the update before running it.
To elaborate, the title update is not 'installed' at all, but remains on the hard disk unmodified, and (if it passes the sig check) is used to patch the game at runtime. A bit of API wizardry allows the executable in the update to run as if it were running off the DVD, even though it's still on the hard drive, and yet still see any updated data files contained in the updates. Further API magic allows the executable on the DVD to verify and then hand-off to the executable on the disk without any kind of special provision in the source code.