Konstantin Lapeev ttkoma

## Docker Desktop v 4.0.0 thru 4.22.1 direct download links
This list was compiled from https://web.archive.org/web/20230911135706/https://docs.docker.com/desktop/release-notes/, retrieved on 2024-05-24

It appears links for later updates than 4.22.1 are currently (as of early Aug 2024) being kept up to date on https://docs.docker.com/desktop/release-notes, I'm not going to continuously update this but others may in the comments below, so check that link or the comments if you need a later version than 4.22.1.

The information may not be correct in all cases, or may have changed since archive.org archived the page. At time of posting, I spot-checked a few links and they appeared to be good, but really, all I've done is copied, pasted, and visually formatted the information I found on archive.org, so no warrantee that it's good.

If the download links don't work, sometimes archive.org has the download archive, and you can try adding https://web.archive.org/web/20230911135706/ to the beginning of the URL. For instance, as of this writing, the 4.22.1 Windows download i

## ReadingPortableExecutable_PE_header.cs
// Credits: John Stewien
// From: http://code.cheesydesign.com/?p=572

/*
Reading the Portable Executable (PE) header in C#
My job consists of writing fully custom applications for groups of people. The time pressure of these projects is quite high, so generally people start using the application while I’m still writing it, which means I write it modularly and add features as I go along. I also fix bugs as they are discovered. My clients are 2 tiered where expert users get a new build first, they test if for a while, and if they think it’s acceptable they then pass it on to others.

This method of distribution is quite ad-hoc so when a client rings me up and asks me to view their screen to look at something, it’s useful to know what build they are running. To facillitate this I print the link date in the main Window Title so I instantly have an idea about how old the version is that I am looking at. This date is calculated at run time. To do this requires reading in the Portable Executable (PE) header from th

## remove_node_modules_recursively.ps1
<#
Note: Eliminate `-WhatIf` parameter to get action be actually done
Note: PS with version prior to 4.0 can't delete non-empty folders
#>

Get-ChildItem -Path "." -Include "node_modules" -Recurse -Directory | Remove-Item -Recurse -Force -WhatIf
	This list was compiled from https://web.archive.org/web/20230911135706/https://docs.docker.com/desktop/release-notes/, retrieved on 2024-05-24

	It appears links for later updates than 4.22.1 are currently (as of early Aug 2024) being kept up to date on https://docs.docker.com/desktop/release-notes, I'm not going to continuously update this but others may in the comments below, so check that link or the comments if you need a later version than 4.22.1.

	The information may not be correct in all cases, or may have changed since archive.org archived the page. At time of posting, I spot-checked a few links and they appeared to be good, but really, all I've done is copied, pasted, and visually formatted the information I found on archive.org, so no warrantee that it's good.

	If the download links don't work, sometimes archive.org has the download archive, and you can try adding https://web.archive.org/web/20230911135706/ to the beginning of the URL. For instance, as of this writing, the 4.22.1 Windows download i
	// Credits: John Stewien
	// From: http://code.cheesydesign.com/?p=572

	/*
	Reading the Portable Executable (PE) header in C#
	My job consists of writing fully custom applications for groups of people. The time pressure of these projects is quite high, so generally people start using the application while I’m still writing it, which means I write it modularly and add features as I go along. I also fix bugs as they are discovered. My clients are 2 tiered where expert users get a new build first, they test if for a while, and if they think it’s acceptable they then pass it on to others.

	This method of distribution is quite ad-hoc so when a client rings me up and asks me to view their screen to look at something, it’s useful to know what build they are running. To facillitate this I print the link date in the main Window Title so I instantly have an idea about how old the version is that I am looking at. This date is calculated at run time. To do this requires reading in the Portable Executable (PE) header from th
	<#
	Note: Eliminate `-WhatIf` parameter to get action be actually done
	Note: PS with version prior to 4.0 can't delete non-empty folders
	#>

	Get-ChildItem -Path "." -Include "node_modules" -Recurse -Directory \| Remove-Item -Recurse -Force -WhatIf