Windows 7 and Windows 8 users:
- Download the portable version of the latest Rufus release: Rufus - The Official Website (Download, New Releases)
- Connect a USB stick to the computer and launch Rufus.
- Select the correct device from the "device" drop-down menu (the USB-stick) and select MS-DOS from the "Boot selection" drop-down menu.
- Click start and wait the process to complete.
- Extract the two .exe files found in FRZN.zip archive to the root of the USB stick.
- Reboot the system and enter the bios. Under "Boot" tab make sure that CSM is enabled (if not, enable & save). Select the correct USB device from the boot override section (NOTE: NOT the one beginning with "UEFI:").
- After the system has loaded DOS, you can type in "flashrom -p internal" command to check if the SPI controller and the flash part itself is being detected properly.
Windows 10 users:
Starting from Windows 10, Microsoft no longer supplies the files required by MS-DOS environment with the OS.
Because of that, there are couple additional things that are required to get around the issue. First, instead of using the normal version of Rufus, you need to use a version which have been modified in a way which prevents the app from hiding the "MS-DOS" option on Win 10 systems. Secondly, you need to download the required Dll, which contains the files that are no longer supplied with Windows 10. After downloading the Dll, you need to place it to the "Windows\System32" folder in the sysroot. Then you are able to create a MS-DOS bootable USB stick using the same instructions as for Windows 7 / Windows 8. The dll can be removed after the MS-DOS bootable drive has been created, since obviously it is not used by the Win 10 system.
- The modified version, which I have personally compiled from Git sources can be downloaded from this link: Rufus_3.8.1579_Win10_MSDOS-Mod
- Since the required Dll file is property of Microsoft, I cannot share it. An untampered copy of the required diskcopy.dll file (e.g. on my system) has SHA-1 checksum of 6761320C6CDC0870D1DF62C2C988A8D1622CBC6E and it can be found from third party sites (such as this: diskcopy.dll from WinPCWare) through Googling the SHA-1 hash. But as I said, you can get the file from other locations / sources as well as long as you make sure its clean.
Note: DOS requires the filenames to meet the 8.3 naming format. This means that the filename "xxxx." cannot be longer than 8 characters, and that the suffix ".xxx" cannot be longer than three characters.
So if you have the time to try the new flasher, please do so.
That way we can see if there are any flash parts that need to be added to the program.
The program will state: "Found xxx flash chip "xxx" (xxx kB, SPI) mapped at physical address 0xfe000000" if the flash is detected.
Otherwise the flash part isn't detected and needs to be added. In this case, please take a picture of the message the program outputs and post it to this threads inside "Spoiler" tags.
The custom Flashrom version has been tested on 3000-series Ryzen CPUs, but it should work on all Ryzen generations regardless.
GPL compliance
