![]() ![]() Open an HTTPS connection to the update site (Probably something like, , os., etc.If using a locally specified update server, go to the one supplied by the user.The best thing I can come up with is if the DNS is going to change, have the old one only offer an update to ReactOSUpdate that will redirect it to the correct one. I'm not sure about this step: How for it to determine the ReactOS update sites DNS and/or IP and not be liable to spoofing.If this is the case, in the following steps, read "The local media" instead of a remote server where network transactions are being discussed. inf file paths that are always requested for always requested on driver installs) is called in the end). If a local source, ask for the path to the "INFO.UPD" (Or whatever the update data file (Think sort of like.If a local update server, ask for the name/IP (If not preselected by the Administrator), and if required credentials (Using a standard connect dialog box).If over the Internet normally, continue.Ask the user how they want to update: Over the Internet (Recommended) (Sub-option of a local update server), or via a local update source."It is strongly recommended you restart your system before attempting to update ReactOS")). If so, state that for some other reason the system should be restarted before any updating is attempted (Maybe give an option to go ahead anyway, with sufficient warning (e.g.Check if there's a previous update/restart pending.If the UserID is allowed, it silently continues to the next step, asks for your password.If RunAs is unavailable or unimplemented, gives an error along the lines of "Your user account has not been granted permission to run ReactOS Update.".If not, it can prompt with a RunAs box to enter valid credentials (Like MacOS X does with its control panel). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |