[USETUP] Don't error out in case one tries to "delete" empty partition space. Just... don't delete it ¯\_(ツ)_/¯
[USETUP] Further simplify partition creation UI code (#5837) - Use the same keypress 'C' to create either primary or logical partitions. Their type is automatically determined, whether they are created in general unpartitioned space, or space within an extended partition. - Extensively adapt the translations to reflect these changes.
[USETUP] Show the partition description (and its disk) being formatted and checked (#5837) And improve some strings -- Translations need to be rechecked!
[USETUP] Rename some MUI string identifiers (#5837) STRING_CHOOSENEWPARTITION --> STRING_CHOOSE_NEW_PARTITION STRING_FORMATTINGDISK --> STRING_FORMATTINGPART STRING_HDDSIZE --> STRING_HDPARTSIZE STRING_HDINFOPARTCREATE_1 --> STRING_HDDISK1 STRING_HDINFOPARTDELETE_1 --> STRING_HDDISK2 STRING_HDDINFO_{1,2} --> STRING_HDDINFO{1,2} Move STRING_NEWPARTITION just before STRING_PARTFORMAT and renumber the STRING_* identifiers.
[USETUP] Decouple bootloader install choice page from its actual installation (#5786) This allows to move this choice sooner in the process, thus having all the user key presses at first, then all the actual installation going without any key presses needed anymore... (that is, unless you wanted to install the bootloader on a removable device. Then it will prompt you there!) - Additional "cosmetic"/future-proof changes: Rename all instances of "floppy" in the bootloader install variables to "RemovableDisk" because it would be great to have this install choice later. - Layout adjustments in the translated bootloader pages. - Skip bootloader installation on upgrades. The idea here is that if we were able to find a ReactOS installation to upgrade, this means we were able to find a valid bootloader + boot entry. See also PR #5633. This logic may be slightly improved in the future to detect whether the underlying bootloader is FreeLdr and if so, only update its files. But this is for the future.
[USETUP] Display some contents in the page whilst installing the bootloader (#3559) CORE-17523
[USETUP] Display the "check the FS" section as a MUI page (#3474)
[USETUP] Add partition and disk description helpers to get standardized description strings. Replace and simplify USETUP code.
[USETUP] Update now-redirected 'http' and 'reactos.org' URLs (#2622) NB: http://www.reactos.org/uk/ is not updated, as it returns Error 404 - Page not found.
[USETUP] Remove redundant TEXT_STYLE_NORMAL flag on empty MUI entry field (#2275)
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
[SETUPLIB][USETUP] Slightly modify how and when the HW system partition is detected and used. CORE-16274 SETUPLIB: ========= - Find the system partition initially when we create the list of partitions. - Split the old CheckActiveSystemPartition() helper in two helpers: FindSupportedSystemPartition() and SetActivePartition(). This allows simplifying slightly the former one, and allows the user, in an interactive situation, to decide whether the "supported system partition" found can actually be used or not. - Remove the "OriginalSystemPartition" hack in the PARTLIST structure. - Add a note regarding the SystemPartition member in PARTLIST. USETUP: ======= - Use the introduced helpers from above. If the "system" partition we are going to use, in case we install ReactOS on a fixed disk, is *NOT* the same as the original one (e.g. because it is detected to be not supported by ReactOS...), display an informative screen to the user and let him confirm whether or not he wants to change the partition. If we install on a fixed disk, try to find a supported system partition on the system. Otherwise if we install on a removable disk, use the install partition as the system partition instead. This allows providing a fix for CORE-16274.
[USETUP] Localize the rest of the hardcoded error message strings
[USETUP] Use "L" key instead of "D" for deleting partitions at 1st setup stage
[USETUP] Modify the integrated user-mode PnP manager along the lines of UMPNPMGR, so that we can wait until all the queued device installations finish before continuing the installation further. Add a corresponding please-wait page and update the translations.
[USETUP] Display the chosen filesystem name in case of bootcode installation failure. Simplified implementation of the proposed solution by George Bișoc and revised by Victor Perevertkin from PR #952. NOTE: For whatever reason ERROR_INSTALL_BOOTCODE and ERROR_WRITE_BOOT seem to be redundant with each other. To be investigated...
[USETUP] Add new file-operation-related messages for deletion, moving and renaming.
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
[USETUP] Resources: fix a typo. svn path=/branches/setup_improvements/; revision=75748
[SETUPLIB][USETUP][INPUT.CPL] MUI integration with setuplib. [SETUPLIB] Copy the mui* files from usetup into the setuplib for later usage, and add mui.c to build. svn path=/branches/setup_improvements/; revision=75711 [SETUPLIB][USETUP] Start massaging the MUI files and split up what concerns only the usetup "resources", and what concerns general language parameters (in the setuplib). It may be interesting to retrieve the language parameters from INF file (e.g. intl.inf) (suggested by Giannis). svn path=/branches/setup_improvements/; revision=75715 [SETUPLIB] Add the necessary headers to mui.c to be able to compile. [USETUP] Comment out the languages that don't have any resources. svn path=/branches/setup_improvements/; revision=75716 [SETUPLIB][USETUP] Adjust MUI and settings code. - Re-enable settings code concerning language, keyboards & layout in the setuplib, and remove the old code in usetup. - Remove useless code in setuplib's mui.c. - Rename usetup's MUI "LanguageList" into "ResourceList" so as to avoid colliding with the "LanguageList" of setuplib. - Add the magic CMakeLists line "add_definitions(${I18N_DEFS})" that I forgot previously, that caused the "LanguageList" of setuplib to be empty! The code compiles and works during my tests. svn path=/branches/setup_improvements/; revision=75717 [SETUPLIB] Change some string pointer types & function prototypes so that the usetup-specific "SelectedLanguageId" variable is not used in the library. svn path=/branches/setup_improvements/; revision=75719 [SETUPLIB] Change some function prototypes so that the usetup-specific "SelectedLanguageId" variable is not used in the library. Also, make AddEntriesFromInfSection(), DefaultProcessEntry() and the typedef PPROCESS_ENTRY_ROUTINE private again. svn path=/branches/setup_improvements/; revision=75720 svn path=/branches/setup_improvements/; revision=75724 [USETUP] Code adaptations. - Transform some do{}while() loops into while(){} ones, since the lists on which we work may only contain one single {NULL} element. - Modify MUIGetOEMCodePage() call after r75719. - Use PCWSTR where needed. svn path=/branches/setup_improvements/; revision=75722 [USETUP] Adjust some MUI & settings calls, following the commits r75719, r75720 and r75721. svn path=/branches/setup_improvements/; revision=75723 [INPUT.CPL] Adjust inclusion of "muifonts.h" (commit 3dbd44f) due to changes introduced in r75711 and r75715.