В случае, если на компьютере установлена Windows 7 редакций Starter, Home Basic, Home Premium и Professional, можно не переустанавливая ОС, получить более функциональную редакцию вплоть до Ultimate, просто введя ключ от необходимой редакции... Для этого:

1. Идём в меню Пуск –> жмём ПКМ по Компьютер –> Свойства
2. Нажимаем наверху ссылку "Получить доступ к дополнительным функциям, установив новый выпуск Windows 7".
3. Далее все понятно и показано на скриншотах...

https://forums.mydigitallife.info/th...C-Modification

A new tool to perform insert a SLIC table using one of three main methods:

1) SSV3 - used for most AMI BIOSes. Does NOT work for some MSI boards. This is the safest for non-MSI boards.

2) SSV2 - used for MSI boards. Asus boards should use the SSV3 method, SSV2 is NOT needed.

3) Dynamic - The SLIC table is introduced into the BIOS so that, along with other ACPI tables, it's memory location is dynamically allocated by the BIOS. This is how manufacturers would insert a SLIC table, HOWEVER, it requires code modification to overcome locks - hence it is less safe than SSV2 or 3 which should be used in preference.

There is now (v1.00 RC2+) an attempt to automatically identify the manufacturer from the BIOS. Please ensure the correct BIOS manufacturer is selected from the drop down list before modding. This is most important for MSI, BIOSTAR and XFX. If your manufacturer is not listed then it is safe to select Other and try an SSV2 or SSV3 mod.

This is only needed for core v8 mods.

Notes:
- BIOS flashing is not for the faint hearted. There is ALWAYS an element of risk. Please ensure you are familiar with the procedure, and have necessary floppy disks etc., to allow a recovery in case of a flash failure.
- We assume you have a legitimate edition of Vista. Piracy is NOT condoned.
- Please remove any softmods. For Vistalo*der this includes repairing the boot sector and MBR of the hard disk. Use VOATK STANDALONE TOOL 2.5 (http://www.mediafire.com/?2fkigdmiwlx).
- Requires .NET v2.0+

Flash recovery information:
- Read here - http://www.biosman.com/biosrecovery.html - note that sometimes the filename needs to be different - the boot block error message will tell you, however this does mean you need a second machine to be able to change the file name.
- Also read here - http://forums.mydigitallife.info/showthread.php?t=2105
- Ensure that the version on the disk is the (unmodified) version you are trying to flash with SLIC - avoids problems with bootblock flashing.

SLIC and SLP files - The program needs:
- A 374 byte SLIC file (ASUS included, others available from other tools and softmod archives). Checksum is automatically corrected.
- A one line text file containing the SLP string you wish to be inserted. Again, ASUS is included. See http://www.msfn.org/board/index.php?...dpost&p=534097 - only the text string (without ') after the hex numbers is needed in the TXT file
- 911medic has kindly uploaded his collection of SLIC .BIN files here - http://urlisdown.org/slic.rar.

Vista Keys and Certificates
- Keys can be found here - http://forums.mydigitallife.info/showthread.php?t=2581
- Certificates can be found here - http://rapidshare.com/files/118119842/39-CERTS.zip

XP Keys and OEMBIOS files
- Keys can be foud here - http://forums.mydigitallife.info/showthread.php?t=2602

Method
1) Flash, using the manufacturers recommended method, the unmodified BIOS of the same version. This allows the bootblock etc. to be updated.
2) Mod the BIOS using the tool
3) Flash the SLIC'd BIOS from DOS. Use only the /i switch. This ensures the bootblock is left intact and maximises the chance of a successful recovery if a problem was to occur.
4) You then still need to use the appropriate key and certificate for Vista, and key and OEMBIOS files for XP.

Many thanks to Yen, Zort, 911medic and P4Spooky for their invaluable advice and feedback.

NOTE for automated Mod - sometimes a simulated keystroke is 'lost' causing the automated process to fail. In this case just click Go again.

I have added the ability (based on the methodology here - http://forums.mydigitallife.info/showthread.php?t=4792) to see if a certificate matches a SLIC file or the existing SLIC table in an already modded BIOS. Just click the verify button adjacent to the certificate text box after selecting a pre-SLIC'd BIOS or SLIC file. This does not need to be done to mod a BIOS, it is completely independant.

Enjoy :D
Andy

--------------------------

Latest version

Please always use latest version

v1.63 - https://mega.nz/#!BkBGyYjK!EgFEk_Lz0...zVJZTE2FL0vRgQ
SHA1 - 604BDC34EA096DFF65A5C18010037538249CD3DE

ADD: Recognise OA2.2 SLICs
ADD: Recompiled in VS 2012

Notes

Note - For more information about the DSDT modification (for SLI) see - http://forums.mydigitallife.info/sho...d.php?p=151297

Note - DSDT modification options are not enabled by default and can be found in the advanced options. You will be warned prior to modification if you are going to alter the DSDT table.

Note - For those ASUS BIOSes where a dynamic mod is not working (the RSDT/XSDT OEM/Table IDs don't change) - try a dynamic mod with 1.38+ (these have the OEMX string)

https://forums.mydigitallife.info/th...M-Certificates

Unlike SLIC tables, OEM Certificates aren't as easy to identify.
So here's a little tutorial that will allow you to properly identify an OEM Certificate, and match it with its correspondent SLIC table.

Tools needed:
- WinHex

Note: I will use as an example, the ubiquitous Asus SLIC table and OEM Certificate.

1. Open up the OEM Certificate with Winhex.


2. Locate and highlight the software licensing data (it always starts with "kgAAAAAAA").
In this case (Asus certificate) we will highlight this:
3. Go to "Edit" > "Copy Block" > "Into New File".
Give it any name you want and save. You will get this:

4. In the new file you've just created, go to "Edit" > "Convert..." > "Base64->Binary"
You will get this:

As you can see, the information in the OEM Certificate (encoded in Base64) matches the one in the Asus SLIC:

BLUE - OEMID

RED - RSA modulus

ORANGE - RSA public exponent
Always: 01 00 01 00 (65537)

GREEN - Windows Marker version
Always: 00 00 02 00 (0x20000)

PURPLE - Size of the OEM Certificate's licensing data.
Always: 92 00 00 00 (146 bytes)