РЕДАКТИРУЕМ ВНЕШНИЙ ВИД МЕНЮ ЗАГРУЗКИ

: Пред. 1, 2, 3 ... 7, 8, 9, 10, 11 След.

Опции показа
Не показывать Аватары Картинки званий Картинки в сообщениях Смайлики Подписи Показывать Спойлер открытым Загружаемые картинки

Отправлено: 16-Фев-2018 15:12

Belov_spy

Стаж: 6 лет 9 месяцев
Сообщений: 11
Репутация:0
[+] [-]

51019

51017Просто у других видел такие пункты на меню

Покажите где в EFI загрузчике видели...
А пункты, бесполезные... понты одни.

Ну вот, есть тут такой пункт http://usbtor.ru/viewtopic.php?t=465 на титульной
и тут http://usbtor.ru/viewtopic.php?t=562

Отправлено: 16-Фев-2018 15:19 (спустя 7 минут)

Joker-2013

Стаж: 9 лет 5 месяцев
Сообщений: 2053
Репутация:120
[+] [-]
Откуда: из прошлого

Belov_spy, так это же не EFI...
В Legacy то можно...

Отправлено: 16-Фев-2018 15:25 (спустя 5 минут)

Belov_spy

Стаж: 6 лет 9 месяцев
Сообщений: 11
Репутация:0
[+] [-]

51021Belov_spy, так это же не EFI...
В Legacy то можно...

Понятно, по картинке не совсем ясно это Legacy или Uefi

Отправлено: 16-Фев-2018 15:32 (спустя 6 минут)

Joker-2013

Стаж: 9 лет 5 месяцев
Сообщений: 2053
Репутация:120
[+] [-]
Откуда: из прошлого

Belov_spy, Вполне ясно. Efi меню, более скудное...
Никаких переходов и тем более не может быть загрузки WinXP.

Отправлено: 16-Фев-2018 16:51 (спустя 1 час 19 минут)

Belov_spy

Стаж: 6 лет 9 месяцев
Сообщений: 11
Репутация:0
[+] [-]

51023Belov_spy, Вполне ясно. Efi меню, более скудное...
Никаких переходов и тем более не может быть загрузки WinXP.

Что то про XP не подумал. А на счет скудности, понятно. Буду знать.
Спасибо.

Отправлено: 16-Фев-2018 23:53 (спустя 7 часов)

KottoSOFT

Стаж: 9 лет 10 месяцев
Сообщений: 562
Репутация:65
[+] [-]

51022Понятно, по картинке не совсем ясно это Legacy или Uefi

Понятно и видно с первого раза, если хоть раз запускал систему в UEFI или в LEGACY меню перепутать невозможно. Тут можно настроить (прописать в BCD)

Переходы к другим, bootmgr

Здесь же только запуск выбранного boot.wim

Это так не лучший вариант примера.

Отправлено: 17-Фев-2018 09:00 (спустя 9 часов)

Belov_spy

Стаж: 6 лет 9 месяцев
Сообщений: 11
Репутация:0
[+] [-]

Спасибо за примеры. Буду знать и учитывать. С UEFI флешкой почти закончил. Осталось софт найти на подобии kon-boot под uefi, и софтину которая показывает реальный нанешние пароли пользователей. Если есть инфа скиньте пожалуйста. Под 7-10 винду х32 и х 64

Отправлено: 17-Фев-2018 09:09 (спустя 8 минут)

Joker-2013

Стаж: 9 лет 5 месяцев
Сообщений: 2053
Репутация:120
[+] [-]
Откуда: из прошлого

Belov_spy, типо Konboot утиль от никза, другие можно выбрать в BootPass

и софтину которая показывает реальный нынешние пароли пользователей

читайте мат часть. пароль в системе нигде открыто не хранится, и возможно получение лишь перебором.
Но это уже оффтоп.

Отправлено: 01-Июл-2018 13:22 (спустя 4 месяца 12 дней)

Mariolast

Стаж: 6 лет 5 месяцев
Сообщений: 41
Репутация:0
[+] [-]

Где храняться оформления bootx64.efi, который при загрузке на UEFI?
Брал из сборки стрельца, но надо на GPT диске прикрутить груб2.
Прикрутил, bootx64.efi от стрельца поменял на bootx64w.efi дабы грубовский запускался.
Далее из меню самого груба вызываю bootx64w.efi
Запускается все как надо, но оформление напрочь теряется.

Отправлено: 01-Июл-2018 13:42 (спустя 20 минут)

Joker-2013

Стаж: 9 лет 5 месяцев
Сообщений: 2053
Репутация:120
[+] [-]
Откуда: из прошлого

Mariolast, Ищите в файлах MUI

Отправлено: 01-Июл-2018 20:32 (спустя 6 часов)

KottoSOFT

Стаж: 9 лет 10 месяцев
Сообщений: 562
Репутация:65
[+] [-]

54937Где храняться оформления bootx64.efi, который при загрузке на UEFI?
Брал из сборки стрельца, но надо на GPT диске прикрутить груб2.
Прикрутил, bootx64.efi от стрельца поменял на bootx64w.efi дабы грубовский запускался.
Далее из меню самого груба вызываю bootx64w.efi
Запускается все как надо, но оформление напрочь теряется.

Если судить по содержимому, которое можно выдернуть открыв файл restorator ом особо и не прикрутишь оформления, хотя попытаться не составит труда.
Сам сейчас не смогу нету свободной флешки для проведения опытов, способ прикрутки UEFI к оригинальному образу Windows 7x64 наглядно показан в Этом ролике
Вытащил файл из образа просмотреть на него

Содержимое bootmgr.xsl

<?xml version="1.0" encoding="unicode"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:osxml="osxml" version="1.0">
<_locDefinition>
<_locDefault _loc="locData"/>
<_locTag _locAttrData="pad-left,pad-right">p</_locTag>
<_locTag _locAttrData="height,width">textarea</_locTag>
<_locTag _locAttrData="minsize,noindent">select</_locTag>
<_locTag _locAttrData="size">progressbar</_locTag>
<_locTag _locAttrData="size,maxlen">input</_locTag>
<_locTag _locAttrData="value">osxml:update</_locTag>
</_locDefinition>
<xsl:template match="fve-bad-pcr-registers">
<osxml:text-mode-ui>
<head>
<footer color="RGBIXXXX"><xsl:text> ENTER=Continue</xsl:text></footer>
<meta key="ENTER" action="continue"/>
</head>
<body background-color="XXXX" foreground-color="RGBX">

Windows BitLocker Drive Encryption Information 

 
 
The system boot information has changed since BitLocker was enabled. 
 
You must supply a BitLocker recovery key to start this system. 
 
Confirm that the changes to the system boot information are authorized. 
 
If the changes to the system boot information are trusted, then suspend and resume BitLocker. This will reset BitLocker to use the new boot information. 
 
Otherwise restore the system boot information. 
 
</body>
</osxml:text-mode-ui>
</xsl:template>
<xsl:template match="fve-bad-code-id">
<osxml:text-mode-ui>
<head>
<footer color="RGBIXXXX"><xsl:text> ENTER=Continue</xsl:text></footer>
<meta key="ENTER" action="continue"/>
</head>
<body background-color="XXXX" foreground-color="RGBX">

Windows BitLocker Drive Encryption Information 

 
 
This boot application has changed since BitLocker was enabled. 
 
You must supply a BitLocker recovery key to start this system. 
 
Confirm that the changes to this boot application are trusted. 
 
If the changes are trusted then suspend and resume BitLocker. This will reset BitLocker to use the new boot application information. 
 
Otherwise re-install the previous version of this boot application. 
 
 

<xsl:for-each select="@filename">Boot Application: </xsl:for-each><xsl:value-of select="@filename"/> 
<xsl:for-each select="@badoption">Changed Option: </xsl:for-each><xsl:value-of select="@badoption"/> 

</body>
</osxml:text-mode-ui>
</xsl:template>
<xsl:template match="fve-bad-code-options">
<osxml:text-mode-ui>
<head>
<footer color="RGBIXXXX"><xsl:text> ENTER=Continue</xsl:text></footer>
<meta key="ENTER" action="continue"/>
</head>
<body background-color="XXXX" foreground-color="RGBX">

Windows BitLocker Drive Encryption Information 

 
 
The Boot Configuration Data (BCD) settings for the following boot application have changed since BitLocker was enabled. 
 

<xsl:for-each select="@filename">Boot Application: </xsl:for-each><xsl:value-of select="@filename"/> 
<xsl:for-each select="@badoption">Changed Setting: </xsl:for-each><xsl:value-of select="@badoption"/> 

 
You must supply a BitLocker recovery key to start this system. 
 
Confirm that the changes to the BCD settings are trusted. 
 
If the changes are trusted then suspend and resume BitLocker. This will reset BitLocker to use the new BCD settings. 
 
Otherwise restore the original BCD settings. 
 
</body>
</osxml:text-mode-ui>
</xsl:template>
<xsl:template match="fve-bad-srk">
<osxml:text-mode-ui>
<head>
<footer color="RGBIXXXX"><xsl:text> ENTER=Continue</xsl:text></footer>
<meta key="ENTER" action="continue"/>
</head>
<body background-color="XXXX" foreground-color="RGBX">

Windows BitLocker Drive Encryption Information 

 
 
The Storage Root Key (SRK) of the Trusted Platform Module (TPM) is incompatible with BitLocker. 
 
You must supply a BitLocker recovery key to start this system until the authorization information for the SRK of the TPM is reset to zero. 
 
</body>
</osxml:text-mode-ui>
</xsl:template>
<xsl:template match="fve-debugger-enabled">
<osxml:text-mode-ui>
<head>
<footer color="RGBIXXXX"><xsl:text> ENTER=Continue</xsl:text></footer>
<meta key="ENTER" action="continue"/>
</head>
<body background-color="XXXX" foreground-color="RGBX">

Windows BitLocker Drive Encryption Information 

 
 
The boot debugger is enabled. 
 
You must supply a BitLocker recovery key to start this system until the boot debugger is disabled. 
 
Disable the boot debugger by running this command in a command prompt window: 
 
bcdedit -bootdebug {bootmgr} off 
 
</body>
</osxml:text-mode-ui>
</xsl:template>
<xsl:template match="fve-ci-disabled">
<osxml:text-mode-ui>
<head>
<footer color="RGBIXXXX"><xsl:text> ENTER=Continue</xsl:text></footer>
<meta key="ENTER" action="continue"/>
</head>
<body background-color="XXXX" foreground-color="RGBX">

Windows BitLocker Drive Encryption Information 

 
 
Code integrity checks have been disabled or test signing is enabled in the Boot Configuration Data (BCD) store. 
 
You must supply a BitLocker recovery key to start this system until the BCD settings are updated to enable code integrity checks and disable test signing. 
 
</body>
</osxml:text-mode-ui>
</xsl:template>
<xsl:template match="fve-bad-partition-size">
<osxml:text-mode-ui>
<head>
<footer color="RGBIXXXX"><xsl:text> ENTER=Continue</xsl:text></footer>
<meta key="ENTER" action="continue"/>
</head>
<body background-color="XXXX" foreground-color="RGBX">

Windows BitLocker Drive Encryption Information 

 
 
The partition size specified in the partition table is smaller than the size of the file system contained by that partition. 
 
You must supply a BitLocker recovery key to start this system until the size of the partition calculated from the partition table is consistent with the size of the file system calculated from the bytes per sector and number of sectors fields in the boot sector. 
 
</body>
</osxml:text-mode-ui>
</xsl:template>
<xsl:template match="fve-tpm-invalidated">
<osxml:text-mode-ui>
<head>
<footer color="RGBIXXXX"><xsl:text> ENTER=Continue ESC=Reboot </xsl:text></footer>
<meta key="ENTER" action="continue"/>
<meta key="ESC" action="reboot"/>
</head>
<body background-color="XXXX" foreground-color="RGBX">

Windows BitLocker Drive Encryption Information 

 
 
The Trusted Platform Module (TPM) has locked out access to BitLocker keys until the system is rebooted. 
 
You must supply a BitLocker recovery key to start this system. 
 
You can also reboot the system to restore access to this selection without a recovery key. 
 
</body>
</osxml:text-mode-ui>
</xsl:template>
<xsl:template match="fve-tpm-lockout">
<osxml:text-mode-ui>
<head>
<footer color="RGBIXXXX"><xsl:text> ENTER=Retry ESC=Recovery </xsl:text></footer>
<meta key="ENTER" action="retry"/>
<meta key="ESC" action="continue"/>
</head>
<body background-color="XXXX" foreground-color="RGBX">

Windows BitLocker Drive Encryption TPM Lockout 

 
Too many incorrect PINs have been entered. 
 
Trusted Platform Modules (TPMs) temporarily lockout entering of a PIN if an incorrect PIN is used too many times to prevent guessing PINs. 
 
The TPM on this computer is currently locked out. The last PIN entered was ignored by the TPM. To start this system using a PIN, wait awhile or turn off the computer before reentering your PIN. To start this system immediately, use the BitLocker recovery console. 
 
Some TPMs store a counter of PIN attempts. Resetting the TPM lockout erases the counter of past PIN attempts. An administrator with the TPM owner password may use the TPM Management Console (tpm.msc) to reset the TPM lockout. 
 
Press ENTER to re-enter the PIN. Press ESC for recovery. 
 
</body>
</osxml:text-mode-ui>
</xsl:template>
<xsl:template match="fve-tpm-disabled">
<osxml:text-mode-ui>
<head>
<footer color="RGBIXXXX"><xsl:text> ENTER=Continue</xsl:text></footer>
<meta key="ENTER" action="continue"/>
</head>
<body background-color="XXXX" foreground-color="RGBX">

Windows BitLocker Drive Encryption Information 

 
 
The Trusted Platform Module (TPM) in this system is disabled. 
 
You must supply a BitLocker recovery key to start this system until the TPM is re-enabled. 
 
Enable the TPM from the system BIOS setup or from the TPM management console. 
 
</body>
</osxml:text-mode-ui>
</xsl:template>
<xsl:template match="fve-edit-boot-options-enabled">
<osxml:text-mode-ui>
<head>
<footer color="RGBIXXXX"><xsl:text> ENTER=Continue</xsl:text></footer>
<meta key="ENTER" action="continue"/>
</head>
<body background-color="XXXX" foreground-color="RGBX">

Windows BitLocker Drive Encryption Information 

 
 
You pressed the F8 or F10 key to enable alternative operating system boot options. 
 
You must supply a BitLocker recovery key to start this system with alternative boot options. 
 
 
</body>
</osxml:text-mode-ui>
</xsl:template>
<xsl:template match="fve-bad-shutdown">
<osxml:text-mode-ui>
<head>
<footer color="RGBIXXXX"><xsl:text> ENTER=Continue ESC=Reboot </xsl:text></footer>
<meta key="ENTER" action="continue"/>
<meta key="ESC" action="reboot"/>
</head>
<body background-color="XXXX" foreground-color="RGBX">

Windows BitLocker Drive Encryption Information 

 
 
Your computer did not start or shutdown normally, and you selected a boot option other than Start Windows Normally. 
 
You must supply a BitLocker recovery key to start this system with alternative boot options. 
 
You can also reboot the system and select Start Windows Normally to restore access without a recovery key. 
 
</body>
</osxml:text-mode-ui>
</xsl:template>
<xsl:template match="fve-restart-winload">
<osxml:text-mode-ui>
<head>
<footer color="RGBIXXXX"><xsl:text> ENTER=Continue</xsl:text></footer>
<meta key="ENTER" action="continue"/>
</head>
<body background-color="XXXX" foreground-color="RGBX">

Windows BitLocker Drive Encryption Information 

 
 
The BitLocker encryption key obtained from the Trusted Platform Module (TPM) was discarded by the operating system loader. 
 
The Trusted Platform Module (TPM) has locked out access to BitLocker keys until the system is rebooted. 
 
You must supply a BitLocker recovery key to start this system. 
 
</body>
</osxml:text-mode-ui>
</xsl:template>
<xsl:template match="fve-bad-external-key-file">
<osxml:text-mode-ui>
<head>
<footer color="RGBIXXXX"><xsl:text> ENTER=Continue</xsl:text></footer>
<meta key="ENTER" action="continue"/>
</head>
<body background-color="XXXX" foreground-color="RGBX">

Windows BitLocker Drive Encryption Information 

 

<xsl:for-each select="@volumeid">Drive Label: </xsl:for-each><xsl:value-of select="@volumeid"/> 
<xsl:for-each select="@keyfile">Key Filename: </xsl:for-each><xsl:value-of select="@keyfile"/> 

 
This key file exists on the USB flash drive, but is corrupt or invalid. Replace this file with a copy of the original key file. 
 
</body>
</osxml:text-mode-ui>
</xsl:template>
<xsl:template match="fve-external-key-needed">
<osxml:text-mode-ui>
<head>
<footer color="RGBIXXXX"><xsl:text> ENTER=Recovery ESC=Reboot </xsl:text></footer>
<meta key="ENTER" action="continue"/>
<meta key="ESC" action="reboot"/>
</head>
<body background-color="XXXX" foreground-color="RGBX">
 
 
 
 
 
 

Windows BitLocker Drive Encryption key needed. 

 
 
Insert key storage media. 
 
 
Press ESC to reboot after the media is in place. 
 
 
 
 
 

<xsl:for-each select="@volumeid">Drive Label: </xsl:for-each><xsl:value-of select="@volumeid"/> 
<xsl:for-each select="@keyfile">Key Filename: </xsl:for-each><xsl:value-of select="@keyfile"/> 

</body>
</osxml:text-mode-ui>
</xsl:template>
<xsl:template match="fve-external-key-loaded">
<osxml:text-mode-ui>
<body background-color="XXXX" foreground-color="RGBX">
 
 
 
 
 
 
 

Windows BitLocker Drive Encryption key loaded. 

 
 
 
Remove key storage media. 
 
 
</body>
</osxml:text-mode-ui>
</xsl:template>
<xsl:template match="fve-get-password">
<osxml:text-mode-ui>
<head>
<footer color="RGBIXXXX"><xsl:text> ENTER=Continue ESC=Exit </xsl:text></footer>
</head>
<body background-color="XXXX" foreground-color="RGBX">

Windows BitLocker Drive Encryption Recovery Key Entry 

 
Enter the recovery key for this drive. 
 
 
 
 
<xsl:for-each select="@volumeid">Drive Label: </xsl:for-each><xsl:value-of select="@volumeid"/> 
<xsl:for-each select="@passwordid">Recovery Key ID: </xsl:for-each><xsl:value-of select="@passwordid"/> 
 
Use the function keys F1 - F9 for the digits 1 - 9. Use the F10 key for 0. 
Use the TAB, SHIFT-TAB, HOME, END and ARROW keys to move the cursor. 
 
The UP and DOWN ARROW keys may be used to modify already entered digits. 
 
</body>
</osxml:text-mode-ui>
</xsl:template>
<xsl:template match="fve-bad-password">
<osxml:text-mode-ui>
<head>
<footer color="RGBIXXXX"><xsl:text> ENTER=Retry ESC=Exit </xsl:text></footer>
<meta key="ENTER" action="retry"/>
<meta key="ESC" action="continue"/>
</head>
<body background-color="XXXX" foreground-color="RGBX">

Windows BitLocker Drive Encryption Recovery Key Entry 

 
That recovery key is incorrect. 
 
Press ENTER to try another recovery key. 
 
</body>
</osxml:text-mode-ui>
</xsl:template>
<xsl:template match="fve-get-pin">
<osxml:text-mode-ui>
<head>
<footer color="RGBIXXXX"><xsl:text> ENTER=Continue ESC=Recovery </xsl:text></footer>
</head>
<body background-color="XXXX" foreground-color="RGBX">

Windows BitLocker Drive Encryption PIN Entry 

 
Enter the PIN for this drive. 
 
 
 
<xsl:for-each select="@volumeid">Drive Label: </xsl:for-each><xsl:value-of select="@volumeid"/> 
 
Use the function keys F1 - F9 for the digits 1 - 9. Use the F10 key for 0. 
Use the HOME and BACKSPACE keys to clear incorrect digits. 
 
Press ENTER after the PIN is typed. Press ESC for recovery. 
 
</body>
</osxml:text-mode-ui>
</xsl:template>
<xsl:template match="fve-get-pin-enhanced">
<osxml:text-mode-ui>
<head>
<footer color="RGBIXXXX">
<xsl:text> ENTER=Continue ESC=Recovery </xsl:text>
</footer>
</head>
<body background-color="XXXX" foreground-color="RGBX">

Windows BitLocker Drive Encryption PIN Entry 

 
Enter the PIN for this drive. 
 
 
 
<xsl:for-each select="@volumeid">Drive Label: </xsl:for-each>
<xsl:value-of select="@volumeid"/>
 
 
 
Use the HOME and BACKSPACE keys to clear incorrect characters. 
 
Press ENTER after the PIN is typed. Press ESC for recovery. 
 
</body>
</osxml:text-mode-ui>
</xsl:template>
<xsl:template match="fve-bad-pin">
<osxml:text-mode-ui>
<head>
<footer color="RGBIXXXX"><xsl:text> ENTER=Retry ESC=Recovery </xsl:text></footer>
<meta key="ENTER" action="retry"/>
<meta key="ESC" action="continue"/>
</head>
<body background-color="XXXX" foreground-color="RGBX">

Windows BitLocker Drive Encryption PIN Incorrect 

 
The PIN entered is incorrect. 
 
If you entered the PIN using the number keys, try using the function keys F1 – F10 instead.
Use F10 for the number zero. 
 
The Trusted Platform Module (TPM) verifies the PIN and the system boot information at the same time.
Some TPMs report that the PIN is incorrect when the system boot information has changed. If there
are known, trusted changes to the system boot information, press ESC to use the BitLocker recovery
console to start the system. To configure BitLocker to use the current system boot information, use
the BitLocker Control Panel to suspend and resume BitLocker. This will reset BitLocker to use the
new boot information. 
 
Press ENTER to try another PIN. Press ESC for recovery. 
 
</body>
</osxml:text-mode-ui>
</xsl:template>
<xsl:template match="fve-bad-pin-enhanced">
<osxml:text-mode-ui>
<head>
<footer color="RGBIXXXX">
<xsl:text> ENTER=Retry ESC=Recovery </xsl:text>
</footer>
<meta key="ENTER" action="retry"/>
<meta key="ESC" action="continue"/>
</head>
<body background-color="XXXX" foreground-color="RGBX">

Windows BitLocker Drive Encryption PIN Incorrect 

 
The PIN entered is incorrect. 
 
Some computers process keys differently during startup than during normal operation. If you are
sure you entered your PIN correctly, your computer may not be properly configured to support an
Enhanced BitLocker PIN. 
 
The Trusted Platform Module (TPM) verifies the PIN and the system boot information at the same time.
Some TPMs report that the PIN is incorrect when the system boot information has changed. If there
are known, trusted changes to the system boot information, press ESC to use the BitLocker recovery
console to start the system. To configure BitLocker to use the current system boot information, use
the BitLocker Control Panel to suspend and resume BitLocker. This will reset BitLocker to use the
new boot information. 
 
Press ENTER to try another PIN. Press ESC for recovery. 
 
</body>
</osxml:text-mode-ui>
</xsl:template>
<xsl:template match="osboot-error">
<osxml:text-mode-ui>
<head>
<xsl:for-each select="@nowds">
<title color="XXXXRGBX"><xsl:text> Windows Boot Manager </xsl:text></title>
</xsl:for-each>
<xsl:for-each select="@wds">
<title color="XXXXRGBX"><xsl:text> Windows Boot Manager (Server IP: <xsl:value-of select="."/>) </xsl:text></title>
</xsl:for-each>
<footer color="XXXXRGBX"><xsl:text> ENTER=Continue ESC=Exit </xsl:text></footer>
<meta key="ENTER" action="continue"/>
<meta key="ESC" action="exit"/>
</head>
<body background-color="XXXX" foreground-color="RGBX">
 
<xsl:for-each select="@generic-help">
Windows failed to start. A recent hardware or software change might be the cause.
To fix the problem:
 
 
1. Insert your Windows installation disc and restart your computer.
2. Choose your language settings, and then click "Next."
3. Click "Repair your computer."
 
If you do not have this disc, contact your system administrator or computer
manufacturer for assistance.
</xsl:for-each>
<xsl:for-each select="@hash-help">
A recent hardware or software change might have installed a file that is signed incorrectly or
damaged, or that might be malicious software from an unknown source.
 
 
If you have a Windows installation disc, insert the disc and restart your computer. Click
"Repair your computer," and then choose a recovery tool.
 
 
Otherwise, to start Windows so you can investigate further, press the ENTER key to display the boot
menu, press F8 for Advanced Boot Options, and select Last Known Good. If you understand why the
digital signature cannot be verified and want to start Windows without this file, temporarily
disable driver signature enforcement.
</xsl:for-each>
<xsl:for-each select="@io-help">
Windows has encountered a problem communicating with a device connected to your computer.
 
 
This error can be caused by unplugging a removable storage device such as an external USB drive
while the device is in use, or by faulty hardware such as a hard drive or CD-ROM drive that is
failing. Make sure any removable storage is properly connected and then restart your computer.
 
 
If you continue to receive this error message, contact the hardware manufacturer.
</xsl:for-each>
 
 

<xsl:for-each select="@file">
<xsl:text>File: </xsl:text>
</xsl:for-each>
<xsl:value-of select="@file"/>
 
<xsl:for-each select="@source">
Source:
</xsl:for-each>
<xsl:value-of select="@source"/>
 
Status: <xsl:value-of select="@status"/>
 
<xsl:for-each select="@line">
Line:
</xsl:for-each>
<xsl:value-of select="@line"/>
 
<xsl:for-each select="@info">
Info:
</xsl:for-each>
<textarea height="3"><xsl:value-of select="@info"/></textarea>

</body>
</osxml:text-mode-ui>
</xsl:template>
<xsl:template match="resume-error">
<osxml:text-mode-ui>
<head>
<title color="XXXXRGBX"><xsl:text> Windows Boot Manager </xsl:text></title>
<footer color="XXXXRGBX"><xsl:text> ENTER=Continue </xsl:text></footer>
<meta key="ENTER" action="continue"/>
</head>
<body background-color="XXXX" foreground-color="RGBX">
 
Your computer can't come out of hibernation. 
 
 

Status: <xsl:value-of select="@status"/>
 
<xsl:for-each select="@source">
Source:
</xsl:for-each>
<xsl:value-of select="@source"/>
 
<xsl:for-each select="@line">
Line:
</xsl:for-each>
<xsl:value-of select="@line"/>
 
 
<xsl:for-each select="@info">
Info:
</xsl:for-each>
<textarea height="2"><xsl:value-of select="@info"/></textarea>
 
 
<xsl:for-each select="@file">
File:
</xsl:for-each>
<xsl:value-of select="@file"/>

 
Any information that was not saved before the computer went into hibernation 
will be lost. 
</body>
</osxml:text-mode-ui>
</xsl:template>
<xsl:template match="osboot-list-tools">
<osxml:text-mode-ui>
<head>
<xsl:for-each select="@nowds">
<title><xsl:text> Windows Boot Manager </xsl:text></title>
</xsl:for-each>
<xsl:for-each select="@wds">
<title><xsl:text> Windows Boot Manager (Server IP: <xsl:value-of select="."/>) </xsl:text></title>
</xsl:for-each>
<footer><xsl:text> ENTER=Choose TAB=Menu ESC=Cancel </xsl:text></footer>
<meta key="ENTER" action="submit"/>
<meta key="ESC" action="exit"/>
<meta key="F8" action="advops"/>
<meta key="F8" action="submit"/>
<meta key="F10" action="bootops"/>
<meta key="F10" action="submit"/>
<meta key="OEMKEY" action="oem"/>
<xsl:for-each select="@timeout">
<meta key="ANY" action="anykey"/>
<meta event="TIMEOUT" action="submit"/>
<timer initial="{.}" control="timerval"/>
</xsl:for-each>
</head>
<body background-color="XXXX" foreground-color="RGBX">
 

Choose an operating system to start, or press TAB to select a tool:

 
(Use the arrow keys to highlight your choice, then press ENTER.)
 
 
<form>

<select name="osboot-selection" minsize="6" tip-target="advops-prompt" right-justify="true" noindent="false">
<xsl:for-each select="osboot-entry">
<xsl:element name="option">
<xsl:for-each select="@default">
<xsl:attribute name="selected">true</xsl:attribute>
</xsl:for-each>
<xsl:attribute name="value"><xsl:value-of select="@value"/></xsl:attribute>
<xsl:attribute name="tip"><xsl:value-of select="@tip"/></xsl:attribute>
<xsl:attribute name="carat"><xsl:value-of select="@carat"/></xsl:attribute>
<xsl:value-of select="@name"/>
<xsl:for-each select="@ems"> [EMS Enabled]</xsl:for-each>
<xsl:for-each select="@debugger"> [debugger enabled]</xsl:for-each>
</xsl:element>
</xsl:for-each>
</select>
 


<textarea name="advops-prompt" width="76" height="1"/>

 
<xsl:for-each select="@timeout">
<textarea name="timerstr" width="68">Seconds until the highlighted choice will be started automatically: </textarea><textarea name="timerval" width="8"/>
</xsl:for-each>
 
 
 
 

Tools:

 
 

<select name="osboot-tool-selection" minsize="3" tip-target="advops-prompt" right-justify="true">
<xsl:for-each select="osboot-tool">
<xsl:element name="option">
<xsl:for-each select="@default">
<xsl:attribute name="selected">true</xsl:attribute>
</xsl:for-each>
<xsl:attribute name="value"><xsl:value-of select="@value"/></xsl:attribute>
<xsl:attribute name="tip"><xsl:value-of select="@tip"/></xsl:attribute>
<xsl:value-of select="@name"/>
</xsl:element>
</xsl:for-each>
</select>

</form>
</body>
</osxml:text-mode-ui>
</xsl:template>
<xsl:template match="osboot-list">
<osxml:text-mode-ui>
<head>
<xsl:for-each select="@nowds">
<title><xsl:text> Windows Boot Manager </xsl:text></title>
</xsl:for-each>
<xsl:for-each select="@wds">
<title><xsl:text> Windows Boot Manager (Server IP: <xsl:value-of select="."/>) </xsl:text></title>
</xsl:for-each>
<footer><xsl:text> ENTER=Choose ESC=Exit </xsl:text></footer>
<meta key="ENTER" action="submit"/>
<meta key="ESC" action="exit"/>
<meta key="F8" action="advops"/>
<meta key="F8" action="submit"/>
<meta key="F10" action="bootops"/>
<meta key="F10" action="submit"/>
<meta key="OEMKEY" action="oem"/>
<xsl:for-each select="@timeout">
<meta key="ANY" action="anykey"/>
<meta event="TIMEOUT" action="submit"/>
<timer initial="{.}" control="timerval"/>
</xsl:for-each>
</head>
<body background-color="XXXX" foreground-color="RGBX">
 

Choose an operating system to start:

 
(Use the arrow keys to highlight your choice, then press ENTER.)
 
 

<form>
<select name="osboot-selection" minsize="10" tip-target="advops-prompt" right-justify="true" noindent="false">
<xsl:for-each select="osboot-entry">
<xsl:element name="option">
<xsl:for-each select="@default">
<xsl:attribute name="selected">true</xsl:attribute>
</xsl:for-each>
<xsl:attribute name="value"><xsl:value-of select="@value"/></xsl:attribute>
<xsl:attribute name="tip"><xsl:value-of select="@tip"/></xsl:attribute>
<xsl:attribute name="carat"><xsl:value-of select="@carat"/></xsl:attribute>
<xsl:value-of select="@name"/>
<xsl:for-each select="@ems"> [EMS Enabled]</xsl:for-each>
<xsl:for-each select="@debugger"> [debugger enabled]</xsl:for-each>
</xsl:element>
</xsl:for-each>
</select>
</form>
 


<textarea name="advops-prompt" width="76" height="1"/>

 
<xsl:for-each select="@timeout">
<textarea name="timerstr" width="68">Seconds until the highlighted choice will be started automatically: </textarea><textarea name="timerval" width="8"/>
</xsl:for-each>
 
</body>
</osxml:text-mode-ui>
</xsl:template>
<xsl:template match="bcd-entry-error">
<osxml:text-mode-ui>
<head>
<title color="XXXXRGBX"><xsl:text> Windows Boot Manager </xsl:text></title>
<footer color="XXXXRGBX"><xsl:text> ENTER=Continue </xsl:text></footer>
<meta key="ENTER" action="continue"/>
</head>
<body background-color="XXXX" foreground-color="RGBX">
 
The Windows Boot Configuration Data (BCD) store file contains some invalid information. 
 
 

Object GUID: <xsl:value-of select="@objectid"/>
 
<xsl:for-each select="@desc">
Description:
</xsl:for-each>
<xsl:value-of select="@desc"/>
 
<xsl:for-each select="@status">
Status:
</xsl:for-each>
<xsl:value-of select="@status"/>
 
<xsl:for-each select="@info">
Info:
</xsl:for-each>
<textarea height="2"><xsl:value-of select="@info"/></textarea>
 
 
 

 
The associated Windows Boot Loader entry may not be available for selection until the problem is rectified by an administrator. 
</body>
</osxml:text-mode-ui>
</xsl:template>
<xsl:template match="timeout-cancel">
<osxml:update disable-timer="true"/>
<osxml:update control="timerval" value=""/>
<osxml:update control="timerstr" value=""/>
</xsl:template>
<xsl:template match="progress-bar">
<osxml:text-mode-ui>
<body background-color="XXXX" foreground-color="RGBX">
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Windows is loading files...
 
<meter name="progressbar" size="76"/>

<textarea name="progressinfo" width="76"/>

</body>
</osxml:text-mode-ui>
</xsl:template>
<xsl:template match="progress-update">
<osxml:update control="progressbar" value="{@value}"/>
</xsl:template>
<xsl:template match="progress-info">
<osxml:update control="progressinfo" value="{@value}"/>
</xsl:template>
<xsl:template match="multicast-prestart">
<osxml:text-mode-ui>
<head>
<xsl:for-each select="@wds">
<title><xsl:text> Windows Boot Manager (Server IP: <xsl:value-of select="."/>) </xsl:text></title>
</xsl:for-each>
<footer><xsl:text> ESC=Exit </xsl:text></footer>
<meta key="ESC" action="exit"/>
</head>
<body background-color="XXXX" foreground-color="RGBX">
 

Waiting for Multicast session to start: <textarea name="activity" width="1"/>

 
</body>
</osxml:text-mode-ui>
</xsl:template>
<xsl:template match="multicast-end-prestart">
<osxml:text-mode-ui>
<body background-color="XXXX" foreground-color="RGBX">
 
</body>
</osxml:text-mode-ui>
</xsl:template>
<xsl:template match="multicast-activity-update">
<osxml:update control="activity" value="{@value}"/>
</xsl:template>
<xsl:template match="bootmgr">
<osxml:text-mode-ui>
<head>
<meta key="ANY" action="anykey"/>
<meta key="F8" action="advops"/>
<meta key="F10" action="bootops"/>
<meta key="OEMKEY" action="oem"/>
</head>
</osxml:text-mode-ui>
</xsl:template>
<xsl:template match="bootmgr-end-menu">
<osxml:text-mode-ui>
<body background-color="XXXX" foreground-color="RGBX">
 
</body>
</osxml:text-mode-ui>
</xsl:template>
<xsl:template match="*|@*|text()"/>
</xsl:stylesheet>

То , что обычно редактируется, если речь идёт об bootia32.efi.mui\bootx64.efi.mui

Отправлено: 02-Июл-2018 01:26 (спустя 4 часа)

Mariolast

Стаж: 6 лет 5 месяцев
Сообщений: 41
Репутация:0
[+] [-]

Тем не мение, переименовал bootx64.efi.mui в bootx64w.efi.mui (по аналогии с тем что переименовал bootx64.efi от стрельца на bootx64w.efi) и оформление подхватилось норм.

Отправлено: 02-Июл-2018 01:38 (спустя 11 минут)

KottoSOFT

Стаж: 9 лет 10 месяцев
Сообщений: 562
Репутация:65
[+] [-]

54952Тем не мение, переименовал bootx64.efi.mui в bootx64w.efi.mui (по аналогии с тем что переименовал bootx64.efi от стрельца на bootx64w.efi) и оформление подхватилось норм.

Ну что же раз вопрос решился, можем только порадоваться за вас.
Хотя насколько я понимаю, в принцип вникать не пробовали.

Отправлено: 09-Июл-2018 14:27 (спустя 7 дней)

Mariolast

Стаж: 6 лет 5 месяцев
Сообщений: 41
Репутация:0
[+] [-]

Почему же, разбирался немного. Но остался нюанс. С включенным SecureBoot оформление не применяется.

Отправлено: 09-Июл-2018 14:43 (спустя 16 минут)

Гость

Репутация:0
[+] [-]

Mariolast, и не будет применяться. Если применяется правленный MUI (без корректной цифровой подписи), он будет проигнорирован при загрузке в режиме SecureBoot.

Страница 8 из 11

: Пред. 1, 2, 3 ... 7, 8, 9, 10, 11 След.

Текущее время: 23-Ноя 21:16

Часовой пояс: UTC + 3

Вы не можете начинать темы
Вы не можете отвечать на сообщения
Вы не можете редактировать свои сообщения
Вы не можете удалять свои сообщения
Вы не можете голосовать в опросах
Вы не можете прикреплять файлы к сообщениям
Вы можете скачивать файлы