Microsoft Windows Build 133 is a mistypo, didn't exist, or an unknown build.
Unless it is a typo and supposed to be 1.33
but if it is meant to be 133 then the build DOES NOT exist. The closest I can find to 133 is Build 33, compiled just 4 days before the date Build 133 has on WinWorld. The build date is offset by 4 days.
So either Build 133 is:
Never existed and is fake (10%)
Actually real, but is a mistypo for 1.33 & date typo by 4 days (70%)
A build that was mislabeled as 1.33 and is actually a different unknown build that is not archived anywhere else (5%)
(The percentage means how much I would believe in these options.)
The following is the only photo I can find of the Build 1.33 diskset (Which it is NOT labeled 133.)
but if it is meant to be 133 then the build DOES NOT exist. The closest I can find to 133 is Build 33, compiled just 4 days before the date Build 133 has on WinWorld. The build date is offset by 4 days.
So either Build 133 is:
Never existed and is fake (10%)
Actually real, but is a mistypo for 1.33 & date typo by 4 days (70%)
A build that was mislabeled as 1.33 and is actually a different unknown build that is not archived anywhere else (5%)
(The percentage means how much I would believe in these options.)
The following is the only photo I can find of the Build 1.33 diskset (Which it is NOT labeled 133.)
Comments
It's 3.0 beta 1.33
Yeah, I know that it's a 1.33 build, but the "133" will be misinformation as I saw some people refer to 1.33 AS 133.
And if the original 1.33 dumper said that its "133", then something could have been tampered with the Floppy disk images.
I probably assumed it was formatted that way in some version string or something.
If not, then it is simply an error and I will make a note to correct it.
The disk scan is included in the download, so there is really no mistaking it for anything else.
The WinWorld build is labeled as 133 and it is actually 3.00.033 (1.33) and this will fix a lot of misinformation if re-labeled.
But you never know behind the scenes, as tens if not hundreds of fake builds have been falsely verified and uploaded on BetaArchive and then deleted after-wards, and could include 1.33 with a tiny chance.