A list of useful commands for the FFmpeg command line tool.
Download FFmpeg: https://www.ffmpeg.org/download.html
Full documentation: https://www.ffmpeg.org/ffmpeg.html
A list of useful commands for the FFmpeg command line tool.
Download FFmpeg: https://www.ffmpeg.org/download.html
Full documentation: https://www.ffmpeg.org/ffmpeg.html
node: Platform built on V8 to build network applications | |
git: Distributed revision control system | |
wget: Internet file retriever | |
yarn: JavaScript package manager | |
python3: Interpreted, interactive, object-oriented programming language | |
coreutils: GNU File, Shell, and Text utilities | |
pkg-config: Manage compile and link flags for libraries | |
chromedriver: Tool for automated testing of webapps across many browsers | |
awscli: Official Amazon AWS command-line interface | |
automake: Tool for generating GNU Standards-compliant Makefiles |
#!/usr/bin/env python | |
from sys import argv, stdout | |
from os import system, remove, path | |
from urlparse import urlparse | |
import re | |
import dfu | |
import ssl | |
import math | |
import json | |
import getopt |
#!/usr/bin/env python3 | |
import struct | |
import sys | |
from Crypto.Hash import SHA1 | |
stage2file = sys.argv[1] | |
outfile = sys.argv[2] | |
stage2 = bytearray(open(stage2file, "rb").read()) |
Guide created by Andrew Lee. Supports Windows 7, 8, 10, and 11.
Note that this guide does not go into detail, it's just providing the commands to install Windows.
Be cautions when doing this when dualbooting, please backup any existing data or you will lose them all.
First open CMD by pressing the following keys after booting into setup: Shift + F10
This list gives every product key for every BINK ID (that we know the algorithm of) and Channel ID. Not every product key can be listed, but if you have a Microsoft product that doesn't use pidgenx (pre-Vista and Office 2010), at least one of these keys will work. If it does, tell so in the comments! That way, we can properly label what goes to which.
Note: If NONE of these keys work,
BINK ID's are essentially the product identifier. 2A and 2B is Windows XP Home Edition, 50 and 51 is Halo: Combat Evolved, etc. These can overlap (because the geniuses at Microsoft decided to have them overlap), so the BINK doesn't really identify anything.