> the names of the modules and divides them (many if not all) according to OS because there is a *.rti file for each OS
no. the .rti file be there or not have no change about this. there's one rti file to each release because you may not need all them. just that
> Does autopatcher load the entire module
autopatcher reads the module to look for [OperatingSystem] tag. if matches, it will load it later
> apup gets the information on which module is for where to create the *.rti file
apup doesn't create the .rti files, we do. then, we just set that .rti files to be downloaded from our server when the script runs, like any other update
> why does it take minimum 10 minutes to do the "Loading..." before it starts "Verifying..." ?
because of the amount of the files that are checked using infos stored in the .rti file. plus, hd speed, processor, etc has his share of guilt in that time too. besides of that, even if not checking each module, autopatcher need read the full patch, looking for the .apm files. this may take some time, according to the number of files or, in this case, modules. so, even if you remove the .rti files, the load will not start in 1s (unless you have an really fast computer)
> *.script file 'knows' that the following modules are part of the Windows 2000 Critical Modules I figure
yes, but the .script files aren't loaded by autopatcher. those files are for apup only. if i'm not mistaken, i've read some time ago that one new version of autopatcher was borning, making apup.exe and autopatcher.exe the same thing. but i don't know when or if this will arrive some day
> 5 minutes to transfer 2GB
transfer isn't the same thing than open each file to read, you know. read operations us to take a lot more time than just copy
> "Loading.." stage.. or even how the *.rti/*.script files are created.
i believe that i already did it, but in loading process, autopatcher will look into subfolders looking for .apm files, read each one found, compare the file found with the fingerprint stored in the .rti file, do the same thing to each .exe and other files listed in .rti file, read the .apm file to learn if the files need to be loaded into your system, read the translation interface to your system, then prepare every single module in proper install order, create the module tree and then it's finished.
basically, this are fast tasks, except for the part of " compare the file found with the fingerprint stored in the .rti file, do the same thing to each .exe and other files listed in .rti file", that takes a lot more time than the other tasks to execute
about the .rti files, we do that, not apup and not autopatcher.exe. after make an release, we run a tool to read the fingerprint of each file found in subfolders and store it in an .rti file. that isn't really needed by autopatcher, except for check integrity
about the .script files, since ms bore us, we can't offer their updates from our own computers/servers. they say that it must come only from their servers. so, in order to do that, a lot of tasks need be performed, a lot of files need to be downloaded, like an download manager does. so, in that .script file, you found download locations for each update and each module. in order to save time in future updates, it also checks each file to see if the module needs to be updated. if so, it will download it again. in that file, you also found instructions to remove obsolete things, so, the user don't need remove manually any module. but after download, this file is useless. in apup 1.05, you will not see the current file anymore, since this file will be stored in a temp folder, that will be removed after apup finish his task or be closed
edit: sorry about the time that i'm taking to answer. i'm with an broken bone in my right arm, so, i'm taking more time to type. besides, i need think before i type and also think something about the translation (i speak brazilian portuguese...)