startergo

## Find Available Target Editions
DISM.exe /Online /Get-TargetEditions

## Convert Server Standard 2019 Evaluation to Server Standard 2019
DISM /online /Set-Edition:ServerStandard /ProductKey:N69G4-B89J2-4G8F4-WWYCC-J464C /AcceptEula

## How To Activate 
slmgr /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
slmgr /skms [server]:[port]
slmgr /ato

startergo

Disable:

sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.metadata.mds.plist

Enable:

sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.metadata.mds.plist

startergo

• Patch the Fusion EFI boot ROMs

• Fusion blocks the use of regular 10.6 (not server) in the EFI ROM. To work around this, patch it using the EFI unlocker from GitHub. Uncompress in your downloads folder. Open the Terminal and run the following two commands:

 cd /Users/$USER/Downloads/efi-unlocker-master
./efi-macos.sh

• If the command succeeds, you should have two new files, EFI32-MACOS.ROM and EFI64-MACOS.ROM in the efi-unlocker-master folder.
• Modify the VM configuration

startergo

Linux Desktop on Apple Silicon in Practice

I bought M1 MacBook Air. It is the fastest computer I have, and I have been a GNOME/GNU/Linux user for long time. It is obvious conclusion that I need practical Linux desktop environment on Apple Silicon.

Fortunately, Linux already works on Apple Silicon/M1. But how practical is it?

• Two native ports exist.

startergo

##Use Powershell to Remove Network Boot Devices from the Boot Order You can use PowerShell to strip the Network BootTypes from the VMs boot order.

###Extract the Current Boot Order Using Powershell you can use this command to extract the current boot order:

    $old_boot_order = Get-VMFirmware -VMName testvm -ComputerName MyHyperVHost `
                      | Select-Object -ExpandProperty BootOrder

If you inspect $old_boot_order You should see the list of boot devices for testvm. Something like this:

startergo

• This commit drops support for mavericks: https://github.com/Homebrew/install/commit/4016e8675278dc7d5633179caf5507020091762b
• So you could take the parent commit: https://github.com/Homebrew/install/commit/4432ed3d3951613a10aa7180a384724ebea4314d
• Take its install.sh
• And plug that into the command:

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/4432ed3d3951613a10aa7180a384724ebea4314d/install.sh)"

startergo

• In LuCI: Network/ interfaces/wan->edit/advanced-> use custom dns servers/add a different dns server like 1.1.1.1/click + (plus)/ save/save and apply.

startergo

• In WSL2 run:

sudo apt update
sudo apt install qemu qemu-kvm libvirt-daemon-system libvirt-clients bridge-utils cpu-checker \
network-manager iptables-persistent linux-headers-generic \
qemu uml-utilities virt-manager git \
wget libguestfs-tools p7zip-full make dmg2img tesseract-ocr \
tesseract-ocr-eng genisoimage vim net-tools screen firewalld libncurses-dev -y
sudo apt install virt-manager
sudo addgroup kvm

startergo

The principle here is simple: Have a ready Windows installation on a partition on a GPT disk. Then add the boot files and boot record to an MBR disk, and add a bootloader entry to the BCD pointing to the Windows installation (more precisely, winload.exe) Install in BIOS mode on MBR and then convert using gptgen Install in UEFI mode using DUET. (ONLY for 64-bit!) Apply the windows install image (install.wim) using ImageX (Windows 7) or DISM (Windows 8+)on the GPT disk (best)

Next insert the Windows DVD, and that small disk, whatever it may be. Open the command prompt.

Use diskpart to verify for yourself which drives are data drives, and which is your windows boot drive. For safety, I recommend removing the drive letters of all other drives except the windows boot drive, which I'll refer to as C:, using the command :

startergo

Put the EFI Shell as EFI_System_Partition/EFI/BOOT/Bootx64.efi and the following script as EFI_System_Partition/EFI/BOOT/Startup.nsh

REM Enabling VGA on the PCI Bridge that the NVidia card is connected to
REM Setting Bridge Control Register (0x3e) to 8
mm 0010003E 8 -PCI

REM Enabling NVidia Card "I/O Space Access" and setting it as Bus Master
REM Setting Command Register (0x04) to 7
mm 03000004 7 -PCI