https://betawiki.net/api.php?action=feedcontributions&user=Ovctvct&feedformat=atomBetaWiki - User contributions [en]2024-03-29T13:20:33ZUser contributionsMediaWiki 1.39.6https://betawiki.net/index.php?title=BetaWiki:Community_portal&diff=311998BetaWiki:Community portal2023-12-27T09:45:50Z<p>Ovctvct: Changed protection settings for "BetaWiki:Community portal" ([Move=Allow only administrators] (indefinite))</p>
<hr />
<div>__NEWSECTIONLINK__<br />
{{fmbox|type=system|image=none|text=<center><br />
<span style="font-size: 150%;">Welcome to BetaWiki community portal!</span><br />
<br />
This is where we discuss the operations of BetaWiki. Please help us to set down policies and guidelines, improve articles and more.<br />
<br />
If you want to request a specific administration action to be done, please use the [[BetaWiki:administrators' noticeboard|administrators' noticeboard]] instead.<br />
<br />
To add discussion, please add a new heading under this line.<br />
</center><br />
<br />
}}<br />
{{archives}}<br />
{{TOC|clear=left|limit=2}}<br />
<br />
== adding language parameter to the infobox windows build ==<br />
<br />
it will become easier to know the languages. [[Special:Contributions/51.15.78.38|51.15.78.38]] 10:38, 24 June 2023 (UTC)<br />
<br />
=== Support ===<br />
#per myself. [[Special:Contributions/51.15.78.38|51.15.78.38]] 10:38, 24 June 2023 (UTC)<br />
#I support this. Same feature is available for TheCollectionBook. But I doubt it's going to be accepted. This was requested a few times, and it was ignored. {{Unsigned|94.121.82.195}}<br />
#I support this, but only for releases preceding the introduction of the [[w:Multilingual_User_Interface|Multilingual User Interface (MUI)]] in Windows 2000. [[User:Ahernandez094|Ahernandez094]]<br />
=== Oppose ===<br />
#Unnecessary - Most internal beta builds are only available in a single language and if other languages are available, they ''will'' be mentioned on the respective build page. Public beta builds are available in basically every single language supported by Microsoft, so mentioning available languages on the respective build page is also unnecessary. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 12:12, 24 June 2023 (UTC)<br />
#:Also, most non-English builds of Windows, especially before Windows 8, are only official Beta/CTP/Preview/RTM builds and not internal ones. - <code>[[File:Windows logo (2003).svg|18px]] [[User:Bob2204|Bob2204]]</code> [[File:Arrow.png|15px]] Click here to begin. Or here. [[File:Arrow2.png|15px]] <code>[[User talk:Bob2204|Talk]]</code> - 16:18, 24 June 2023 (UTC)<br />
#::This https://betawiki.net/wiki/Windows_10_build_18327.1, it's not an official build. However it's available for many languages. {{Unsigned|94.121.82.195}}<br />
#::Do you seriously think that everyone who visit this wiki like reading long paragraphs? {{Unsigned|94.121.82.195}}<br />
#:::Read again. I only have said "most, '''especially before Windows 8'''". The Technical/Insider Preview thing changed many things, as they no longer release Preview/Beta/Alpha builds, but only multiple "Insider Previews", which can reach up to around 30 Insider Previews per version before a new version becomes released. - <code>[[File:Windows logo (2003).svg|18px]] [[User:Bob2204|Bob2204]]</code> [[File:Arrow.png|15px]] Click here to begin. Or here. [[File:Arrow2.png|15px]] <code>[[User talk:Bob2204|Talk]]</code> - 14:38, 25 June 2023 (UTC)<br />
#::::Understood. {{Unsigned|94.121.82.195}}<br />
#That's not how it works. Every build is compiled in all of the 23 base languages and all available SKUs. I oppose this simply because it would clutter the infobox, especially on Insider previews because they are indeed released in those base languages. --[[Special:Contributions/217.131.99.140|217.131.99.140]] 07:44, 29 June 2023 (UTC)<br />
#:Not '''every ''' is compiled in '''all''' languages. Some builds are only compiled for specific languages. Also what will you say about unleaked, shared or betas before Windows 7? {{Unsigned|94.120.197.130}}<br />
#::Simple: We never know what Microsoft did to their builds and if they're compiled in all languages or not. New languages were gradually added over time, so we need to remind ourselves of the past. Also, don't use {{tl|Unsigned}} to sign your comments, use <nowiki>~~~~</nowiki>. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 14:21, 4 July 2023 (UTC)<br />
#:::It's already impossible to know which languages are available in builds. But he said '''Every build is compiled in all of the 23 base languages''', which is definitely false. Otherwise we would have the builds 4074 in German or 5048 in French. The list goes on. [[User:94.120.197.130|94.120.197.130]] ([[User talk:94.120.197.130|talk]]) 14:29, 4 July 2023 (UTC)<br />
# Putting information to the infobox is a double-edged sword, it might make the information more discoverable but it also makes it more cluttered that it needs to be. Not to mention the relationship between SKUs, architectures and languages, since builds rarely are available in all listed combinations. A better approach would be a table like done for [[Windows 11 build 22000.1]]. --{{User:Ryuzaki/Signature}} 07:39, 29 June 2023 (UTC)<br />
#: Like in 2296.1 page? {{Unsigned|94.120.197.130}}<br />
<br />
== Changing recommended resolution images to 1,920 × 1,080 ==<br />
<br />
Literally every single build of Windows 11 use it for some reason, so I guess why not do it on other builds. [[Special:Contributions/37.120.213.238|37.120.213.238]] 11:36, 2 July 2023 (UTC)<br />
: I guess 1366 x 768 or 1400 x 900 would be better. 1920 x 1080 is too large. {{User:Someone200/Signature|23:36, 3 July 2023 (UTC)}}<br />
: The guidelines don't actually recommend a single resolution, they only say it should be period appropriate but ''at least'' 1024x768, unless the OS doesn't support that resolution. {{Unsigned|Ryuzaki}}<br />
<br />
==== Support ====<br />
#[[Special:Contributions/37.120.213.238|37.120.213.238]] 11:36, 2 July 2023 (UTC)<br />
<br />
==== Oppose ====<br />
#Most old hardware and older versions of Windows do not support such a ridiculously high resolution. Due to DPI scaling being a hit-or-miss on older OSes, the contents of the screenshots will also be too small, requiring the reader to click on the image to better view the screenshot. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 11:40, 2 July 2023 (UTC)<br />
#:Then why do Windows 11 builds do it then? I only requested this all because of Windows 11 images. [[Special:Contributions/37.120.213.238|37.120.213.238]] 11:43, 2 July 2023 (UTC)<br />
#::Newer versions of Windows are better suited for high-resolution displays, also blame the uploader for using that resolution. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 11:46, 2 July 2023 (UTC)<br />
#:::OH okay. Anyways, does 1,366 × 768 count as a "ridiculously" higher resolution? This is the alternative to 1,920 × 1,080, I guess. [[Special:Contributions/37.120.213.238|37.120.213.238]] 11:52, 2 July 2023 (UTC)<br />
#::::I don't think it counts, since it's basically 1024 × 768, but wider. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 12:18, 2 July 2023 (UTC)<br />
#:::I think we should only use 1920x1080 for win10 and win11 builds, and the problem is that there are a lot of Windows 10 builds that currently use 1024x768, which for Windows 10's time period is rather low. - [[User:Upseguest|Upseguest]] ([[User talk:Upseguest|talk]])<br />
<br />
==winmain in 2009/2010==<br />
There is a very odd thing I found out about winmain in the time period between builds 7232 (Win7) and 7700 (Win8). While 7232 already features the final Harmony wallpaper, 7700 oddly reused the betta fish one. The 7700 page said that it can be implied that this build was formed from a Win7 RC build. I really doubt this, because it's also possible that they just reverted this wallpaper thing for Win8/future winmain development. (At least the betta fish was used until Microsoft started the Technical Preview/Insider Program.) - <code>[[File:Windows logo (2003).svg|18px]] [[User:Bob2204|Bob2204]]</code> [[File:Arrow.png|15px]] Click here to begin. Or here. [[File:Arrow2.png|15px]] <code>[[User talk:Bob2204|Talk]]</code> - 23:29, 3 July 2023 (UTC)<br />
<br />
== Page Previews ==<br />
<br />
This wiki needs page previews feature. <small> —— This newly signed comment was added by [[File:Windows logo (2012).svg|15px]] [[User:LazytownSpo4015|<span class="signature-lazytownspo4015-userpage">'''<big>Lazytown Sportacus (LazytownSpo4015)</big>'''</span>]] • [[User talk:LazytownSpo4015|<span class="signature-lazytownspo4015-talk">Talk page]] • {{#if: | <nowiki>|</nowiki> '''{{{1}}}''' | }}</small> 14:03, 4 July 2023 (UTC)<br />
<br />
=== Support ===<br />
#Per myself. <small> —— This newly signed comment was added by [[File:Windows logo (2012).svg|15px]] [[User:LazytownSpo4015|<span class="signature-lazytownspo4015-userpage">'''<big>Lazytown Sportacus (LazytownSpo4015)</big>'''</span>]] • [[User talk:LazytownSpo4015|<span class="signature-lazytownspo4015-talk">Talk page]] • {{#if: | <nowiki>|</nowiki> '''{{{1}}}''' | }}</small> 14:03, 4 July 2023 (UTC)<br />
#I was so used to this exact feature on Wikipedia and it allows you to view pages without actually navigating to the specific page. When I first joined this wiki, I actually wondered why page previews aren't supported. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 14:12, 4 July 2023 (UTC)<br />
#This is a really convenient feature. I also wonder why they haven't been implemented yet. [[User:BetaReporter|BetaReporter]] ([[User talk:BetaReporter|talk]]) 17:27, 4 July 2023 (UTC)<br />
<br />
=== Oppose ===<br />
#You could use Visual Editor instead [[User:PikaaxYT|PikaaxYT]] ([[User talk:PikaaxYT|talk]]) 12:04, 22 October 2023 (UTC)<br />
<br />
== Move Insider Preview update pages to their respective build pages ==<br />
This is [https://betawiki.net/wiki/BetaWiki:Community_portal/Archive_9#Move_Insider_service_pipeline_updates_to_their_respective_build_pages. a (probably abandoned) proposal] made by [[Special:Contributions/Xeno|Xeno]]. I reopened this because the final decision hasn't been made, and I feel like the servicing pipelines updates are cluttering up the pages.<br />
<br />
If this reach 15+ support, I'll do it. It will take a long time though. (as always, please consider providing a reason if support/oppose as it helps me understand your opinion.)<br />
<br />
{{User:Someone200/Signature|14:23, 3 August 2023 (UTC)}}<br />
<br />
:The consensus was to carry that out, not sure why this needs another vote. --{{User:Ryuzaki/Signature}} 14:33, 3 August 2023 (UTC)<br />
<br />
== Purge <s>all</s> non-Windows related content (reopen) ==<br />
This is a reopen of [https://betawiki.net/wiki/BetaWiki:Community_portal/Archive_11#Purge_all_non-Windows_related_content my version] of [https://betawiki.net/wiki/BetaWiki:Community_portal/Archive_6#Purge_all_non-Windows_related_content a proposal by orbitron] that was abandoned, because apparently the aforementioned proposals aren't being passed through.<br />
<br />
Basically, most non-Windows stuff on the wiki, except macOS, iOS, DOS, and OS/2, gets literally no activity besides one or two users. Most pages covering Linux are too short and hardly contain any notable information (and no, bugs don't count as notable). The new features and changes present in each distro version are also not covered properly and the pages only contain the image of the desktop or the home screen, which is not enough for a good article.<br />
<br />
While the original proposal focused on all non-Windows content, I wanted to only focus on free-and-open-source OSes (such as Linux, BSD, and Haiku), Android, non-preinstalled web browsers (such as Google Chrome, Mozilla Firefox, Opera, and Netscape) and other less important OSes. For free-and-open source OSes and Android, they have been moved to [https://distro.wikitide.com/ a dedicated wiki that focused on these OSes.] For non-preinstalled web browsers, there are already Wikipedia pages for these browsers. I hope this makes BetaWiki a much cleaner site and live up to its name. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 14:40, 3 August 2023 (UTC)<br />
:The proposal was archived because it was dead with no clear consensus. Not sure what makes you think reopening it immediately after it got archived will reach a different result. --{{User:Ryuzaki/Signature}} 16:48, 3 August 2023 (UTC)<br />
::OK, I understand. I did not know that proposals would be archived if it was dead with no clear consensus. I first thought reopening my proposal would bring up attention to the two proposals I mentioned above, so I'm sorry for the mistake I made. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 23:11, 3 August 2023 (UTC)<br />
<br />
== Moving all GitHub issue related builds to a separate page ==<br />
<br />
I think that most of the Windows 10/11 pages are being cluttered with GitHub issue pages. Since these builds doesn't have a proper buildtag (only build number), I think they should be moved to a separate instead of being purged. Some of them could cause confusions because its build number is identical to another one.<br />
{{User:Someone200/Signature|03:15, 6 August 2023 (UTC)}}<br />
<br />
=== Support ===<br />
# Per myself. {{User:Someone200/Signature|03:15, 6 August 2023 (UTC)}}<br />
# Welp, this should also be done for servicing pipeline update builds. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 03:21, 6 August 2023 (UTC)<br />
# We should also do that for builds mentionned in SSUComp_KB*******.xml and Desktop_neutral_Forward_*****.****.***************.******-****.CompDB.xml files [[User:PikaaxYT|PikaaxYT]] ([[User talk:PikaaxYT|talk]]) 10:27, 11 August 2023 (UTC)<br />
<br />
=== Oppose ===<br />
<br />
== Adding downloads of the builds in their infoboxes (CLOSED) ==<br />
<br />
<s>Or at least adding an information on where to download the builds <small>—&nbsp;Preceding unsigned comment added by [[User:PikaaxYT|PikaaxYT]] ([[User talk:PikaaxYT|talk]] • [[Special:Contributions/PikaaxYT|contribs]]) </small></s><br />
<br />
I closed the request because download links would violate the guidelines {{unsigned|PikaaxYT}}<br />
<br />
=== Support ===<br />
<br />
1. [[User:PikaaxYT|PikaaxYT]]<br />
<br />
=== Oppose ===<br />
<br />
# See [[BW:Guidelines#Legal|BW:Guidelines § Legal]]. [[User:Jurta|Jurta]] ([[User talk:Jurta|talk]] • [[Special:Contributions/Jurta|contribs]]) 19:52, 10 August 2023 (UTC)<br />
# We are most certainly '''NOT''' providing download links to these builds on the wiki. The wiki is intended to be a knowledge base for these builds. Find the builds yourself. The Windows build FAQ page points out that archive.org and WinWorld are good starting points to find most builds. Although, be careful as there are fake builds out there. It is very easy to find these builds anyways. <code>[[File:Windows Orb logo (2006).png|18px]] [[User:WindowsGuy2021|WindowsGuy2021]]</code> 2:59, 10 August 2023 (UTC)<br />
<br />
== Purge Linux and Android content ==<br />
here we go again...<br />
<br />
Most Linux distributions in BetaWiki are not notable, and by "not notable" I mean most of the articles talking about a Linux distro are too short, low quality, and hardly contain any useful or notable information. The Android articles are a good example of this, since they are made of an infobox, a lead sentence, a list of changes (or builds), and that's it. The information necessary for a knowledge base, such as the development history, features, and the overall aspects of a Linux distro, is also missing from the aforementioned articles. Other websites did a much better job at documenting these distros since they are not Windows-centric, unlike BetaWiki. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 09:10, 22 August 2023 (UTC)<br />
:I agree for purging Linux articles but not for purging Android articles because if they are deleted we should also purge iOS articles since most builds doesn’t even have an article and the few builds that have an article only have an infobox and a smaller sentence than Android articles [[User:PikaaxYT|PikaaxYT]] ([[User talk:PikaaxYT|talk]]) 12:03, 22 October 2023 (UTC)<br />
::now that DistroWiki got closed, following with the stepdown of Nara and GT610, I think that never ending purging discussion finally reached a dead end, at least for now. <br />
::Yes, there are still better wikis and pages for operating systems other than windows, but that discussion didn't really help us to make steps forward. At the end, the consequence was another wiki for just that reason, which failed to gain any reputation in their scene like betawiki does and thus failing overall. No one came out from there as winner. <br />
<br />
::The best thing that we can do for now is just continuing our work here. - <code>[[File:Windows logo (2003).svg|18px]] [[User:Bob2204|Bob2204]]</code> [[File:Arrow.png|15px]] Click here to begin. Or here. [[File:Arrow2.png|15px]] <code>[[User talk:Bob2204|Talk]]</code> - 23:00, 30 November 2023 (UTC)<br />
:::Nara here. Yes, BetaWiki should've stayed the same and the DistroWiki effort, in my opinion, was just a waste of time. Despite having 99% of its focus on Windows, there are still people who do Linux stuff here and we should respect them. I'll say the discussion is finally over, like you said. [[Special:Contributions/139.192.153.112|139.192.153.112]] 03:53, 2 December 2023 (UTC)<br />
<br />
== discord server invite link ==<br />
<br />
i'm trying to rejoin the BW discord, but it says the link is expired. Has the server been deleted or is it a dead invite? {{Unsigned|Grafality}}<br />
:It's a dead invite. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 05:33, 16 September 2023 (UTC)<br />
::if it is a dead invite, then why wouldn't I rejoin BW Discord server? Also I'm sorry for my past actions while I'm in the server. <small> —— This newly signed comment was added by [[File:Windows logo (2012).svg|15px]] [[User:LazytownSpo4015|<span class="signature-lazytownspo4015-userpage">'''<big>Lazytown Sportacus (LazytownSpo4015)</big>'''</span>]] • [[User talk:LazytownSpo4015|<span class="signature-lazytownspo4015-talk">Talk page]] • {{#if: | <nowiki>|</nowiki> '''{{{1}}}''' | }}</small> 08:57, 16 September 2023 (UTC)<br />
:::I hate to tell you this, but you have been banned from the BW Discord server. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 08:59, 16 September 2023 (UTC)<br />
::::I know but, I'm very sorry for my past actions when i was there. How am i going to appeal a ban from the BW discord server? <small> —— This newly signed comment was added by [[File:Windows logo (2012).svg|15px]] [[User:LazytownSpo4015|<span class="signature-lazytownspo4015-userpage">'''<big>Lazytown Sportacus (LazytownSpo4015)</big>'''</span>]] • [[User talk:LazytownSpo4015|<span class="signature-lazytownspo4015-talk">Talk page]] • {{#if: | <nowiki>|</nowiki> '''{{{1}}}''' | }}</small> 09:13, 11 October 2023 (UTC)<br />
:::"if it is a dead invite, then why wouldn't I rejoin BW Discord server?" Precisely because it was a dead invite? It is fixed now though. --{{User:Ryuzaki/Signature}} 09:46, 16 September 2023 (UTC)<br />
<br />
== 8297.0.fbl_fun_embedded_xos.120311-1700 ==<br />
<br />
Please make a page for Xbox One OS build 8297. It's availible, so it should be possible. I'm not experienced enough to get the OS and run it in some sort of emulator. {{Unsigned|146.212.161.185}}<br />
:You literally put the same thing in here and in [[Talk:Main Page]]. [[File:Windows_logo_(2006).svg|35px]] [[User:763004|'''763004''']] ([[User talk:763004|Talk]] &bull; [[User:763004/Sandbox|Sandbox]]) 17:27, 10 October 2023 (UTC)<br />
<br />
== Cleaning up Bugs and quirks section ==<br />
<br />
After some deep review about a few additions within these sections lately, it's been seen that we're getting a lot of hardware/VM-only related problems that seems to be extremely niche to encounter, and in several cases, results from using a config that is way above what was the norm/available at the time. Most of these bugs tend to be of sensitive/setup-specific, and often are just encountered by one user due to a bad config.<br />
<br />
As a result of this, I'm going to start suggesting that any compatibility bugs are heavily stripped down, since adding these bugs aren't necessarily of "meaningful" edits and ends up being more disruptive for the flow of the page. This would mean that the following changes will be made, with some examples of what we don't want:<br />
* Any bugs that mention [https://betawiki.net/index.php?title=Windows_Longhorn_build_4002_%28Lab06_N%29&type=revision&diff=307656&oldid=303257 "this build won't install in modern versions of <program>"] will no longer be allowed and will be removed. This is a setup-specific problem, and also this wiki is not a compatibility checklist.<br />
* Any bugs that mention [https://betawiki.net/index.php?title=Windows_NT_4.0_build_1130&type=revision&diff=261298&oldid=260828 "this driver doesn't work"] will also no longer be allowed and will be removed. Generally a setup-specific problem or incomplete driver support; again betas aren't meant to be complete.<br />
* A lot of [https://betawiki.net/index.php?title=Windows_XP_build_2202&type=revision&diff=308836&oldid=303304 VM compatibility bugs] will be stripped down. I'd prefer they'd be removed completely, but that's not necessarily going to be favorable for certain builds that need an abnormally early compatibility. But then again, it's preferable to use the version that was closest to when that build was compiled. For reference, VMware 5.0 released around 2005, while VMware 6.0 released around 2007. So it would not make sense to install say build 5231 on modern versions, and vise versa. This is also largely a setup-related problem, usually.<br />
<br />
Most of the bugs that are intended to be removed will usually be of that hardware related, unless they are a widespread problem and often well-known by Microsoft in documentation, such as the Windows NT 3.x processor setup bug. But for singular builds, these bugs would have to go, and don't contribute as a "meaningful" edit and more of a way to inflate the page with niche setups.<br />
<br />
Also to note adding "persists until build" isn't necessarily a meaningful edit, as well. We do not need to document every little bug you see, as again beta builds are often unstable and prone to bugs and inconveniences. Bugs are to only be documented usually when they often affect real hardware too and is major enough that it often impacts the usability of the build even in the most general scenario. Subsequently reverting/adding these oft-unnecessary bugs is means of disruptive editing, and warnings will be handed out.<br />
<br />
[[User:BF10|BF10]] ([[User talk:BF10|talk]]) 13:35, 4 December 2023 (UTC)<br />
:We also have to remove "this build has some stabillity issues" edits, because these are '''beta builds''', '''''of course '''''theyre gonna be unstable. [[Special:Contributions/37.231.130.49|37.231.130.49]] 21:52, 4 December 2023 (UTC)<br />
: Just a question, does 3rd party app compatibility bugs notable? {{User:Someone200/Signature|14:19, 6 December 2023 (UTC)}}<br />
::no. Pre-release builds aren't designed at first place to run third-party apps, maybe at most those ones from the era of the specific build. For example, imagine you were one of the testers of Vista Beta 2 or RC in 2006, you would've likely tested out how the ''back then'' latest versions of Firefox, 1.5 or 2.0, would perform. The builds weren't designed to run way newer versions like 38. Still, bugs and quirks with 3rd-party apps wouldn't really that useful for that wiki, per bf10. - <code>[[File:Windows logo (2003).svg|18px]] [[User:Bob2204|Bob2204]]</code> [[File:Arrow.png|15px]] Click here to begin. Or here. [[File:Arrow2.png|15px]] <code>[[User talk:Bob2204|Talk]]</code> - 14:31, 6 December 2023 (UTC)<br />
<br />
== Creating new user warning templates ==<br />
<br />
I think there should be more user warning templates, since there is only one set of user warning templates. Who agrees with me? [[File:Windows_logo_(2006).svg|35px]] [[User:763004|'''763004''']] ([[User talk:763004|Talk]] &bull; [[User:763004/Sandbox|Sandbox]]) 13:25, 20 December 2023 (UTC)<br />
:Well then create them. No need to bother with voting... --{{User:Ryuzaki/Signature}} 13:29, 20 December 2023 (UTC)<br />
::Alrighty then. <small>(I'll test these in the sandbox first, or on [[Template:Test]])</small> [[File:Windows_logo_(2006).svg|35px]] [[User:763004|'''763004''']] ([[User talk:763004|Talk]] &bull; [[User:763004/Sandbox|Sandbox]]) 13:32, 20 December 2023 (UTC)<br />
<br />
=== Support ===<br />
# Per above. [[File:Windows_logo_(2006).svg|35px]] [[User:763004|'''763004''']] ([[User talk:763004|Talk]] &bull; [[User:763004/Sandbox|Sandbox]]) 13:25, 20 December 2023 (UTC)<br />
<br />
=== Oppose ===</div>Ovctvcthttps://betawiki.net/index.php?title=BetaWiki:Administrators%27_noticeboard&diff=311901BetaWiki:Administrators' noticeboard2023-12-26T11:03:56Z<p>Ovctvct: Changed protection settings for "BetaWiki:Administrators' noticeboard" ([Edit=Allow only autoconfirmed users] (expires 11:03, 27 December 2023 (UTC)) [Move=Allow only administrators] (indefinite))</p>
<hr />
<div>__NEWSECTIONLINK__<br />
{{fmbox|type=system|image=none|text=<center><br />
<span style="font-size: 150%;">Welcome to BetaWiki administrators' noticeboard!</span><br />
<br />
Use this page to request operations that can't be done without administrator (sysop) privileges. This includes user account renames, or content import requests.<br />
<br />
Requests that can be satisfied by non-administrator users should be raised at the [[BetaWiki:community portal|community portal]]. [[Main Page]] issues should be raised at its [[Talk:Main Page|talk page]].<br />
<br />
To add a discussion, please add a new heading under this line.<br />
</center><br />
}}<br />
{{archives}}<br />
{{TOC|clear=left|limit=2}}<br />
== Please change username ==<br />
I'd like to change my username to "th3at0m" if that's possible. Thanks :) [[User:At00m|At00m]] ([[User talk:At00m|talk]]) 17:49, 10 December 2023 (UTC)<br />
:✅ '''Renamed''' to "Th3at0m" due to MediaWiki limitations. --{{User:Ryuzaki/Signature}} 12:12, 11 December 2023 (UTC) <br />
<br />
== Block 46.123.245.70 ==<br />
<br />
That IP is literally another Deborahh1995, who is already blocked. Please block that IP address. [[File:Windows_logo_(2006).svg|35px]] [[User:763004|'''763004''']] ([[User talk:763004|Talk]] &bull; [[User:763004/Sandbox|Sandbox]]) 12:28, 2 October 2023 (UTC)<br />
:Also block 122.43.139.77, if you will. [[File:Windows_logo_(2006).svg|35px]] [[User:763004|'''763004''']] ([[User talk:763004|Talk]] &bull; [[User:763004/Sandbox|Sandbox]]) 12:23, 4 October 2023 (UTC)<br />
:46.123.245.46 as well! Find the IP address range that this and 46.123.245.70 are in, and block them. [[File:Windows_logo_(2006).svg|35px]] [[User:763004|'''763004''']] ([[User talk:763004|Talk]] &bull; [[User:763004/Sandbox|Sandbox]]) 12:42, 13 October 2023 (UTC)<br />
<br />
== Username change ==<br />
<s>I would like to have my username changed to "Tjari" because I don't like my current name anymore. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 04:23, 13 October 2023 (UTC)<br />
:it has also been a year since my [[BetaWiki:Administrators'_noticeboard/Archive_8#Change_my_username|last rename]]. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 05:13, 14 October 2023 (UTC)<br />
:i think the admins either didn't notice me or ignored me because of my bad actions. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 06:41, 17 October 2023 (UTC)<br />
:yes, the admins only care about my bad side. [[User:NaraInsider1694|Tjari]] ([[User talk:NaraInsider1694|talk]]) 14:26, 5 November 2023 (UTC)</s><br />
:Canceled because the admins are so ignorant and do not take username change requests seriously. [[User:NaraInsider1694|Tjari]] ([[User talk:NaraInsider1694|talk]]) 05:04, 7 November 2023 (UTC)<br />
::Most of us have lives outside of this wiki and therefore stuff might slip our eyes at times. No need for such strong language. --{{User:Ryuzaki/Signature}} 10:29, 7 November 2023 (UTC)<br />
<br />
== Block H0unsel h04rds 6748 ==<br />
<br />
The name said is an unacceptable username. [[File:Windows_logo_(2006).svg|35px]] [[User:763004|'''763004''']] ([[User talk:763004|Talk]] &bull; [[User:763004/Sandbox|Sandbox]]) 16:49, 19 October 2023 (UTC)<br />
<br />
== "panda009." is banned from BetaWiki Discord server, can anyone please help? ==<br />
Can anyone please help me now! My Discord username is "panda009." and I got banned from the BetaWiki Discord server. I am very sorry because I sent a link to a Discord server of mine there. I wanted my ban revoked. [[User:Earldridge Jazzed Pineda|Earldridge Jazzed Pineda]] ([[User talk:Earldridge Jazzed Pineda|talk]]) 12:45, 31 October 2023 (UTC)<br />
:Sorry, the admins are not going to unban you. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 12:46, 31 October 2023 (UTC)<br />
::I mean, temporary bans on Discord are a thing... [[User:Earldridge Jazzed Pineda|Earldridge Jazzed Pineda]] ([[User talk:Earldridge Jazzed Pineda|talk]]) 12:47, 31 October 2023 (UTC)<br />
:::Not that I heard of... [[File:Windows_logo_(2006).svg|35px]] [[User:763004|'''763004''']] ([[User talk:763004|Talk]] &bull; [[User:763004/Sandbox|Sandbox]]) 12:48, 31 October 2023 (UTC)<br />
:::...which don't apply to the BetaWiki server. If you're banned, you're doomed. [[User:NaraInsider1694|Tjari]] ([[User talk:NaraInsider1694|talk]]) 12:49, 31 October 2023 (UTC)<br />
::Please don't talk on the staff's behalf. Thanks. --{{User:Ryuzaki/Signature}} 13:57, 5 November 2023 (UTC)<br />
:If you are an administrator of the BetaWiki Discord server, simply follow these steps:<br />
# Open the server settings of the BetaWiki Discord server.<br />
# Scroll down and click on "Bans".<br />
# Click on "panda009."<br />
# Click "Revoke Ban". {{Unsigned|Earldridge Jazzed Pineda}}<br />
::admins: lmao we're not doing that [[User:NaraInsider1694|Tjari]] ([[User talk:NaraInsider1694|talk]]) 13:00, 31 October 2023 (UTC)<br />
::Just for the record, posting such guides actually reduces your likelihood of a timely unban. --{{User:Ryuzaki/Signature}} 13:57, 5 November 2023 (UTC)<br />
:This situation is a mess. We were talking about Microsoft Theme Packager, and then banned out of nowhere<br />
<br><br />
The server should adopt a second offense = ban rule [[User:Earldridge Jazzed Pineda|Earldridge Jazzed Pineda]] ([[User talk:Earldridge Jazzed Pineda|talk]]) 13:06, 31 October 2023 (UTC)<br />
:Drop the lies, you advertised your server according to the admins. [[User:NaraInsider1694|Tjari]] ([[User talk:NaraInsider1694|talk]]) 13:07, 31 October 2023 (UTC)<br />
::I saw other users posting links to Discord servers, so I thought it was allowed. But why there was no rule for self-promotion? [[User:Earldridge Jazzed Pineda|Earldridge Jazzed Pineda]] ([[User talk:Earldridge Jazzed Pineda|talk]]) 13:33, 31 October 2023 (UTC)<br />
:::It's Discord common sense, you were never supposed to self-promote in most Discord servers. [[User:NaraInsider1694|Tjari]] ([[User talk:NaraInsider1694|talk]]) 13:39, 31 October 2023 (UTC)<br />
:::You were explained how our server advertising policy works and you still broke it. --{{User:Ryuzaki/Signature}} 13:57, 5 November 2023 (UTC)<br />
:Promise, I will come back to the BetaWiki Discord server if and only if I can get Microsoft to release their Theme Packager. [[User:Earldridge Jazzed Pineda|Earldridge Jazzed Pineda]] ([[User talk:Earldridge Jazzed Pineda|talk]]) 14:58, 31 October 2023 (UTC)<br />
:: Didn't Microsoft included it in the NT 5 source code? {{User:Someone200/Signature|15:13, 31 October 2023 (UTC)}}<br />
: I do not consent to being banned. Last edit before being autoconfirmed. [[User:Earldridge Jazzed Pineda|Earldridge Jazzed Pineda]] ([[User talk:Earldridge Jazzed Pineda|talk]]) 03:25, 5 November 2023 (UTC)<br />
::BetaWiki is not your website, and its admins can do whatever they want. [[User:NaraInsider1694|Tjari]] ([[User talk:NaraInsider1694|talk]]) 03:30, 5 November 2023 (UTC)<br />
::That's not how consent works. At this point I am starting to suspect you shouldn't even be on Discord according to its terms of service. Also, you have shown exactly zero contributions to this site so far, so you are also on a good track to be blocked from editing your user page. --{{User:Ryuzaki/Signature}} 13:57, 5 November 2023 (UTC)<br />
:Just for the record, telling us what rules we should adopt reduces your likelyhood for a timely unban. And no, you weren't banned out of nowhere. --{{User:Ryuzaki/Signature}} 13:57, 5 November 2023 (UTC)<br />
<br />
Not even 24 hours after rejoining, I was banned from the BetaWiki Discord server for the 2nd time. I tried not to break the rules. Moderators locked one of my threads and banned me without notice. Can you please appeal my ban? [[User:Earldridge Jazzed Pineda|Earldridge Jazzed Pineda]] ([[User talk:Earldridge Jazzed Pineda|talk]]) 10:23, 5 November 2023 (UTC)<br />
:You were unbanned by mistake, we didn't mean to actually revoke your ban at this time. Sorry for the confusion. --{{User:Ryuzaki/Signature}} 13:57, 5 November 2023 (UTC)<br />
::I legitimately feel traumatized after reading this. Unfortunately, I have made the hard decision to leave the BetaWiki. Goodbye, [[User:Earldridge Jazzed Pineda|Earldridge Jazzed Pineda]] ([[User talk:Earldridge Jazzed Pineda|talk]]) 22:29, 5 November 2023 (UTC)<br />
== Block Antony Matheus dos Santos ==<br />
<br />
Said user (Antony Matheus dos Santos) is vandalizing BetaWiki. Please block said user (Antony Matheus dos Santos). [[File:Windows_logo_(2006).svg|35px]] [[User:763004|'''763004''']] ([[User talk:763004|Talk]] &bull; [[User:763004/Sandbox|Sandbox]]) 12:25, 2 November 2023 (UTC)<br />
<br />
== Username change request ==<br />
<br />
Would it be possible to change my username to "XenoPanther"? I'm trying to ensure my usernames are the same across all platforms I use, thanks! [[User:Xeno|Xeno]] ([[User talk:Xeno|talk]]) 12:57, 12 December 2023 (UTC)<br />
:<s>✔ Ryuzaki changed your name. [[File:Windows_logo_(2006).svg|35px]] [[User:763004|'''763004''']] ([[User talk:763004|Talk]] &bull; [[User:763004/Sandbox|Sandbox]]) 18:24, 12 December 2023 (UTC)</s><br />
:✅ '''Done''', please check your preferences to make sure everything matches, I had to delete an impersonator account to do this and I don't trust MediaWiki enough --{{User:Ryuzaki/Signature}} 18:27, 12 December 2023 (UTC)<br />
<br />
== Username change ==<br />
<br />
I would like change my username to "Enperfectify" to simplify it with my other social media accounts. Thanks! [[User:FinnieLoudtiago|FinnieLoudtiago]] ([[User talk:FinnieLoudtiago|talk]]) 05:56, 17 December 2023 (UTC)</div>Ovctvcthttps://betawiki.net/index.php?title=BetaWiki:Administrators%27_noticeboard&diff=311900BetaWiki:Administrators' noticeboard2023-12-26T11:03:15Z<p>Ovctvct: Reverted edits by 185.253.96.178 (talk) to last revision by AlfCraft07</p>
<hr />
<div>__NEWSECTIONLINK__<br />
{{fmbox|type=system|image=none|text=<center><br />
<span style="font-size: 150%;">Welcome to BetaWiki administrators' noticeboard!</span><br />
<br />
Use this page to request operations that can't be done without administrator (sysop) privileges. This includes user account renames, or content import requests.<br />
<br />
Requests that can be satisfied by non-administrator users should be raised at the [[BetaWiki:community portal|community portal]]. [[Main Page]] issues should be raised at its [[Talk:Main Page|talk page]].<br />
<br />
To add a discussion, please add a new heading under this line.<br />
</center><br />
}}<br />
{{archives}}<br />
{{TOC|clear=left|limit=2}}<br />
== Please change username ==<br />
I'd like to change my username to "th3at0m" if that's possible. Thanks :) [[User:At00m|At00m]] ([[User talk:At00m|talk]]) 17:49, 10 December 2023 (UTC)<br />
:✅ '''Renamed''' to "Th3at0m" due to MediaWiki limitations. --{{User:Ryuzaki/Signature}} 12:12, 11 December 2023 (UTC) <br />
<br />
== Block 46.123.245.70 ==<br />
<br />
That IP is literally another Deborahh1995, who is already blocked. Please block that IP address. [[File:Windows_logo_(2006).svg|35px]] [[User:763004|'''763004''']] ([[User talk:763004|Talk]] &bull; [[User:763004/Sandbox|Sandbox]]) 12:28, 2 October 2023 (UTC)<br />
:Also block 122.43.139.77, if you will. [[File:Windows_logo_(2006).svg|35px]] [[User:763004|'''763004''']] ([[User talk:763004|Talk]] &bull; [[User:763004/Sandbox|Sandbox]]) 12:23, 4 October 2023 (UTC)<br />
:46.123.245.46 as well! Find the IP address range that this and 46.123.245.70 are in, and block them. [[File:Windows_logo_(2006).svg|35px]] [[User:763004|'''763004''']] ([[User talk:763004|Talk]] &bull; [[User:763004/Sandbox|Sandbox]]) 12:42, 13 October 2023 (UTC)<br />
<br />
== Username change ==<br />
<s>I would like to have my username changed to "Tjari" because I don't like my current name anymore. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 04:23, 13 October 2023 (UTC)<br />
:it has also been a year since my [[BetaWiki:Administrators'_noticeboard/Archive_8#Change_my_username|last rename]]. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 05:13, 14 October 2023 (UTC)<br />
:i think the admins either didn't notice me or ignored me because of my bad actions. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 06:41, 17 October 2023 (UTC)<br />
:yes, the admins only care about my bad side. [[User:NaraInsider1694|Tjari]] ([[User talk:NaraInsider1694|talk]]) 14:26, 5 November 2023 (UTC)</s><br />
:Canceled because the admins are so ignorant and do not take username change requests seriously. [[User:NaraInsider1694|Tjari]] ([[User talk:NaraInsider1694|talk]]) 05:04, 7 November 2023 (UTC)<br />
::Most of us have lives outside of this wiki and therefore stuff might slip our eyes at times. No need for such strong language. --{{User:Ryuzaki/Signature}} 10:29, 7 November 2023 (UTC)<br />
<br />
== Block H0unsel h04rds 6748 ==<br />
<br />
The name said is an unacceptable username. [[File:Windows_logo_(2006).svg|35px]] [[User:763004|'''763004''']] ([[User talk:763004|Talk]] &bull; [[User:763004/Sandbox|Sandbox]]) 16:49, 19 October 2023 (UTC)<br />
<br />
== "panda009." is banned from BetaWiki Discord server, can anyone please help? ==<br />
Can anyone please help me now! My Discord username is "panda009." and I got banned from the BetaWiki Discord server. I am very sorry because I sent a link to a Discord server of mine there. I wanted my ban revoked. [[User:Earldridge Jazzed Pineda|Earldridge Jazzed Pineda]] ([[User talk:Earldridge Jazzed Pineda|talk]]) 12:45, 31 October 2023 (UTC)<br />
:Sorry, the admins are not going to unban you. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 12:46, 31 October 2023 (UTC)<br />
::I mean, temporary bans on Discord are a thing... [[User:Earldridge Jazzed Pineda|Earldridge Jazzed Pineda]] ([[User talk:Earldridge Jazzed Pineda|talk]]) 12:47, 31 October 2023 (UTC)<br />
:::Not that I heard of... [[File:Windows_logo_(2006).svg|35px]] [[User:763004|'''763004''']] ([[User talk:763004|Talk]] &bull; [[User:763004/Sandbox|Sandbox]]) 12:48, 31 October 2023 (UTC)<br />
:::...which don't apply to the BetaWiki server. If you're banned, you're doomed. [[User:NaraInsider1694|Tjari]] ([[User talk:NaraInsider1694|talk]]) 12:49, 31 October 2023 (UTC)<br />
::Please don't talk on the staff's behalf. Thanks. --{{User:Ryuzaki/Signature}} 13:57, 5 November 2023 (UTC)<br />
:If you are an administrator of the BetaWiki Discord server, simply follow these steps:<br />
# Open the server settings of the BetaWiki Discord server.<br />
# Scroll down and click on "Bans".<br />
# Click on "panda009."<br />
# Click "Revoke Ban". {{Unsigned|Earldridge Jazzed Pineda}}<br />
::admins: lmao we're not doing that [[User:NaraInsider1694|Tjari]] ([[User talk:NaraInsider1694|talk]]) 13:00, 31 October 2023 (UTC)<br />
::Just for the record, posting such guides actually reduces your likelihood of a timely unban. --{{User:Ryuzaki/Signature}} 13:57, 5 November 2023 (UTC)<br />
:This situation is a mess. We were talking about Microsoft Theme Packager, and then banned out of nowhere<br />
<br><br />
The server should adopt a second offense = ban rule [[User:Earldridge Jazzed Pineda|Earldridge Jazzed Pineda]] ([[User talk:Earldridge Jazzed Pineda|talk]]) 13:06, 31 October 2023 (UTC)<br />
:Drop the lies, you advertised your server according to the admins. [[User:NaraInsider1694|Tjari]] ([[User talk:NaraInsider1694|talk]]) 13:07, 31 October 2023 (UTC)<br />
::I saw other users posting links to Discord servers, so I thought it was allowed. But why there was no rule for self-promotion? [[User:Earldridge Jazzed Pineda|Earldridge Jazzed Pineda]] ([[User talk:Earldridge Jazzed Pineda|talk]]) 13:33, 31 October 2023 (UTC)<br />
:::It's Discord common sense, you were never supposed to self-promote in most Discord servers. [[User:NaraInsider1694|Tjari]] ([[User talk:NaraInsider1694|talk]]) 13:39, 31 October 2023 (UTC)<br />
:::You were explained how our server advertising policy works and you still broke it. --{{User:Ryuzaki/Signature}} 13:57, 5 November 2023 (UTC)<br />
:Promise, I will come back to the BetaWiki Discord server if and only if I can get Microsoft to release their Theme Packager. [[User:Earldridge Jazzed Pineda|Earldridge Jazzed Pineda]] ([[User talk:Earldridge Jazzed Pineda|talk]]) 14:58, 31 October 2023 (UTC)<br />
:: Didn't Microsoft included it in the NT 5 source code? {{User:Someone200/Signature|15:13, 31 October 2023 (UTC)}}<br />
: I do not consent to being banned. Last edit before being autoconfirmed. [[User:Earldridge Jazzed Pineda|Earldridge Jazzed Pineda]] ([[User talk:Earldridge Jazzed Pineda|talk]]) 03:25, 5 November 2023 (UTC)<br />
::BetaWiki is not your website, and its admins can do whatever they want. [[User:NaraInsider1694|Tjari]] ([[User talk:NaraInsider1694|talk]]) 03:30, 5 November 2023 (UTC)<br />
::That's not how consent works. At this point I am starting to suspect you shouldn't even be on Discord according to its terms of service. Also, you have shown exactly zero contributions to this site so far, so you are also on a good track to be blocked from editing your user page. --{{User:Ryuzaki/Signature}} 13:57, 5 November 2023 (UTC)<br />
:Just for the record, telling us what rules we should adopt reduces your likelyhood for a timely unban. And no, you weren't banned out of nowhere. --{{User:Ryuzaki/Signature}} 13:57, 5 November 2023 (UTC)<br />
<br />
Not even 24 hours after rejoining, I was banned from the BetaWiki Discord server for the 2nd time. I tried not to break the rules. Moderators locked one of my threads and banned me without notice. Can you please appeal my ban? [[User:Earldridge Jazzed Pineda|Earldridge Jazzed Pineda]] ([[User talk:Earldridge Jazzed Pineda|talk]]) 10:23, 5 November 2023 (UTC)<br />
:You were unbanned by mistake, we didn't mean to actually revoke your ban at this time. Sorry for the confusion. --{{User:Ryuzaki/Signature}} 13:57, 5 November 2023 (UTC)<br />
::I legitimately feel traumatized after reading this. Unfortunately, I have made the hard decision to leave the BetaWiki. Goodbye, [[User:Earldridge Jazzed Pineda|Earldridge Jazzed Pineda]] ([[User talk:Earldridge Jazzed Pineda|talk]]) 22:29, 5 November 2023 (UTC)<br />
== Block Antony Matheus dos Santos ==<br />
<br />
Said user (Antony Matheus dos Santos) is vandalizing BetaWiki. Please block said user (Antony Matheus dos Santos). [[File:Windows_logo_(2006).svg|35px]] [[User:763004|'''763004''']] ([[User talk:763004|Talk]] &bull; [[User:763004/Sandbox|Sandbox]]) 12:25, 2 November 2023 (UTC)<br />
<br />
== Username change request ==<br />
<br />
Would it be possible to change my username to "XenoPanther"? I'm trying to ensure my usernames are the same across all platforms I use, thanks! [[User:Xeno|Xeno]] ([[User talk:Xeno|talk]]) 12:57, 12 December 2023 (UTC)<br />
:<s>✔ Ryuzaki changed your name. [[File:Windows_logo_(2006).svg|35px]] [[User:763004|'''763004''']] ([[User talk:763004|Talk]] &bull; [[User:763004/Sandbox|Sandbox]]) 18:24, 12 December 2023 (UTC)</s><br />
:✅ '''Done''', please check your preferences to make sure everything matches, I had to delete an impersonator account to do this and I don't trust MediaWiki enough --{{User:Ryuzaki/Signature}} 18:27, 12 December 2023 (UTC)<br />
<br />
== Username change ==<br />
<br />
I would like change my username to "Enperfectify" to simplify it with my other social media accounts. Thanks! [[User:FinnieLoudtiago|FinnieLoudtiago]] ([[User talk:FinnieLoudtiago|talk]]) 05:56, 17 December 2023 (UTC)</div>Ovctvcthttps://betawiki.net/index.php?title=Windows_Longhorn_build_4048&diff=311897Windows Longhorn build 40482023-12-26T10:17:19Z<p>Ovctvct: Reverted edits by 77.73.69.156 (talk) to last revision by BF10</p>
<hr />
<div>{{Infobox Windows build<br />
|build of = [[Windows Longhorn]]<br />
|buildtag = 6.0.4048.idx02.030925-1900<br />
|family = nt<br />
|version = 6.0<br />
|build = 4048<br />
|lab = idx02<br />
|revision = <br />
|arch = x86<br />
|image = Longhorn build 4048 Desktop.png<br />
|winver = 4048idx02 winver.png<br />
|sku = Professional<br />
|compiled = 2003-09-25<br />
|timebomb = 2004-03-23<br />
|key = TCP8W-T8PQJ-WWRRH-QH76C-99FBW<br />
|ba = 67aafc93-f5a0-4f30-8abe-db710747841d<br />
}}<br />
<br />
'''Windows Longhorn build 4048''' is a Milestone 7 build of [[Windows Vista|Windows Longhorn]]. On 23 January 2020, this build was listed on a thread by [[UX.Unleaked]] blog founder Grabberslasher to be released to the [[BetaArchive]] FTP server, and was released in the third set of his 33 Longhorn/Vista builds on 26 January 2020, alongside multiple compiles of [[Windows Vista build 5000|build 5000]] and [[Windows Vista build 5001|build 5001]].<ref>https://www.betaarchive.com/forum/viewtopic.php?t=40726</ref> The shared ISO image is incomplete, hence parts of <code>install.wim</code> as well as all files below it are missing. As of 2023, the complete ISO of this build has yet to be found.<br />
<br />
== File Recovery ==<br />
The first two indexes ([[Windows Preinstallation Environment|WinPE]]) of <code>install.wim</code> survived and the third index (Longhorn) got partially cut off. The file table is missing due to it being at the very end of the image, however it is possible to reconstruct the file table based on [[Windows Longhorn build 4051|4051]]'s. The metadata resource of the first two indexes are intact, hence information such as attributes and timestamps is available. The third index is missing a good portion of compressed data and all of its metadata resource, so recovered files do not contain any (valid) metadata. Community member lucasm published a patched <code>install.wim</code> with a reconstructed file table and metadata resource for the third index based on 4051's <code>install.wim</code> on 31 December 2021.<br />
<br />
== Installation ==<br />
Currently, the only way of installing this build is by copying the recovered files from the third index of <code>install.wim</code> onto a partition with [[Windows Longhorn build 4042 (Lab06 n)|build 4042 (Lab06_n)]] pre-imaged. Second stage setup will continue with files from build 4048 and eventually complete the installation. However, the installation using this method will be single-use only. It is unable to log on anymore once the user reboot or log off, so it is recommended to make a backup, or if using a hypervisor, a snapshot before the second stage setup.<br />
<br />
An I386 repack with files taken from build 4051 is also possible, however there'll be many driver prompts showing up during installation due to the catalog files being missing, but this installation can be used multiple times and the user can still log on after rebooting or logging off.<br />
<br />
== Changes ==<br />
* A new <code>[[winver]]</code> banner has been added, which was first seen in [[Windows Longhorn build 4044|build 4044]].<br />
* The [[watermark]] has been changed to read "''Windows® Code Name "Longhorn"''" instead of "''Longhorn [SKU name]''". This was also first seen in build 4044.<br />
<br />
== Bugs ==<br />
=== General ===<br />
As mentioned above, it is not recommended to log off or restart on this build. If triggered, the machine will be unable to log on anymore (unless the [[Windows Setup#Windows NT|I386 installation method]] was used). Therefore, it is recommended to make a backup before the second stage of setup, or if using a hypervisor, a snapshot is recommended.<br />
<br />
== [[Windows Setup|Setup]] ==<br />
It is unknown whether this build includes the redesigned Setup as seen in [[Windows Longhorn build 4050 (idx02)|build 4050]] due to the setup media being corrupted from <code>install.wim</code> onwards, making files containing setup assets unrecoverable. However, the <code>setup.exe</code> file located on the disc root suggests that this build most likely contained the redesigned Setup.<br />
<br />
== Gallery ==<br />
<gallery><br />
Longhorn40424093Boot.png|Boot screen<br />
Longhorn build 4048 Setup Autorun.png|Autorun prompt<br />
Longhorn build 4048 Explorer.png|[[File Explorer|Windows Explorer]]<br />
Longhorn build 4048 Games.png|Games<br />
Longhorn build 4048 Blue Luna.png|Blue [[Luna]] theme<br />
Longhorn build 4048 Olive Green Luna.png|Olive Green Luna theme<br />
Longhorn build 4048 Silver Luna.png|Silver Luna theme<br />
Longhorn build 4048 Classic.png|[[Windows Classic]] theme<br />
Longhorn build 4048 Slate.png|[[Slate]] theme<br />
Longhorn build 4048 Demo.png|Demo<br />
SafeLonghorn.PNG|Safe to shutdown screen<br />
</gallery><br />
<br />
== References ==<br />
{{reflist}}<br />
<br />
[[Category:Windows Longhorn builds]]</div>Ovctvcthttps://betawiki.net/index.php?title=Windows_Longhorn_build_4050_(idx02)&diff=311896Windows Longhorn build 4050 (idx02)2023-12-26T10:17:18Z<p>Ovctvct: Reverted edits by 77.73.69.156 (talk) to last revision by BF10</p>
<hr />
<div>{{Infobox Windows build<br />
|build of = [[Windows Longhorn]]<br />
|image = 4050idx02-Desktop.png<br />
|buildtag = 6.0.4050.idx02.030928-0552<br />
|family = nt<br />
|version = 6.0<br />
|build = 4050<br />
|lab = idx02<br />
|revision = <br />
|arch = x86<br />
|sku = Home Edition<br />
|compiled = 2003-09-28<br />
|timebomb = 2004-03-26<br />
|key = TCP8W-T8PQJ-WWRRH-QH76C-99FBW<br />
|winver = 4050idx02-Winver.png<br />
|rivals = {{Rivals|TCB=http://www.thecollectionbook.info/windows/vista/4863}}<br />
}}<br />
<br />
'''Windows Longhorn build 4050 (idx02)''' is a Milestone 7 build of [[Windows Vista|Windows Longhorn]]. On 23 January 2020, this build was listed on a thread by [[UX.Unleaked]] blog founder Grabberslasher to be released to the [[BetaArchive]] FTP, and was later released in the fifth set of his 33 Longhorn/Vista builds on 28 January 2020 as a checked/debug build alongside [[Windows Longhorn build 4085 (Lab07 N)|build 4085 (Lab07_N)]].<ref>grabberslasher. [https://www.betaarchive.com/forum/viewtopic.php?t=40726 New Longhorn Builds for a New Decade], ''BetaArchive''. 23 January 2020.</ref> It is the second publicly available Home Edition pre-reset build of Longhorn.<br />
<br />
== [[Windows Setup|Setup]] ==<br />
Although setup is mostly the same as [[Windows Longhorn build 4048|the previous build]] of Windows Longhorn, a new [[Slate]]-styled background is used.<br />
<gallery><br />
4050 SetupAutorun.png|CD-autorun<br />
4050 Setup.png|Setup<br />
4050 ProductKey.png|Enter product key<br />
4050 EULA.png|EULA<br />
4050 CleanInstallSummary.png|Clean install summary<br />
Setup DiskPartitioning.png|Drive partitioning<br />
4050 PCName.png|Enter computer name<br />
4050 CopyingFiles.png|Setup is copying files<br />
4050 HardwarePortion.png|Hardware portion<br />
</gallery><br />
<br />
== Changes ==<br />
=== Login screen ===<br />
* The login screen has changed once again, now it is transparent as it does not have a background. This is because, in these builds, the "SYSTEM" user account does not have a default wallpaper. This change was most likely done to in order to let OEMs put a logon background with their logos.<ref>Googulator. [https://www.betaarchive.com/forum/viewtopic.php?p=465495#p465495 Why did Microsoft replace the blueish Login background from 4042 to the black one from 4074], ''BetaArchive''. 25 November 2021.</ref><br />
* The Windows logo upon logging in now comes up instead of coming down.<br />
<br />
=== ClearType ===<br />
ClearType is enabled by default again, after being disabled in [[Windows Longhorn build 4042 (Lab06 n)|Lab06_n compile of build 4042]]. This would persist up to [[Windows Longhorn build 4074|build 4074]].<br />
<br />
== Bugs and quirks ==<br />
=== <code>winver</code> dialog ===<br />
This build uses the older <code>[[winver]]</code> banner first seen in [[Windows Longhorn build 4005|build 4005]] instead of the new one from [[Windows Longhorn build 4044|build 4044]], likely because the change did not make into Home Edition at that time.<br />
=== Installation ===<br />
* This build cannot be installed normally due to an assertion failure in <code>AGP440.SYS</code>, thus resulting in a <code>0x0000007E</code> (<code>SYSTEM_THREAD_EXCEPTION_NOT_HANDLED</code>) [[bugcheck]] when booting into the second stage of setup. To bypass this issue, set up kernel-mode debugging with WinDbg to ignore the failure<ref>[https://www.betaarchive.com/forum/viewtopic.php?t=40269 <nowiki>[Guide] Install Longhorn 4051 x64 chk</nowiki>], ''BetaArchive''. 20 December 2012.</ref> or replace drivers with ones from the non-checked/debug compile of [[Windows Longhorn build 4051|build 4051]]. This error does not happen on real hardware and on [[86Box]] machines that don't have an AGP slot.<br />
* When booting into the second stage of setup, the system will play a long beep on systems that have a [[w:PC speaker|PC speaker]].<br />
* Due to this build being a PDC build like [[Windows Longhorn build 4051|build 4051]], this build cannot be normally upgraded from a previous build and can only be clean installed.<br />
<br />
== Gallery ==<br />
<gallery><br />
Longhorn40424093Boot.png|[[Boot screen]]<br />
4050 LoginScreen.png|Login screen<br />
WindowsLonghorn-6.0.4050-ClassicStartMenu.png|Classic [[Start menu]]<br />
</gallery><br />
<br />
== References ==<br />
{{reflist}}<br />
<br />
[[Category:Windows Longhorn builds]]</div>Ovctvcthttps://betawiki.net/index.php?title=Windows_Longhorn_build_4053&diff=311895Windows Longhorn build 40532023-12-26T10:17:18Z<p>Ovctvct: Reverted edits by 77.73.69.156 (talk) to last revision by BF10</p>
<hr />
<div>{{Infobox Windows build<br />
|build of = [[Windows Longhorn]]<br />
|image = 4053main031022-1720.png<br />
|buildtag = 6.0.4053.main.031022-1720<br />
|family = nt<br />
|version = 6.0<br />
|build = 4053<br />
|lab = main<br />
|revision = <br />
|arch = x86<br />
|sku = Professional<br />
|compiled = 2003-10-22<br />
|timebomb = +180 days<br />
|key = CKY24-Q8QRH-X3KMR-C6BCY-T847Y<br />
|rivals = {{Rivals|TCB=http://www.thecollectionbook.info/builds/windows/build/526|TCBGallery=http://www.thecollectionbook.info/gallery/?f=/windows/nt%20kernel/windows%20vista/6.0.4053.0/english/professional/x86}}<br />
|winver = Longhorn-6.0.4053-Winver-About.png<br />
}}<br />
<br />
'''Windows Longhorn build 4053''' is a Milestone 7 build of [[Windows Vista|Windows Longhorn]], which is reported to have been shared online on 1 March 2004.<ref>[http://dk.toastednet.org/iex_lh/ emoaddict15's hosted Vista files]. 26 January 2009.</ref> Overall, this build is very similar to [[Windows Longhorn build 4051|build 4051]], but with networking bugs patched.<br />
<br />
Although the watermark shows that this build was test-signed, it was compiled in evaluation mode and can be installed on the current date. Attempting to log onto the desktop once the [[timebomb]] has been triggered will return the user to the login screen.<br />
<br />
== Setup ==<br />
Setup is mostly similar to previous builds of Longhorn. This build can also be upgraded from previous builds too.<br />
<gallery><br />
File:Longhorn-6.0-4053-CD-autorun.png|CD autorun<br />
File:4053 Setup.png|Setup<br />
File:4053 ProductKey.png|Enter product key<br />
File:4053 EULA.png|EULA<br />
File:4053 CleanInstallSummary.png|Clean install settings summary<br />
File:4053 DiskPartition.png|Drive partitioning<br />
File:4053 PCNAme.png|Enter computer name<br />
File:4053 HardwarePoritnio.png|Hardware portion<br />
File:LH 4053 - Unknown problem.png|Unknown error when upgrading from [[Windows Longhorn build 4028|build 4028]] ~ [[Windows Longhorn build 4051|build 4051]]<br />
File:LH 4053 - Winsetup.dll error.png|Setup reporting that <code>WinSetup.dll</code> could not be loaded.<br />
</gallery><br />
<br />
== Changes ==<br />
This is the earliest available build of Windows to support disabling upgrades via an empty <code>noupgrade.txt</code> placed in the sources folder.<br />
<br />
== Bugs and quirks ==<br />
=== Theming ===<br />
If any application handled by Explorer like [[Windows Explorer]] or [[Internet Explorer]] stops responding, the theming of these applications will bug out and show the classic theme title bar.<br />
<br />
=== Control Panel ===<br />
The normal method of creating user accounts does not work in this build. However, accounts can still be created by going to run and typing in either <code>control userpasswords2</code> or <code>netplwiz.exe</code>. An alternative method is porting <code>nusrmgr.cpl</code> from another build to replace the one in the <code>\WINDOWS\SYSTEM32</code> directory in order to get it to work or using the Local Users and Groups MMC snap-in can be used (<code>lusrmgr.msc</code>).<br />
<br />
=== [[Start menu]] ===<br />
The most frequently used items list of the [[Start menu]] resets itself after every reboot.<br />
<br />
=== Notifications ===<br />
Notifications tend to reappear quite a lot. Fully closing the notifications may take several attempts.<br />
<br />
=== Upgrade ===<br />
On some machines, after the first reboot during an upgrade, an "Unknown problem in upgrade happened" error will appear, and clicking OK will cause the machine to restart. After restarting, setup will continue normally until another reboot takes place, in which "The file WinSetup.dll could not be loaded or is corrupt. Setup cannot continue." will appear. Clicking OK will restart the computer and on some machines, there will be no mouse and keyboard support (since the hardware detection phase of setup did not start), and the only workaround is to reinstall Windows and does not occur on some machines. This bug persists until [[Windows Longhorn build 4093|build 4093]].<br />
<br />
== Gallery ==<br />
<gallery><br />
File:2003-10-02 185232.png|Boot screen<br />
File:WindowsLonghorn-6.0.4053m7-blstartmenu.png|Blue Luna theme<br />
File:WindowsLonghorn-6.0.4053m7-oglstartmenu.png|Olive Green Luna theme<br />
File:WindowsLonghorn-6.0.4053m7-slstartmenu.png|Silver Luna theme<br />
File:WindowsLonghorn-6.0.4053m7-wcstartmenu.png|Windows Classic theme<br />
File:WindowsLonghorn-6.0.4053m7-sstartmenu.png|Slate theme<br />
File:Longhorn-6.0-4053-System Properties and Winver.png|System Properties and Winver<br />
File:Longhorn-6.0-4053-System Properties and Winver (Windows XP theme).png|System Properties and Winver (Blue Luna theme)<br />
File:Longhorn-6.0-4053-System Properties and Winver (Classic theme).png|System Properties and Winver (Classic theme)<br />
File:Longhorn-6.0-4053-Winver on the desktop.png|Winver on the desktop<br />
File:Longhorn-6.0-4053-Winver on the desktop (Windows XP theme).png|Winver on the desktop (Blue Luna theme)<br />
File:Longhorn-6.0-4053-Winver on the desktop (Classic theme).png|Winver on the desktop (Classic theme)<br />
File:Longhorn-6.0-4053-CMD.png|Command prompt<br />
File:SafeLonghorn.PNG|Safe to shutdown screen<br />
</gallery><br />
<br />
== References ==<br />
{{reflist}}<br />
<br />
[[Category:Windows Longhorn builds]]</div>Ovctvcthttps://betawiki.net/index.php?title=BetaWiki:Community_portal&diff=311892BetaWiki:Community portal2023-12-26T10:00:32Z<p>Ovctvct: Changed protection settings for "BetaWiki:Community portal": Excessive vandalism ([Edit=Allow only autoconfirmed users] (expires 10:00, 2 January 2024 (UTC)) [Move=Allow only administrators] (indefinite))</p>
<hr />
<div>__NEWSECTIONLINK__<br />
{{fmbox|type=system|image=none|text=<center><br />
<span style="font-size: 150%;">Welcome to BetaWiki community portal!</span><br />
<br />
This is where we discuss the operations of BetaWiki. Please help us to set down policies and guidelines, improve articles and more.<br />
<br />
If you want to request a specific administration action to be done, please use the [[BetaWiki:administrators' noticeboard|administrators' noticeboard]] instead.<br />
<br />
To add discussion, please add a new heading under this line.<br />
</center><br />
<br />
}}<br />
{{archives}}<br />
{{TOC|clear=left|limit=2}}<br />
<br />
== adding language parameter to the infobox windows build ==<br />
<br />
it will become easier to know the languages. [[Special:Contributions/51.15.78.38|51.15.78.38]] 10:38, 24 June 2023 (UTC)<br />
<br />
=== Support ===<br />
#per myself. [[Special:Contributions/51.15.78.38|51.15.78.38]] 10:38, 24 June 2023 (UTC)<br />
#I support this. Same feature is available for TheCollectionBook. But I doubt it's going to be accepted. This was requested a few times, and it was ignored. {{Unsigned|94.121.82.195}}<br />
#I support this, but only for releases preceding the introduction of the [[w:Multilingual_User_Interface|Multilingual User Interface (MUI)]] in Windows 2000. [[User:Ahernandez094|Ahernandez094]]<br />
=== Oppose ===<br />
#Unnecessary - Most internal beta builds are only available in a single language and if other languages are available, they ''will'' be mentioned on the respective build page. Public beta builds are available in basically every single language supported by Microsoft, so mentioning available languages on the respective build page is also unnecessary. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 12:12, 24 June 2023 (UTC)<br />
#:Also, most non-English builds of Windows, especially before Windows 8, are only official Beta/CTP/Preview/RTM builds and not internal ones. - <code>[[File:Windows logo (2003).svg|18px]] [[User:Bob2204|Bob2204]]</code> [[File:Arrow.png|15px]] Click here to begin. Or here. [[File:Arrow2.png|15px]] <code>[[User talk:Bob2204|Talk]]</code> - 16:18, 24 June 2023 (UTC)<br />
#::This https://betawiki.net/wiki/Windows_10_build_18327.1, it's not an official build. However it's available for many languages. {{Unsigned|94.121.82.195}}<br />
#::Do you seriously think that everyone who visit this wiki like reading long paragraphs? {{Unsigned|94.121.82.195}}<br />
#:::Read again. I only have said "most, '''especially before Windows 8'''". The Technical/Insider Preview thing changed many things, as they no longer release Preview/Beta/Alpha builds, but only multiple "Insider Previews", which can reach up to around 30 Insider Previews per version before a new version becomes released. - <code>[[File:Windows logo (2003).svg|18px]] [[User:Bob2204|Bob2204]]</code> [[File:Arrow.png|15px]] Click here to begin. Or here. [[File:Arrow2.png|15px]] <code>[[User talk:Bob2204|Talk]]</code> - 14:38, 25 June 2023 (UTC)<br />
#::::Understood. {{Unsigned|94.121.82.195}}<br />
#That's not how it works. Every build is compiled in all of the 23 base languages and all available SKUs. I oppose this simply because it would clutter the infobox, especially on Insider previews because they are indeed released in those base languages. --[[Special:Contributions/217.131.99.140|217.131.99.140]] 07:44, 29 June 2023 (UTC)<br />
#:Not '''every ''' is compiled in '''all''' languages. Some builds are only compiled for specific languages. Also what will you say about unleaked, shared or betas before Windows 7? {{Unsigned|94.120.197.130}}<br />
#::Simple: We never know what Microsoft did to their builds and if they're compiled in all languages or not. New languages were gradually added over time, so we need to remind ourselves of the past. Also, don't use {{tl|Unsigned}} to sign your comments, use <nowiki>~~~~</nowiki>. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 14:21, 4 July 2023 (UTC)<br />
#:::It's already impossible to know which languages are available in builds. But he said '''Every build is compiled in all of the 23 base languages''', which is definitely false. Otherwise we would have the builds 4074 in German or 5048 in French. The list goes on. [[User:94.120.197.130|94.120.197.130]] ([[User talk:94.120.197.130|talk]]) 14:29, 4 July 2023 (UTC)<br />
# Putting information to the infobox is a double-edged sword, it might make the information more discoverable but it also makes it more cluttered that it needs to be. Not to mention the relationship between SKUs, architectures and languages, since builds rarely are available in all listed combinations. A better approach would be a table like done for [[Windows 11 build 22000.1]]. --{{User:Ryuzaki/Signature}} 07:39, 29 June 2023 (UTC)<br />
#: Like in 2296.1 page? {{Unsigned|94.120.197.130}}<br />
<br />
== Changing recommended resolution images to 1,920 × 1,080 ==<br />
<br />
Literally every single build of Windows 11 use it for some reason, so I guess why not do it on other builds. [[Special:Contributions/37.120.213.238|37.120.213.238]] 11:36, 2 July 2023 (UTC)<br />
: I guess 1366 x 768 or 1400 x 900 would be better. 1920 x 1080 is too large. {{User:Someone200/Signature|23:36, 3 July 2023 (UTC)}}<br />
: The guidelines don't actually recommend a single resolution, they only say it should be period appropriate but ''at least'' 1024x768, unless the OS doesn't support that resolution. {{Unsigned|Ryuzaki}}<br />
<br />
==== Support ====<br />
#[[Special:Contributions/37.120.213.238|37.120.213.238]] 11:36, 2 July 2023 (UTC)<br />
<br />
==== Oppose ====<br />
#Most old hardware and older versions of Windows do not support such a ridiculously high resolution. Due to DPI scaling being a hit-or-miss on older OSes, the contents of the screenshots will also be too small, requiring the reader to click on the image to better view the screenshot. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 11:40, 2 July 2023 (UTC)<br />
#:Then why do Windows 11 builds do it then? I only requested this all because of Windows 11 images. [[Special:Contributions/37.120.213.238|37.120.213.238]] 11:43, 2 July 2023 (UTC)<br />
#::Newer versions of Windows are better suited for high-resolution displays, also blame the uploader for using that resolution. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 11:46, 2 July 2023 (UTC)<br />
#:::OH okay. Anyways, does 1,366 × 768 count as a "ridiculously" higher resolution? This is the alternative to 1,920 × 1,080, I guess. [[Special:Contributions/37.120.213.238|37.120.213.238]] 11:52, 2 July 2023 (UTC)<br />
#::::I don't think it counts, since it's basically 1024 × 768, but wider. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 12:18, 2 July 2023 (UTC)<br />
#:::I think we should only use 1920x1080 for win10 and win11 builds, and the problem is that there are a lot of Windows 10 builds that currently use 1024x768, which for Windows 10's time period is rather low. - [[User:Upseguest|Upseguest]] ([[User talk:Upseguest|talk]])<br />
<br />
==winmain in 2009/2010==<br />
There is a very odd thing I found out about winmain in the time period between builds 7232 (Win7) and 7700 (Win8). While 7232 already features the final Harmony wallpaper, 7700 oddly reused the betta fish one. The 7700 page said that it can be implied that this build was formed from a Win7 RC build. I really doubt this, because it's also possible that they just reverted this wallpaper thing for Win8/future winmain development. (At least the betta fish was used until Microsoft started the Technical Preview/Insider Program.) - <code>[[File:Windows logo (2003).svg|18px]] [[User:Bob2204|Bob2204]]</code> [[File:Arrow.png|15px]] Click here to begin. Or here. [[File:Arrow2.png|15px]] <code>[[User talk:Bob2204|Talk]]</code> - 23:29, 3 July 2023 (UTC)<br />
<br />
== Page Previews ==<br />
<br />
This wiki needs page previews feature. <small> —— This newly signed comment was added by [[File:Windows logo (2012).svg|15px]] [[User:LazytownSpo4015|<span class="signature-lazytownspo4015-userpage">'''<big>Lazytown Sportacus (LazytownSpo4015)</big>'''</span>]] • [[User talk:LazytownSpo4015|<span class="signature-lazytownspo4015-talk">Talk page]] • {{#if: | <nowiki>|</nowiki> '''{{{1}}}''' | }}</small> 14:03, 4 July 2023 (UTC)<br />
<br />
=== Support ===<br />
#Per myself. <small> —— This newly signed comment was added by [[File:Windows logo (2012).svg|15px]] [[User:LazytownSpo4015|<span class="signature-lazytownspo4015-userpage">'''<big>Lazytown Sportacus (LazytownSpo4015)</big>'''</span>]] • [[User talk:LazytownSpo4015|<span class="signature-lazytownspo4015-talk">Talk page]] • {{#if: | <nowiki>|</nowiki> '''{{{1}}}''' | }}</small> 14:03, 4 July 2023 (UTC)<br />
#I was so used to this exact feature on Wikipedia and it allows you to view pages without actually navigating to the specific page. When I first joined this wiki, I actually wondered why page previews aren't supported. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 14:12, 4 July 2023 (UTC)<br />
#This is a really convenient feature. I also wonder why they haven't been implemented yet. [[User:BetaReporter|BetaReporter]] ([[User talk:BetaReporter|talk]]) 17:27, 4 July 2023 (UTC)<br />
<br />
=== Oppose ===<br />
#You could use Visual Editor instead [[User:PikaaxYT|PikaaxYT]] ([[User talk:PikaaxYT|talk]]) 12:04, 22 October 2023 (UTC)<br />
<br />
== Move Insider Preview update pages to their respective build pages ==<br />
This is [https://betawiki.net/wiki/BetaWiki:Community_portal/Archive_9#Move_Insider_service_pipeline_updates_to_their_respective_build_pages. a (probably abandoned) proposal] made by [[Special:Contributions/Xeno|Xeno]]. I reopened this because the final decision hasn't been made, and I feel like the servicing pipelines updates are cluttering up the pages.<br />
<br />
If this reach 15+ support, I'll do it. It will take a long time though. (as always, please consider providing a reason if support/oppose as it helps me understand your opinion.)<br />
<br />
{{User:Someone200/Signature|14:23, 3 August 2023 (UTC)}}<br />
<br />
:The consensus was to carry that out, not sure why this needs another vote. --{{User:Ryuzaki/Signature}} 14:33, 3 August 2023 (UTC)<br />
<br />
== Purge <s>all</s> non-Windows related content (reopen) ==<br />
This is a reopen of [https://betawiki.net/wiki/BetaWiki:Community_portal/Archive_11#Purge_all_non-Windows_related_content my version] of [https://betawiki.net/wiki/BetaWiki:Community_portal/Archive_6#Purge_all_non-Windows_related_content a proposal by orbitron] that was abandoned, because apparently the aforementioned proposals aren't being passed through.<br />
<br />
Basically, most non-Windows stuff on the wiki, except macOS, iOS, DOS, and OS/2, gets literally no activity besides one or two users. Most pages covering Linux are too short and hardly contain any notable information (and no, bugs don't count as notable). The new features and changes present in each distro version are also not covered properly and the pages only contain the image of the desktop or the home screen, which is not enough for a good article.<br />
<br />
While the original proposal focused on all non-Windows content, I wanted to only focus on free-and-open-source OSes (such as Linux, BSD, and Haiku), Android, non-preinstalled web browsers (such as Google Chrome, Mozilla Firefox, Opera, and Netscape) and other less important OSes. For free-and-open source OSes and Android, they have been moved to [https://distro.wikitide.com/ a dedicated wiki that focused on these OSes.] For non-preinstalled web browsers, there are already Wikipedia pages for these browsers. I hope this makes BetaWiki a much cleaner site and live up to its name. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 14:40, 3 August 2023 (UTC)<br />
:The proposal was archived because it was dead with no clear consensus. Not sure what makes you think reopening it immediately after it got archived will reach a different result. --{{User:Ryuzaki/Signature}} 16:48, 3 August 2023 (UTC)<br />
::OK, I understand. I did not know that proposals would be archived if it was dead with no clear consensus. I first thought reopening my proposal would bring up attention to the two proposals I mentioned above, so I'm sorry for the mistake I made. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 23:11, 3 August 2023 (UTC)<br />
<br />
== Moving all GitHub issue related builds to a separate page ==<br />
<br />
I think that most of the Windows 10/11 pages are being cluttered with GitHub issue pages. Since these builds doesn't have a proper buildtag (only build number), I think they should be moved to a separate instead of being purged. Some of them could cause confusions because its build number is identical to another one.<br />
{{User:Someone200/Signature|03:15, 6 August 2023 (UTC)}}<br />
<br />
=== Support ===<br />
# Per myself. {{User:Someone200/Signature|03:15, 6 August 2023 (UTC)}}<br />
# Welp, this should also be done for servicing pipeline update builds. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 03:21, 6 August 2023 (UTC)<br />
# We should also do that for builds mentionned in SSUComp_KB*******.xml and Desktop_neutral_Forward_*****.****.***************.******-****.CompDB.xml files [[User:PikaaxYT|PikaaxYT]] ([[User talk:PikaaxYT|talk]]) 10:27, 11 August 2023 (UTC)<br />
<br />
=== Oppose ===<br />
<br />
== Adding downloads of the builds in their infoboxes (CLOSED) ==<br />
<br />
<s>Or at least adding an information on where to download the builds <small>—&nbsp;Preceding unsigned comment added by [[User:PikaaxYT|PikaaxYT]] ([[User talk:PikaaxYT|talk]] • [[Special:Contributions/PikaaxYT|contribs]]) </small></s><br />
<br />
I closed the request because download links would violate the guidelines {{unsigned|PikaaxYT}}<br />
<br />
=== Support ===<br />
<br />
1. [[User:PikaaxYT|PikaaxYT]]<br />
<br />
=== Oppose ===<br />
<br />
# See [[BW:Guidelines#Legal|BW:Guidelines § Legal]]. [[User:Jurta|Jurta]] ([[User talk:Jurta|talk]] • [[Special:Contributions/Jurta|contribs]]) 19:52, 10 August 2023 (UTC)<br />
# We are most certainly '''NOT''' providing download links to these builds on the wiki. The wiki is intended to be a knowledge base for these builds. Find the builds yourself. The Windows build FAQ page points out that archive.org and WinWorld are good starting points to find most builds. Although, be careful as there are fake builds out there. It is very easy to find these builds anyways. <code>[[File:Windows Orb logo (2006).png|18px]] [[User:WindowsGuy2021|WindowsGuy2021]]</code> 2:59, 10 August 2023 (UTC)<br />
<br />
== Purge Linux and Android content ==<br />
here we go again...<br />
<br />
Most Linux distributions in BetaWiki are not notable, and by "not notable" I mean most of the articles talking about a Linux distro are too short, low quality, and hardly contain any useful or notable information. The Android articles are a good example of this, since they are made of an infobox, a lead sentence, a list of changes (or builds), and that's it. The information necessary for a knowledge base, such as the development history, features, and the overall aspects of a Linux distro, is also missing from the aforementioned articles. Other websites did a much better job at documenting these distros since they are not Windows-centric, unlike BetaWiki. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 09:10, 22 August 2023 (UTC)<br />
:I agree for purging Linux articles but not for purging Android articles because if they are deleted we should also purge iOS articles since most builds doesn’t even have an article and the few builds that have an article only have an infobox and a smaller sentence than Android articles [[User:PikaaxYT|PikaaxYT]] ([[User talk:PikaaxYT|talk]]) 12:03, 22 October 2023 (UTC)<br />
::now that DistroWiki got closed, following with the stepdown of Nara and GT610, I think that never ending purging discussion finally reached a dead end, at least for now. <br />
::Yes, there are still better wikis and pages for operating systems other than windows, but that discussion didn't really help us to make steps forward. At the end, the consequence was another wiki for just that reason, which failed to gain any reputation in their scene like betawiki does and thus failing overall. No one came out from there as winner. <br />
<br />
::The best thing that we can do for now is just continuing our work here. - <code>[[File:Windows logo (2003).svg|18px]] [[User:Bob2204|Bob2204]]</code> [[File:Arrow.png|15px]] Click here to begin. Or here. [[File:Arrow2.png|15px]] <code>[[User talk:Bob2204|Talk]]</code> - 23:00, 30 November 2023 (UTC)<br />
:::Nara here. Yes, BetaWiki should've stayed the same and the DistroWiki effort, in my opinion, was just a waste of time. Despite having 99% of its focus on Windows, there are still people who do Linux stuff here and we should respect them. I'll say the discussion is finally over, like you said. [[Special:Contributions/139.192.153.112|139.192.153.112]] 03:53, 2 December 2023 (UTC)<br />
<br />
== discord server invite link ==<br />
<br />
i'm trying to rejoin the BW discord, but it says the link is expired. Has the server been deleted or is it a dead invite? {{Unsigned|Grafality}}<br />
:It's a dead invite. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 05:33, 16 September 2023 (UTC)<br />
::if it is a dead invite, then why wouldn't I rejoin BW Discord server? Also I'm sorry for my past actions while I'm in the server. <small> —— This newly signed comment was added by [[File:Windows logo (2012).svg|15px]] [[User:LazytownSpo4015|<span class="signature-lazytownspo4015-userpage">'''<big>Lazytown Sportacus (LazytownSpo4015)</big>'''</span>]] • [[User talk:LazytownSpo4015|<span class="signature-lazytownspo4015-talk">Talk page]] • {{#if: | <nowiki>|</nowiki> '''{{{1}}}''' | }}</small> 08:57, 16 September 2023 (UTC)<br />
:::I hate to tell you this, but you have been banned from the BW Discord server. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 08:59, 16 September 2023 (UTC)<br />
::::I know but, I'm very sorry for my past actions when i was there. How am i going to appeal a ban from the BW discord server? <small> —— This newly signed comment was added by [[File:Windows logo (2012).svg|15px]] [[User:LazytownSpo4015|<span class="signature-lazytownspo4015-userpage">'''<big>Lazytown Sportacus (LazytownSpo4015)</big>'''</span>]] • [[User talk:LazytownSpo4015|<span class="signature-lazytownspo4015-talk">Talk page]] • {{#if: | <nowiki>|</nowiki> '''{{{1}}}''' | }}</small> 09:13, 11 October 2023 (UTC)<br />
:::"if it is a dead invite, then why wouldn't I rejoin BW Discord server?" Precisely because it was a dead invite? It is fixed now though. --{{User:Ryuzaki/Signature}} 09:46, 16 September 2023 (UTC)<br />
<br />
== 8297.0.fbl_fun_embedded_xos.120311-1700 ==<br />
<br />
Please make a page for Xbox One OS build 8297. It's availible, so it should be possible. I'm not experienced enough to get the OS and run it in some sort of emulator. {{Unsigned|146.212.161.185}}<br />
:You literally put the same thing in here and in [[Talk:Main Page]]. [[File:Windows_logo_(2006).svg|35px]] [[User:763004|'''763004''']] ([[User talk:763004|Talk]] &bull; [[User:763004/Sandbox|Sandbox]]) 17:27, 10 October 2023 (UTC)<br />
<br />
== Cleaning up Bugs and quirks section ==<br />
<br />
After some deep review about a few additions within these sections lately, it's been seen that we're getting a lot of hardware/VM-only related problems that seems to be extremely niche to encounter, and in several cases, results from using a config that is way above what was the norm/available at the time. Most of these bugs tend to be of sensitive/setup-specific, and often are just encountered by one user due to a bad config.<br />
<br />
As a result of this, I'm going to start suggesting that any compatibility bugs are heavily stripped down, since adding these bugs aren't necessarily of "meaningful" edits and ends up being more disruptive for the flow of the page. This would mean that the following changes will be made, with some examples of what we don't want:<br />
* Any bugs that mention [https://betawiki.net/index.php?title=Windows_Longhorn_build_4002_%28Lab06_N%29&type=revision&diff=307656&oldid=303257 "this build won't install in modern versions of <program>"] will no longer be allowed and will be removed. This is a setup-specific problem, and also this wiki is not a compatibility checklist.<br />
* Any bugs that mention [https://betawiki.net/index.php?title=Windows_NT_4.0_build_1130&type=revision&diff=261298&oldid=260828 "this driver doesn't work"] will also no longer be allowed and will be removed. Generally a setup-specific problem or incomplete driver support; again betas aren't meant to be complete.<br />
* A lot of [https://betawiki.net/index.php?title=Windows_XP_build_2202&type=revision&diff=308836&oldid=303304 VM compatibility bugs] will be stripped down. I'd prefer they'd be removed completely, but that's not necessarily going to be favorable for certain builds that need an abnormally early compatibility. But then again, it's preferable to use the version that was closest to when that build was compiled. For reference, VMware 5.0 released around 2005, while VMware 6.0 released around 2007. So it would not make sense to install say build 5231 on modern versions, and vise versa. This is also largely a setup-related problem, usually.<br />
<br />
Most of the bugs that are intended to be removed will usually be of that hardware related, unless they are a widespread problem and often well-known by Microsoft in documentation, such as the Windows NT 3.x processor setup bug. But for singular builds, these bugs would have to go, and don't contribute as a "meaningful" edit and more of a way to inflate the page with niche setups.<br />
<br />
Also to note adding "persists until build" isn't necessarily a meaningful edit, as well. We do not need to document every little bug you see, as again beta builds are often unstable and prone to bugs and inconveniences. Bugs are to only be documented usually when they often affect real hardware too and is major enough that it often impacts the usability of the build even in the most general scenario. Subsequently reverting/adding these oft-unnecessary bugs is means of disruptive editing, and warnings will be handed out.<br />
<br />
[[User:BF10|BF10]] ([[User talk:BF10|talk]]) 13:35, 4 December 2023 (UTC)<br />
:We also have to remove "this build has some stabillity issues" edits, because these are '''beta builds''', '''''of course '''''theyre gonna be unstable. [[Special:Contributions/37.231.130.49|37.231.130.49]] 21:52, 4 December 2023 (UTC)<br />
: Just a question, does 3rd party app compatibility bugs notable? {{User:Someone200/Signature|14:19, 6 December 2023 (UTC)}}<br />
::no. Pre-release builds aren't designed at first place to run third-party apps, maybe at most those ones from the era of the specific build. For example, imagine you were one of the testers of Vista Beta 2 or RC in 2006, you would've likely tested out how the ''back then'' latest versions of Firefox, 1.5 or 2.0, would perform. The builds weren't designed to run way newer versions like 38. Still, bugs and quirks with 3rd-party apps wouldn't really that useful for that wiki, per bf10. - <code>[[File:Windows logo (2003).svg|18px]] [[User:Bob2204|Bob2204]]</code> [[File:Arrow.png|15px]] Click here to begin. Or here. [[File:Arrow2.png|15px]] <code>[[User talk:Bob2204|Talk]]</code> - 14:31, 6 December 2023 (UTC)<br />
<br />
== Creating new user warning templates ==<br />
<br />
I think there should be more user warning templates, since there is only one set of user warning templates. Who agrees with me? [[File:Windows_logo_(2006).svg|35px]] [[User:763004|'''763004''']] ([[User talk:763004|Talk]] &bull; [[User:763004/Sandbox|Sandbox]]) 13:25, 20 December 2023 (UTC)<br />
:Well then create them. No need to bother with voting... --{{User:Ryuzaki/Signature}} 13:29, 20 December 2023 (UTC)<br />
::Alrighty then. <small>(I'll test these in the sandbox first, or on [[Template:Test]])</small> [[File:Windows_logo_(2006).svg|35px]] [[User:763004|'''763004''']] ([[User talk:763004|Talk]] &bull; [[User:763004/Sandbox|Sandbox]]) 13:32, 20 December 2023 (UTC)<br />
<br />
=== Support ===<br />
# Per above. [[File:Windows_logo_(2006).svg|35px]] [[User:763004|'''763004''']] ([[User talk:763004|Talk]] &bull; [[User:763004/Sandbox|Sandbox]]) 13:25, 20 December 2023 (UTC)<br />
<br />
=== Oppose ===</div>Ovctvcthttps://betawiki.net/index.php?title=BetaWiki:Community_portal&diff=311891BetaWiki:Community portal2023-12-26T10:00:09Z<p>Ovctvct: Reverted edits by 46.165.250.77 (talk) to last revision by Ovctvct</p>
<hr />
<div>__NEWSECTIONLINK__<br />
{{fmbox|type=system|image=none|text=<center><br />
<span style="font-size: 150%;">Welcome to BetaWiki community portal!</span><br />
<br />
This is where we discuss the operations of BetaWiki. Please help us to set down policies and guidelines, improve articles and more.<br />
<br />
If you want to request a specific administration action to be done, please use the [[BetaWiki:administrators' noticeboard|administrators' noticeboard]] instead.<br />
<br />
To add discussion, please add a new heading under this line.<br />
</center><br />
<br />
}}<br />
{{archives}}<br />
{{TOC|clear=left|limit=2}}<br />
<br />
== adding language parameter to the infobox windows build ==<br />
<br />
it will become easier to know the languages. [[Special:Contributions/51.15.78.38|51.15.78.38]] 10:38, 24 June 2023 (UTC)<br />
<br />
=== Support ===<br />
#per myself. [[Special:Contributions/51.15.78.38|51.15.78.38]] 10:38, 24 June 2023 (UTC)<br />
#I support this. Same feature is available for TheCollectionBook. But I doubt it's going to be accepted. This was requested a few times, and it was ignored. {{Unsigned|94.121.82.195}}<br />
#I support this, but only for releases preceding the introduction of the [[w:Multilingual_User_Interface|Multilingual User Interface (MUI)]] in Windows 2000. [[User:Ahernandez094|Ahernandez094]]<br />
=== Oppose ===<br />
#Unnecessary - Most internal beta builds are only available in a single language and if other languages are available, they ''will'' be mentioned on the respective build page. Public beta builds are available in basically every single language supported by Microsoft, so mentioning available languages on the respective build page is also unnecessary. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 12:12, 24 June 2023 (UTC)<br />
#:Also, most non-English builds of Windows, especially before Windows 8, are only official Beta/CTP/Preview/RTM builds and not internal ones. - <code>[[File:Windows logo (2003).svg|18px]] [[User:Bob2204|Bob2204]]</code> [[File:Arrow.png|15px]] Click here to begin. Or here. [[File:Arrow2.png|15px]] <code>[[User talk:Bob2204|Talk]]</code> - 16:18, 24 June 2023 (UTC)<br />
#::This https://betawiki.net/wiki/Windows_10_build_18327.1, it's not an official build. However it's available for many languages. {{Unsigned|94.121.82.195}}<br />
#::Do you seriously think that everyone who visit this wiki like reading long paragraphs? {{Unsigned|94.121.82.195}}<br />
#:::Read again. I only have said "most, '''especially before Windows 8'''". The Technical/Insider Preview thing changed many things, as they no longer release Preview/Beta/Alpha builds, but only multiple "Insider Previews", which can reach up to around 30 Insider Previews per version before a new version becomes released. - <code>[[File:Windows logo (2003).svg|18px]] [[User:Bob2204|Bob2204]]</code> [[File:Arrow.png|15px]] Click here to begin. Or here. [[File:Arrow2.png|15px]] <code>[[User talk:Bob2204|Talk]]</code> - 14:38, 25 June 2023 (UTC)<br />
#::::Understood. {{Unsigned|94.121.82.195}}<br />
#That's not how it works. Every build is compiled in all of the 23 base languages and all available SKUs. I oppose this simply because it would clutter the infobox, especially on Insider previews because they are indeed released in those base languages. --[[Special:Contributions/217.131.99.140|217.131.99.140]] 07:44, 29 June 2023 (UTC)<br />
#:Not '''every ''' is compiled in '''all''' languages. Some builds are only compiled for specific languages. Also what will you say about unleaked, shared or betas before Windows 7? {{Unsigned|94.120.197.130}}<br />
#::Simple: We never know what Microsoft did to their builds and if they're compiled in all languages or not. New languages were gradually added over time, so we need to remind ourselves of the past. Also, don't use {{tl|Unsigned}} to sign your comments, use <nowiki>~~~~</nowiki>. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 14:21, 4 July 2023 (UTC)<br />
#:::It's already impossible to know which languages are available in builds. But he said '''Every build is compiled in all of the 23 base languages''', which is definitely false. Otherwise we would have the builds 4074 in German or 5048 in French. The list goes on. [[User:94.120.197.130|94.120.197.130]] ([[User talk:94.120.197.130|talk]]) 14:29, 4 July 2023 (UTC)<br />
# Putting information to the infobox is a double-edged sword, it might make the information more discoverable but it also makes it more cluttered that it needs to be. Not to mention the relationship between SKUs, architectures and languages, since builds rarely are available in all listed combinations. A better approach would be a table like done for [[Windows 11 build 22000.1]]. --{{User:Ryuzaki/Signature}} 07:39, 29 June 2023 (UTC)<br />
#: Like in 2296.1 page? {{Unsigned|94.120.197.130}}<br />
<br />
== Changing recommended resolution images to 1,920 × 1,080 ==<br />
<br />
Literally every single build of Windows 11 use it for some reason, so I guess why not do it on other builds. [[Special:Contributions/37.120.213.238|37.120.213.238]] 11:36, 2 July 2023 (UTC)<br />
: I guess 1366 x 768 or 1400 x 900 would be better. 1920 x 1080 is too large. {{User:Someone200/Signature|23:36, 3 July 2023 (UTC)}}<br />
: The guidelines don't actually recommend a single resolution, they only say it should be period appropriate but ''at least'' 1024x768, unless the OS doesn't support that resolution. {{Unsigned|Ryuzaki}}<br />
<br />
==== Support ====<br />
#[[Special:Contributions/37.120.213.238|37.120.213.238]] 11:36, 2 July 2023 (UTC)<br />
<br />
==== Oppose ====<br />
#Most old hardware and older versions of Windows do not support such a ridiculously high resolution. Due to DPI scaling being a hit-or-miss on older OSes, the contents of the screenshots will also be too small, requiring the reader to click on the image to better view the screenshot. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 11:40, 2 July 2023 (UTC)<br />
#:Then why do Windows 11 builds do it then? I only requested this all because of Windows 11 images. [[Special:Contributions/37.120.213.238|37.120.213.238]] 11:43, 2 July 2023 (UTC)<br />
#::Newer versions of Windows are better suited for high-resolution displays, also blame the uploader for using that resolution. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 11:46, 2 July 2023 (UTC)<br />
#:::OH okay. Anyways, does 1,366 × 768 count as a "ridiculously" higher resolution? This is the alternative to 1,920 × 1,080, I guess. [[Special:Contributions/37.120.213.238|37.120.213.238]] 11:52, 2 July 2023 (UTC)<br />
#::::I don't think it counts, since it's basically 1024 × 768, but wider. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 12:18, 2 July 2023 (UTC)<br />
#:::I think we should only use 1920x1080 for win10 and win11 builds, and the problem is that there are a lot of Windows 10 builds that currently use 1024x768, which for Windows 10's time period is rather low. - [[User:Upseguest|Upseguest]] ([[User talk:Upseguest|talk]])<br />
<br />
==winmain in 2009/2010==<br />
There is a very odd thing I found out about winmain in the time period between builds 7232 (Win7) and 7700 (Win8). While 7232 already features the final Harmony wallpaper, 7700 oddly reused the betta fish one. The 7700 page said that it can be implied that this build was formed from a Win7 RC build. I really doubt this, because it's also possible that they just reverted this wallpaper thing for Win8/future winmain development. (At least the betta fish was used until Microsoft started the Technical Preview/Insider Program.) - <code>[[File:Windows logo (2003).svg|18px]] [[User:Bob2204|Bob2204]]</code> [[File:Arrow.png|15px]] Click here to begin. Or here. [[File:Arrow2.png|15px]] <code>[[User talk:Bob2204|Talk]]</code> - 23:29, 3 July 2023 (UTC)<br />
<br />
== Page Previews ==<br />
<br />
This wiki needs page previews feature. <small> —— This newly signed comment was added by [[File:Windows logo (2012).svg|15px]] [[User:LazytownSpo4015|<span class="signature-lazytownspo4015-userpage">'''<big>Lazytown Sportacus (LazytownSpo4015)</big>'''</span>]] • [[User talk:LazytownSpo4015|<span class="signature-lazytownspo4015-talk">Talk page]] • {{#if: | <nowiki>|</nowiki> '''{{{1}}}''' | }}</small> 14:03, 4 July 2023 (UTC)<br />
<br />
=== Support ===<br />
#Per myself. <small> —— This newly signed comment was added by [[File:Windows logo (2012).svg|15px]] [[User:LazytownSpo4015|<span class="signature-lazytownspo4015-userpage">'''<big>Lazytown Sportacus (LazytownSpo4015)</big>'''</span>]] • [[User talk:LazytownSpo4015|<span class="signature-lazytownspo4015-talk">Talk page]] • {{#if: | <nowiki>|</nowiki> '''{{{1}}}''' | }}</small> 14:03, 4 July 2023 (UTC)<br />
#I was so used to this exact feature on Wikipedia and it allows you to view pages without actually navigating to the specific page. When I first joined this wiki, I actually wondered why page previews aren't supported. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 14:12, 4 July 2023 (UTC)<br />
#This is a really convenient feature. I also wonder why they haven't been implemented yet. [[User:BetaReporter|BetaReporter]] ([[User talk:BetaReporter|talk]]) 17:27, 4 July 2023 (UTC)<br />
<br />
=== Oppose ===<br />
#You could use Visual Editor instead [[User:PikaaxYT|PikaaxYT]] ([[User talk:PikaaxYT|talk]]) 12:04, 22 October 2023 (UTC)<br />
<br />
== Move Insider Preview update pages to their respective build pages ==<br />
This is [https://betawiki.net/wiki/BetaWiki:Community_portal/Archive_9#Move_Insider_service_pipeline_updates_to_their_respective_build_pages. a (probably abandoned) proposal] made by [[Special:Contributions/Xeno|Xeno]]. I reopened this because the final decision hasn't been made, and I feel like the servicing pipelines updates are cluttering up the pages.<br />
<br />
If this reach 15+ support, I'll do it. It will take a long time though. (as always, please consider providing a reason if support/oppose as it helps me understand your opinion.)<br />
<br />
{{User:Someone200/Signature|14:23, 3 August 2023 (UTC)}}<br />
<br />
:The consensus was to carry that out, not sure why this needs another vote. --{{User:Ryuzaki/Signature}} 14:33, 3 August 2023 (UTC)<br />
<br />
== Purge <s>all</s> non-Windows related content (reopen) ==<br />
This is a reopen of [https://betawiki.net/wiki/BetaWiki:Community_portal/Archive_11#Purge_all_non-Windows_related_content my version] of [https://betawiki.net/wiki/BetaWiki:Community_portal/Archive_6#Purge_all_non-Windows_related_content a proposal by orbitron] that was abandoned, because apparently the aforementioned proposals aren't being passed through.<br />
<br />
Basically, most non-Windows stuff on the wiki, except macOS, iOS, DOS, and OS/2, gets literally no activity besides one or two users. Most pages covering Linux are too short and hardly contain any notable information (and no, bugs don't count as notable). The new features and changes present in each distro version are also not covered properly and the pages only contain the image of the desktop or the home screen, which is not enough for a good article.<br />
<br />
While the original proposal focused on all non-Windows content, I wanted to only focus on free-and-open-source OSes (such as Linux, BSD, and Haiku), Android, non-preinstalled web browsers (such as Google Chrome, Mozilla Firefox, Opera, and Netscape) and other less important OSes. For free-and-open source OSes and Android, they have been moved to [https://distro.wikitide.com/ a dedicated wiki that focused on these OSes.] For non-preinstalled web browsers, there are already Wikipedia pages for these browsers. I hope this makes BetaWiki a much cleaner site and live up to its name. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 14:40, 3 August 2023 (UTC)<br />
:The proposal was archived because it was dead with no clear consensus. Not sure what makes you think reopening it immediately after it got archived will reach a different result. --{{User:Ryuzaki/Signature}} 16:48, 3 August 2023 (UTC)<br />
::OK, I understand. I did not know that proposals would be archived if it was dead with no clear consensus. I first thought reopening my proposal would bring up attention to the two proposals I mentioned above, so I'm sorry for the mistake I made. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 23:11, 3 August 2023 (UTC)<br />
<br />
== Moving all GitHub issue related builds to a separate page ==<br />
<br />
I think that most of the Windows 10/11 pages are being cluttered with GitHub issue pages. Since these builds doesn't have a proper buildtag (only build number), I think they should be moved to a separate instead of being purged. Some of them could cause confusions because its build number is identical to another one.<br />
{{User:Someone200/Signature|03:15, 6 August 2023 (UTC)}}<br />
<br />
=== Support ===<br />
# Per myself. {{User:Someone200/Signature|03:15, 6 August 2023 (UTC)}}<br />
# Welp, this should also be done for servicing pipeline update builds. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 03:21, 6 August 2023 (UTC)<br />
# We should also do that for builds mentionned in SSUComp_KB*******.xml and Desktop_neutral_Forward_*****.****.***************.******-****.CompDB.xml files [[User:PikaaxYT|PikaaxYT]] ([[User talk:PikaaxYT|talk]]) 10:27, 11 August 2023 (UTC)<br />
<br />
=== Oppose ===<br />
<br />
== Adding downloads of the builds in their infoboxes (CLOSED) ==<br />
<br />
<s>Or at least adding an information on where to download the builds <small>—&nbsp;Preceding unsigned comment added by [[User:PikaaxYT|PikaaxYT]] ([[User talk:PikaaxYT|talk]] • [[Special:Contributions/PikaaxYT|contribs]]) </small></s><br />
<br />
I closed the request because download links would violate the guidelines {{unsigned|PikaaxYT}}<br />
<br />
=== Support ===<br />
<br />
1. [[User:PikaaxYT|PikaaxYT]]<br />
<br />
=== Oppose ===<br />
<br />
# See [[BW:Guidelines#Legal|BW:Guidelines § Legal]]. [[User:Jurta|Jurta]] ([[User talk:Jurta|talk]] • [[Special:Contributions/Jurta|contribs]]) 19:52, 10 August 2023 (UTC)<br />
# We are most certainly '''NOT''' providing download links to these builds on the wiki. The wiki is intended to be a knowledge base for these builds. Find the builds yourself. The Windows build FAQ page points out that archive.org and WinWorld are good starting points to find most builds. Although, be careful as there are fake builds out there. It is very easy to find these builds anyways. <code>[[File:Windows Orb logo (2006).png|18px]] [[User:WindowsGuy2021|WindowsGuy2021]]</code> 2:59, 10 August 2023 (UTC)<br />
<br />
== Purge Linux and Android content ==<br />
here we go again...<br />
<br />
Most Linux distributions in BetaWiki are not notable, and by "not notable" I mean most of the articles talking about a Linux distro are too short, low quality, and hardly contain any useful or notable information. The Android articles are a good example of this, since they are made of an infobox, a lead sentence, a list of changes (or builds), and that's it. The information necessary for a knowledge base, such as the development history, features, and the overall aspects of a Linux distro, is also missing from the aforementioned articles. Other websites did a much better job at documenting these distros since they are not Windows-centric, unlike BetaWiki. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 09:10, 22 August 2023 (UTC)<br />
:I agree for purging Linux articles but not for purging Android articles because if they are deleted we should also purge iOS articles since most builds doesn’t even have an article and the few builds that have an article only have an infobox and a smaller sentence than Android articles [[User:PikaaxYT|PikaaxYT]] ([[User talk:PikaaxYT|talk]]) 12:03, 22 October 2023 (UTC)<br />
::now that DistroWiki got closed, following with the stepdown of Nara and GT610, I think that never ending purging discussion finally reached a dead end, at least for now. <br />
::Yes, there are still better wikis and pages for operating systems other than windows, but that discussion didn't really help us to make steps forward. At the end, the consequence was another wiki for just that reason, which failed to gain any reputation in their scene like betawiki does and thus failing overall. No one came out from there as winner. <br />
<br />
::The best thing that we can do for now is just continuing our work here. - <code>[[File:Windows logo (2003).svg|18px]] [[User:Bob2204|Bob2204]]</code> [[File:Arrow.png|15px]] Click here to begin. Or here. [[File:Arrow2.png|15px]] <code>[[User talk:Bob2204|Talk]]</code> - 23:00, 30 November 2023 (UTC)<br />
:::Nara here. Yes, BetaWiki should've stayed the same and the DistroWiki effort, in my opinion, was just a waste of time. Despite having 99% of its focus on Windows, there are still people who do Linux stuff here and we should respect them. I'll say the discussion is finally over, like you said. [[Special:Contributions/139.192.153.112|139.192.153.112]] 03:53, 2 December 2023 (UTC)<br />
<br />
== discord server invite link ==<br />
<br />
i'm trying to rejoin the BW discord, but it says the link is expired. Has the server been deleted or is it a dead invite? {{Unsigned|Grafality}}<br />
:It's a dead invite. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 05:33, 16 September 2023 (UTC)<br />
::if it is a dead invite, then why wouldn't I rejoin BW Discord server? Also I'm sorry for my past actions while I'm in the server. <small> —— This newly signed comment was added by [[File:Windows logo (2012).svg|15px]] [[User:LazytownSpo4015|<span class="signature-lazytownspo4015-userpage">'''<big>Lazytown Sportacus (LazytownSpo4015)</big>'''</span>]] • [[User talk:LazytownSpo4015|<span class="signature-lazytownspo4015-talk">Talk page]] • {{#if: | <nowiki>|</nowiki> '''{{{1}}}''' | }}</small> 08:57, 16 September 2023 (UTC)<br />
:::I hate to tell you this, but you have been banned from the BW Discord server. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 08:59, 16 September 2023 (UTC)<br />
::::I know but, I'm very sorry for my past actions when i was there. How am i going to appeal a ban from the BW discord server? <small> —— This newly signed comment was added by [[File:Windows logo (2012).svg|15px]] [[User:LazytownSpo4015|<span class="signature-lazytownspo4015-userpage">'''<big>Lazytown Sportacus (LazytownSpo4015)</big>'''</span>]] • [[User talk:LazytownSpo4015|<span class="signature-lazytownspo4015-talk">Talk page]] • {{#if: | <nowiki>|</nowiki> '''{{{1}}}''' | }}</small> 09:13, 11 October 2023 (UTC)<br />
:::"if it is a dead invite, then why wouldn't I rejoin BW Discord server?" Precisely because it was a dead invite? It is fixed now though. --{{User:Ryuzaki/Signature}} 09:46, 16 September 2023 (UTC)<br />
<br />
== 8297.0.fbl_fun_embedded_xos.120311-1700 ==<br />
<br />
Please make a page for Xbox One OS build 8297. It's availible, so it should be possible. I'm not experienced enough to get the OS and run it in some sort of emulator. {{Unsigned|146.212.161.185}}<br />
:You literally put the same thing in here and in [[Talk:Main Page]]. [[File:Windows_logo_(2006).svg|35px]] [[User:763004|'''763004''']] ([[User talk:763004|Talk]] &bull; [[User:763004/Sandbox|Sandbox]]) 17:27, 10 October 2023 (UTC)<br />
<br />
== Cleaning up Bugs and quirks section ==<br />
<br />
After some deep review about a few additions within these sections lately, it's been seen that we're getting a lot of hardware/VM-only related problems that seems to be extremely niche to encounter, and in several cases, results from using a config that is way above what was the norm/available at the time. Most of these bugs tend to be of sensitive/setup-specific, and often are just encountered by one user due to a bad config.<br />
<br />
As a result of this, I'm going to start suggesting that any compatibility bugs are heavily stripped down, since adding these bugs aren't necessarily of "meaningful" edits and ends up being more disruptive for the flow of the page. This would mean that the following changes will be made, with some examples of what we don't want:<br />
* Any bugs that mention [https://betawiki.net/index.php?title=Windows_Longhorn_build_4002_%28Lab06_N%29&type=revision&diff=307656&oldid=303257 "this build won't install in modern versions of <program>"] will no longer be allowed and will be removed. This is a setup-specific problem, and also this wiki is not a compatibility checklist.<br />
* Any bugs that mention [https://betawiki.net/index.php?title=Windows_NT_4.0_build_1130&type=revision&diff=261298&oldid=260828 "this driver doesn't work"] will also no longer be allowed and will be removed. Generally a setup-specific problem or incomplete driver support; again betas aren't meant to be complete.<br />
* A lot of [https://betawiki.net/index.php?title=Windows_XP_build_2202&type=revision&diff=308836&oldid=303304 VM compatibility bugs] will be stripped down. I'd prefer they'd be removed completely, but that's not necessarily going to be favorable for certain builds that need an abnormally early compatibility. But then again, it's preferable to use the version that was closest to when that build was compiled. For reference, VMware 5.0 released around 2005, while VMware 6.0 released around 2007. So it would not make sense to install say build 5231 on modern versions, and vise versa. This is also largely a setup-related problem, usually.<br />
<br />
Most of the bugs that are intended to be removed will usually be of that hardware related, unless they are a widespread problem and often well-known by Microsoft in documentation, such as the Windows NT 3.x processor setup bug. But for singular builds, these bugs would have to go, and don't contribute as a "meaningful" edit and more of a way to inflate the page with niche setups.<br />
<br />
Also to note adding "persists until build" isn't necessarily a meaningful edit, as well. We do not need to document every little bug you see, as again beta builds are often unstable and prone to bugs and inconveniences. Bugs are to only be documented usually when they often affect real hardware too and is major enough that it often impacts the usability of the build even in the most general scenario. Subsequently reverting/adding these oft-unnecessary bugs is means of disruptive editing, and warnings will be handed out.<br />
<br />
[[User:BF10|BF10]] ([[User talk:BF10|talk]]) 13:35, 4 December 2023 (UTC)<br />
:We also have to remove "this build has some stabillity issues" edits, because these are '''beta builds''', '''''of course '''''theyre gonna be unstable. [[Special:Contributions/37.231.130.49|37.231.130.49]] 21:52, 4 December 2023 (UTC)<br />
: Just a question, does 3rd party app compatibility bugs notable? {{User:Someone200/Signature|14:19, 6 December 2023 (UTC)}}<br />
::no. Pre-release builds aren't designed at first place to run third-party apps, maybe at most those ones from the era of the specific build. For example, imagine you were one of the testers of Vista Beta 2 or RC in 2006, you would've likely tested out how the ''back then'' latest versions of Firefox, 1.5 or 2.0, would perform. The builds weren't designed to run way newer versions like 38. Still, bugs and quirks with 3rd-party apps wouldn't really that useful for that wiki, per bf10. - <code>[[File:Windows logo (2003).svg|18px]] [[User:Bob2204|Bob2204]]</code> [[File:Arrow.png|15px]] Click here to begin. Or here. [[File:Arrow2.png|15px]] <code>[[User talk:Bob2204|Talk]]</code> - 14:31, 6 December 2023 (UTC)<br />
<br />
== Creating new user warning templates ==<br />
<br />
I think there should be more user warning templates, since there is only one set of user warning templates. Who agrees with me? [[File:Windows_logo_(2006).svg|35px]] [[User:763004|'''763004''']] ([[User talk:763004|Talk]] &bull; [[User:763004/Sandbox|Sandbox]]) 13:25, 20 December 2023 (UTC)<br />
:Well then create them. No need to bother with voting... --{{User:Ryuzaki/Signature}} 13:29, 20 December 2023 (UTC)<br />
::Alrighty then. <small>(I'll test these in the sandbox first, or on [[Template:Test]])</small> [[File:Windows_logo_(2006).svg|35px]] [[User:763004|'''763004''']] ([[User talk:763004|Talk]] &bull; [[User:763004/Sandbox|Sandbox]]) 13:32, 20 December 2023 (UTC)<br />
<br />
=== Support ===<br />
# Per above. [[File:Windows_logo_(2006).svg|35px]] [[User:763004|'''763004''']] ([[User talk:763004|Talk]] &bull; [[User:763004/Sandbox|Sandbox]]) 13:25, 20 December 2023 (UTC)<br />
<br />
=== Oppose ===</div>Ovctvcthttps://betawiki.net/index.php?title=BetaWiki:Community_portal&diff=311889BetaWiki:Community portal2023-12-26T09:57:52Z<p>Ovctvct: Reverted edits by 185.80.221.85 (talk) to last revision by Ovctvct</p>
<hr />
<div>__NEWSECTIONLINK__<br />
{{fmbox|type=system|image=none|text=<center><br />
<span style="font-size: 150%;">Welcome to BetaWiki community portal!</span><br />
<br />
This is where we discuss the operations of BetaWiki. Please help us to set down policies and guidelines, improve articles and more.<br />
<br />
If you want to request a specific administration action to be done, please use the [[BetaWiki:administrators' noticeboard|administrators' noticeboard]] instead.<br />
<br />
To add discussion, please add a new heading under this line.<br />
</center><br />
<br />
}}<br />
{{archives}}<br />
{{TOC|clear=left|limit=2}}<br />
<br />
== adding language parameter to the infobox windows build ==<br />
<br />
it will become easier to know the languages. [[Special:Contributions/51.15.78.38|51.15.78.38]] 10:38, 24 June 2023 (UTC)<br />
<br />
=== Support ===<br />
#per myself. [[Special:Contributions/51.15.78.38|51.15.78.38]] 10:38, 24 June 2023 (UTC)<br />
#I support this. Same feature is available for TheCollectionBook. But I doubt it's going to be accepted. This was requested a few times, and it was ignored. {{Unsigned|94.121.82.195}}<br />
#I support this, but only for releases preceding the introduction of the [[w:Multilingual_User_Interface|Multilingual User Interface (MUI)]] in Windows 2000. [[User:Ahernandez094|Ahernandez094]]<br />
=== Oppose ===<br />
#Unnecessary - Most internal beta builds are only available in a single language and if other languages are available, they ''will'' be mentioned on the respective build page. Public beta builds are available in basically every single language supported by Microsoft, so mentioning available languages on the respective build page is also unnecessary. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 12:12, 24 June 2023 (UTC)<br />
#:Also, most non-English builds of Windows, especially before Windows 8, are only official Beta/CTP/Preview/RTM builds and not internal ones. - <code>[[File:Windows logo (2003).svg|18px]] [[User:Bob2204|Bob2204]]</code> [[File:Arrow.png|15px]] Click here to begin. Or here. [[File:Arrow2.png|15px]] <code>[[User talk:Bob2204|Talk]]</code> - 16:18, 24 June 2023 (UTC)<br />
#::This https://betawiki.net/wiki/Windows_10_build_18327.1, it's not an official build. However it's available for many languages. {{Unsigned|94.121.82.195}}<br />
#::Do you seriously think that everyone who visit this wiki like reading long paragraphs? {{Unsigned|94.121.82.195}}<br />
#:::Read again. I only have said "most, '''especially before Windows 8'''". The Technical/Insider Preview thing changed many things, as they no longer release Preview/Beta/Alpha builds, but only multiple "Insider Previews", which can reach up to around 30 Insider Previews per version before a new version becomes released. - <code>[[File:Windows logo (2003).svg|18px]] [[User:Bob2204|Bob2204]]</code> [[File:Arrow.png|15px]] Click here to begin. Or here. [[File:Arrow2.png|15px]] <code>[[User talk:Bob2204|Talk]]</code> - 14:38, 25 June 2023 (UTC)<br />
#::::Understood. {{Unsigned|94.121.82.195}}<br />
#That's not how it works. Every build is compiled in all of the 23 base languages and all available SKUs. I oppose this simply because it would clutter the infobox, especially on Insider previews because they are indeed released in those base languages. --[[Special:Contributions/217.131.99.140|217.131.99.140]] 07:44, 29 June 2023 (UTC)<br />
#:Not '''every ''' is compiled in '''all''' languages. Some builds are only compiled for specific languages. Also what will you say about unleaked, shared or betas before Windows 7? {{Unsigned|94.120.197.130}}<br />
#::Simple: We never know what Microsoft did to their builds and if they're compiled in all languages or not. New languages were gradually added over time, so we need to remind ourselves of the past. Also, don't use {{tl|Unsigned}} to sign your comments, use <nowiki>~~~~</nowiki>. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 14:21, 4 July 2023 (UTC)<br />
#:::It's already impossible to know which languages are available in builds. But he said '''Every build is compiled in all of the 23 base languages''', which is definitely false. Otherwise we would have the builds 4074 in German or 5048 in French. The list goes on. [[User:94.120.197.130|94.120.197.130]] ([[User talk:94.120.197.130|talk]]) 14:29, 4 July 2023 (UTC)<br />
# Putting information to the infobox is a double-edged sword, it might make the information more discoverable but it also makes it more cluttered that it needs to be. Not to mention the relationship between SKUs, architectures and languages, since builds rarely are available in all listed combinations. A better approach would be a table like done for [[Windows 11 build 22000.1]]. --{{User:Ryuzaki/Signature}} 07:39, 29 June 2023 (UTC)<br />
#: Like in 2296.1 page? {{Unsigned|94.120.197.130}}<br />
<br />
== Changing recommended resolution images to 1,920 × 1,080 ==<br />
<br />
Literally every single build of Windows 11 use it for some reason, so I guess why not do it on other builds. [[Special:Contributions/37.120.213.238|37.120.213.238]] 11:36, 2 July 2023 (UTC)<br />
: I guess 1366 x 768 or 1400 x 900 would be better. 1920 x 1080 is too large. {{User:Someone200/Signature|23:36, 3 July 2023 (UTC)}}<br />
: The guidelines don't actually recommend a single resolution, they only say it should be period appropriate but ''at least'' 1024x768, unless the OS doesn't support that resolution. {{Unsigned|Ryuzaki}}<br />
<br />
==== Support ====<br />
#[[Special:Contributions/37.120.213.238|37.120.213.238]] 11:36, 2 July 2023 (UTC)<br />
<br />
==== Oppose ====<br />
#Most old hardware and older versions of Windows do not support such a ridiculously high resolution. Due to DPI scaling being a hit-or-miss on older OSes, the contents of the screenshots will also be too small, requiring the reader to click on the image to better view the screenshot. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 11:40, 2 July 2023 (UTC)<br />
#:Then why do Windows 11 builds do it then? I only requested this all because of Windows 11 images. [[Special:Contributions/37.120.213.238|37.120.213.238]] 11:43, 2 July 2023 (UTC)<br />
#::Newer versions of Windows are better suited for high-resolution displays, also blame the uploader for using that resolution. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 11:46, 2 July 2023 (UTC)<br />
#:::OH okay. Anyways, does 1,366 × 768 count as a "ridiculously" higher resolution? This is the alternative to 1,920 × 1,080, I guess. [[Special:Contributions/37.120.213.238|37.120.213.238]] 11:52, 2 July 2023 (UTC)<br />
#::::I don't think it counts, since it's basically 1024 × 768, but wider. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 12:18, 2 July 2023 (UTC)<br />
#:::I think we should only use 1920x1080 for win10 and win11 builds, and the problem is that there are a lot of Windows 10 builds that currently use 1024x768, which for Windows 10's time period is rather low. - [[User:Upseguest|Upseguest]] ([[User talk:Upseguest|talk]])<br />
<br />
==winmain in 2009/2010==<br />
There is a very odd thing I found out about winmain in the time period between builds 7232 (Win7) and 7700 (Win8). While 7232 already features the final Harmony wallpaper, 7700 oddly reused the betta fish one. The 7700 page said that it can be implied that this build was formed from a Win7 RC build. I really doubt this, because it's also possible that they just reverted this wallpaper thing for Win8/future winmain development. (At least the betta fish was used until Microsoft started the Technical Preview/Insider Program.) - <code>[[File:Windows logo (2003).svg|18px]] [[User:Bob2204|Bob2204]]</code> [[File:Arrow.png|15px]] Click here to begin. Or here. [[File:Arrow2.png|15px]] <code>[[User talk:Bob2204|Talk]]</code> - 23:29, 3 July 2023 (UTC)<br />
<br />
== Page Previews ==<br />
<br />
This wiki needs page previews feature. <small> —— This newly signed comment was added by [[File:Windows logo (2012).svg|15px]] [[User:LazytownSpo4015|<span class="signature-lazytownspo4015-userpage">'''<big>Lazytown Sportacus (LazytownSpo4015)</big>'''</span>]] • [[User talk:LazytownSpo4015|<span class="signature-lazytownspo4015-talk">Talk page]] • {{#if: | <nowiki>|</nowiki> '''{{{1}}}''' | }}</small> 14:03, 4 July 2023 (UTC)<br />
<br />
=== Support ===<br />
#Per myself. <small> —— This newly signed comment was added by [[File:Windows logo (2012).svg|15px]] [[User:LazytownSpo4015|<span class="signature-lazytownspo4015-userpage">'''<big>Lazytown Sportacus (LazytownSpo4015)</big>'''</span>]] • [[User talk:LazytownSpo4015|<span class="signature-lazytownspo4015-talk">Talk page]] • {{#if: | <nowiki>|</nowiki> '''{{{1}}}''' | }}</small> 14:03, 4 July 2023 (UTC)<br />
#I was so used to this exact feature on Wikipedia and it allows you to view pages without actually navigating to the specific page. When I first joined this wiki, I actually wondered why page previews aren't supported. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 14:12, 4 July 2023 (UTC)<br />
#This is a really convenient feature. I also wonder why they haven't been implemented yet. [[User:BetaReporter|BetaReporter]] ([[User talk:BetaReporter|talk]]) 17:27, 4 July 2023 (UTC)<br />
<br />
=== Oppose ===<br />
#You could use Visual Editor instead [[User:PikaaxYT|PikaaxYT]] ([[User talk:PikaaxYT|talk]]) 12:04, 22 October 2023 (UTC)<br />
<br />
== Move Insider Preview update pages to their respective build pages ==<br />
This is [https://betawiki.net/wiki/BetaWiki:Community_portal/Archive_9#Move_Insider_service_pipeline_updates_to_their_respective_build_pages. a (probably abandoned) proposal] made by [[Special:Contributions/Xeno|Xeno]]. I reopened this because the final decision hasn't been made, and I feel like the servicing pipelines updates are cluttering up the pages.<br />
<br />
If this reach 15+ support, I'll do it. It will take a long time though. (as always, please consider providing a reason if support/oppose as it helps me understand your opinion.)<br />
<br />
{{User:Someone200/Signature|14:23, 3 August 2023 (UTC)}}<br />
<br />
:The consensus was to carry that out, not sure why this needs another vote. --{{User:Ryuzaki/Signature}} 14:33, 3 August 2023 (UTC)<br />
<br />
== Purge <s>all</s> non-Windows related content (reopen) ==<br />
This is a reopen of [https://betawiki.net/wiki/BetaWiki:Community_portal/Archive_11#Purge_all_non-Windows_related_content my version] of [https://betawiki.net/wiki/BetaWiki:Community_portal/Archive_6#Purge_all_non-Windows_related_content a proposal by orbitron] that was abandoned, because apparently the aforementioned proposals aren't being passed through.<br />
<br />
Basically, most non-Windows stuff on the wiki, except macOS, iOS, DOS, and OS/2, gets literally no activity besides one or two users. Most pages covering Linux are too short and hardly contain any notable information (and no, bugs don't count as notable). The new features and changes present in each distro version are also not covered properly and the pages only contain the image of the desktop or the home screen, which is not enough for a good article.<br />
<br />
While the original proposal focused on all non-Windows content, I wanted to only focus on free-and-open-source OSes (such as Linux, BSD, and Haiku), Android, non-preinstalled web browsers (such as Google Chrome, Mozilla Firefox, Opera, and Netscape) and other less important OSes. For free-and-open source OSes and Android, they have been moved to [https://distro.wikitide.com/ a dedicated wiki that focused on these OSes.] For non-preinstalled web browsers, there are already Wikipedia pages for these browsers. I hope this makes BetaWiki a much cleaner site and live up to its name. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 14:40, 3 August 2023 (UTC)<br />
:The proposal was archived because it was dead with no clear consensus. Not sure what makes you think reopening it immediately after it got archived will reach a different result. --{{User:Ryuzaki/Signature}} 16:48, 3 August 2023 (UTC)<br />
::OK, I understand. I did not know that proposals would be archived if it was dead with no clear consensus. I first thought reopening my proposal would bring up attention to the two proposals I mentioned above, so I'm sorry for the mistake I made. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 23:11, 3 August 2023 (UTC)<br />
<br />
== Moving all GitHub issue related builds to a separate page ==<br />
<br />
I think that most of the Windows 10/11 pages are being cluttered with GitHub issue pages. Since these builds doesn't have a proper buildtag (only build number), I think they should be moved to a separate instead of being purged. Some of them could cause confusions because its build number is identical to another one.<br />
{{User:Someone200/Signature|03:15, 6 August 2023 (UTC)}}<br />
<br />
=== Support ===<br />
# Per myself. {{User:Someone200/Signature|03:15, 6 August 2023 (UTC)}}<br />
# Welp, this should also be done for servicing pipeline update builds. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 03:21, 6 August 2023 (UTC)<br />
# We should also do that for builds mentionned in SSUComp_KB*******.xml and Desktop_neutral_Forward_*****.****.***************.******-****.CompDB.xml files [[User:PikaaxYT|PikaaxYT]] ([[User talk:PikaaxYT|talk]]) 10:27, 11 August 2023 (UTC)<br />
<br />
=== Oppose ===<br />
<br />
== Adding downloads of the builds in their infoboxes (CLOSED) ==<br />
<br />
<s>Or at least adding an information on where to download the builds <small>—&nbsp;Preceding unsigned comment added by [[User:PikaaxYT|PikaaxYT]] ([[User talk:PikaaxYT|talk]] • [[Special:Contributions/PikaaxYT|contribs]]) </small></s><br />
<br />
I closed the request because download links would violate the guidelines {{unsigned|PikaaxYT}}<br />
<br />
=== Support ===<br />
<br />
1. [[User:PikaaxYT|PikaaxYT]]<br />
<br />
=== Oppose ===<br />
<br />
# See [[BW:Guidelines#Legal|BW:Guidelines § Legal]]. [[User:Jurta|Jurta]] ([[User talk:Jurta|talk]] • [[Special:Contributions/Jurta|contribs]]) 19:52, 10 August 2023 (UTC)<br />
# We are most certainly '''NOT''' providing download links to these builds on the wiki. The wiki is intended to be a knowledge base for these builds. Find the builds yourself. The Windows build FAQ page points out that archive.org and WinWorld are good starting points to find most builds. Although, be careful as there are fake builds out there. It is very easy to find these builds anyways. <code>[[File:Windows Orb logo (2006).png|18px]] [[User:WindowsGuy2021|WindowsGuy2021]]</code> 2:59, 10 August 2023 (UTC)<br />
<br />
== Purge Linux and Android content ==<br />
here we go again...<br />
<br />
Most Linux distributions in BetaWiki are not notable, and by "not notable" I mean most of the articles talking about a Linux distro are too short, low quality, and hardly contain any useful or notable information. The Android articles are a good example of this, since they are made of an infobox, a lead sentence, a list of changes (or builds), and that's it. The information necessary for a knowledge base, such as the development history, features, and the overall aspects of a Linux distro, is also missing from the aforementioned articles. Other websites did a much better job at documenting these distros since they are not Windows-centric, unlike BetaWiki. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 09:10, 22 August 2023 (UTC)<br />
:I agree for purging Linux articles but not for purging Android articles because if they are deleted we should also purge iOS articles since most builds doesn’t even have an article and the few builds that have an article only have an infobox and a smaller sentence than Android articles [[User:PikaaxYT|PikaaxYT]] ([[User talk:PikaaxYT|talk]]) 12:03, 22 October 2023 (UTC)<br />
::now that DistroWiki got closed, following with the stepdown of Nara and GT610, I think that never ending purging discussion finally reached a dead end, at least for now. <br />
::Yes, there are still better wikis and pages for operating systems other than windows, but that discussion didn't really help us to make steps forward. At the end, the consequence was another wiki for just that reason, which failed to gain any reputation in their scene like betawiki does and thus failing overall. No one came out from there as winner. <br />
<br />
::The best thing that we can do for now is just continuing our work here. - <code>[[File:Windows logo (2003).svg|18px]] [[User:Bob2204|Bob2204]]</code> [[File:Arrow.png|15px]] Click here to begin. Or here. [[File:Arrow2.png|15px]] <code>[[User talk:Bob2204|Talk]]</code> - 23:00, 30 November 2023 (UTC)<br />
:::Nara here. Yes, BetaWiki should've stayed the same and the DistroWiki effort, in my opinion, was just a waste of time. Despite having 99% of its focus on Windows, there are still people who do Linux stuff here and we should respect them. I'll say the discussion is finally over, like you said. [[Special:Contributions/139.192.153.112|139.192.153.112]] 03:53, 2 December 2023 (UTC)<br />
<br />
== discord server invite link ==<br />
<br />
i'm trying to rejoin the BW discord, but it says the link is expired. Has the server been deleted or is it a dead invite? {{Unsigned|Grafality}}<br />
:It's a dead invite. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 05:33, 16 September 2023 (UTC)<br />
::if it is a dead invite, then why wouldn't I rejoin BW Discord server? Also I'm sorry for my past actions while I'm in the server. <small> —— This newly signed comment was added by [[File:Windows logo (2012).svg|15px]] [[User:LazytownSpo4015|<span class="signature-lazytownspo4015-userpage">'''<big>Lazytown Sportacus (LazytownSpo4015)</big>'''</span>]] • [[User talk:LazytownSpo4015|<span class="signature-lazytownspo4015-talk">Talk page]] • {{#if: | <nowiki>|</nowiki> '''{{{1}}}''' | }}</small> 08:57, 16 September 2023 (UTC)<br />
:::I hate to tell you this, but you have been banned from the BW Discord server. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 08:59, 16 September 2023 (UTC)<br />
::::I know but, I'm very sorry for my past actions when i was there. How am i going to appeal a ban from the BW discord server? <small> —— This newly signed comment was added by [[File:Windows logo (2012).svg|15px]] [[User:LazytownSpo4015|<span class="signature-lazytownspo4015-userpage">'''<big>Lazytown Sportacus (LazytownSpo4015)</big>'''</span>]] • [[User talk:LazytownSpo4015|<span class="signature-lazytownspo4015-talk">Talk page]] • {{#if: | <nowiki>|</nowiki> '''{{{1}}}''' | }}</small> 09:13, 11 October 2023 (UTC)<br />
:::"if it is a dead invite, then why wouldn't I rejoin BW Discord server?" Precisely because it was a dead invite? It is fixed now though. --{{User:Ryuzaki/Signature}} 09:46, 16 September 2023 (UTC)<br />
<br />
== 8297.0.fbl_fun_embedded_xos.120311-1700 ==<br />
<br />
Please make a page for Xbox One OS build 8297. It's availible, so it should be possible. I'm not experienced enough to get the OS and run it in some sort of emulator. {{Unsigned|146.212.161.185}}<br />
:You literally put the same thing in here and in [[Talk:Main Page]]. [[File:Windows_logo_(2006).svg|35px]] [[User:763004|'''763004''']] ([[User talk:763004|Talk]] &bull; [[User:763004/Sandbox|Sandbox]]) 17:27, 10 October 2023 (UTC)<br />
<br />
== Cleaning up Bugs and quirks section ==<br />
<br />
After some deep review about a few additions within these sections lately, it's been seen that we're getting a lot of hardware/VM-only related problems that seems to be extremely niche to encounter, and in several cases, results from using a config that is way above what was the norm/available at the time. Most of these bugs tend to be of sensitive/setup-specific, and often are just encountered by one user due to a bad config.<br />
<br />
As a result of this, I'm going to start suggesting that any compatibility bugs are heavily stripped down, since adding these bugs aren't necessarily of "meaningful" edits and ends up being more disruptive for the flow of the page. This would mean that the following changes will be made, with some examples of what we don't want:<br />
* Any bugs that mention [https://betawiki.net/index.php?title=Windows_Longhorn_build_4002_%28Lab06_N%29&type=revision&diff=307656&oldid=303257 "this build won't install in modern versions of <program>"] will no longer be allowed and will be removed. This is a setup-specific problem, and also this wiki is not a compatibility checklist.<br />
* Any bugs that mention [https://betawiki.net/index.php?title=Windows_NT_4.0_build_1130&type=revision&diff=261298&oldid=260828 "this driver doesn't work"] will also no longer be allowed and will be removed. Generally a setup-specific problem or incomplete driver support; again betas aren't meant to be complete.<br />
* A lot of [https://betawiki.net/index.php?title=Windows_XP_build_2202&type=revision&diff=308836&oldid=303304 VM compatibility bugs] will be stripped down. I'd prefer they'd be removed completely, but that's not necessarily going to be favorable for certain builds that need an abnormally early compatibility. But then again, it's preferable to use the version that was closest to when that build was compiled. For reference, VMware 5.0 released around 2005, while VMware 6.0 released around 2007. So it would not make sense to install say build 5231 on modern versions, and vise versa. This is also largely a setup-related problem, usually.<br />
<br />
Most of the bugs that are intended to be removed will usually be of that hardware related, unless they are a widespread problem and often well-known by Microsoft in documentation, such as the Windows NT 3.x processor setup bug. But for singular builds, these bugs would have to go, and don't contribute as a "meaningful" edit and more of a way to inflate the page with niche setups.<br />
<br />
Also to note adding "persists until build" isn't necessarily a meaningful edit, as well. We do not need to document every little bug you see, as again beta builds are often unstable and prone to bugs and inconveniences. Bugs are to only be documented usually when they often affect real hardware too and is major enough that it often impacts the usability of the build even in the most general scenario. Subsequently reverting/adding these oft-unnecessary bugs is means of disruptive editing, and warnings will be handed out.<br />
<br />
[[User:BF10|BF10]] ([[User talk:BF10|talk]]) 13:35, 4 December 2023 (UTC)<br />
:We also have to remove "this build has some stabillity issues" edits, because these are '''beta builds''', '''''of course '''''theyre gonna be unstable. [[Special:Contributions/37.231.130.49|37.231.130.49]] 21:52, 4 December 2023 (UTC)<br />
: Just a question, does 3rd party app compatibility bugs notable? {{User:Someone200/Signature|14:19, 6 December 2023 (UTC)}}<br />
::no. Pre-release builds aren't designed at first place to run third-party apps, maybe at most those ones from the era of the specific build. For example, imagine you were one of the testers of Vista Beta 2 or RC in 2006, you would've likely tested out how the ''back then'' latest versions of Firefox, 1.5 or 2.0, would perform. The builds weren't designed to run way newer versions like 38. Still, bugs and quirks with 3rd-party apps wouldn't really that useful for that wiki, per bf10. - <code>[[File:Windows logo (2003).svg|18px]] [[User:Bob2204|Bob2204]]</code> [[File:Arrow.png|15px]] Click here to begin. Or here. [[File:Arrow2.png|15px]] <code>[[User talk:Bob2204|Talk]]</code> - 14:31, 6 December 2023 (UTC)<br />
<br />
== Creating new user warning templates ==<br />
<br />
I think there should be more user warning templates, since there is only one set of user warning templates. Who agrees with me? [[File:Windows_logo_(2006).svg|35px]] [[User:763004|'''763004''']] ([[User talk:763004|Talk]] &bull; [[User:763004/Sandbox|Sandbox]]) 13:25, 20 December 2023 (UTC)<br />
:Well then create them. No need to bother with voting... --{{User:Ryuzaki/Signature}} 13:29, 20 December 2023 (UTC)<br />
::Alrighty then. <small>(I'll test these in the sandbox first, or on [[Template:Test]])</small> [[File:Windows_logo_(2006).svg|35px]] [[User:763004|'''763004''']] ([[User talk:763004|Talk]] &bull; [[User:763004/Sandbox|Sandbox]]) 13:32, 20 December 2023 (UTC)<br />
<br />
=== Support ===<br />
# Per above. [[File:Windows_logo_(2006).svg|35px]] [[User:763004|'''763004''']] ([[User talk:763004|Talk]] &bull; [[User:763004/Sandbox|Sandbox]]) 13:25, 20 December 2023 (UTC)<br />
<br />
=== Oppose ===</div>Ovctvcthttps://betawiki.net/index.php?title=BetaWiki:Community_portal&diff=311887BetaWiki:Community portal2023-12-26T09:49:29Z<p>Ovctvct: Reverted edits by 92.38.148.60 (talk) to last revision by AlfCraft07</p>
<hr />
<div>__NEWSECTIONLINK__<br />
{{fmbox|type=system|image=none|text=<center><br />
<span style="font-size: 150%;">Welcome to BetaWiki community portal!</span><br />
<br />
This is where we discuss the operations of BetaWiki. Please help us to set down policies and guidelines, improve articles and more.<br />
<br />
If you want to request a specific administration action to be done, please use the [[BetaWiki:administrators' noticeboard|administrators' noticeboard]] instead.<br />
<br />
To add discussion, please add a new heading under this line.<br />
</center><br />
<br />
}}<br />
{{archives}}<br />
{{TOC|clear=left|limit=2}}<br />
<br />
== adding language parameter to the infobox windows build ==<br />
<br />
it will become easier to know the languages. [[Special:Contributions/51.15.78.38|51.15.78.38]] 10:38, 24 June 2023 (UTC)<br />
<br />
=== Support ===<br />
#per myself. [[Special:Contributions/51.15.78.38|51.15.78.38]] 10:38, 24 June 2023 (UTC)<br />
#I support this. Same feature is available for TheCollectionBook. But I doubt it's going to be accepted. This was requested a few times, and it was ignored. {{Unsigned|94.121.82.195}}<br />
#I support this, but only for releases preceding the introduction of the [[w:Multilingual_User_Interface|Multilingual User Interface (MUI)]] in Windows 2000. [[User:Ahernandez094|Ahernandez094]]<br />
=== Oppose ===<br />
#Unnecessary - Most internal beta builds are only available in a single language and if other languages are available, they ''will'' be mentioned on the respective build page. Public beta builds are available in basically every single language supported by Microsoft, so mentioning available languages on the respective build page is also unnecessary. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 12:12, 24 June 2023 (UTC)<br />
#:Also, most non-English builds of Windows, especially before Windows 8, are only official Beta/CTP/Preview/RTM builds and not internal ones. - <code>[[File:Windows logo (2003).svg|18px]] [[User:Bob2204|Bob2204]]</code> [[File:Arrow.png|15px]] Click here to begin. Or here. [[File:Arrow2.png|15px]] <code>[[User talk:Bob2204|Talk]]</code> - 16:18, 24 June 2023 (UTC)<br />
#::This https://betawiki.net/wiki/Windows_10_build_18327.1, it's not an official build. However it's available for many languages. {{Unsigned|94.121.82.195}}<br />
#::Do you seriously think that everyone who visit this wiki like reading long paragraphs? {{Unsigned|94.121.82.195}}<br />
#:::Read again. I only have said "most, '''especially before Windows 8'''". The Technical/Insider Preview thing changed many things, as they no longer release Preview/Beta/Alpha builds, but only multiple "Insider Previews", which can reach up to around 30 Insider Previews per version before a new version becomes released. - <code>[[File:Windows logo (2003).svg|18px]] [[User:Bob2204|Bob2204]]</code> [[File:Arrow.png|15px]] Click here to begin. Or here. [[File:Arrow2.png|15px]] <code>[[User talk:Bob2204|Talk]]</code> - 14:38, 25 June 2023 (UTC)<br />
#::::Understood. {{Unsigned|94.121.82.195}}<br />
#That's not how it works. Every build is compiled in all of the 23 base languages and all available SKUs. I oppose this simply because it would clutter the infobox, especially on Insider previews because they are indeed released in those base languages. --[[Special:Contributions/217.131.99.140|217.131.99.140]] 07:44, 29 June 2023 (UTC)<br />
#:Not '''every ''' is compiled in '''all''' languages. Some builds are only compiled for specific languages. Also what will you say about unleaked, shared or betas before Windows 7? {{Unsigned|94.120.197.130}}<br />
#::Simple: We never know what Microsoft did to their builds and if they're compiled in all languages or not. New languages were gradually added over time, so we need to remind ourselves of the past. Also, don't use {{tl|Unsigned}} to sign your comments, use <nowiki>~~~~</nowiki>. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 14:21, 4 July 2023 (UTC)<br />
#:::It's already impossible to know which languages are available in builds. But he said '''Every build is compiled in all of the 23 base languages''', which is definitely false. Otherwise we would have the builds 4074 in German or 5048 in French. The list goes on. [[User:94.120.197.130|94.120.197.130]] ([[User talk:94.120.197.130|talk]]) 14:29, 4 July 2023 (UTC)<br />
# Putting information to the infobox is a double-edged sword, it might make the information more discoverable but it also makes it more cluttered that it needs to be. Not to mention the relationship between SKUs, architectures and languages, since builds rarely are available in all listed combinations. A better approach would be a table like done for [[Windows 11 build 22000.1]]. --{{User:Ryuzaki/Signature}} 07:39, 29 June 2023 (UTC)<br />
#: Like in 2296.1 page? {{Unsigned|94.120.197.130}}<br />
<br />
== Changing recommended resolution images to 1,920 × 1,080 ==<br />
<br />
Literally every single build of Windows 11 use it for some reason, so I guess why not do it on other builds. [[Special:Contributions/37.120.213.238|37.120.213.238]] 11:36, 2 July 2023 (UTC)<br />
: I guess 1366 x 768 or 1400 x 900 would be better. 1920 x 1080 is too large. {{User:Someone200/Signature|23:36, 3 July 2023 (UTC)}}<br />
: The guidelines don't actually recommend a single resolution, they only say it should be period appropriate but ''at least'' 1024x768, unless the OS doesn't support that resolution. {{Unsigned|Ryuzaki}}<br />
<br />
==== Support ====<br />
#[[Special:Contributions/37.120.213.238|37.120.213.238]] 11:36, 2 July 2023 (UTC)<br />
<br />
==== Oppose ====<br />
#Most old hardware and older versions of Windows do not support such a ridiculously high resolution. Due to DPI scaling being a hit-or-miss on older OSes, the contents of the screenshots will also be too small, requiring the reader to click on the image to better view the screenshot. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 11:40, 2 July 2023 (UTC)<br />
#:Then why do Windows 11 builds do it then? I only requested this all because of Windows 11 images. [[Special:Contributions/37.120.213.238|37.120.213.238]] 11:43, 2 July 2023 (UTC)<br />
#::Newer versions of Windows are better suited for high-resolution displays, also blame the uploader for using that resolution. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 11:46, 2 July 2023 (UTC)<br />
#:::OH okay. Anyways, does 1,366 × 768 count as a "ridiculously" higher resolution? This is the alternative to 1,920 × 1,080, I guess. [[Special:Contributions/37.120.213.238|37.120.213.238]] 11:52, 2 July 2023 (UTC)<br />
#::::I don't think it counts, since it's basically 1024 × 768, but wider. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 12:18, 2 July 2023 (UTC)<br />
#:::I think we should only use 1920x1080 for win10 and win11 builds, and the problem is that there are a lot of Windows 10 builds that currently use 1024x768, which for Windows 10's time period is rather low. - [[User:Upseguest|Upseguest]] ([[User talk:Upseguest|talk]])<br />
<br />
==winmain in 2009/2010==<br />
There is a very odd thing I found out about winmain in the time period between builds 7232 (Win7) and 7700 (Win8). While 7232 already features the final Harmony wallpaper, 7700 oddly reused the betta fish one. The 7700 page said that it can be implied that this build was formed from a Win7 RC build. I really doubt this, because it's also possible that they just reverted this wallpaper thing for Win8/future winmain development. (At least the betta fish was used until Microsoft started the Technical Preview/Insider Program.) - <code>[[File:Windows logo (2003).svg|18px]] [[User:Bob2204|Bob2204]]</code> [[File:Arrow.png|15px]] Click here to begin. Or here. [[File:Arrow2.png|15px]] <code>[[User talk:Bob2204|Talk]]</code> - 23:29, 3 July 2023 (UTC)<br />
<br />
== Page Previews ==<br />
<br />
This wiki needs page previews feature. <small> —— This newly signed comment was added by [[File:Windows logo (2012).svg|15px]] [[User:LazytownSpo4015|<span class="signature-lazytownspo4015-userpage">'''<big>Lazytown Sportacus (LazytownSpo4015)</big>'''</span>]] • [[User talk:LazytownSpo4015|<span class="signature-lazytownspo4015-talk">Talk page]] • {{#if: | <nowiki>|</nowiki> '''{{{1}}}''' | }}</small> 14:03, 4 July 2023 (UTC)<br />
<br />
=== Support ===<br />
#Per myself. <small> —— This newly signed comment was added by [[File:Windows logo (2012).svg|15px]] [[User:LazytownSpo4015|<span class="signature-lazytownspo4015-userpage">'''<big>Lazytown Sportacus (LazytownSpo4015)</big>'''</span>]] • [[User talk:LazytownSpo4015|<span class="signature-lazytownspo4015-talk">Talk page]] • {{#if: | <nowiki>|</nowiki> '''{{{1}}}''' | }}</small> 14:03, 4 July 2023 (UTC)<br />
#I was so used to this exact feature on Wikipedia and it allows you to view pages without actually navigating to the specific page. When I first joined this wiki, I actually wondered why page previews aren't supported. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 14:12, 4 July 2023 (UTC)<br />
#This is a really convenient feature. I also wonder why they haven't been implemented yet. [[User:BetaReporter|BetaReporter]] ([[User talk:BetaReporter|talk]]) 17:27, 4 July 2023 (UTC)<br />
<br />
=== Oppose ===<br />
#You could use Visual Editor instead [[User:PikaaxYT|PikaaxYT]] ([[User talk:PikaaxYT|talk]]) 12:04, 22 October 2023 (UTC)<br />
<br />
== Move Insider Preview update pages to their respective build pages ==<br />
This is [https://betawiki.net/wiki/BetaWiki:Community_portal/Archive_9#Move_Insider_service_pipeline_updates_to_their_respective_build_pages. a (probably abandoned) proposal] made by [[Special:Contributions/Xeno|Xeno]]. I reopened this because the final decision hasn't been made, and I feel like the servicing pipelines updates are cluttering up the pages.<br />
<br />
If this reach 15+ support, I'll do it. It will take a long time though. (as always, please consider providing a reason if support/oppose as it helps me understand your opinion.)<br />
<br />
{{User:Someone200/Signature|14:23, 3 August 2023 (UTC)}}<br />
<br />
:The consensus was to carry that out, not sure why this needs another vote. --{{User:Ryuzaki/Signature}} 14:33, 3 August 2023 (UTC)<br />
<br />
== Purge <s>all</s> non-Windows related content (reopen) ==<br />
This is a reopen of [https://betawiki.net/wiki/BetaWiki:Community_portal/Archive_11#Purge_all_non-Windows_related_content my version] of [https://betawiki.net/wiki/BetaWiki:Community_portal/Archive_6#Purge_all_non-Windows_related_content a proposal by orbitron] that was abandoned, because apparently the aforementioned proposals aren't being passed through.<br />
<br />
Basically, most non-Windows stuff on the wiki, except macOS, iOS, DOS, and OS/2, gets literally no activity besides one or two users. Most pages covering Linux are too short and hardly contain any notable information (and no, bugs don't count as notable). The new features and changes present in each distro version are also not covered properly and the pages only contain the image of the desktop or the home screen, which is not enough for a good article.<br />
<br />
While the original proposal focused on all non-Windows content, I wanted to only focus on free-and-open-source OSes (such as Linux, BSD, and Haiku), Android, non-preinstalled web browsers (such as Google Chrome, Mozilla Firefox, Opera, and Netscape) and other less important OSes. For free-and-open source OSes and Android, they have been moved to [https://distro.wikitide.com/ a dedicated wiki that focused on these OSes.] For non-preinstalled web browsers, there are already Wikipedia pages for these browsers. I hope this makes BetaWiki a much cleaner site and live up to its name. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 14:40, 3 August 2023 (UTC)<br />
:The proposal was archived because it was dead with no clear consensus. Not sure what makes you think reopening it immediately after it got archived will reach a different result. --{{User:Ryuzaki/Signature}} 16:48, 3 August 2023 (UTC)<br />
::OK, I understand. I did not know that proposals would be archived if it was dead with no clear consensus. I first thought reopening my proposal would bring up attention to the two proposals I mentioned above, so I'm sorry for the mistake I made. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 23:11, 3 August 2023 (UTC)<br />
<br />
== Moving all GitHub issue related builds to a separate page ==<br />
<br />
I think that most of the Windows 10/11 pages are being cluttered with GitHub issue pages. Since these builds doesn't have a proper buildtag (only build number), I think they should be moved to a separate instead of being purged. Some of them could cause confusions because its build number is identical to another one.<br />
{{User:Someone200/Signature|03:15, 6 August 2023 (UTC)}}<br />
<br />
=== Support ===<br />
# Per myself. {{User:Someone200/Signature|03:15, 6 August 2023 (UTC)}}<br />
# Welp, this should also be done for servicing pipeline update builds. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 03:21, 6 August 2023 (UTC)<br />
# We should also do that for builds mentionned in SSUComp_KB*******.xml and Desktop_neutral_Forward_*****.****.***************.******-****.CompDB.xml files [[User:PikaaxYT|PikaaxYT]] ([[User talk:PikaaxYT|talk]]) 10:27, 11 August 2023 (UTC)<br />
<br />
=== Oppose ===<br />
<br />
== Adding downloads of the builds in their infoboxes (CLOSED) ==<br />
<br />
<s>Or at least adding an information on where to download the builds <small>—&nbsp;Preceding unsigned comment added by [[User:PikaaxYT|PikaaxYT]] ([[User talk:PikaaxYT|talk]] • [[Special:Contributions/PikaaxYT|contribs]]) </small></s><br />
<br />
I closed the request because download links would violate the guidelines {{unsigned|PikaaxYT}}<br />
<br />
=== Support ===<br />
<br />
1. [[User:PikaaxYT|PikaaxYT]]<br />
<br />
=== Oppose ===<br />
<br />
# See [[BW:Guidelines#Legal|BW:Guidelines § Legal]]. [[User:Jurta|Jurta]] ([[User talk:Jurta|talk]] • [[Special:Contributions/Jurta|contribs]]) 19:52, 10 August 2023 (UTC)<br />
# We are most certainly '''NOT''' providing download links to these builds on the wiki. The wiki is intended to be a knowledge base for these builds. Find the builds yourself. The Windows build FAQ page points out that archive.org and WinWorld are good starting points to find most builds. Although, be careful as there are fake builds out there. It is very easy to find these builds anyways. <code>[[File:Windows Orb logo (2006).png|18px]] [[User:WindowsGuy2021|WindowsGuy2021]]</code> 2:59, 10 August 2023 (UTC)<br />
<br />
== Purge Linux and Android content ==<br />
here we go again...<br />
<br />
Most Linux distributions in BetaWiki are not notable, and by "not notable" I mean most of the articles talking about a Linux distro are too short, low quality, and hardly contain any useful or notable information. The Android articles are a good example of this, since they are made of an infobox, a lead sentence, a list of changes (or builds), and that's it. The information necessary for a knowledge base, such as the development history, features, and the overall aspects of a Linux distro, is also missing from the aforementioned articles. Other websites did a much better job at documenting these distros since they are not Windows-centric, unlike BetaWiki. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 09:10, 22 August 2023 (UTC)<br />
:I agree for purging Linux articles but not for purging Android articles because if they are deleted we should also purge iOS articles since most builds doesn’t even have an article and the few builds that have an article only have an infobox and a smaller sentence than Android articles [[User:PikaaxYT|PikaaxYT]] ([[User talk:PikaaxYT|talk]]) 12:03, 22 October 2023 (UTC)<br />
::now that DistroWiki got closed, following with the stepdown of Nara and GT610, I think that never ending purging discussion finally reached a dead end, at least for now. <br />
::Yes, there are still better wikis and pages for operating systems other than windows, but that discussion didn't really help us to make steps forward. At the end, the consequence was another wiki for just that reason, which failed to gain any reputation in their scene like betawiki does and thus failing overall. No one came out from there as winner. <br />
<br />
::The best thing that we can do for now is just continuing our work here. - <code>[[File:Windows logo (2003).svg|18px]] [[User:Bob2204|Bob2204]]</code> [[File:Arrow.png|15px]] Click here to begin. Or here. [[File:Arrow2.png|15px]] <code>[[User talk:Bob2204|Talk]]</code> - 23:00, 30 November 2023 (UTC)<br />
:::Nara here. Yes, BetaWiki should've stayed the same and the DistroWiki effort, in my opinion, was just a waste of time. Despite having 99% of its focus on Windows, there are still people who do Linux stuff here and we should respect them. I'll say the discussion is finally over, like you said. [[Special:Contributions/139.192.153.112|139.192.153.112]] 03:53, 2 December 2023 (UTC)<br />
<br />
== discord server invite link ==<br />
<br />
i'm trying to rejoin the BW discord, but it says the link is expired. Has the server been deleted or is it a dead invite? {{Unsigned|Grafality}}<br />
:It's a dead invite. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 05:33, 16 September 2023 (UTC)<br />
::if it is a dead invite, then why wouldn't I rejoin BW Discord server? Also I'm sorry for my past actions while I'm in the server. <small> —— This newly signed comment was added by [[File:Windows logo (2012).svg|15px]] [[User:LazytownSpo4015|<span class="signature-lazytownspo4015-userpage">'''<big>Lazytown Sportacus (LazytownSpo4015)</big>'''</span>]] • [[User talk:LazytownSpo4015|<span class="signature-lazytownspo4015-talk">Talk page]] • {{#if: | <nowiki>|</nowiki> '''{{{1}}}''' | }}</small> 08:57, 16 September 2023 (UTC)<br />
:::I hate to tell you this, but you have been banned from the BW Discord server. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 08:59, 16 September 2023 (UTC)<br />
::::I know but, I'm very sorry for my past actions when i was there. How am i going to appeal a ban from the BW discord server? <small> —— This newly signed comment was added by [[File:Windows logo (2012).svg|15px]] [[User:LazytownSpo4015|<span class="signature-lazytownspo4015-userpage">'''<big>Lazytown Sportacus (LazytownSpo4015)</big>'''</span>]] • [[User talk:LazytownSpo4015|<span class="signature-lazytownspo4015-talk">Talk page]] • {{#if: | <nowiki>|</nowiki> '''{{{1}}}''' | }}</small> 09:13, 11 October 2023 (UTC)<br />
:::"if it is a dead invite, then why wouldn't I rejoin BW Discord server?" Precisely because it was a dead invite? It is fixed now though. --{{User:Ryuzaki/Signature}} 09:46, 16 September 2023 (UTC)<br />
<br />
== 8297.0.fbl_fun_embedded_xos.120311-1700 ==<br />
<br />
Please make a page for Xbox One OS build 8297. It's availible, so it should be possible. I'm not experienced enough to get the OS and run it in some sort of emulator. {{Unsigned|146.212.161.185}}<br />
:You literally put the same thing in here and in [[Talk:Main Page]]. [[File:Windows_logo_(2006).svg|35px]] [[User:763004|'''763004''']] ([[User talk:763004|Talk]] &bull; [[User:763004/Sandbox|Sandbox]]) 17:27, 10 October 2023 (UTC)<br />
<br />
== Cleaning up Bugs and quirks section ==<br />
<br />
After some deep review about a few additions within these sections lately, it's been seen that we're getting a lot of hardware/VM-only related problems that seems to be extremely niche to encounter, and in several cases, results from using a config that is way above what was the norm/available at the time. Most of these bugs tend to be of sensitive/setup-specific, and often are just encountered by one user due to a bad config.<br />
<br />
As a result of this, I'm going to start suggesting that any compatibility bugs are heavily stripped down, since adding these bugs aren't necessarily of "meaningful" edits and ends up being more disruptive for the flow of the page. This would mean that the following changes will be made, with some examples of what we don't want:<br />
* Any bugs that mention [https://betawiki.net/index.php?title=Windows_Longhorn_build_4002_%28Lab06_N%29&type=revision&diff=307656&oldid=303257 "this build won't install in modern versions of <program>"] will no longer be allowed and will be removed. This is a setup-specific problem, and also this wiki is not a compatibility checklist.<br />
* Any bugs that mention [https://betawiki.net/index.php?title=Windows_NT_4.0_build_1130&type=revision&diff=261298&oldid=260828 "this driver doesn't work"] will also no longer be allowed and will be removed. Generally a setup-specific problem or incomplete driver support; again betas aren't meant to be complete.<br />
* A lot of [https://betawiki.net/index.php?title=Windows_XP_build_2202&type=revision&diff=308836&oldid=303304 VM compatibility bugs] will be stripped down. I'd prefer they'd be removed completely, but that's not necessarily going to be favorable for certain builds that need an abnormally early compatibility. But then again, it's preferable to use the version that was closest to when that build was compiled. For reference, VMware 5.0 released around 2005, while VMware 6.0 released around 2007. So it would not make sense to install say build 5231 on modern versions, and vise versa. This is also largely a setup-related problem, usually.<br />
<br />
Most of the bugs that are intended to be removed will usually be of that hardware related, unless they are a widespread problem and often well-known by Microsoft in documentation, such as the Windows NT 3.x processor setup bug. But for singular builds, these bugs would have to go, and don't contribute as a "meaningful" edit and more of a way to inflate the page with niche setups.<br />
<br />
Also to note adding "persists until build" isn't necessarily a meaningful edit, as well. We do not need to document every little bug you see, as again beta builds are often unstable and prone to bugs and inconveniences. Bugs are to only be documented usually when they often affect real hardware too and is major enough that it often impacts the usability of the build even in the most general scenario. Subsequently reverting/adding these oft-unnecessary bugs is means of disruptive editing, and warnings will be handed out.<br />
<br />
[[User:BF10|BF10]] ([[User talk:BF10|talk]]) 13:35, 4 December 2023 (UTC)<br />
:We also have to remove "this build has some stabillity issues" edits, because these are '''beta builds''', '''''of course '''''theyre gonna be unstable. [[Special:Contributions/37.231.130.49|37.231.130.49]] 21:52, 4 December 2023 (UTC)<br />
: Just a question, does 3rd party app compatibility bugs notable? {{User:Someone200/Signature|14:19, 6 December 2023 (UTC)}}<br />
::no. Pre-release builds aren't designed at first place to run third-party apps, maybe at most those ones from the era of the specific build. For example, imagine you were one of the testers of Vista Beta 2 or RC in 2006, you would've likely tested out how the ''back then'' latest versions of Firefox, 1.5 or 2.0, would perform. The builds weren't designed to run way newer versions like 38. Still, bugs and quirks with 3rd-party apps wouldn't really that useful for that wiki, per bf10. - <code>[[File:Windows logo (2003).svg|18px]] [[User:Bob2204|Bob2204]]</code> [[File:Arrow.png|15px]] Click here to begin. Or here. [[File:Arrow2.png|15px]] <code>[[User talk:Bob2204|Talk]]</code> - 14:31, 6 December 2023 (UTC)<br />
<br />
== Creating new user warning templates ==<br />
<br />
I think there should be more user warning templates, since there is only one set of user warning templates. Who agrees with me? [[File:Windows_logo_(2006).svg|35px]] [[User:763004|'''763004''']] ([[User talk:763004|Talk]] &bull; [[User:763004/Sandbox|Sandbox]]) 13:25, 20 December 2023 (UTC)<br />
:Well then create them. No need to bother with voting... --{{User:Ryuzaki/Signature}} 13:29, 20 December 2023 (UTC)<br />
::Alrighty then. <small>(I'll test these in the sandbox first, or on [[Template:Test]])</small> [[File:Windows_logo_(2006).svg|35px]] [[User:763004|'''763004''']] ([[User talk:763004|Talk]] &bull; [[User:763004/Sandbox|Sandbox]]) 13:32, 20 December 2023 (UTC)<br />
<br />
=== Support ===<br />
# Per above. [[File:Windows_logo_(2006).svg|35px]] [[User:763004|'''763004''']] ([[User talk:763004|Talk]] &bull; [[User:763004/Sandbox|Sandbox]]) 13:25, 20 December 2023 (UTC)<br />
<br />
=== Oppose ===</div>Ovctvcthttps://betawiki.net/index.php?title=Template:Archives/styles.css&diff=311885Template:Archives/styles.css2023-12-26T09:48:11Z<p>Ovctvct: Protected "Template:Archives/styles.css" ([Edit=Require extended confirmed access] (indefinite) [Move=Require extended confirmed access] (indefinite))</p>
<hr />
<div>.archive-list .mbox-text {<br />
text-align: center;<br />
}<br />
<br />
.archive-list ul {<br />
margin: 0;<br />
}<br />
<br />
.archive-list li {<br />
display: inline;<br />
}<br />
<br />
.archive-list li + li::before {<br />
content: "\2022";<br />
}</div>Ovctvcthttps://betawiki.net/index.php?title=Template:Archive&diff=311884Template:Archive2023-12-26T09:47:54Z<p>Ovctvct: Protected "Template:Archive" ([Edit=Allow only autoconfirmed users] (indefinite) [Move=Allow only autoconfirmed users] (indefinite))</p>
<hr />
<div><onlyinclude>{{mbox|image=[[File:org.gnome.Nautilus.svg|40px]]|text=This page is an '''archive'''. If you wish to start a new discussion or revive an old one, please do so on the current [[{{#titleparts:{{FULLPAGENAME}}|-1}}|discussion page]].}} __NOEDITSECTION__ __NONEWSECTIONLINK__</onlyinclude></div>Ovctvcthttps://betawiki.net/index.php?title=Template:Android&diff=311883Template:Android2023-12-26T09:47:35Z<p>Ovctvct: Protected "Template:Android" ([Edit=Allow only autoconfirmed users] (indefinite) [Move=Allow only autoconfirmed users] (indefinite))</p>
<hr />
<div>{{Navbox<br />
|name = Android<br />
|title = [[Android]]<br />
|bodyclass = hlist<br />
|state = {{{state|}}}<br />
|image = [[File:Android OS logo.png|50px]]<br />
|list1 =<br />
* [[Android 1.x]]<br />
* [[Android 2.x]]<br />
* [[Android 3.x]]<br />
* [[Android 4.x]]<br />
* [[Android 5.x]]<br />
* [[Android 6.x]]<br />
* [[Android 7.x]]<br />
* [[Android 8.x]]<br />
* [[Android 9]]<br />
* [[Android 10]]<br />
* [[Android 11]]<br />
* [[Android 12]]<br />
** [[Android 12L|12L]]<br />
* [[Android 13]]<br />
* [[Android 14]]<br />
}}</div>Ovctvcthttps://betawiki.net/index.php?title=Template:Afd_close&diff=311882Template:Afd close2023-12-26T09:47:06Z<p>Ovctvct: Protected "Template:Afd close" ([Edit=Allow only autoconfirmed users] (indefinite) [Move=Allow only autoconfirmed users] (indefinite))</p>
<hr />
<div><onlyinclude><br />
<templatestyles src="Xfd/styles.css"/><br />
<div class="afd vfd xfd-closed"><br />
<span class="xfd-headline">Closed "Article for deletion" discussion</span><br />
----<br />
</onlyinclude></div>Ovctvcthttps://betawiki.net/index.php?title=Template:Did_you_know/Facts&diff=311881Template:Did you know/Facts2023-12-26T09:05:42Z<p>Ovctvct: Protected "Template:Did you know/Facts": High traffic page ([Edit=Allow only autoconfirmed users] (indefinite) [Move=Allow only autoconfirmed users] (indefinite))</p>
<hr />
<div>* ...that '''[[Windows XP]]''' has been supported in [[Windows Embedded 2009|various forms]] for almost 18 years, which is the longest compared to any other version of [[Microsoft Windows]]?<br />
* ...that the '''[[Windows Server 2003 build 2462 (main.010315-1720)|IA-64 compile of Windows Server 2003 build 2462]]''' includes login banners for a Personal edition of Windows 2000?<br />
* ...that in 1985, Microsoft produced a '''[[multitasking MS-DOS 4|multitasking MS-DOS]]''' that natively supported preemptive multitasking and would later become the base for [[OS/2]]?<br />
* ...that the [[Windows XP]] team created a [[Watercolor|decoy theme]] in order to prevent any leaks about [[Luna]]?<br />
* ...that the '''[[Neptune]]''' project was a cancelled version of Windows that ought to bring a new user interface reminiscent of the Metro elements later introduced in [[Windows 8]]?<br />
* ...that an updated version of '''[[Reversi]]''' (normally not preinstalled) is included in the [[Windows 3.1x|Windows 3.1]] Driver Library?<br />
* ...that while the first shipping 64-bit version of [[Microsoft Windows]] was for the [[w:Itanium|Itanium]], the 64-bit port was actually developed on '''[[w:DEC Alpha|DEC Alpha]]''' systems?<br />
* ...that the Gizmo theme that was present in '''[[Mac OS 8.5b6]]''' originates from [[Copland]] as "Z Theme" and was intended for testing the theming service for both versions?<br />
* ...that there were multiple '''[[Shell Technology Preview]]s''' that backported the [[Windows Explorer]] to a stock installation of [[Windows NT 3.5x]]?<br />
* ...that [[wikipedia:September 11 attacks|terrorism]] caused a major sudden change to '''[[Windows XP]]'''<nowiki>'</nowiki>s advertising campaign?<br />
* ...that versions of '''[[Microsoft Windows]]''' for [[w:DEC Alpha|DEC Alpha]] and [[w:ARMv7|ARMv7]] platforms continued to be maintained internally even after official end of support, as the systems proved valuable for specific projects?<br />
* ...that the [[w:Federal government of the United States|United States government]] once [[w:United States v. Microsoft Corp.|filed an antitrust lawsuit against Microsoft]] over its decision to bundle the '''[[Internet Explorer]]''' web browser with the [[Windows]] operating system?<br />
* ...that '''[[Windows Vista build 5000 (vbl_core.040803-2000)]]''' was compiled earlier than the [[Windows Vista build 3790.1232|official development reset build]]?<br />
* ...that there was an '''E''' variant planned for '''[[Windows 7]]''' in addition to K, N and KN, which didn't include [[Internet Explorer]]?<br />
* ...that the Start button in '''[[Windows 95 build 302]]''' says "Ship It!", as a developer temporarily renamed the button in December 1994 for a joke?<br />
* ...that [[Paint]] was once on the second disk of '''[[Windows 1.0 Alpha Release]]''' but later deleted by either Microsoft or the owner for unknown reasons?<br />
* ...that the special actors in '''[[Microsoft Bob]]''' generally still have existing code that allows them to be used as normal actors outside of their apps?<br />
* ...that '''[[Windows XP build 2223 (main)|Windows XP build 2223]]''' had commented out code in its Business theme file that would allow the user to configure different colors based on its settings?<br />
* ...that Apple has officially released [[Apple Rhapsody Developer Release 1|several]] [[Apple Rhapsody Developer Release 2|developer]] releases of what would later become '''[[macOS|Mac OS X]]''' for the x86 architecture as a part of its NeXT legacy, and secretly continued to maintain the port until [[Mac OS X Tiger|Tiger]]?<br />
* ...that '''[[Windows NT 3.5 build 612]]''' has a debug flag for <code>winnt.exe</code>, <code>/I_am_TedM</code>, in order to bypass the error to run the DOS-based setup in NTVDM?<br />
* ...that some builds of '''[[Windows 98]]''' and '''[[Windows 2000]]''' contained a Show Desktop button on the taskbar, which would be scrapped later until [[Windows 7 build 6568]]?<br />
* ...that the supposed '''[[Windows Vista|Longhorn]]''' sound scheme in fact wasn't included in any Windows build and actually originated from a Samsung OEM theme for [[Windows XP]]?<br />
* ...that '''[[Windows 1.0]] and [[Windows 2.x]]''' have a hidden easter egg with a list of members of the Windows team?<br />
* ...that '''[[Windows Server 2003]]''' has been renamed four times during development, before settling on its final name?<br />
* ...that the boot animation used in [[Windows 11 2022 Update]] builds first appeared in '''[[Windows 10X]]''' and '''[[Windows 10 build 19587]]'''?<br />
* ...that '''[[Windows Longhorn build 4088]]''' includes an early version of the .NET Managed rewrite of [[Desktop Window Manager]] that is not installed by default?<br />
* ...that '''[[Windows 98 build 1387]]''' has a hidden button in display properties to enable title bar gradients, and is also the first build of Windows to support this feature?<br />
* ...that the WarpCenter shell included in '''[[OS/2 Warp 4 build 9.012]]''' refers itself to as Lotus SmartCenter?<br />
* ...that early builds of '''[[Windows Me]]''' replaced the safe to shutdown screen with a [[Blue screen of death|blue screen]] due to the removal of real-mode [[MS-DOS]]?<br />
* ...that every Classic Mac OS version since '''[[Mac OS 7]]''' renames the "Special" menu to a unique word beginning with S in beta builds for easy identification of such?<br />
* ...that '''[[Windows 95 build 58s]]''' includes a hidden tabbed mode in the [[File Explorer|Cabinet]]?<br />
* ...that '''[[Windows Longhorn build 4015 (main)]]''' includes an early iteration of transparent window borders?<br />
* ...that '''[[Windows NT 4.0 Terminal Server Edition]]''' is the only released version of Windows to use the login screen originating from [[Windows 2000#Beta 2|beta 2 builds]] of [[Windows 2000]]?<br />
* ...that '''[[Windows XP build 2257]]''' supports the ability to render the newly animated boot screen used in later builds?<br />
* ...that [[Reversi]] in the '''[[Windows NT 3.1 April 1991 build]]''' displays square pieces, because the code for drawing circles wasn't implemented yet?<br />
<noinclude>[[Category:Templates]]</noinclude></div>Ovctvcthttps://betawiki.net/index.php?title=Windows_3.0_with_Multimedia_Extensions_1.0&diff=310114Windows 3.0 with Multimedia Extensions 1.02023-12-11T18:31:28Z<p>Ovctvct: /* Gallery */</p>
<hr />
<div>{{Infobox Windows build<br />
|build of = [[Windows 3.0]]<br />
|image = Windows30-MME-Desktop.png<br />
|buildtag = 3.0 with Multimedia Extensions 1.0<br />
|arch = x86, PC-98, Fujitsu FM-Towns<br />
|family = 16<br />
|version = 3.00a<br />
|winver = Windows30-MME-About.png<br />
|rivals = {{Rivals|TCB=https://www.thecollectionbook.info/builds/windows/build/672|TCBGallery=https://www.thecollectionbook.info/gallery/?f=/windows/16-bit%20kernel/windows%203.0/3.0a%20mme/english}}<br />
}}<br />
<br />
'''Windows 3.0 with Multimedia Extensions 1.0''' (also called ''Multimedia Windows'' by some sources) is a special, multimedia-centric release of [[Windows 3.0]], exclusively released on 20 October 1991 by various [[w:original equipment manufacturer|original equipment manufacturers]] (OEMs). Currently available releases include Tandy for the PC in English and German, an English release for the PC by Creative Labs, and Japanese releases for NEC PC-98 and Fujitsu FM-Towns.<br />
<br />
It is the first version of Windows to support sound output and includes new programs for audio and video playback, including the first version of [[Windows Media Player|Media Player]], new drivers for CD-ROM drives, sound cards, displays and joysticks and screensavers, as well an updated Control Panel. Most of these changes were later incorporated into [[Windows 3.1]]. Although the operating system supports running in real mode, the new changes are only available in the Standard and 386 Enhanced modes.<br />
<br />
== Information from computer magazines ==<br />
Another possible OEM release is shown and described in the November 1991 issue of Serbian computer magazine ''Svet Kompjutera'' ("World of Computers").<ref>[http://retrospec.sgn.net/users/tomcat/yu/magshow.php?auto=190&page=2 Multimedijalni Windows], ''Magazine Scans''. November 1991.</ref> The boot screen shown in the magazine is different from the one in Tandy's release, referring to itself as '''Version 3.0 + Multimedia Extensions 1.0''', whereas Tandy's release refers to itself as "'''graphical environment with Multimedia Extensions 1.0'''". The Tandy release uses both names during the installation process.<br />
<br />
It is unknown if the version shown in the magazine is from a different OEM (see below) or a pre-release, as the magazine also calls it a "Multimedia Development Kit" (MDK).<br />
<br />
== Information from antitrust documents ==<br />
An internal Microsoft document released during the Comes v. Microsoft antitrust hearings details the initial development plan for a "Multimedia Windows" release.<ref>Iowa District Court for Polk County. [http://antitrust.slated.org/www.iowaconsumercase.org/011607/7000/PX07531.pdf Plaintiff's Exhibit #7531], ''Comes v. Microsoft.''</ref> According to the document, the alpha release was shipped to 35 external testing groups on 15 June 1990, with 25-30 additional sites to receive it on 1 August 1990. The beta release was to be released in mid-October 1990 and the final OEM Adaptation Kit (OAK) in December 1990.<br />
<br />
Tandy is mentioned as the first OEM to launch their multimedia-capable PC-compatibles with Multimedia Windows. IBM, Fujitsu, Sharp, Olivetti, Zenith, Sony and Intel are listed as potential candidates for release. Microsoft Works for Windows with Multimedia extensions is mentioned as one of the apps to tie in with new features of Multimedia Windows.<br />
<br />
== New applications (Tandy OEM) ==<br />
=== Windows Help ===<br />
Windows Help in this release is version '''3.07'''. The About dialog also states "'''Version 3.1.061d'''", which is caused because <code>SHELL.DLL</code> from [[Windows 3.1 build 061d]] is included.<br />
<br />
=== Control Panel ===<br />
About dialog says "Control Panel for Windows graphical environment with Multimedia Extensions 1.0" and "Version 1.0".<br />
<br />
=== Auto Install ===<br />
A Tandy OEM application for installing other applications from removable media. Version 1.0.<br />
<br />
=== Welcome ===<br />
A fullscreen, run-once Tandy OEM application that says, "Tandy presents the world of multimedia".<br />
<br />
=== Multimedia Main Menu ===<br />
A Tandy OEM application for easy access to various multimedia demos, applications, and the Program Manager.<br />
<br />
=== Reset Tandy Demo ===<br />
A Tandy OEM application which resets the default shell back to FindCD.<br />
<br />
=== FindCD ===<br />
A Tandy OEM application that offers a tutorial and sound test. When finished, it first starts the Welcome application and then the Multimedia Main Menu.<br />
<br />
== New applications (Creative Labs OEM) ==<br />
The Creative Labs OEM notably includes utilities from the Sound Blaster driver kit, including the Sound Blaster Pro Mixer.<br />
<br />
== Problems and fixes ==<br />
=== Display drivers ===<br />
Certain newer graphics cards (like S3 ViRGE or Paradise) may not work as it could lead to display corruption upon loading the graphical interface.<br />
<br />
=== Startup fix ===<br />
Tandy has changed the default shell in their release to their application called FindCD (see above). This requires you to insert the installation CD, but the application often hangs at the start (possibly due to bad soundcard configuration) and you won't be able to get into Windows itself without changing the shell back to Program Manager in <code>SYSTEM.INI</code>.<br />
<br />
To do this you must open the file <code>SYSTEM.INI</code> in the installation directory, find the <code>[boot]</code> section and change the line <code>shell=findcd.exe</code> to <code>shell=progman.exe</code>. Windows will now start Program Manager on startup.<br />
<br />
This doesn't apply to the non-Tandy versions since they set the shell to <code>PROGMAN.EXE</code> by default.<br />
<br />
=== Virtual PC Enhanced Mode fix ===<br />
As this release is based on Windows 3.00a, it also requires a change to <code>SYSTEM.INI</code> if you wish to run it in 386 Enhanced Mode in Virtual PC 2004/2007.<ref>http://www.betaarchive.com/forum/viewtopic.php?f=39&t=29023</ref><br />
<br />
== Other ==<br />
Both Tandy and non-Tandy versions include special video drivers, including a [https://www.betaarchive.com/forum/viewtopic.php?f=59&t=36024 320×200×256 color driver], with special fonts, it works on any virtualization software that emulates a VGA card. It can also be used on later versions of Windows (up to [[Windows 95]]) by upgrading from this version.<br />
<br />
== File differences ==<br />
<div class="toccolours mw-collapsible mw-collapsed"><br />
The following files have been introduced or removed compared to [[Windows 3.00 MDK Version 59]]:<br />
<div class="mw-collapsible-content"><br />
{{:Document:Windows 3.0 with Multimedia Extensions 1.0 file differences}}<br />
</div></div><br />
<br />
== Gallery ==<br />
<gallery><br />
Win3mmesetup1.png|Starting setup<br />
Win3mmesetup2.png|Setup<br />
Win3mmesetup3.png|Directory confirmation<br />
Win3mmesetup4.png|Config confirmation<br />
Win3mmesetup5.png|Sound card port value selection<br />
Win3mmesetup6.png|Hardware interrupt value selection<br />
Win3mmesetup7.png|Hardware DMA channel selection<br />
Win3mmesetup8.png|Copying files<br />
Win3mmesetup9.png|Exiting TXT setup<br />
Win3mmesetup10.png|Starting GUI setup<br />
Win3mmesetup11.png|Setup<br />
Win3mmesetup12.png|Copying files<br />
Win3mmesetup13.png|Ditto<br />
Win3mmesetup14.png|Ditto<br />
Win3mmesetup16.png|Ditto<br />
Win3mmesetup17.png|Printers<br />
Win3mmesetup18.png|Set up applications<br />
Win3mmesetup19.png|Scanning<br />
Win3mmesetup20.png|Select applications<br />
Win3mmesetup21.png|Release notes<br />
Win3mmesetup22.png|Confirmation to modify <code>AUTOEXEC.BAT</code> and <code>CONFIG.SYS</code><br />
Win3mmesetup23.png|Notice about backups<br />
Win3mmesetup24.png|End of setup<br />
Win3mmelogo.png|Boot screen<br />
Win3mmefb.png|First boot<br />
3.0WithMME1.0 TandyOEMDialogue.png|Tandy OEM starting page<br />
Win3mmepm.png|Program Manager<br />
Win3mmeaee.png|Application Execution Error<br />
Win3mmecal.png|Calendar<br />
Win3mmecalc1.png|Calculator<br />
Win3mmecalc2.png|Calculator in Scientific mode<br />
Win3mmecard.png|Cardfile<br />
Win3mmecb.png|ChatterBox<br />
Win3mmeclip.png|Clipboard<br />
Win3mmeclock1.png|Clock starts minimized<br />
Win3mmeclock2.png|Clock in Digital theme<br />
Win3mmeclock3.png|Clock in Analog theme<br />
Win3mmecp1.png|Control Panel<br />
Win3mmecp2.png|Color<br />
Win3mmecp3.png|Printers<br />
Win3mmecp4.png|Fonts<br />
Win3mmecp5.png|International<br />
Win3mmecp6.png|Ports<br />
Win3mmecp7.png|Keyboard<br />
Win3mmecp8.png|Mouse<br />
Win3mmecp9.png|Date & Time<br />
Win3mmecp10.png|Desktop<br />
Win3mmecp11.png|386 Enhanced<br />
Win3mmecp12.png|Display<br />
Win3mmecp13.png|Installed drivers<br />
Win3mmecp14.png|Joystick warning<br />
Win3mmecp15.png|Joystick<br />
Win3mmecp16.png|MIDI Mapper warning<br />
Win3mmecp17.png|MIDI Mapper<br />
Win3mmecp18.png|Sound<br />
Win3mmecp19.png|Screen Saver<br />
Win3mmecp20.png|List of screensavers<br />
Win3mmecp21.png|Blackness screensaver<br />
Win3mmecp22.png|Lissajous Figures screensaver<br />
Win3mmecp23.png|Marquee screensaver<br />
Win3mmecp24.png|Melt / Slime Screen screensaver<br />
Win3mmecp25.png|Mystify screensaver<br />
Win3mmecp26.png|Starfield Simulation screensaver<br />
Win3mmefm.png|File Manager<br />
Win3mmejb.png|JukeBox<br />
Win3mmemb.png|Music Box<br />
WMP1About.PNG|About Media Player<br />
Win3mmenp.png|Notepad<br />
Win3mmepaintbrush.png|Paintbrush<br />
Win3mmepifeditor.png|PIF Editor<br />
Win3mmeprintm.png|Print Manager without a printer plugged in<br />
Win3mmer.png|Reversi<br />
Win3mmereadme.png|<code>README.TXT</code><br />
Win3mmerecorder.png|Recorder<br />
Win3mmesbpmc2.png|Device error<br />
Win3mmesbpmc1.png|Sound Blaster Pro Mixer Control<br />
Win3mmese.png|Cannot read from drive D: error<br />
Win3mmesol.png|Solitaire<br />
Win3mmesr.png|Sound Recorder<br />
Win3mmeterminal1.png|Select default serial port<br />
Win3mmeterminal2.png|COM1 isn't available error<br />
Win3mmeterminal3.png|Terminal<br />
Win3mmewrite.png|Write<br />
Win3mmews.png|Windows Setup<br />
Win3mmemulti.png|Multimedia demo<br />
Windows30-MME-Demo.png|Demo<br />
Mme16bpp.png|High color mode with color selector<br />
Win3 320x200.png|320×200 mode<br />
</gallery><br />
<br />
==References==<br />
{{reflist}}<br />
<br />
[[Category:Retail builds of Windows 3.0]]<br />
[[Category:Builds of Windows 3.0 with Multimedia Extensions]]</div>Ovctvcthttps://betawiki.net/index.php?title=File:Mme16bpp.png&diff=310113File:Mme16bpp.png2023-12-11T18:30:22Z<p>Ovctvct: Windows 3.0 MME in high color mode(86box)</p>
<hr />
<div>== Summary ==<br />
Windows 3.0 MME in high color mode(86box)</div>Ovctvcthttps://betawiki.net/index.php?title=Windows_7_build_6748&diff=299690Windows 7 build 67482023-10-20T09:24:18Z<p>Ovctvct: Protected "Windows 7 build 6748": Excessive vandalism ([Edit=Allow only autoconfirmed users] (indefinite) [Move=Require extended confirmed access] (indefinite))</p>
<hr />
<div>{{Infobox Windows build<br />
|build of = [[Windows 7]]<br />
|image = Windows7-6.1.6748-Desktop.png<br />
|buildtag = 6.1.6748.0.winmain.080710-2059<br />
|arch = x86, x64<br />
|sku = Starter<br/>Home Basic<br/>Home Basic N<br/>Home Premium<br>Business<br/>Business N<br/>Ultimate<br/><br />
|compiled = 2008-07-10<br />
|timebomb = 2008-10-04<br />
|winver = Windows7-6.1.6748-About.png<br />
|rivals = {{Rivals|TCBGallery=https://www.thecollectionbook.info/gallery/?f=/member%20contribution/unleaked%20screenshots%20collection/windows%207/6.1.6748}}<br />
}}<br />
<br />
'''Windows 7 build 6748''' is a Milestone 3 build of [[Windows 7]]. The Collection Book had shown only one screenshot of this build. It seems to reintroduce a feedback desktop shortcut as "Tell Microsoft About Your Experience", after it had been removed in [[Windows 7 build 6568|build 6568]]. The build itself has yet to be shared.<br />
<br />
==Gallery==<br />
<gallery><br />
Windows7-6.1.6748-TCB.jpg|Screenshot from The Collection Book<br />
</gallery><br />
<br />
[[Category:Windows 7 builds]]<br />
[[Category:Unleaked builds]]</div>Ovctvcthttps://betawiki.net/index.php?title=Windows_8.2&diff=298757Windows 8.22023-10-13T15:08:14Z<p>Ovctvct: Protected "Windows 8.2" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))</p>
<hr />
<div>#REDIRECT [[Windows 10 (original release)]]</div>Ovctvcthttps://betawiki.net/index.php?title=User_talk:Pivotman319&diff=284638User talk:Pivotman3192023-07-28T10:07:41Z<p>Ovctvct: Protected "User talk:Pivotman319": Excessive vandalism ([Edit=Allow only autoconfirmed users] (expires 10:07, 28 October 2023 (UTC)) [Move=Allow only administrators] (indefinite))</p>
<hr />
<div></div>Ovctvcthttps://betawiki.net/index.php?title=User_talk:Neil2212_l%C3%A0_k%C3%AAnh_tr%C3%AAn_m%E1%BB%99_truy%E1%BB%81n_1_ngh%C4%A9&diff=282828User talk:Neil2212 là kênh trên mộ truyền 1 nghĩ2023-07-18T05:30:37Z<p>Ovctvct: Reverted edits by Banned4414 (talk) to last revision by NitroGD</p>
<hr />
<div>==Talk==<br />
You have left talk messages in Vietnamese. Could you please talk in English instead? - <code>[[File:Windows logo (2003).svg|18px]] [[User:Bob2204|Bob2204]]</code> [[File:Arrow.png|15px]] Click here to begin. Or here. [[File:Arrow2.png|15px]] <code>[[User talk:Bob2204|Talk]]</code> - 04:39, 30 June 2023 (UTC)<br />
:This user is alt of User:Neil2212 [[Special:Contributions/37.231.126.71|37.231.126.71]] 04:41, 30 June 2023 (UTC)<br />
::Or an impersonator of him. - <code>[[File:Windows logo (2003).svg|18px]] [[User:Bob2204|Bob2204]]</code> [[File:Arrow.png|15px]] Click here to begin. Or here. [[File:Arrow2.png|15px]] <code>[[User talk:Bob2204|Talk]]</code> - 04:42, 30 June 2023 (UTC)<br />
::: As a Vietnamese, I can say that this guy is harassing Neil2212 or maybe this guy is swearing to himself? I can talk something to him in Vietnamese {{User:Someone200/Signature|05:15, 30 June 2023 (UTC)}}<br />
Nah he's most likely an alt of User:Neil2212 [[Special:Contributions/37.231.126.71|37.231.126.71]] 05:17, 30 June 2023 (UTC)<br />
I think they said gay [[Special:Contributions/37.231.126.71|37.231.126.71]] 04:43, 30 June 2023 (UTC)<br />
:I don't think they will listen to you because they've been vandalizing this wiki before. [[User:NaraInsider1694|NaraInsider1694]] ([[User talk:NaraInsider1694|talk]]) 04:42, 30 June 2023 (UTC)<br />
::Does this mean we have to call mr. pivot again? - <code>[[File:Windows logo (2003).svg|18px]] [[User:Bob2204|Bob2204]]</code> [[File:Arrow.png|15px]] Click here to begin. Or here. [[File:Arrow2.png|15px]] <code>[[User talk:Bob2204|Talk]]</code> - 04:44, 30 June 2023 (UTC)<br />
:::nope he’s been banned. [[User:NitroGD|NitroGD]] 05:36, 30 June 2023 (UTC)</div>Ovctvcthttps://betawiki.net/index.php?title=Draft:Metro&diff=279893Draft:Metro2023-07-02T09:24:58Z<p>Ovctvct: /* Gallery */</p>
<hr />
<div>{{Infobox design language<br />
| title = Metro<br />
| screenshot = Windows_8_Start_Screen.png<br />
| caption = Metro start screen in [[Windows 8]]<br />
| summary = Introduced a flatter user interface<br />
| included in = [[Windows 8]] - [[Windows 10]], artifacts found in [[Windows 11]]<br />
| first seen in = [[Windows 8 build 7777]] (libraries)<br>[[Windows 8 build 7779]] (UI)<br />
| replaces = [[Aero]]<br />
| replacedby = Fluent<br />
}}<br />
'''Metro''' is a design language primarily used in [[Windows 8]], [[Windows 8.1]] and [[Windows 10]]. It removes the skeuomorphic design used in [[Aero]] and replaces it with a much more flatter design. It was replaced by Fluent in 2017, although artifacts can still be found in [[Windows 11]].<br />
<br />
== Gallery ==<br />
<gallery><br />
File:7779MetroDownspace.png|Metro Downspace in [[Windows 8 build 7779]]<br />
File:Windows8-6.1.7850-RP.png|Start screen in [[Windows 8 build 7850]]<br />
File:7899_systemsettings.png|Settings in [[Windows 8 build 7899]]<br />
File:Windows-8.1-Update-Store.png|Microsoft Store in [[Windows 8.1]] Update<br />
File:Windows10-10.0.10240-Settings.png|Settings in [[Windows 10 (original release)]]<br />
</gallery><br />
<br />
[[Category:Introduced in Windows 8]]</div>Ovctvcthttps://betawiki.net/index.php?title=BetaWiki:Featured_article/2023-07&diff=278863BetaWiki:Featured article/2023-072023-06-26T13:42:58Z<p>Ovctvct: Protected "BetaWiki:Featured article/2023-07": High traffic page ([Edit=Require extended confirmed access] (indefinite) [Move=Require extended confirmed access] (indefinite))</p>
<hr />
<div>[[File:WindowsXPBuild2210Boot.png|thumb|200px|[[Windows XP build 2210]]]] '''[[Windows XP build 2210]]''' is an early build of [[Windows XP]]. It is the only available build of the 64-bit port of [[Windows NT]] to the [[w:DEC Alpha|DEC Alpha]], an internal project which aimed to prepare the operating system to run natively on a 64-bit architecture before the [[w:Itanium|Itanium]] processor design was finalized. It is distinct from prior DEC Alpha builds of [[Windows 2000]] and earlier, which used a 32-bit [[w:application binary interface|application binary interface]] on the otherwise 64-bit processor, comparable to Linux's [[w:x32 ABI|x32 ABI]] on AMD64 systems.<br />
<br />
It is overall the earliest known preserved build of 64-bit Windows, predating [[Windows Server 2003 build 2462 (main.010315-1720)|server build 2462]], the next available 64-bit build (although compiled for the Itanium and not the DEC Alpha), by a year.</div>Ovctvcthttps://betawiki.net/index.php?title=Windows_Longhorn_build_3683&diff=277695Windows Longhorn build 36832023-06-16T09:42:38Z<p>Ovctvct: Reverted edits by 2402:800:63A7:D9DC:9449:2558:68AE:8C7D (talk) to last revision by Explorerdotexe</p>
<hr />
<div>{{Infobox Windows build<br />
|build of = [[Windows Longhorn]]<br />
|image = 3683_1.png<br />
|buildtag = 6.0.3683.Lab06_N.020923-1821<br />
|arch = x86<br />
|sku = Professional<br>Media Center Edition<br />
|compiled = 2002-09-23<br />
|timebomb = 2003-09-18<br />
|key = CKY24-Q8QRH-X3KMR-C6BCY-T847Y<br />
|winver = LH3683_Winver.png<br />
|rivals = {{Rivals|TCB=http://www.thecollectionbook.info/builds/windows/build/514|TCBGallery=http://www.thecollectionbook.info/gallery/?f=/windows/nt%20kernel/windows%20vista/6.0.3683.0/english/professional/x86|BAWiki=https://www.betaarchive.com/wiki/index.php?title=Windows_Longhorn/6.0.3683.Lab06_N.020923-1821}}<br />
}}<br />
<br />
'''Windows Longhorn build 3683''' is a Milestone 3 build of [[Windows Vista|Windows Longhorn]]. It is currently the earliest available build of pre-reset Longhorn, which was originally leaked on 19 November 2002 by the beta group xBetas,<ref>https://web.archive.org/web/20021217200845/http://www.xbetas.com/modules.php?name=NukeNews&req=article&sid=735</ref> with their branding visible in the setup handle and in a modified wallpaper present within the install media (advertising for their now long-gone IRC channel).<br />
<br />
This build is one of the earliest to introduce the blue [[Plex]] theme, which would be used all the way up to Milestone 6. Builds from this timeframe are also notable in that the window captions are centered when the Plex theme is enabled, which is reminiscent of early Windows versions and which was also later used in [[Windows 8]], [[Windows 8.1]], up to some earlier pre-release builds of [[Windows 10 (original release)|Windows 10]]. The Windows flag on the Start button has been changed to monochrome white in order to fit in the new theme. The login screen was changed to include a clock in the top-right corner and to use a silver and dark blue color scheme, although it still gets to keep the same overall layout as in [[Windows XP]]. [[File Explorer|Windows Explorer]] was updated with a new Plex-styled task pane and new templates for the My Documents and My Pictures directories. A new file copy dialog has been implemented, although it doesn't use Avalon. The fold/unfold buttons have been added to Windows Explorer when the ''Show in Groups'' option is enabled.<br />
<br />
A preliminary version of the Avalon user interface framework is included and is used to implement the new [[Windows Sidebar]] and Desktop Properties. The [[Windows Sidebar|Sidebar]] is empty upon enabling and similarly to later builds, it can be combined with the taskbar, which enables a new Start button design also found in later builds. A new virtual desktops feature is also accessible from the Sidebar. [[Desktop Compositing Engine]] is also included with this build, although it is quite unstable and is only known to work on real hardware. When enabled, it renders open windows with a translucency effect.<br />
<br />
This is the last build to have a version of [[Program Manager]] (<code>progman.exe</code>) that is still usable. Starting with [[Windows Longhorn build 3706|build 3706]], it turned into a stub which just redirects to [[File Explorer|Windows Explorer]] instead.<br />
<br />
==New features and changes==<br />
=== Setup ===<br />
Although this build still uses the i386-based installation method used in previous versions of Windows (and as such still utilizes the same minimum requirements as [[Windows XP]]), the ability to install Windows by invoking <code>winnt.exe</code> from [[MS-DOS]] has been removed, and attempting to do so will result in the following deprecation notice, even if the <code>/I_am_TedM</code> debug parameter is passed over to the command line:<br />
<br />
{{quote|Thank you for trying to install Windows Longhorn 2004 using DOS 1985.<br />
<br />
Installing Windows using <code>WINNT.EXE</code> is no longer supported.<br />
Please refer to <nowiki>http://winweb/setup/winntexe.htm</nowiki> for further information.}}<br />
<br />
This removal is likely attributed to development of the then-new Windows Imaging (WIM) format, which had been in the works from as early as March 2002.<ref>Gurr, Rob. [http://web.archive.org/web/20221219203342/https://github.com/jeffglaum/mu_oem_sample/blob/personal/rogurr/cbmr_driver/OemPkg/cBMR/MsCbmrDriver/common/wimfile.h <code>wimfile.h</code> in <code>jeffglaum/mu_oem_sample</code> GitHub repository] ([http://web.archive.org/web/20221219203858/https://github.com/jeffglaum/mu_oem_sample/commit/f5be86a9d17be46cdb24250b2fe536ea8232b897 commit]). 21 September 2022. Archived from the originals <sup>([https://github.com/jeffglaum/mu_oem_sample/blob/personal/rogurr/cbmr_driver/OemPkg/cBMR/MsCbmrDriver/common/wimfile.h 1], [https://github.com/jeffglaum/mu_oem_sample/blob/personal/rogurr/cbmr_driver/OemPkg/cBMR/MsCbmrDriver/common/wimfile.h 2])</sup> on 19 December 2022.</ref><br />
<br />
===Avalon===<br />
This build includes an early version of [[Windows Presentation Foundation]] (WPF), codenamed ''Avalon'', which unlike versions found builds later than [[Windows Longhorn build 3713|3713]], is built against the original .NET Framework 1.0 and can therefore be installed on [[Windows XP]] or other systems supported by the framework.<br />
<br />
==== Windows Trust Manager====<br />
This build features the new Windows Trust Manager, which can be seen when launching a copy of <code>mytvapp.container</code> obtained from a later build, for example. In this case, it does nothing more than asking the user for permission to install the aforementioned app.<br />
<br />
===WinFS===<br />
An early revision of [[WinFS]], referred to as "Windows Future Storage" in <code>services.msc</code> and in the "Windows Components Wizard", is also included in this build, but very little in the way of a user interface was included, and as such it appeared to early testers to be nothing more than a service that consumed large amounts of memory and processor time. In reality, WinFS is responsible for a few of the new features found in this build, such as the "My Contacts" library and Pivots. Thus, disabling WinFS will make it impossible to open the aforementioned library, as well as accessing the Pivots functionality.<br />
<br />
===Windows Explorer===<br />
*Windows Explorer features a huge number of enhancements: three new buttons have been added to the toolbar, namely Zoom, through which it is possible to change the size of the icons in the current folder; Details, which acts as a toggle for the new preview pane; and Pivots, which allows grouping of items such as pictures or music by a specific property, such as "Music Grouped By Album". It should be noted that when selecting a pivot, the system will not filter the contents of the current folder, but it will rather filter the content of the whole hard drive.<br />
<br />
*A new breadcrumb bar has taken the place of the traditional address bar and the tasks pane on the left has changed as well: other than featuring a new background which fits the new [[Plex]] theme, it also includes a new "Find" section with a TextBox, through which it is possible to filter the contents of the current folder. A new Explorer Bar called "Media" has been added, however it fails to load a non-existent page called "Media Places". The media controls are shown, however. A few new options are also available in the "Folder Options" dialog, such as "Check box select".<br />
<br />
*The "New" context menu allows the creation of two new items, namely "Photo Album" and "Playlist".<br />
* The previously mentioned "My Contacts" library can be enabled via "Customize Start Menu" dialog. It is possible to create new contacts through its context menu, but this feature is very rudimentary, and once created it is possible to edit just their name and e-mail address. Double-clicking a contact will open an IM window.<br />
*A friendlier version of the more advanced Device Manager, the "My Hardware" folder, appears by default in the Start menu.<br />
<br />
===New file copy conflict resolve dialog ===<br />
This build has a new file copy conflict resolve dialog, it can be enabled by setting the DWORD value <code>NewResolve</code> to 1 in <code>HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer</code>.<br />
<br />
It will show huge icons of both the source and destination file and will let the users choose if they want to skip or overwrite the file.<br />
<br />
=== Briefcase introduction===<br />
This build contains a briefcase introduction dialog, which can be opened by running <code>rundll32 syncui.dll,Briefcase_IntroW</code>.<ref name="lhMS-3683Tips">[https://longhorn.ms/3683-tips-tricks/ 3683 Tips & tricks], ''longhorn.ms''.</ref><br />
<br />
=== Sidebar===<br />
This build features the sidebar, which is disabled by default and can be enabled in the "Taskbar and Start Menu Properties" dialog. Among its options, there is the possibility to toggle its transparency as well as side, other than an "Unlock bar" option in order to resize it and a "Taskbar" one, which is an early implementation of a combined taskbar and sidebar: upon clicking it, the taskbar will disappear and a new Start button will appear at the top of the sidebar; currently open applications will not be displayed though. The sidebar includes several tiles already, which are the equivalent of the gadgets that would much later be seen in [[Windows Sidebar]], such as Clock, DesktopManager (a functionality that would have not made it into a final [[Microsoft Windows|Windows]] version until [[Windows 10]]), MFU, Quick Launch, Search, SlideShow and UserTile. When the sidebar contains tiles and is set to be minimized, a second tray will appear in the taskbar, showing the icons of the added tiles. Clicking each icon will open the flyout of its associated tile, if it has any.<br />
<br />
===Hidden sidebar tiles===<br />
===="People" sidebar tile====<br />
This build features a normally hidden People sidebar tile. It can be enabled by changing the following values in the registry:<ref>https://wiki.betaworld.cn/Windows_Vista:6.0.3683.0.Lab06_N.020923-1821</ref><br />
<syntaxhighlight lang="registry"><br />
Windows Registry Editor Version 5.00<br />
<br />
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\StartBar\Modules\PeopleTile]<br />
"Assembly"="Microsoft.Windows.PPLRTC1"<br />
"Module"="Microsoft.Windows.Collaboration.Controls.PeopleTile"<br />
</syntaxhighlight><br />
<br />
====Digital clock sidebar tile====<br />
Another hidden sidebar tile, included in this build is a digital clock tile, which also can be enabled by changing the following values in the registry:<br />
<syntaxhighlight lang="registry"><br />
Windows Registry Editor Version 5.00<br />
<br />
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\StartBar\Modules\DigClock]<br />
"Assembly"="Microsoft.Windows.Client"<br />
"Module"="Microsoft.Windows.Client.Sidebar.DigClockTile"<br />
</syntaxhighlight><br />
<br />
=== Game manager ===<br />
This build contains an early prototype of a game manager. Game Definition (GDF) files are recognized by Explorer, and a sample file can be downloaded [https://longhorn.ms/download/resethorn-the-game.zip here].<ref name="lhMS-3683Tips" /> Additionally, it's possible to open a "My Games News" window by running <code>mgui /news general</code>.<ref>[https://twitter.com/thebookisclosed/status/1321870678283460609 Albacore on Twitter]</ref><br />
<br />
===Desktop Compositing Engine===<br />
Contrary to popular belief, this build already contains [[Desktop Compositing Engine]], but it is unstable and only renders window transparency. It is only known to work on real hardware, and it lacks a user interface as well. It can be enabled on the next startup by adding the following registry key and restarting:<br />
<syntaxhighlight lang="registry"><br />
Windows Registry Editor Version 5.00<br />
<br />
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\DesktopComposition]<br />
"StartupOptions"=dword:00000001<br />
</syntaxhighlight><br />
<br />
Alternatively, [[Desktop Window Manager|DCE]] may be started or stopped on request by substituting <code>"StartupOptions"=dword:00000001</code> with <code>"StartupOptions"=dword:00000002</code> in the reg key above. After restarting the computer, DCE may be started by entering <code>rundll32 user32.dll,StartDCE</code> in a command prompt window and stopped with <code>rundll32 user32.dll,StopDCE</code>. After stopping DCE it is helpful to drag a few open windows around to redraw the screen.<br />
<br />
===Avalon-based Display Properties===<br />
This build also includes a new [[Windows Presentation Foundation|Avalon]]-based display settings applet, which can be accessed by right clicking the desktop and then selecting "Properties". However, this applet is largely incomplete; only the "Desktop Background" and "Use Classic Display Control Panel" options work (the earlier option is partially broken), while "Scale and Resolution" and "Display Connection Settings" crashes the applet and Theme and Screen Saver applets and "More Information" option of Display Connection Properties only lead to a screen saying these components are under construction.<br />
<br />
In the Desktop Background, one can select to choose a solid color background, gradient background, rotate to different images (this functionality was under construction) or even make picture collages. The option to change images on the desktop periodically would eventually be a feature that would come in the [[Windows Vista build 6000.16386|final release of Vista]]. Gradient backgrounds made by the applet will be created as a bitmap file named "Wallpaper1".<br />
<br />
===Media Center===<br />
Much like other Milestone 3 builds, this build contains an early version of the Media Center components, codenamed ''Freestyle''. The components can be added from the Add or Remove Programs in the Control Panel under the name of "Freestyle". Once installed, restart the computer to complete the installation. This changes the boot screen, altering the "Professional" text to "Freestyle", while the About Program banner changes from "Professional" to "Media Center Edition". The Media Center application itself is heavily broken, and crashes shortly after launching.<br />
<br />
If prompted for the second disk, it should be pointed to the I386 directory of the installation media.<br />
<br />
===Start Page===<br />
This build, along with the other Milestone 3 builds, contains a new Start Page feature, appearing to be a prototype of a different OOBE to replace the one used in Windows XP. By default, it is not accessible, but Stanimir Stoyanov provided the original Start Page Launcher which can be used to open the Start Page.<ref>[https://longhorn.ms/startpage/ Start page], ''longhorn.ms''.</ref> Due to its earliness, it only contains four tiles that are nonfunctional, being E-Mail, Calendar, Quick Launch, and PromotionsTile.<br />
<br />
===Login screen===<br />
The Welcome login screen now has the ability to require the user to press {{key press|Ctrl|Alt|Del}} to log in to the system. Previously, this was only possible when using the classic login screen.<br />
<br />
=== Miscellaneous ===<br />
*The kernel version has been changed to 6.0.<br />
*The [[out-of-box experience]] music has been changed to ''No Hay Problema'' by [[w:Pink Martini|Pink Martini]], which is included but not used in the final release of [[Windows Server 2003]].<br />
*The [[Windows Product Activation]] grace period has been reduced to 14 days.<br />
*[[Microsoft DirectX|DirectX]] has been updated to version [[DirectX 9|9.0]].<br />
*The Castle service has been introduced.<br />
*[[Internet Explorer]] has been updated to version 6.05.<br />
<br />
==Bugs and quirks==<br />
=== DiskPart ===<br />
DiskPart does not work and will tell the user that <code>This version of diskpart is not supported on this platform.</code><br />
<br />
===OOBE===<br />
The [[out-of-box experience]] may take up a much longer time to initialize unlike other builds.<br />
<br />
===Explorer=== <br />
*When logging in, Windows Explorer will be fairly un-responsive for several minutes.<br />
*Logging off has a chance of crashing Windows Explorer.<br />
*Deleting the registry key <code>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\WebView</code> will disable the details pane in Explorer and enable the [[Windows XP]]-style task pane instead.<br />
<br />
===Sidebar===<br />
*Often, switching to a virtual desktop will fail if the virtual desktop has at least one open program.<br />
*When combining the taskbar with the sidebar, balloons will still pop at the same place as where the taskbar would be at if not combined with the sidebar.<br />
<br />
=== Applications===<br />
[[File:3683 paint crash.PNG|250px|thumb|Paint crash]]<br />
* [[Task Manager]] allows the user to terminate critical system processes.<br />
*[[Paint]] and <code>mshta.exe</code> crashes on exit with a <code>memory could not be "read"</code>error.<br />
* As with later builds of Longhorn, this build is incompatible with a number of applications that require Windows XP or earlier due to the kernel version. Many of these compatibility issues can be resolved by running applications in Windows Compatibility Mode or by editing the ''CSDVersion'' key located in the Windows Registry.<br />
*Some installers that rely on Windows Installer may incorrectly say that this build is x64.<br />
* [[Outlook Express]] has a broken pane close button and the bitmap shown in the About box is not properly displayed.<br />
<br />
===Media Center===<br />
Once installed, it is impossible to uninstall Media Center. The only way to uninstall this is to reinstall Windows.<br />
<br />
=== Upgrading===<br />
[[File:3683UpgradeFileCopyError.PNG|250px|thumb|File copy error when upgrading from Windows XP]]<br />
* On some software configurations, upgrading from [[Windows XP]] can result in setup reporting that a file is missing in <code>C:\$WIN_NT$~BT</code>. The filename will always start with the letter 'a' followed by a random string of seven alphanumeric characters, but the file extension will always be <code>.sys</code>. This can be fixed by expanding any valid <code>.sys</code> file into the <code>C:\$WIN_NT$.~BT</code> folder.<br />
*When upgrading from a clean install of [[Windows XP build 2600.1106|Windows XP Service Pack 1]] and higher, the system will be upgraded to the Media Center SKU. However, most branding will not be updated, and will still say Professional.<br />
* It is not possible to upgrade from [[Windows 98]] or [[Windows Me]] due to the folders <code>win9xupg</code> and <code>win9xmig</code> being missing, however an upgrade can be performed by re-adding these folders to the install CD from a [[Windows XP]] CD with the missing folders.<br />
*On some machines, setup will crash the system on registering components. When the system reboots, setup will restart. However, it will fail to find several files (mainly during Installing Start Menu Items) despite the files being in the correct location.<br />
*Some drivers may cause a [[Blue screen of death|BSOD]] when booting to the desktop. This can be fixed by booting into [[safe mode]], uninstalling the malfunctioning driver and then reinstalling the driver.<br />
<br />
===Control Panel ===<br />
In Display Properties, the Luna theme is referred to as Plex.<br />
<br />
===Internet Explorer===<br />
Downloading a file will cause Internet Explorer to crash. Additionally, the download animation is broken. This does not affect downloads from a FTP site when the file is drag-and-dropped to the desktop.<br />
<br />
==Gallery==<br />
=== Setup ===<br />
<gallery><br />
3683 EULA.png|Text-mode setup<br />
3683 OOBE.png|[[Out-of-box experience]]<br />
</gallery><br />
<br />
=== Interface ===<br />
==== Sidebar ====<br />
<gallery><br />
Longhorn3683-Sidebar.png|Desktop with Sidebar enabled<br />
3683 SidebarAndTaskbar.png|Sidebar and taskbar combined<br />
3683LargerPictureSlideshowGadget.png|Larger Slideshow Gadget<br />
3683DesktopManagerGadget.png|Desktop without wallpaper<br />
3683DesktopWithSidebarMinimized.png|Desktop with Sidebar minimized<br />
3683-Peopletile.png|People Tile<br />
3683-digital-clock-tile.png|Sidebar with Digital Clock Tile<br />
3683 Balloon.png|Balloon bug<br />
</gallery><br />
<br />
===== Desktop Manager =====<br />
<gallery><br />
LH3683 DesktopManager Balloon Tip.png|Desktop Manager balloon tip<br />
LH3683 DesktopManager Prompt.png|Desktop Manager enable prompt<br />
WindowsLonghorn-6.0.3683-MultiDesktop.png|Virtual desktops<br />
</gallery><br />
<br />
==== [[Windows Explorer]] ====<br />
<gallery><br />
3683 Explorer.png|Main window<br />
3683WindowsExplorerMediaPane.png|Ditto, with Media pane enabled<br />
3683-oldexplorer.png|Ditto, with older XP task pane design<br />
3683GDF.png|GDF file details<br />
3683GDFMenu.png|Game datafile (GDF) context menu<br />
3683GDFProperties.png|GDF properties<br />
3683TrustManager.png|Windows Trust Manager<br />
3683MyGamesNews.png|My Games News<br />
</gallery><br />
<br />
==== Miscellaneous ====<br />
<gallery><br />
WinLonghorn36834011Boot.png|Boot screen<br />
WindowsLonghorn-6.0.3683-WelcomeCtrlAltDel.png|{{key press|Ctrl|Alt|Del}} prompt<br />
WindowsLonghorn-6.0.3683-Login.png|Login screen<br />
LonghornWelcome.png|Welcome<br />
WindowsLonghorn-6.0.3683-DCE.png|[[Desktop Composition Engine]]<br />
3683-DCEDemo.PNG|[[Desktop Composition Engine]] with Sidebar<br />
3683CreatePhotoAlbumWizard.png|Create Photo Album Wizard<br />
CreatePlaylist3683.png|Create Playlist<br />
WindowsLonghorn-6.0.3683-InternetExplorer.png|[[Internet Explorer]]<br />
3683OutlookExpress.png|[[Outlook Express]]<br />
Longhorn3683TerminateCsrss.png|[[Task Manager]] with process termination warning<br />
3683StartupPrograms.png|StartUp Applications Monitor<br />
3683Startpage.png|Start page<br />
3683NewSaveDialog.png|New file save dialog<br />
3683NewFCConflictResolve.png|New file copy conflict resolve dialog<br />
3683BriefcaseIntro.png|Windows Briefcase Intro<br />
WinXPSafe.png|Safe to shutdown screen<br />
</gallery><br />
<br />
===== Display Properties =====<br />
<gallery><br />
WindowsLonghorn-6.0.3683-Avalon.png|Avalon display settings<br />
3683 Avalon.png|Desktop Background preferences where Avalon is throwing out errors<br />
3683ColorBlend.png|Color blend<br />
3683ScaleAndResolution.png|Scale and Resolution<br />
3683DesktopCollage1.png|Desktop Collage Preferences #1<br />
3683DesktopCollage2.png|Desktop Collage Preferences #2<br />
3683ChooseASolidColor.png|Choose a solid color<br />
3683ThisFunctionalityIsCurrentlyUnderConstruction.png|"This functionality is currently under construction" error in Avalon Display Properties<br />
3683DisplayConnectionProperties.png|Display Connection Properties<br />
</gallery><br />
<br />
===== Themes =====<br />
<gallery><br />
WindowsLonghorn-6.0.3683m3-blstartmenu.png|Blue Luna theme<br />
WindowsLonghorn-6.0.3683m3-ogstartmenu.png|Olive Green Luna theme<br />
WindowsLonghorn-6.0.3683m3-slstartmenu.png|Silver Luna theme<br />
WindowsLonghorn-6.0.3683m3-cwstartmenu.png|Windows Classic theme<br />
WindowsLonghorn-6.0.3683m3-pstartmenu.png|Plex theme<br />
</gallery><br />
<br />
===== Media Center Edition =====<br />
<gallery><br />
WindowsLonghorn-6.0.3683-Freestyle.png|Boot screen<br />
3683 Freestyle Desktop.png|Desktop<br />
3683 MCE winver.PNG|<code>winver</code><br />
3683 MCE OOBE1.png|Media Center OOBE<br />
3683 freestyle uninstallation error.PNG|Uninstallation error<br />
</gallery><br />
<br />
===xBetas.com images===<br />
<gallery><br />
LH05.jpg|Lock screen<br />
LH02.jpg|Desktop<br />
LH07_small.jpg|Desktop and <code>winver</code><br />
LH04.jpg|Avalon display settings<br />
LH06.jpg|My Hardware<br />
</gallery><br />
<br />
==External links ==<br />
*[https://web.archive.org/web/20021116132801/http://www.winsupersite.com/reviews/longhorn_alpha.asp "Longhorn" Alpha Preview] - Build 3683 reviewed by Paul Thurrott<br />
<br />
==References==<br />
{{reflist}}<br />
<br />
[[Category:Windows Longhorn builds]]</div>Ovctvcthttps://betawiki.net/index.php?title=Windows_Longhorn_build_3670&diff=277692Windows Longhorn build 36702023-06-16T09:41:19Z<p>Ovctvct: Reverted edits by 2402:800:63A7:D9DC:9449:2558:68AE:8C7D (talk) to last revision by Ryuzaki</p>
<hr />
<div>{{Infobox Windows build<br />
|build of = [[Windows Longhorn]]<br />
|image = Longhorn_3670_(1).jpg<br />
|buildtag = 6.0.3670.Lab06_N.020819-1749<br />
|arch = x86<br />
|compiled = 2002-08-19<br />
|sku = Professional<br />
|winver = WindowsLonghorn-6.0.3670-About.png<br />
}}<br />
<br />
'''Windows Longhorn build 3670''' is an unconfirmed build of [[Windows Vista|Windows Longhorn]]. Not much information is known about this build apart from a few screenshots.<br />
<br />
This build does not contain much apparent differences compared to [[Windows Longhorn build 3663|build 3663]], apart from the build referring to itself as ''"Microsoft Windows XP Standard Server Version 2003"'' in the System Properties applet. It remains unleaked as of 2023.<br />
<br />
It is unknown if this build has the [[Plex]] theme due to the theme being set to the default [[Luna]] in the screenshots.<br />
<br />
== Gallery ==<br />
<gallery><br />
LH3670 1.JPG|[[Start menu]] and System Properties<br />
LH3670 2.jpg|Start menu, <code>[[Winver]]</code> and System Properties<br />
LH3670 3.JPG|My Computer<br />
LH3670 4.JPG|My Hardware<br />
LH3670 5.jpg|MSN Explorer<br />
</gallery><br />
<br />
[[Category:Windows Longhorn builds]]<br />
[[Category:Unconfirmed builds]]<br />
[[Category:Unleaked builds]]</div>Ovctvcthttps://betawiki.net/index.php?title=Windows_95_build_499&diff=277515Windows 95 build 4992023-06-15T07:25:39Z<p>Ovctvct: Protected "Windows 95 build 499": Edit warring ([Edit=Allow only autoconfirmed users] (expires 07:25, 15 July 2023 (UTC)) [Move=Allow only autoconfirmed users] (indefinite))</p>
<hr />
<div>{{Infobox Windows build<br />
|build of = [[Windows 95]]<br />
|image = Windows95-4.0.499-Desktop.png<br />
|buildtag = 4.00.499<br />
|arch = x86<br />
|compiled = 1995-06-16<br />
|timebomb = 1995-12-31<br />
|winver = Windows95-RTM-About.png<br />
|key = ''Use a Windows 95 Upgrade serial''<br />
|rivals =<br />
{{Rivals|TCB=http://www.thecollectionbook.info/builds/windows/build/757|TCBGallery=http://www.thecollectionbook.info/gallery/?f=/windows/9x%20kernel/windows%2095/4.00.499/english}}<br />
}}<br />
'''Windows 95 build 499''' is one of the final June Test Release builds of [[Windows 95]]. Like the builds before it, it does not have any new features and focuses mainly on bug fixes. This build is available as an English upgrade copy in DMF floppy format and in German as an upgrade all-in-one CD-ROM which also contains Office 95, Project 95 and Plus! prerelease versions.<ref>https://archive.org/details/4.00.499-x-86fre-client-de-de</ref> A Japanese version of this build for NEC PC-98 may potentially exist based on debug files included in the SDK for [[Windows 95 build 950 r-2|build 950 r-2]].<ref>https://archive.org/download/win-95-interim-build-950/Win95_InterimBuild_950.iso/WIN32SDK%2FMSTOOLS%2FDEBUG%2FNEC%2FUSER.EXE</ref><br />
<br />
== German CD with Plus! 4.4.210 and Office 95 7.0.1911 ==<br />
The German release comes on a CD which also includes [[Microsoft Plus! 95 build 210|Plus! 4.4.210]] and [[Office 95 build 1911 (RC)|Office 95 7.0.1911]] and therefore benefits from their enhancements. According to winhistory.de, this CD was sold in local computer shops for 70 DM (around 36 €).<ref>https://www.winhistory.de/more/chicago.htm#499</ref><br />
<br />
The CD also contains [[Project 95 build 710]] in English and a folder "Vortrag" (which translates to "Presentation") with a lot of demonstration materials in form of PowerPoint, Word and Excel documents and also several AVI video files showing how to do tasks such as sharing files over network.<br />
<br />
Unlike the German build [[Windows 95 build 347|347]], the boot screen has not been translated to German and is identical to the English version.<br />
<br />
=== Bugs of the German version ===<br />
The Windows flag on the Start button looks crumpled, regardless of the video driver, color depth and resolution being used.<br />
<br />
== Installation notes ==<br />
* This is an upgrade build, you must upgrade from a previous Windows version or Windows 95 build.<br />
* The English DMF version has a boot sector on disk 2 that was already modified by setup, and as such, the default owner name is pre-set. You cannot change it during setup (except by replacing the boot sector by that of an untouched RTM disk 2), but it can be changed later by modifying the registry.<br />
* This is the first build in which the Advanced button on the non-OEM product key entry or Product Identification Number (for some floppy media) screens in Setup is dummied out. All code remains for the button, but it is marked not visible in the resources (and no code enables that flag at runtime).<br />
<br />
== Gallery ==<br />
<br />
=== English version ===<br />
<gallery><br />
Windows95-4.0.484-Boot.png|Boot screen<br />
4.00.499.png|Demo<br />
Win9xSafe.png|Safe to shutdown screen<br />
</gallery><br />
<br />
=== German version (with Plus! and Office) ===<br />
<gallery><br />
Windows95.499DE.setup.welcome.png|Welcome to Setup<br />
Windows95.499DE.setup.installing.png|Copying files...<br />
Windows95.499DE.firstboot.png|First boot<br />
Windows95.499DE.sysdm.png|System Properties and Start menu (with Plus! installed)<br />
Windows95.499DE.command.explorer.png|<code>VER</code> and [[Control Panel]]<br />
Windows95.499DE.controlpanel.pluspak2.png|alt=Plus! Themes dialog and control panel|Plus! ''Themes'' dialog and control panel<br />
Windows95.499DE.video.winver.png|<code>Winver</code> and a video being played which comes on the release CD<br />
Win9xGermanSafe.png|Safe to shutdown screen<br />
</gallery><br />
<br />
===Miscellaneous===<br />
<gallery><br />
Win95.499DE.CD.jpg|German installation CD-ROM<br />
</gallery><br />
<br />
==References==<br />
{{reflist}}<br />
<br />
[[Category:Windows 95 builds]]</div>Ovctvcthttps://betawiki.net/index.php?title=Bluepill&diff=276687Bluepill2023-06-10T13:12:03Z<p>Ovctvct: Protected "Bluepill" ([Edit=Require extended confirmed access] (indefinite) [Move=Require extended confirmed access] (indefinite))</p>
<hr />
<div>#REDIRECT [[Redpill]]</div>Ovctvcthttps://betawiki.net/index.php?title=Windows_Server_2012_build_8051&diff=221049Windows Server 2012 build 80512022-06-30T09:22:10Z<p>Ovctvct: /* User Interface */</p>
<hr />
<div>{{Infobox Windows build<br />
|arch = x64<br />
|build of = [[Windows Server 2012]]<br />
|buildtag = 6.2.8051.0.fbl_srv.110719-1928<br />
|compiled = 2011-07-19<br />
|timebomb = 2012-04-08<br />
|image=Server8051-Desktop.png|winver=Server8051-Winver.png}}<br />
<br />
'''Windows Server 2012 build 8051''' is a build of [[Windows Server 2012]], which was shared onto the BetaWiki Discord server on 29 June 2022.<br />
<br />
==Editions and keys==<br />
{| class="wikitable"<br />
!Edition / SKU Name<br />
!Key<br />
|-<br />
|Standard<br />
|HMG6P-C7VGP-47GJ9-TWBD4-2YYCD<br />
|-<br />
|Enterprise (edition upgrade only)<br />
|7P8GH-FV2FF-8FDCR-YK49D-D7P97<br />
|-<br />
|Datacenter<br />
|7X29B-RDCR7-J6R29-K27FF-H9CR9<br />
|}<br />
<br />
== New features and changes ==<br />
<br />
===Branding===<br />
*The branding for the Standard and Datacenter Server SKUs have been updated to now refer to itself as "Windows Server Developer Preview".<br />
*Most references to its [[Windows Server 2008 R2|predecessor]] have been removed.<br />
===Setup===<br />
*When booting from the installation media, the <code>Windows is loading files</code> text has been changed to simply <code>Loading files</code> and it is now left aligned.<br />
*Setup now uses the [[Windows Basic]] theme.<br />
*The second stage of [[Windows Setup|setup]] is now identical to the boot screen.<br />
===Server Manager===<br />
The Server Manager received a major overhaul with this build. UI elements have been redesigned to fit with the Metro design language. It also received a new icon.<br />
<br />
Additionally, this build removes the legacy Server Manager in favor of the newer version.<br />
<br />
=== Miscellaneous ===<br />
*The [[taskbar]] user tile has been removed.<br />
*The background in the wordoku puzzle desktop wallpaper has been changed to a dark purple and feature a set of colorful strands at the bottom of the image.<br />
*An early version of [[Internet Explorer 10]] is now included, replacing [[Internet Explorer 9]].<br />
*[[Help and Support Center]] received new in-app icons.<br />
<br />
== Bugs and quirks ==<br />
<br />
=== Setup ===<br />
The background wallpaper to the "Finalizing your settings" phase of setup seems to be broken.<br />
<br />
== Gallery ==<br />
<br />
=== Setup ===<br />
<gallery><br />
File:Server8051-Setup.png|Language<br />
File:WindowsServer2012-6.2.7965.0-Installing Windows.png|Installing Windows<br />
File:Server8051-Setup2.png|Almost ready<br />
File:Server8064-OOBE.png|Finalizing your settings<br />
</gallery><br />
<br />
=== User Interface ===<br />
<gallery><br />
File:Windows8-6.2.8056-Boot.png|Boot screen<br />
8051start.png|Start screen<br />
</gallery></div>Ovctvcthttps://betawiki.net/index.php?title=File:8051start.png&diff=221048File:8051start.png2022-06-30T09:21:57Z<p>Ovctvct: </p>
<hr />
<div></div>Ovctvcthttps://betawiki.net/index.php?title=Windows_8_build_7985_(fbl_core1_kernel_cptx.110419-1745)&diff=221047Windows 8 build 7985 (fbl core1 kernel cptx.110419-1745)2022-06-30T09:15:02Z<p>Ovctvct: /* Gallery */</p>
<hr />
<div>{{DISPLAYTITLE:Windows 8 build 7985 (fbl_core1_kernel_cptx.110419-1745)}}<br />
{{Infobox Windows build<br />
|build of = [[Windows 8]]<br />
|image =Windows8-6.2.7985.0.110419-1745-Desktop.png<br />
|buildtag = 6.2.7985.0.fbl_core1_kernel_cptx.110419-1745<br />
|arch = x86<br />
|compiled = 2011-04-19<br />
|timebomb = 2012-03-15<br />
|winver = Windows8-6.2.7985.0.110419-1745-Winver.png<br />
}}<br />
'''Windows 8 build 7985 (fbl_core1_kernel_cptx.110419-1745)''' is a Milestone 3 build of [[Windows 8]], which was shared on 28 June 2022. This build features a new wallpaper with an updated wordoku puzzle.<br />
<br />
== Redpill ==<br />
Continuing on with the evolution of Metro starting with [[Windows 8 build 7978|build 7978]], the unlocked features in this build are a middle ground between the early Milestone 2 Metro of builds [[Windows 8 build 7927|7927]] to [[Windows 8 build 7963|7963]] and the closer to final looks of builds [[Windows 8 build 8032|8032]] and [[Windows 8 build 8056|8056]]. The Start screen now has the "Start" header, along with the Other Programs UI being replaced with the Applications list. The Charms bar now has a clock appear along with it, along with the Settings charm being redesigned, adding some non-functional toggles for the Power, keyboard, and a placeholder toggle called "VanUI", possibly standing for View Active Networks.<br />
<br />
The [[Windows Aero|Aero]] theme is also updated to a more flat and squared theme, resembling the Windows Basic of this build. In this build, it is already possible to change the accent color of the start screen, however there are only two colors available. To do this, open regedit, go to <code>HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Accent</code> and create a DWORD named <code>ColorSet</code> and set its value to 1. When you logoff and logon again, the start screen will be a different blue gradient.<br />
<br />
== Bugs ==<br />
*It appears that it is possible to "uninstall" the desktop. However,clicking Uninstall does nothing.<br />
*The Task Manager shows erratic values for the network usage.<br />
*Installing display drivers does not work.<br />
== Compiler ==<br />
This is one of the first builds to be compiled using a new compiler. However, the problems surrounding it at that time resulted in the build becoming unbootable on certain hardware, as the boot loader does not properly function on modern x86 CPUs, namely Intel processors with the AVX instruction set and a select number of AMD CPUs. As a result, a CPU triple fault occurs resulting in either a crash on a hypervisor or a reboot on real hardware.<br />
<br />
Most of the bugs found in this build are a side effect of the new compiler.<br />
<br />
=== Patching winload.exe to run on Intel processors with AVX ===<br />
In order to properly enable SSE instructions for machines using Intel processor with AVX, the 9th bit in Control Register 4 (CR4) must be turned on. The following code is executed and is located in winload.exe at offset A137:<br />
<syntaxhighlight lang="nasm"><br />
mov eax, cr4 ; 0f20e0<br />
or eax, 20h ; 83c820 -- Turn on 5th bit, PAE (Physical Address Extension)<br />
mov cr4, eax ; 0f22e0 -- Store it in CR4<br />
mov eax, cr0 ; 0f20c0<br />
or eax, 80000000h ; 0d00000080 -- Enable paging<br />
mov cr0, eax ; 0f22c0<br />
</syntaxhighlight><br />
<br />
By default the following bits are set in CR0: Protected Mode (PE) (0x00000001), Monitor co-processor (MP) (0x00000002) and Extension type (ET) (0x00000010), with no bits in CR4 set initially, so the need to turn on the 9th SSE bit (i.e. OR with 0x600) should be done, but due to limitation in this piece of code, a rewriting needs to be done and the following approach may be used instead:<br />
<br />
<syntaxhighlight lang="nasm"><br />
mov eax,620h ; b820060000<br />
mov cr4,eax ; 0f22e0<br />
mov eax,80000013h ; b813000080<br />
mov cr0,eax ; 0f22c0<br />
nop ; 90<br />
nop ; 90<br />
nop ; 90<br />
nop ; 90<br />
</syntaxhighlight><br />
<br />
As a disclaimer, patching winload.exe with these changes will invalidate integrity checks and thus requires Test Mode to be enabled (by setting <code>NoIntegrityChecks</code> in the BCD to on) in order to boot with the patched winload.exe, as well as ownership of the file in both <code>%systemroot%\System32</code> and <code>%systemroot%\System32\Boot</code> need to be altered in case file replacement was not possible.<br />
<br />
=== Compatibility ===<br />
==== VMware Workstation ====<br />
For another workaround on the Intel SSE bug that does not involve patching and disabling security checks, the compatibility level must be set to version 7.x or lower in order to boot this build. In addition, the following block of code must be added to the VMX (virtual machine configuration) file in order to allow this build to boot on modern Intel CPUs:<br />
<br />
<syntaxhighlight lang="ini"><br />
cpuid.0.ebx = "0110:1000:0111:0100:0111:0101:0100:0001"<br />
cpuid.0.ecx = "0100:0100:0100:1101:0100:0001:0110:0011"<br />
cpuid.0.edx = "0110:1001:0111:0100:0110:1110:0110:0101"<br />
cpuid.1.eax = "0000:0000:0000:0001:0000:0110:0111:0001"<br />
</syntaxhighlight><br />
<br />
The above configuration is mostly not required if the host machine has an AMD processor, and as such only requires the compatibility version to be changed.<br />
<br />
==Gallery==<br />
<gallery><br />
7985boot.png|Boot screen<br />
File:7985start.png|Start screen<br />
7985charm.png|Charm bar<br />
7985charmsettings.png|Settings charm<br />
7989c2.png|2nd accent color<br />
7985share.png|Share error<br />
7985oobe.png|Metro OOBE<br />
</gallery><br />
<br />
[[Category:Windows 8 builds]]</div>Ovctvcthttps://betawiki.net/index.php?title=Windows_8_build_7985_(fbl_core1_kernel_cptx.110419-1745)&diff=221046Windows 8 build 7985 (fbl core1 kernel cptx.110419-1745)2022-06-30T09:14:51Z<p>Ovctvct: /* Gallery */</p>
<hr />
<div>{{DISPLAYTITLE:Windows 8 build 7985 (fbl_core1_kernel_cptx.110419-1745)}}<br />
{{Infobox Windows build<br />
|build of = [[Windows 8]]<br />
|image =Windows8-6.2.7985.0.110419-1745-Desktop.png<br />
|buildtag = 6.2.7985.0.fbl_core1_kernel_cptx.110419-1745<br />
|arch = x86<br />
|compiled = 2011-04-19<br />
|timebomb = 2012-03-15<br />
|winver = Windows8-6.2.7985.0.110419-1745-Winver.png<br />
}}<br />
'''Windows 8 build 7985 (fbl_core1_kernel_cptx.110419-1745)''' is a Milestone 3 build of [[Windows 8]], which was shared on 28 June 2022. This build features a new wallpaper with an updated wordoku puzzle.<br />
<br />
== Redpill ==<br />
Continuing on with the evolution of Metro starting with [[Windows 8 build 7978|build 7978]], the unlocked features in this build are a middle ground between the early Milestone 2 Metro of builds [[Windows 8 build 7927|7927]] to [[Windows 8 build 7963|7963]] and the closer to final looks of builds [[Windows 8 build 8032|8032]] and [[Windows 8 build 8056|8056]]. The Start screen now has the "Start" header, along with the Other Programs UI being replaced with the Applications list. The Charms bar now has a clock appear along with it, along with the Settings charm being redesigned, adding some non-functional toggles for the Power, keyboard, and a placeholder toggle called "VanUI", possibly standing for View Active Networks.<br />
<br />
The [[Windows Aero|Aero]] theme is also updated to a more flat and squared theme, resembling the Windows Basic of this build. In this build, it is already possible to change the accent color of the start screen, however there are only two colors available. To do this, open regedit, go to <code>HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Accent</code> and create a DWORD named <code>ColorSet</code> and set its value to 1. When you logoff and logon again, the start screen will be a different blue gradient.<br />
<br />
== Bugs ==<br />
*It appears that it is possible to "uninstall" the desktop. However,clicking Uninstall does nothing.<br />
*The Task Manager shows erratic values for the network usage.<br />
*Installing display drivers does not work.<br />
== Compiler ==<br />
This is one of the first builds to be compiled using a new compiler. However, the problems surrounding it at that time resulted in the build becoming unbootable on certain hardware, as the boot loader does not properly function on modern x86 CPUs, namely Intel processors with the AVX instruction set and a select number of AMD CPUs. As a result, a CPU triple fault occurs resulting in either a crash on a hypervisor or a reboot on real hardware.<br />
<br />
Most of the bugs found in this build are a side effect of the new compiler.<br />
<br />
=== Patching winload.exe to run on Intel processors with AVX ===<br />
In order to properly enable SSE instructions for machines using Intel processor with AVX, the 9th bit in Control Register 4 (CR4) must be turned on. The following code is executed and is located in winload.exe at offset A137:<br />
<syntaxhighlight lang="nasm"><br />
mov eax, cr4 ; 0f20e0<br />
or eax, 20h ; 83c820 -- Turn on 5th bit, PAE (Physical Address Extension)<br />
mov cr4, eax ; 0f22e0 -- Store it in CR4<br />
mov eax, cr0 ; 0f20c0<br />
or eax, 80000000h ; 0d00000080 -- Enable paging<br />
mov cr0, eax ; 0f22c0<br />
</syntaxhighlight><br />
<br />
By default the following bits are set in CR0: Protected Mode (PE) (0x00000001), Monitor co-processor (MP) (0x00000002) and Extension type (ET) (0x00000010), with no bits in CR4 set initially, so the need to turn on the 9th SSE bit (i.e. OR with 0x600) should be done, but due to limitation in this piece of code, a rewriting needs to be done and the following approach may be used instead:<br />
<br />
<syntaxhighlight lang="nasm"><br />
mov eax,620h ; b820060000<br />
mov cr4,eax ; 0f22e0<br />
mov eax,80000013h ; b813000080<br />
mov cr0,eax ; 0f22c0<br />
nop ; 90<br />
nop ; 90<br />
nop ; 90<br />
nop ; 90<br />
</syntaxhighlight><br />
<br />
As a disclaimer, patching winload.exe with these changes will invalidate integrity checks and thus requires Test Mode to be enabled (by setting <code>NoIntegrityChecks</code> in the BCD to on) in order to boot with the patched winload.exe, as well as ownership of the file in both <code>%systemroot%\System32</code> and <code>%systemroot%\System32\Boot</code> need to be altered in case file replacement was not possible.<br />
<br />
=== Compatibility ===<br />
==== VMware Workstation ====<br />
For another workaround on the Intel SSE bug that does not involve patching and disabling security checks, the compatibility level must be set to version 7.x or lower in order to boot this build. In addition, the following block of code must be added to the VMX (virtual machine configuration) file in order to allow this build to boot on modern Intel CPUs:<br />
<br />
<syntaxhighlight lang="ini"><br />
cpuid.0.ebx = "0110:1000:0111:0100:0111:0101:0100:0001"<br />
cpuid.0.ecx = "0100:0100:0100:1101:0100:0001:0110:0011"<br />
cpuid.0.edx = "0110:1001:0111:0100:0110:1110:0110:0101"<br />
cpuid.1.eax = "0000:0000:0000:0001:0000:0110:0111:0001"<br />
</syntaxhighlight><br />
<br />
The above configuration is mostly not required if the host machine has an AMD processor, and as such only requires the compatibility version to be changed.<br />
<br />
==Gallery==<br />
<gallery><br />
7985boot.png|Boot screen<br />
File:7985start.png|Start screen<br />
7985charm.png|Charm bar<br />
7985charmsettings.png|Settings charm<br />
7989c2.png|2nd accent color<br />
7985share.png|Share error<br />
7985oobe.png|Metro oobe<br />
</gallery><br />
<br />
[[Category:Windows 8 builds]]</div>Ovctvcthttps://betawiki.net/index.php?title=File:7985oobe.png&diff=221045File:7985oobe.png2022-06-30T09:14:26Z<p>Ovctvct: </p>
<hr />
<div></div>Ovctvcthttps://betawiki.net/index.php?title=Windows_8_build_7985_(fbl_core1_kernel_cptx.110419-1745)&diff=221042Windows 8 build 7985 (fbl core1 kernel cptx.110419-1745)2022-06-30T09:08:04Z<p>Ovctvct: /* Gallery */</p>
<hr />
<div>{{DISPLAYTITLE:Windows 8 build 7985 (fbl_core1_kernel_cptx.110419-1745)}}<br />
{{Infobox Windows build<br />
|build of = [[Windows 8]]<br />
|image =Windows8-6.2.7985.0.110419-1745-Desktop.png<br />
|buildtag = 6.2.7985.0.fbl_core1_kernel_cptx.110419-1745<br />
|arch = x86<br />
|compiled = 2011-04-19<br />
|timebomb = 2012-03-15<br />
|winver = Windows8-6.2.7985.0.110419-1745-Winver.png<br />
}}<br />
'''Windows 8 build 7985 (fbl_core1_kernel_cptx.110419-1745)''' is a Milestone 3 build of [[Windows 8]], which was shared on 28 June 2022. This build features a new wallpaper with an updated wordoku puzzle.<br />
<br />
== Redpill ==<br />
Continuing on with the evolution of Metro starting with [[Windows 8 build 7978|build 7978]], the unlocked features in this build are a middle ground between the early Milestone 2 Metro of builds [[Windows 8 build 7927|7927]] to [[Windows 8 build 7963|7963]] and the closer to final looks of builds [[Windows 8 build 8032|8032]] and [[Windows 8 build 8056|8056]]. The Start screen now has the "Start" header, along with the Other Programs UI being replaced with the Applications list. The Charms bar now has a clock appear along with it, along with the Settings charm being redesigned, adding some non-functional toggles for the Power, keyboard, and a placeholder toggle called "VanUI", possibly standing for View Active Networks.<br />
<br />
The [[Windows Aero|Aero]] theme is also updated to a more flat and squared theme, resembling the Windows Basic of this build. In this build, it is already possible to change the accent color of the start screen, however there are only two colors available. To do this, open regedit, go to <code>HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Accent</code> and create a DWORD named <code>ColorSet</code> and set its value to 1. When you logoff and logon again, the start screen will be a different blue gradient.<br />
<br />
== Bugs ==<br />
*It appears that it is possible to "uninstall" the desktop. However,clicking Uninstall does nothing.<br />
*The Task Manager shows erratic values for the network usage.<br />
*Installing display drivers does not work.<br />
== Compiler ==<br />
This is one of the first builds to be compiled using a new compiler. However, the problems surrounding it at that time resulted in the build becoming unbootable on certain hardware, as the boot loader does not properly function on modern x86 CPUs, namely Intel processors with the AVX instruction set and a select number of AMD CPUs. As a result, a CPU triple fault occurs resulting in either a crash on a hypervisor or a reboot on real hardware.<br />
<br />
Most of the bugs found in this build are a side effect of the new compiler.<br />
<br />
=== Patching winload.exe to run on Intel processors with AVX ===<br />
In order to properly enable SSE instructions for machines using Intel processor with AVX, the 9th bit in Control Register 4 (CR4) must be turned on. The following code is executed and is located in winload.exe at offset A137:<br />
<syntaxhighlight lang="nasm"><br />
mov eax, cr4 ; 0f20e0<br />
or eax, 20h ; 83c820 -- Turn on 5th bit, PAE (Physical Address Extension)<br />
mov cr4, eax ; 0f22e0 -- Store it in CR4<br />
mov eax, cr0 ; 0f20c0<br />
or eax, 80000000h ; 0d00000080 -- Enable paging<br />
mov cr0, eax ; 0f22c0<br />
</syntaxhighlight><br />
<br />
By default the following bits are set in CR0: Protected Mode (PE) (0x00000001), Monitor co-processor (MP) (0x00000002) and Extension type (ET) (0x00000010), with no bits in CR4 set initially, so the need to turn on the 9th SSE bit (i.e. OR with 0x600) should be done, but due to limitation in this piece of code, a rewriting needs to be done and the following approach may be used instead:<br />
<br />
<syntaxhighlight lang="nasm"><br />
mov eax,620h ; b820060000<br />
mov cr4,eax ; 0f22e0<br />
mov eax,80000013h ; b813000080<br />
mov cr0,eax ; 0f22c0<br />
nop ; 90<br />
nop ; 90<br />
nop ; 90<br />
nop ; 90<br />
</syntaxhighlight><br />
<br />
As a disclaimer, patching winload.exe with these changes will invalidate integrity checks and thus requires Test Mode to be enabled (by setting <code>NoIntegrityChecks</code> in the BCD to on) in order to boot with the patched winload.exe, as well as ownership of the file in both <code>%systemroot%\System32</code> and <code>%systemroot%\System32\Boot</code> need to be altered in case file replacement was not possible.<br />
<br />
=== Compatibility ===<br />
==== VMware Workstation ====<br />
For another workaround on the Intel SSE bug that does not involve patching and disabling security checks, the compatibility level must be set to version 7.x or lower in order to boot this build. In addition, the following block of code must be added to the VMX (virtual machine configuration) file in order to allow this build to boot on modern Intel CPUs:<br />
<br />
<syntaxhighlight lang="ini"><br />
cpuid.0.ebx = "0110:1000:0111:0100:0111:0101:0100:0001"<br />
cpuid.0.ecx = "0100:0100:0100:1101:0100:0001:0110:0011"<br />
cpuid.0.edx = "0110:1001:0111:0100:0110:1110:0110:0101"<br />
cpuid.1.eax = "0000:0000:0000:0001:0000:0110:0111:0001"<br />
</syntaxhighlight><br />
<br />
The above configuration is mostly not required if the host machine has an AMD processor, and as such only requires the compatibility version to be changed.<br />
<br />
==Gallery==<br />
<gallery><br />
7985boot.png|Boot screen<br />
File:7985start.png|Start screen<br />
7985charm.png|Charm bar<br />
7985charmsettings.png|Settings charm<br />
7989c2.png|2nd accent color<br />
7985share.png|Share error<br />
</gallery><br />
<br />
[[Category:Windows 8 builds]]</div>Ovctvcthttps://betawiki.net/index.php?title=File:7985share.png&diff=221041File:7985share.png2022-06-30T09:07:39Z<p>Ovctvct: </p>
<hr />
<div></div>Ovctvcthttps://betawiki.net/index.php?title=File:7989c2.png&diff=221039File:7989c2.png2022-06-30T09:07:26Z<p>Ovctvct: </p>
<hr />
<div></div>Ovctvcthttps://betawiki.net/index.php?title=File:7985charmsettings.png&diff=221038File:7985charmsettings.png2022-06-30T09:06:55Z<p>Ovctvct: </p>
<hr />
<div></div>Ovctvcthttps://betawiki.net/index.php?title=Windows_8_build_7985_(fbl_core1_kernel_cptx.110419-1745)&diff=221037Windows 8 build 7985 (fbl core1 kernel cptx.110419-1745)2022-06-30T09:05:37Z<p>Ovctvct: /* Redpill */</p>
<hr />
<div>{{DISPLAYTITLE:Windows 8 build 7985 (fbl_core1_kernel_cptx.110419-1745)}}<br />
{{Infobox Windows build<br />
|build of = [[Windows 8]]<br />
|image =Windows8-6.2.7985.0.110419-1745-Desktop.png<br />
|buildtag = 6.2.7985.0.fbl_core1_kernel_cptx.110419-1745<br />
|arch = x86<br />
|compiled = 2011-04-19<br />
|timebomb = 2012-03-15<br />
|winver = Windows8-6.2.7985.0.110419-1745-Winver.png<br />
}}<br />
'''Windows 8 build 7985 (fbl_core1_kernel_cptx.110419-1745)''' is a Milestone 3 build of [[Windows 8]], which was shared on 28 June 2022. This build features a new wallpaper with an updated wordoku puzzle.<br />
<br />
== Redpill ==<br />
Continuing on with the evolution of Metro starting with [[Windows 8 build 7978|build 7978]], the unlocked features in this build are a middle ground between the early Milestone 2 Metro of builds [[Windows 8 build 7927|7927]] to [[Windows 8 build 7963|7963]] and the closer to final looks of builds [[Windows 8 build 8032|8032]] and [[Windows 8 build 8056|8056]]. The Start screen now has the "Start" header, along with the Other Programs UI being replaced with the Applications list. The Charms bar now has a clock appear along with it, along with the Settings charm being redesigned, adding some non-functional toggles for the Power, keyboard, and a placeholder toggle called "VanUI", possibly standing for View Active Networks.<br />
<br />
The [[Windows Aero|Aero]] theme is also updated to a more flat and squared theme, resembling the Windows Basic of this build. In this build, it is already possible to change the accent color of the start screen, however there are only two colors available. To do this, open regedit, go to <code>HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Accent</code> and create a DWORD named <code>ColorSet</code> and set its value to 1. When you logoff and logon again, the start screen will be a different blue gradient.<br />
<br />
== Bugs ==<br />
*It appears that it is possible to "uninstall" the desktop. However,clicking Uninstall does nothing.<br />
*The Task Manager shows erratic values for the network usage.<br />
*Installing display drivers does not work.<br />
== Compiler ==<br />
This is one of the first builds to be compiled using a new compiler. However, the problems surrounding it at that time resulted in the build becoming unbootable on certain hardware, as the boot loader does not properly function on modern x86 CPUs, namely Intel processors with the AVX instruction set and a select number of AMD CPUs. As a result, a CPU triple fault occurs resulting in either a crash on a hypervisor or a reboot on real hardware.<br />
<br />
Most of the bugs found in this build are a side effect of the new compiler.<br />
<br />
=== Patching winload.exe to run on Intel processors with AVX ===<br />
In order to properly enable SSE instructions for machines using Intel processor with AVX, the 9th bit in Control Register 4 (CR4) must be turned on. The following code is executed and is located in winload.exe at offset A137:<br />
<syntaxhighlight lang="nasm"><br />
mov eax, cr4 ; 0f20e0<br />
or eax, 20h ; 83c820 -- Turn on 5th bit, PAE (Physical Address Extension)<br />
mov cr4, eax ; 0f22e0 -- Store it in CR4<br />
mov eax, cr0 ; 0f20c0<br />
or eax, 80000000h ; 0d00000080 -- Enable paging<br />
mov cr0, eax ; 0f22c0<br />
</syntaxhighlight><br />
<br />
By default the following bits are set in CR0: Protected Mode (PE) (0x00000001), Monitor co-processor (MP) (0x00000002) and Extension type (ET) (0x00000010), with no bits in CR4 set initially, so the need to turn on the 9th SSE bit (i.e. OR with 0x600) should be done, but due to limitation in this piece of code, a rewriting needs to be done and the following approach may be used instead:<br />
<br />
<syntaxhighlight lang="nasm"><br />
mov eax,620h ; b820060000<br />
mov cr4,eax ; 0f22e0<br />
mov eax,80000013h ; b813000080<br />
mov cr0,eax ; 0f22c0<br />
nop ; 90<br />
nop ; 90<br />
nop ; 90<br />
nop ; 90<br />
</syntaxhighlight><br />
<br />
As a disclaimer, patching winload.exe with these changes will invalidate integrity checks and thus requires Test Mode to be enabled (by setting <code>NoIntegrityChecks</code> in the BCD to on) in order to boot with the patched winload.exe, as well as ownership of the file in both <code>%systemroot%\System32</code> and <code>%systemroot%\System32\Boot</code> need to be altered in case file replacement was not possible.<br />
<br />
=== Compatibility ===<br />
==== VMware Workstation ====<br />
For another workaround on the Intel SSE bug that does not involve patching and disabling security checks, the compatibility level must be set to version 7.x or lower in order to boot this build. In addition, the following block of code must be added to the VMX (virtual machine configuration) file in order to allow this build to boot on modern Intel CPUs:<br />
<br />
<syntaxhighlight lang="ini"><br />
cpuid.0.ebx = "0110:1000:0111:0100:0111:0101:0100:0001"<br />
cpuid.0.ecx = "0100:0100:0100:1101:0100:0001:0110:0011"<br />
cpuid.0.edx = "0110:1001:0111:0100:0110:1110:0110:0101"<br />
cpuid.1.eax = "0000:0000:0000:0001:0000:0110:0111:0001"<br />
</syntaxhighlight><br />
<br />
The above configuration is mostly not required if the host machine has an AMD processor, and as such only requires the compatibility version to be changed.<br />
<br />
==Gallery==<br />
<gallery><br />
7985boot.png|Boot screen<br />
File:7985start.png|Start screen<br />
7985charm.png|Charm bar<br />
</gallery><br />
<br />
[[Category:Windows 8 builds]]</div>Ovctvcthttps://betawiki.net/index.php?title=Windows_8_build_7989&diff=221036Windows 8 build 79892022-06-30T09:05:15Z<p>Ovctvct: </p>
<hr />
<div>{{Infobox Windows build<br />
|build of = [[Windows 8]]<br />
|image = Windows8-6.2.7989-Desktop.png<br />
|buildtag = 6.2.7989.winmain.110421-1825<br />
|arch = x64, x86<br />
|compiled = 2011-04-21<br />
|timebomb = 2012-03-15<br />
|winver = Winver7989.png<br />
|rivals = {{Rivals|TCB=https://thecollectionbook.info/builds/windows/build/115|TCBGallery=https://www.thecollectionbook.info/gallery/?f=/windows/nt%20kernel/windows%208/6.2.7989.0/english/ultimate/x64}}<br />
}}<br />
'''Windows 8 build 7989''' is a Milestone 3 build of [[Windows 8]], which was originally released on 18 June 2011 in the x64 architecture, then on 8 February 2020, an x86 checked/debug version of it was uploaded to [[BetaArchive]].<br />
<br />
==Editions and keys==<br />
{| class="wikitable"<br />
!Edition / SKU Name<br />
!Key<br />
|-<br />
|Starter<br />
|7Q28W-FT9PC-CMMYT-WHMY2-89M6G<br />
|-<br />
|Home Basic<br />
|YGFVB-QTFXQ-3H233-PTWTJ-YRYRV<br />
|-<br />
|Home Premium<br />
|RHPQ2-RMFJH-74XYM-BH4JX-XM76F<br />
|-<br />
|Professional<br />
|HYF8J-CVRMY-CM74G-RPHKF-PW487<br />
|-<br />
|Ultimate<br />
|D4F6K-QK3RD-TMVMJ-BBMRX-3MBMV<br />
|}<br />
<br />
==Changes==<br />
*The Windows Preinstallation Environment of this build is technically the first to use the [[Windows Basic]] theme.<br />
<br />
==Redpill==<br />
When the "Share" button from the charms bar is clicked, a file called shrscr.png is created in the %temp% folder, with a cat and text saying "U can haz no pix. GIMME FISH", along with a bug ID at the bottom. The text is most likely a reference to the strict NDA that existed during Windows 8's development, implying that no images of the build can be shared.<br />
<br />
==Bugs==<br />
===Compatibility===<br />
To install or run this build in VMware Workstation, you must set the hardware compatibility to version 8.x or below; otherwise, a partially garbled system crash message will occur which will say "Your computer needs to restart. Please hold down the power button", such as error 0x0000001E or 0x0000000A. This error would occur right when the system kernel takes over the startup process but immediately crashes.<br />
<br />
===EFI===<br />
The x64 version of this build appears to not support hardware with EFI, due to being bundled with an x86 7600 WinPE setup. To try and solve this, copy x64 7989's install.wim into an x64 7600/7601 WinPE setup, or deploy the image through DISM - this fix does not work for all UEFI configurations.<br />
<br />
===Start screen===<br />
<br />
*When enabling Redpill, the start screen may appear to be empty.<br />
*There appears to be an option to "uninstall" the desktop on the start screen. However, selecting that option does nothing.<br />
<br />
===Aero Glass in Starter and Home Basic ===<br />
This build automatically enables Aero Glass transparency even when installing the Starter or Home Basic SKUs, which is not supported by default. However, changing the color scheme (visual style) to another one and then back to the default one will disable Aero Glass.<br />
<br />
=== Redpill ===<br />
In this build's x64 compile the twinui.dll file that is installed by default does not work with this build and will result in a broken system if redpilled. To fix this, run the following command in a command prompt and reboot before running Redlock:<br />
<br />
<code>sfc /SCANFILE=C:\Windows\System32\TWINUI.DLL</code><br />
===[[Windows Setup|Setup]]===<br />
At the end of setup, the message "Setup will continue after restarting your computer" can be displayed displaced.<br />
<br />
==Gallery==<br />
<gallery><br />
7989boot.png|Boot screen<br />
Windows 8 build 7989 OOBE.png|Metro OOBE<br />
Windows8-6.2.7989-Login.png|Lock screen<br />
7989ls.png|Lock screen with the desktop wallpaper as the background<br />
7989login.png|Metro login screen<br />
7989loginlang.png|Language selection on the login screen<br />
7989start.png|Start screen<br />
2nd start screen colour on Windows 8 build 7989.png|Second color on the Start screen<br />
Windows8-6.2.7989-CAD.png|{{key press|Ctrl|Alt|Del}} screen<br />
Windows8-6.2.7989-BSOD.png|System crash<br />
7989charm.png|Charms bar<br />
7989 metro autoplay.png|Autoplay flyout<br />
7989charm2.png|Charms bar with Explorer and Task Manager open<br />
7989charmsettings.png|Settings panel<br />
7989store.png|MS Help<br />
Windows8-6.2.7989.0-NDACat.png|Cat image produced from Share button<br />
Bug-StartScreen.png|Start screen shown empty after enabling Redpill.<br />
Bug-UninstallDesktop.png|Uninstall desktop option on the Start screen.<br />
</gallery><br />
<br />
[[Category:Windows 8 builds]]</div>Ovctvcthttps://betawiki.net/index.php?title=Windows_8_build_7989&diff=221035Windows 8 build 79892022-06-30T09:01:28Z<p>Ovctvct: /* Changes */</p>
<hr />
<div>{{Infobox Windows build<br />
|build of = [[Windows 8]]<br />
|image = Windows8-6.2.7989-Desktop.png<br />
|buildtag = 6.2.7989.winmain.110421-1825<br />
|arch = x64, x86<br />
|compiled = 2011-04-21<br />
|timebomb = 2012-03-15<br />
|winver = Winver7989.png<br />
|rivals = {{Rivals|TCB=https://thecollectionbook.info/builds/windows/build/115|TCBGallery=https://www.thecollectionbook.info/gallery/?f=/windows/nt%20kernel/windows%208/6.2.7989.0/english/ultimate/x64}}<br />
}}<br />
'''Windows 8 build 7989''' is a Milestone 3 build of [[Windows 8]], which was originally released on 18 June 2011 in the x64 architecture, then on 8 February 2020, an x86 checked/debug version of it was uploaded to [[BetaArchive]].<br />
<br />
==Editions and keys==<br />
{| class="wikitable"<br />
!Edition / SKU Name<br />
!Key<br />
|-<br />
|Starter<br />
|7Q28W-FT9PC-CMMYT-WHMY2-89M6G<br />
|-<br />
|Home Basic<br />
|YGFVB-QTFXQ-3H233-PTWTJ-YRYRV<br />
|-<br />
|Home Premium<br />
|RHPQ2-RMFJH-74XYM-BH4JX-XM76F<br />
|-<br />
|Professional<br />
|HYF8J-CVRMY-CM74G-RPHKF-PW487<br />
|-<br />
|Ultimate<br />
|D4F6K-QK3RD-TMVMJ-BBMRX-3MBMV<br />
|}<br />
<br />
==Changes==<br />
*The Windows Preinstallation Environment of this build is technically the first to use the [[Windows Basic]] theme.<br />
<br />
==Redpill==<br />
In this build, it is already possible to change the accent color of the start screen, however there are only two colors available. To do this, open regedit, go to <code>HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Accent</code> and create a DWORD named <code>ColorSet</code> and set its value to 1. When you logoff and logon again, the start screen will be a different blue gradient.<br />
<br />
When the "Share" button from the charms bar is clicked, a file called shrscr.png is created in the %temp% folder, with a cat and text saying "U can haz no pix. GIMME FISH", along with a bug ID at the bottom. The text is most likely a reference to the strict NDA that existed during Windows 8's development, implying that no images of the build can be shared.<br />
<br />
==Bugs==<br />
===Compatibility===<br />
To install or run this build in VMware Workstation, you must set the hardware compatibility to version 8.x or below; otherwise, a partially garbled system crash message will occur which will say "Your computer needs to restart. Please hold down the power button", such as error 0x0000001E or 0x0000000A. This error would occur right when the system kernel takes over the startup process but immediately crashes.<br />
<br />
===EFI===<br />
The x64 version of this build appears to not support hardware with EFI, due to being bundled with an x86 7600 WinPE setup. To try and solve this, copy x64 7989's install.wim into an x64 7600/7601 WinPE setup, or deploy the image through DISM - this fix does not work for all UEFI configurations.<br />
<br />
===Start screen===<br />
<br />
*When enabling Redpill, the start screen may appear to be empty.<br />
*There appears to be an option to "uninstall" the desktop on the start screen. However, selecting that option does nothing.<br />
<br />
===Aero Glass in Starter and Home Basic ===<br />
This build automatically enables Aero Glass transparency even when installing the Starter or Home Basic SKUs, which is not supported by default. However, changing the color scheme (visual style) to another one and then back to the default one will disable Aero Glass.<br />
<br />
=== Redpill ===<br />
In this build's x64 compile the twinui.dll file that is installed by default does not work with this build and will result in a broken system if redpilled. To fix this, run the following command in a command prompt and reboot before running Redlock:<br />
<br />
<code>sfc /SCANFILE=C:\Windows\System32\TWINUI.DLL</code><br />
===[[Windows Setup|Setup]]===<br />
At the end of setup, the message "Setup will continue after restarting your computer" can be displayed displaced.<br />
<br />
==Gallery==<br />
<gallery><br />
7989boot.png|Boot screen<br />
Windows 8 build 7989 OOBE.png|Metro OOBE<br />
Windows8-6.2.7989-Login.png|Lock screen<br />
7989ls.png|Lock screen with the desktop wallpaper as the background<br />
7989login.png|Metro login screen<br />
7989loginlang.png|Language selection on the login screen<br />
7989start.png|Start screen<br />
2nd start screen colour on Windows 8 build 7989.png|Second color on the Start screen<br />
Windows8-6.2.7989-CAD.png|{{key press|Ctrl|Alt|Del}} screen<br />
Windows8-6.2.7989-BSOD.png|System crash<br />
7989charm.png|Charms bar<br />
7989 metro autoplay.png|Autoplay flyout<br />
7989charm2.png|Charms bar with Explorer and Task Manager open<br />
7989charmsettings.png|Settings panel<br />
7989store.png|MS Help<br />
Windows8-6.2.7989.0-NDACat.png|Cat image produced from Share button<br />
Bug-StartScreen.png|Start screen shown empty after enabling Redpill.<br />
Bug-UninstallDesktop.png|Uninstall desktop option on the Start screen.<br />
</gallery><br />
<br />
[[Category:Windows 8 builds]]</div>Ovctvcthttps://betawiki.net/index.php?title=Windows_8_build_7985_(fbl_core1_kernel_cptx.110419-1745)&diff=221034Windows 8 build 7985 (fbl core1 kernel cptx.110419-1745)2022-06-30T08:58:02Z<p>Ovctvct: /* Gallery */</p>
<hr />
<div>{{DISPLAYTITLE:Windows 8 build 7985 (fbl_core1_kernel_cptx.110419-1745)}}<br />
{{Infobox Windows build<br />
|build of = [[Windows 8]]<br />
|image =Windows8-6.2.7985.0.110419-1745-Desktop.png<br />
|buildtag = 6.2.7985.0.fbl_core1_kernel_cptx.110419-1745<br />
|arch = x86<br />
|compiled = 2011-04-19<br />
|timebomb = 2012-03-15<br />
|winver = Windows8-6.2.7985.0.110419-1745-Winver.png<br />
}}<br />
'''Windows 8 build 7985 (fbl_core1_kernel_cptx.110419-1745)''' is a Milestone 3 build of [[Windows 8]], which was shared on 28 June 2022. This build features a new wallpaper with an updated wordoku puzzle.<br />
<br />
== Redpill ==<br />
Continuing on with the evolution of Metro starting with [[Windows 8 build 7978|build 7978]], the unlocked features in this build are a middle ground between the early Milestone 2 Metro of builds [[Windows 8 build 7927|7927]] to [[Windows 8 build 7963|7963]] and the closer to final looks of builds [[Windows 8 build 8032|8032]] and [[Windows 8 build 8056|8056]]. The Start screen now has the "Start" header, along with the Other Programs UI being replaced with the Applications list. The Charms bar now has a clock appear along with it, along with the Settings charm being redesigned, adding some non-functional toggles for the Power, keyboard, and a placeholder toggle called "VanUI", possibly standing for View Active Networks.<br />
<br />
The [[Windows Aero|Aero]] theme is also updated to a more flat and squared theme, resembling the Windows Basic of this build.<br />
<br />
== Bugs ==<br />
*It appears that it is possible to "uninstall" the desktop. However,clicking Uninstall does nothing.<br />
*The Task Manager shows erratic values for the network usage.<br />
*Installing display drivers does not work.<br />
== Compiler ==<br />
This is one of the first builds to be compiled using a new compiler. However, the problems surrounding it at that time resulted in the build becoming unbootable on certain hardware, as the boot loader does not properly function on modern x86 CPUs, namely Intel processors with the AVX instruction set and a select number of AMD CPUs. As a result, a CPU triple fault occurs resulting in either a crash on a hypervisor or a reboot on real hardware.<br />
<br />
Most of the bugs found in this build are a side effect of the new compiler.<br />
<br />
=== Patching winload.exe to run on Intel processors with AVX ===<br />
In order to properly enable SSE instructions for machines using Intel processor with AVX, the 9th bit in Control Register 4 (CR4) must be turned on. The following code is executed and is located in winload.exe at offset A137:<br />
<syntaxhighlight lang="nasm"><br />
mov eax, cr4 ; 0f20e0<br />
or eax, 20h ; 83c820 -- Turn on 5th bit, PAE (Physical Address Extension)<br />
mov cr4, eax ; 0f22e0 -- Store it in CR4<br />
mov eax, cr0 ; 0f20c0<br />
or eax, 80000000h ; 0d00000080 -- Enable paging<br />
mov cr0, eax ; 0f22c0<br />
</syntaxhighlight><br />
<br />
By default the following bits are set in CR0: Protected Mode (PE) (0x00000001), Monitor co-processor (MP) (0x00000002) and Extension type (ET) (0x00000010), with no bits in CR4 set initially, so the need to turn on the 9th SSE bit (i.e. OR with 0x600) should be done, but due to limitation in this piece of code, a rewriting needs to be done and the following approach may be used instead:<br />
<br />
<syntaxhighlight lang="nasm"><br />
mov eax,620h ; b820060000<br />
mov cr4,eax ; 0f22e0<br />
mov eax,80000013h ; b813000080<br />
mov cr0,eax ; 0f22c0<br />
nop ; 90<br />
nop ; 90<br />
nop ; 90<br />
nop ; 90<br />
</syntaxhighlight><br />
<br />
As a disclaimer, patching winload.exe with these changes will invalidate integrity checks and thus requires Test Mode to be enabled (by setting <code>NoIntegrityChecks</code> in the BCD to on) in order to boot with the patched winload.exe, as well as ownership of the file in both <code>%systemroot%\System32</code> and <code>%systemroot%\System32\Boot</code> need to be altered in case file replacement was not possible.<br />
<br />
=== Compatibility ===<br />
==== VMware Workstation ====<br />
For another workaround on the Intel SSE bug that does not involve patching and disabling security checks, the compatibility level must be set to version 7.x or lower in order to boot this build. In addition, the following block of code must be added to the VMX (virtual machine configuration) file in order to allow this build to boot on modern Intel CPUs:<br />
<br />
<syntaxhighlight lang="ini"><br />
cpuid.0.ebx = "0110:1000:0111:0100:0111:0101:0100:0001"<br />
cpuid.0.ecx = "0100:0100:0100:1101:0100:0001:0110:0011"<br />
cpuid.0.edx = "0110:1001:0111:0100:0110:1110:0110:0101"<br />
cpuid.1.eax = "0000:0000:0000:0001:0000:0110:0111:0001"<br />
</syntaxhighlight><br />
<br />
The above configuration is mostly not required if the host machine has an AMD processor, and as such only requires the compatibility version to be changed.<br />
<br />
==Gallery==<br />
<gallery><br />
7985boot.png|Boot screen<br />
File:7985start.png|Start screen<br />
7985charm.png|Charm bar<br />
</gallery><br />
<br />
[[Category:Windows 8 builds]]</div>Ovctvcthttps://betawiki.net/index.php?title=File:7985charm.png&diff=221033File:7985charm.png2022-06-30T08:57:39Z<p>Ovctvct: </p>
<hr />
<div></div>Ovctvcthttps://betawiki.net/index.php?title=Windows_8_build_7985_(fbl_core1_kernel_cptx.110419-1745)&diff=221032Windows 8 build 7985 (fbl core1 kernel cptx.110419-1745)2022-06-30T08:56:57Z<p>Ovctvct: </p>
<hr />
<div>{{DISPLAYTITLE:Windows 8 build 7985 (fbl_core1_kernel_cptx.110419-1745)}}<br />
{{Infobox Windows build<br />
|build of = [[Windows 8]]<br />
|image =Windows8-6.2.7985.0.110419-1745-Desktop.png<br />
|buildtag = 6.2.7985.0.fbl_core1_kernel_cptx.110419-1745<br />
|arch = x86<br />
|compiled = 2011-04-19<br />
|timebomb = 2012-03-15<br />
|winver = Windows8-6.2.7985.0.110419-1745-Winver.png<br />
}}<br />
'''Windows 8 build 7985 (fbl_core1_kernel_cptx.110419-1745)''' is a Milestone 3 build of [[Windows 8]], which was shared on 28 June 2022. This build features a new wallpaper with an updated wordoku puzzle.<br />
<br />
== Redpill ==<br />
Continuing on with the evolution of Metro starting with [[Windows 8 build 7978|build 7978]], the unlocked features in this build are a middle ground between the early Milestone 2 Metro of builds [[Windows 8 build 7927|7927]] to [[Windows 8 build 7963|7963]] and the closer to final looks of builds [[Windows 8 build 8032|8032]] and [[Windows 8 build 8056|8056]]. The Start screen now has the "Start" header, along with the Other Programs UI being replaced with the Applications list. The Charms bar now has a clock appear along with it, along with the Settings charm being redesigned, adding some non-functional toggles for the Power, keyboard, and a placeholder toggle called "VanUI", possibly standing for View Active Networks.<br />
<br />
The [[Windows Aero|Aero]] theme is also updated to a more flat and squared theme, resembling the Windows Basic of this build.<br />
<br />
== Bugs ==<br />
*It appears that it is possible to "uninstall" the desktop. However,clicking Uninstall does nothing.<br />
*The Task Manager shows erratic values for the network usage.<br />
*Installing display drivers does not work.<br />
== Compiler ==<br />
This is one of the first builds to be compiled using a new compiler. However, the problems surrounding it at that time resulted in the build becoming unbootable on certain hardware, as the boot loader does not properly function on modern x86 CPUs, namely Intel processors with the AVX instruction set and a select number of AMD CPUs. As a result, a CPU triple fault occurs resulting in either a crash on a hypervisor or a reboot on real hardware.<br />
<br />
Most of the bugs found in this build are a side effect of the new compiler.<br />
<br />
=== Patching winload.exe to run on Intel processors with AVX ===<br />
In order to properly enable SSE instructions for machines using Intel processor with AVX, the 9th bit in Control Register 4 (CR4) must be turned on. The following code is executed and is located in winload.exe at offset A137:<br />
<syntaxhighlight lang="nasm"><br />
mov eax, cr4 ; 0f20e0<br />
or eax, 20h ; 83c820 -- Turn on 5th bit, PAE (Physical Address Extension)<br />
mov cr4, eax ; 0f22e0 -- Store it in CR4<br />
mov eax, cr0 ; 0f20c0<br />
or eax, 80000000h ; 0d00000080 -- Enable paging<br />
mov cr0, eax ; 0f22c0<br />
</syntaxhighlight><br />
<br />
By default the following bits are set in CR0: Protected Mode (PE) (0x00000001), Monitor co-processor (MP) (0x00000002) and Extension type (ET) (0x00000010), with no bits in CR4 set initially, so the need to turn on the 9th SSE bit (i.e. OR with 0x600) should be done, but due to limitation in this piece of code, a rewriting needs to be done and the following approach may be used instead:<br />
<br />
<syntaxhighlight lang="nasm"><br />
mov eax,620h ; b820060000<br />
mov cr4,eax ; 0f22e0<br />
mov eax,80000013h ; b813000080<br />
mov cr0,eax ; 0f22c0<br />
nop ; 90<br />
nop ; 90<br />
nop ; 90<br />
nop ; 90<br />
</syntaxhighlight><br />
<br />
As a disclaimer, patching winload.exe with these changes will invalidate integrity checks and thus requires Test Mode to be enabled (by setting <code>NoIntegrityChecks</code> in the BCD to on) in order to boot with the patched winload.exe, as well as ownership of the file in both <code>%systemroot%\System32</code> and <code>%systemroot%\System32\Boot</code> need to be altered in case file replacement was not possible.<br />
<br />
=== Compatibility ===<br />
==== VMware Workstation ====<br />
For another workaround on the Intel SSE bug that does not involve patching and disabling security checks, the compatibility level must be set to version 7.x or lower in order to boot this build. In addition, the following block of code must be added to the VMX (virtual machine configuration) file in order to allow this build to boot on modern Intel CPUs:<br />
<br />
<syntaxhighlight lang="ini"><br />
cpuid.0.ebx = "0110:1000:0111:0100:0111:0101:0100:0001"<br />
cpuid.0.ecx = "0100:0100:0100:1101:0100:0001:0110:0011"<br />
cpuid.0.edx = "0110:1001:0111:0100:0110:1110:0110:0101"<br />
cpuid.1.eax = "0000:0000:0000:0001:0000:0110:0111:0001"<br />
</syntaxhighlight><br />
<br />
The above configuration is mostly not required if the host machine has an AMD processor, and as such only requires the compatibility version to be changed.<br />
<br />
==Gallery==<br />
<gallery><br />
7985boot.png|Boot screen<br />
File:7985start.png|Start screen<br />
</gallery><br />
<br />
[[Category:Windows 8 builds]]</div>Ovctvcthttps://betawiki.net/index.php?title=File:7985start.png&diff=221031File:7985start.png2022-06-30T08:56:02Z<p>Ovctvct: </p>
<hr />
<div></div>Ovctvcthttps://betawiki.net/index.php?title=File:7985boot.png&diff=221030File:7985boot.png2022-06-30T08:55:52Z<p>Ovctvct: </p>
<hr />
<div></div>Ovctvcthttps://betawiki.net/index.php?title=Windows_8_build_7985_(fbl_core1_kernel_cptx.110419-1745)&diff=221029Windows 8 build 7985 (fbl core1 kernel cptx.110419-1745)2022-06-30T08:49:05Z<p>Ovctvct: please, don't use 7989 screenshots...</p>
<hr />
<div>{{DISPLAYTITLE:Windows 8 build 7985 (fbl_core1_kernel_cptx.110419-1745)}}<br />
{{Infobox Windows build<br />
|build of = [[Windows 8]]<br />
|image =Windows8-6.2.7985.0.110419-1745-Desktop.png<br />
|buildtag = 6.2.7985.0.fbl_core1_kernel_cptx.110419-1745<br />
|arch = x86<br />
|compiled = 2011-04-19<br />
|timebomb = 2012-03-15<br />
|winver = Windows8-6.2.7985.0.110419-1745-Winver.png<br />
}}<br />
'''Windows 8 build 7985 (fbl_core1_kernel_cptx.110419-1745)''' is a Milestone 3 build of [[Windows 8]], which was shared on 28 June 2022. This build features a new wallpaper with an updated wordoku puzzle.<br />
<br />
== Redpill ==<br />
Continuing on with the evolution of Metro starting with [[Windows 8 build 7978|build 7978]], the unlocked features in this build are a middle ground between the early Milestone 2 Metro of builds [[Windows 8 build 7927|7927]] to [[Windows 8 build 7963|7963]] and the closer to final looks of builds [[Windows 8 build 8032|8032]] and [[Windows 8 build 8056|8056]]. The Start screen now has the "Start" header, along with the Other Programs UI being replaced with the Applications list. The Charms bar now has a clock appear along with it, along with the Settings charm being redesigned, adding some non-functional toggles for the Power, keyboard, and a placeholder toggle called "VanUI", possibly standing for View Active Networks.<br />
<br />
The [[Windows Aero|Aero]] theme is also updated to a more flat and squared theme, resembling the Windows Basic of this build.<br />
<br />
== Bugs ==<br />
*It appears that it is possible to "uninstall" the desktop. However,clicking Uninstall does nothing.<br />
*The Task Manager shows erratic values for the network usage.<br />
*Installing display drivers does not work.<br />
== Compiler ==<br />
This is one of the first builds to be compiled using a new compiler. However, the problems surrounding it at that time resulted in the build becoming unbootable on certain hardware, as the boot loader does not properly function on modern x86 CPUs, namely Intel processors with the AVX instruction set and a select number of AMD CPUs. As a result, a CPU triple fault occurs resulting in either a crash on a hypervisor or a reboot on real hardware.<br />
<br />
Most of the bugs found in this build are a side effect of the new compiler.<br />
<br />
=== Patching winload.exe to run on Intel processors with AVX ===<br />
In order to properly enable SSE instructions for machines using Intel processor with AVX, the 9th bit in Control Register 4 (CR4) must be turned on. The following code is executed and is located in winload.exe at offset A137:<br />
<syntaxhighlight lang="nasm"><br />
mov eax, cr4 ; 0f20e0<br />
or eax, 20h ; 83c820 -- Turn on 5th bit, PAE (Physical Address Extension)<br />
mov cr4, eax ; 0f22e0 -- Store it in CR4<br />
mov eax, cr0 ; 0f20c0<br />
or eax, 80000000h ; 0d00000080 -- Enable paging<br />
mov cr0, eax ; 0f22c0<br />
</syntaxhighlight><br />
<br />
By default the following bits are set in CR0: Protected Mode (PE) (0x00000001), Monitor co-processor (MP) (0x00000002) and Extension type (ET) (0x00000010), with no bits in CR4 set initially, so the need to turn on the 9th SSE bit (i.e. OR with 0x600) should be done, but due to limitation in this piece of code, a rewriting needs to be done and the following approach may be used instead:<br />
<br />
<syntaxhighlight lang="nasm"><br />
mov eax,620h ; b820060000<br />
mov cr4,eax ; 0f22e0<br />
mov eax,80000013h ; b813000080<br />
mov cr0,eax ; 0f22c0<br />
nop ; 90<br />
nop ; 90<br />
nop ; 90<br />
nop ; 90<br />
</syntaxhighlight><br />
<br />
As a disclaimer, patching winload.exe with these changes will invalidate integrity checks and thus requires Test Mode to be enabled (by setting <code>NoIntegrityChecks</code> in the BCD to on) in order to boot with the patched winload.exe, as well as ownership of the file in both <code>%systemroot%\System32</code> and <code>%systemroot%\System32\Boot</code> need to be altered in case file replacement was not possible.<br />
<br />
=== Compatibility ===<br />
==== VMware Workstation ====<br />
For another workaround on the Intel SSE bug that does not involve patching and disabling security checks, the compatibility level must be set to version 7.x or lower in order to boot this build. In addition, the following block of code must be added to the VMX (virtual machine configuration) file in order to allow this build to boot on modern Intel CPUs:<br />
<br />
<syntaxhighlight lang="ini"><br />
cpuid.0.ebx = "0110:1000:0111:0100:0111:0101:0100:0001"<br />
cpuid.0.ecx = "0100:0100:0100:1101:0100:0001:0110:0011"<br />
cpuid.0.edx = "0110:1001:0111:0100:0110:1110:0110:0101"<br />
cpuid.1.eax = "0000:0000:0000:0001:0000:0110:0111:0001"<br />
</syntaxhighlight><br />
<br />
The above configuration is mostly not required if the host machine has an AMD processor, and as such only requires the compatibility version to be changed.<br />
<br />
==Gallery==<br />
<gallery><br />
8008-boot.png|Boot screen<br />
Windows8-6.2.7989-CAD.png|{{key press|Ctrl|Alt|Del}} screen<br />
Windows8-6.2.7989-BSOD.png|System crash<br />
</gallery><br />
<br />
[[Category:Windows 8 builds]]</div>Ovctvcthttps://betawiki.net/index.php?title=Windows_8_build_7985_(fbl_core1_kernel_cptx.110419-1745)&diff=220772Windows 8 build 7985 (fbl core1 kernel cptx.110419-1745)2022-06-29T12:37:07Z<p>Ovctvct: </p>
<hr />
<div>{{Infobox Windows build<br />
|build of = [[Windows 8]]<br />
|image =Windows8-6.2.7985.0.110419-1745-Desktop.png<br />
|buildtag = 6.2.7985.fbl_core1_kernel_cptx.110419-1745<br />
|arch = x86<br />
|compiled = 2011-04-19<br />
}}<br />
'''Windows 8 build 7985''' is a Milestone 3 build of [[Windows 8]]. It was shared on 28 June 2022. This build features a new wallpaper and an updated theme with [[Redpill]] enabled.</div>Ovctvcthttps://betawiki.net/index.php?title=Windows_8_build_7985_(fbl_core1_kernel_cptx.110419-1745)&diff=220771Windows 8 build 7985 (fbl core1 kernel cptx.110419-1745)2022-06-29T12:35:25Z<p>Ovctvct: </p>
<hr />
<div>{{Infobox Windows build<br />
|build of = [[Windows 8]]<br />
|image =Windows8-6.2.7985.0.110419-1745-Desktop.png<br />
|buildtag = 6.2.7985.fbl_core1_kernel_cptx.110419-1745<br />
|arch = x86<br />
|compiled = 2011-04-19<br />
}}<br />
'''Windows 8 build 7985''' is a Milestone 3 build of [[Windows 8]]. It was shared on 28 June 2022.</div>Ovctvcthttps://betawiki.net/index.php?title=Windows_8_build_7985_(fbl_core1_kernel_cptx.110419-1745)&diff=220770Windows 8 build 7985 (fbl core1 kernel cptx.110419-1745)2022-06-29T12:34:13Z<p>Ovctvct: Created page with "{{Infobox Windows build |build of = Windows 8 |image = File:Windows8-6.2.7985.0.110419-1745-Desktop.png |buildtag = 6.2.7985.fbl_core1_kernel_cptx.110419-1745 |arch = x86 |compiled = 2011-04-19 }} '''Windows 8 build 7985''' is a Milestone 3 build of Windows 8. It was shared on 28 June 2022."</p>
<hr />
<div>{{Infobox Windows build<br />
|build of = [[Windows 8]]<br />
|image = File:Windows8-6.2.7985.0.110419-1745-Desktop.png<br />
|buildtag = 6.2.7985.fbl_core1_kernel_cptx.110419-1745<br />
|arch = x86<br />
|compiled = 2011-04-19<br />
}}<br />
'''Windows 8 build 7985''' is a Milestone 3 build of [[Windows 8]]. It was shared on 28 June 2022.</div>Ovctvcthttps://betawiki.net/index.php?title=Windows_8&diff=220442Windows 82022-06-28T10:56:43Z<p>Ovctvct: /* Interface */</p>
<hr />
<div>{{Infobox Windows version<br />
|name = Windows 8<br />
|logo = Windows 8 logo and wordmark.svg<br />
|codename = Windows 8<br />
|image = Windows8-RTM-Desktop.png<br />
|family = nt<br />
|version = 6.2<br />
|arch = x86, x64, ARM32<br />
|latestbuild = [[Windows 8 build 9200 (win8_rtm)|6.2.9200.16384]]<br />
|releasedate = 2012-10-26<br />
|support = 2016-01-12<br />
|server = [[Windows Server 2012]]<br />
|replaces = [[Windows 7]]<br />
|replaced-by = [[Windows 8.1]]<br />
}}<br />
<br />
'''Windows 8''' is an operating system developed by Microsoft. It is the ninth major release in the Windows NT operating system line, replacing [[Windows 7]] and being later replaced by [[Windows 8.1]]. It reached RTM on 1 August 2012 and was released to general availability on 26 October 2012. Windows 8 was one of the most short-lived releases, and its support ended on 12 January 2016, as extended support was in favor of Windows 8.1. Despite of this, it still runs on 1.22% of desktop and laptop computers as of <br />
April 2022.<ref>https://gs.statcounter.com/windows-version-market-share/desktop/worldwide/</ref><br />
<br />
This is the first version of Windows to drop support for processors without PAE, SSE2 and NX, as running on these processors will display a black screen with error code 0x05D, and is the last version of 64-bit Windows to support processors without the CMPXCHG16b, PrefetchW and LAHF/SAHF instructions.<br />
<br />
It is the first client release of Windows to drop the traditional Service Pack mechanism in favor of releasing updates in smaller chunks on a continual basis.<br />
<br />
== Editions ==<br />
Windows 8 comes in the following editions:<br />
* '''Windows 8''' (also known as Core) is the base edition intended for the average home user.<br />
** '''Windows RT''' is a version of Windows 8 for ARM-based tablets. Compared to other editions, it can only launch applications that either originate from the Windows Store or were digitally signed by Microsoft. It is functionally identical to the aforementioned Core edition.<br />
** '''Windows 8 Single Language''' is same as Core but limited to a single installed language pack.<br />
** '''Windows 8 China''' (also known as Core Country Specific) is same as Single Language but only allows the Simplified Chinese language pack to be installed. This is a special variant targeting the mainland China market.<br />
* '''Windows 8 Pro''' is targeted at enthusiast and business markets. Compared to Core, it adds the ability to run Hyper-V virtual machines, receive RDP connections and BitLocker support.<br />
** '''Windows 8 Pro with Media Center''' is a variant of Pro that also includes the Windows Media Center.<br />
* '''Windows 8 Enterprise''' is designed for large organizations and can only be activated with a KMS server or MAK keys. It has the same feature set as Pro but supports creating [https://en.wikipedia.org/wiki/Windows%20To%20Go Windows To Go] portable workspaces.<br />
<br />
== Main changes ==<br />
=== Interface ===<br />
Windows 8 was largely designed for use on touchscreen devices such as tablets, and this can be seen all across the OS, with includes bigger buttons, more distinct colors, and a more modern interface with the removal of [[Windows Aero|Aero]] transparency on open windows. The taskbar is still transparent, even though it doesn't blur anything behind it anymore. The renewal of the classic Windows shell was accompanied by the addition of the Metro interface, which includes a new Start menu (named Start screen), with a full-screen UI replacing the smaller Start menu first introduced in [[Windows 95]]. From the Start screen, Metro apps can be launched, which can take the entire screen, providing an immersive interface, or be snapped to a side of the screen alongside another application or the desktop. The File Explorer also got a renewal, with the introduction of the Ribbon UI first seen in [[Windows 7]]. The Up button, which was absent by default or unavailable since [[Windows Longhorn build 3670]] (except for early Vista post-reset builds like [[Windows Vista build 3790.1232|build 3790.1232]] and [[Windows Vista build 5001|build 5001]]), has been readded and the details pane is now vertical.<br />
<br />
The Metro UI is directly integrated with the desktop, which features hot corners: positioning the mouse in certain parts of the screen will reveal new functionality. The right side features the Charms Bar, a vertical bar that includes Search, Share, Start, Devices, and Settings as buttons. Right-clicking on the bottom left corner of the screen opens the Quick Link menu, which contains shortcuts to frequently used areas.<br />
<br />
Windows 8 was the first Windows operating system ever since [[Windows NT 3.51]] to have no Start button. Although the last build of Windows 8 to have the Start button by default was [[Windows 8 build 8176|8176]], it is possible to remove the Start button from the taskbar, on builds [[Windows 8 build 7899|7899]] to [[Windows 8 build 8102|8102]]. To accomplish this, you need to make a new DWORD in <code>HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer</code> called <code>YouBettaHideYoPearl</code>, with its value set to 1. After doing so, log off and log back in. If done correctly, the Start button should be removed.<br />
<br />
[[Desktop Window Manager]] now renders using a software-based 3D rasterizer when such an accelerator is unavailable. Additionally, the [[Windows Classic]] and [[Windows Basic]] themes have been removed. Although the visual styles still exist, they cannot be enabled by default unless the user modifies the system files.<br />
<br />
Progress windows have been modified to remove the animation on the top and make it possible to view "more details", including a graph for tracking transfer speeds. It is also possible to pause file transfer operations.<br />
<br />
Notifications have been updated to be more noticeable, as they appear on the right of the screen and are the same color as the current theme.<br />
<br />
=== Task Manager ===<br />
The [[Task Manager]] now opens up in a simple view which only displays a list of open programs and not processes. Expanding the view reveals a modernized and improved version of the classic Task Manager, featuring tabs and a bigger focus on memory usage.<br />
<br />
=== Windows Store ===<br />
[[Microsoft Store|Windows Store]] allows the consumer to distribute and download Metro apps or advertise desktop software. The Windows Store would later be redesigned in [[Windows 8.1]]. The Store was called "MSHelp" in builds before 8032. The Windows Store would later be rebranded as the Microsoft Store in September 2017 as an update for [[Windows 10]].<br />
<br />
=== Media Center ===<br />
Unlike [[Windows Vista]] and [[Windows 7]], [[Windows Media Center]] is not included by default in any Windows 8 edition. Customers with existing Windows 8 Pro licenses can purchase Media Center with the Windows 8 Pro Pack, which was free previously under a promotional offer (until 31 January 2013).<br />
<br />
=== Display language support ===<br />
Microsoft offered 109 display languages in Windows 8,<ref>Sinofsky, Steven. [https://blogs.msdn.microsoft.com/b8/2012/02/21/using-the-language-you-want/ Using the language you want], ''Building Windows 8''. 21 February 2012. [https://web.archive.org/web/20191226205555/https://blogs.msdn.microsoft.com/b8/2012/02/21/using-the-language-you-want/ Archived] from the original on 26 December 2019.</ref> 14 more than Windows 7, adding the following localizations:<br />
<br />
*English (United Kingdom)<br />
*Punjabi (Pakistan)<br />
*Sindhi (Pakistan)<br />
*Central Kurdish (Iraq)<br />
*Uyghur (People's Republic of China)<br />
*Belarusian (Belarus)<br />
*Kinyarwanda (Rwanda)<br />
*Tigrinya (Ethiopia)<br />
*Tajik (Tajikistan)<br />
*Wolof (Senegal)<br />
*K'iche' (Guatemala)<br />
*Scottish Gaelic (United Kingdom)<br />
*Cherokee (United States)<br />
*Valencian (Spain)<br />
<br />
==Startup sound==<br />
There is a widespread misconception that Windows 8 as well as 8.1 uses [https://www.youtube.com/watch?t=167&v=MJ2Y4K5fgVM&feature=youtu.be this sound] as the startup sound. However, this sound is Windows Logon.wav in <code>%SystemRoot%\Media</code>, but goes unused and isn't the startup sound. In reality, the [[Windows Vista]] startup sound remains in Windows 8, 8.1, and 10, but it's disabled by default. To enable the startup sound:<br />
:1. Right-click the volume tray icon, then click Sounds.<br />
:2. Check "Play Windows startup sound", then click Apply.<br />
:3. Navigate to Control Panel → System and Security → Power Options, click "Choose what the power buttons do" in the left bar.<br />
:4. Click "Change settings that are currently unavailable", then uncheck "Turn on fast startup (recommended)", then click OK.<br />
<br />
Another way to disable fast startup is running <code>powercfg -h off</code> as administrator.<br />
<br />
The actual startup is embedded in <code>%SystemRoot%\System32\imageres.dll</code>, which needs a third-party software tool like Resource Hacker to view its resources. This is also in Windows Vista and 7 and persists up to [[Windows 10 October 2018 Update]] ([[Windows 10 May 2019 Update|May 2019 Update]], and up relocated the resources of imageres.dll to <code>%SystemRoot%\SystemResources\imageres.dll.mun</code>).<br />
<br />
== List of known builds ==<br />
{{builds legend}}<br />
=== Milestone 1 ===<br />
{{BLItem Confirmed|Windows 8 build 7652|7652}}<br />
{{BLItem Unconfirmed|Windows 8 build 7680|7680.0.winmain.091124-1740}}<br />
{{BLItem Leaked|Windows 8 build 7700|7700.0.winmain.100122-1900}}<br />
{{BLItem Leaked|Windows 8 build 7746|7746.0.fbl_grfx.100428-2024}}<br />
{{BLItem Confirmed|Windows 8 build 7758|7758.0.winmain.100604-1503}}<br />
{{BLItem Confirmed|Windows 8 build 7775|7775.0.winmain.100706-1910}}<br />
{{BLItem Leaked|Windows 8 build 7777|7777.0.fbl_grfx.100708-2000}}<br />
{{BLItem Leaked|Windows 8 build 7779|7779.0.fbl_grfx_dev1.100713-1700}}<br />
{{BLItem Unconfirmed|Windows 8 build 7788|7788.fbl_uex_cxe_dev}}<br />
{{BLItem Unconfirmed|Windows 8 build 7791|7791}}<br />
{{BLItem Confirmed|Windows 8 build 7792|7792}}<br />
{{BLItem Confirmed|Windows 8 build 7793|7793.0.fbl_grfx.100804-2000}}<br />
{{BLItem Confirmed|Windows 8 build 7811|7811.0.fbl_dnt1_net2_virtual.100901-1700}}<br />
{{BLItem Leaked|Windows 8 build 7814|7814.0.fbl_core1_kernel_ee.100907-1700}}<br />
{{BLItem Confirmed|Windows 8 build 7817|7817.0.winmain.100910-1622}}<br />
{{BLItem Confirmed|Windows 8 build 7830|7830}}<br />
{{BLItem Leaked|Windows 8 build 7850|7850.0.winmain_win8m1.100922-1508}}<br />
<br />
=== Milestone 2 ===<br />
{{BLItem Confirmed|Windows 8 build 7867|7867}}<br />
{{BLItem Unconfirmed|Windows 8 build 7871|7871}}<br />
{{BLItem Confirmed|Windows 8 build 7874|7874.0.fbl_dnt1.101031-2000}}<br />
{{BLItem Leaked|Windows 8 build 7875|7875.0.fbl_grfx_dev1.101102-1700}}<br />
{{BLItem Leaked|Windows 8 build 7878|7878.0.winmain.101104-1752}}<br />
{{BLItem Leaked|Windows 8 build 7880|7880.0.fbl_grfx_dev1.101110-1700}}<br />
{{BLItem Confirmed|Windows 8 build 7885|7885.0.fbl_fun_eco_platforms.101116-1907}}<br />
{{BLItem Confirmed|Windows 8 build 7898|7898}}<br />
{{BLItem Leaked|Windows 8 build 7899|7899.0.fbl_core2_sfs.101209-1900}}<br />
{{BLItem Confirmed|Windows 8 build 7900|7900}}<br />
{{BLItem Confirmed|Windows 8 build 7901|7901.FBL_UEX_ICP.101213-1800}}<br />
{{BLItem Unconfirmed|Windows 8 build 7910|7910.winmain.110111-1804}}<br />
{{BLItem Confirmed|Windows 8 build 7927 (fbl_srv)|7927.0.fbl_srv.110210-1753}}<br />
{{BLItem Leaked|Windows 8 build 7927 (fbl_srv_wdacxml)|7927.0.fbl_srv_wdacxml.110214-1930}}<br />
{{BLItem Confirmed|Windows 8 build 7947|7947.0}}<br />
{{BLItem Confirmed|Windows 8 build 7950|7950.0.winmain_win8m2.110223-1820}}<br />
<br />
=== Milestone 3 ===<br />
{{BLItem Leaked|Windows 8 build 7955|7955.0.fbl_srv_wdacxml.110228-1930}}<br />
{{BLItem Confirmed|Windows 8 build 7957|7957}}<br />
{{BLItem Unconfirmed|Windows 8 build 7959|7959}}<br />
{{BLItem Confirmed|Windows 8 build 7962 (fbl_srv)|7962.0.fbl_srv.110309-1807}}<br />
{{BLItem Leaked|Windows 8 build 7962 (fbl srv wdacxml)|7962.0.fbl_srv_wdacxml.110311-1930}}<br />
{{BLItem Leaked|Windows 8 build 7963|7963.0.winmain.110310-1721}}<br />
{{BLItem Confirmed|Windows 8 build 7969|7969}}<br />
{{BLItem Confirmed|Windows 8 build 7971|7971.0.winmain.110324-1900}}<br />
{{BLItem Unconfirmed|Windows 8 build 7973 (winmain)|7973.winmain.110329-1742}}<br />
{{BLItem Leaked|Windows 8 build 7973 (fbl_core2_sid_data)|7973.0.fbl_core2_sid_data.110330-1700}}<br />
{{BLItem Leaked|Windows 8 build 7973 (fbl_grfx_dev1)|7973.0.fbl_grfx_dev1.110330-1700}}<br />
{{BLItem Leaked|Windows 8 build 7973 (fbl dnt3 wireless)|7973.0.fbl_dnt3_wireless.110330-1800}}<br />
{{BLItem Leaked|Windows 8 build 7973 (fbl_core1_kernel_npc)|7973.0.fbl_core1_kernel_npc.110330-1809}}<br />
{{BLItem Unconfirmed|Windows 8 build 7976|7976.winmain.110401-1700}}<br />
{{BLItem Leaked|Windows 8 build 7978|7978.0.fbl_grfx_dev1.110406-1700}}<br />
{{BLItem Confirmed|Windows 8 build 7978 (?)|7978.0.110405-1746}}<br />
{{BLItem Confirmed|Windows 8 build 7979|7979.0.110406-1800}}<br />
{{BLItem Confirmed|Windows 8 build 7982|7982.0.winmain.110411-1832}}<br />
{{BLItem Confirmed|Windows 8 build 7985|7985.fbl_core1_kernel_cptx.110503-1501}}<br />
{{BLItem Leaked|Windows 8 build 7989|7989.0.winmain.110421-1825}}<br />
{{BLItem Unconfirmed|Windows 8 build 7992|7992.fbl_srv_wdacxml.110425-1921}}<br />
{{BLItem Confirmed|Windows 8 build 7996|7996.0.fbl_pac_dev2.110504-2214}}<br />
{{BLItem Leaked|Windows 8 build 7997|7997.0.fbl_dnt3_wireless.110504-2014}}<br />
{{BLItem Leaked|Windows 8 build 8002 (fbl_grfx_dev1)|8002.0.fbl_grfx_dev1.110511-1700}}<br />
{{BLItem Leaked|Windows 8 build 8002 (fbl_dnt3_wireless)|8002.0.fbl_dnt3_wireless.110511-1800}}<br />
{{BLItem Leaked|Windows 8 build 8008|8008.0.fbl_dnt3_wireless.110518-1900}}<br />
{{BLItem Unconfirmed|Windows 8 build 8011|8011.winmain.110520-1745}}<br />
{{BLItem Confirmed|Windows 8 build 8013|8013}}<br />
{{BLItem Leaked|Windows 8 build 8014|8014.0.fbl_grfx_dev1.110525-1700}}<br />
{{BLItem Confirmed|Windows 8 build 8027|8027}}<br />
{{BLItem Leaked|Windows 8 build 8032|8032.0.fbl_core2_sid_data.110623-2054}}<br />
{{BLItem Leaked|Windows 8 build 8045|8045.0.fbl_grfx_dev1.110713-1730}}<br />
{{BLItem Unconfirmed|Windows 8 build 8049 (fbl_eeap)|8049.fbl_eeap.110718-0510}}<br />
{{BLItem Unconfirmed|Windows 8 build 8049 (fbl_core2_sid_data)|8049.0.fbl_core2_sid_data.110718-0600}}<br />
{{BLItem Confirmed|Windows 8 build 8056 (winmain)|8056.winmain.110726-1851}}<br />
{{BLItem Leaked|Windows 8 build 8056 (fbl_dnt2_bus)|8056.0.fbl_dnt2_bus.110727-1700}}<br />
{{BLItem Leaked|Windows 8 build 8056 (fbl_grfx_dev1)|8056.0.fbl_grfx_dev1.110727-1728}}<br />
{{BLItem Leaked|Windows 8 build 8056 (fbl_dnt3_wireless)|8056.0.fbl_dnt3_wireless.110727-1800}}<br />
{{BLItem Confirmed|Windows 8 build 8057|8057.winmain.110727-1845}}<br />
{{BLItem Confirmed|Windows 8 build 8059|8059.winmain.110729-1857}}<br />
{{BLItem Leaked|Windows 8 build 8064|8064.0.fbl_eeap.110806-1000}}<br />
{{BLItem Confirmed|Windows 8 build 8065|8065}}<br />
{{BLItem Confirmed|Windows 8 build 8069|8069.winmain.110816-1802}}<br />
{{BLItem Confirmed|Windows 8 build 8090|8090.0}}<br />
{{BLItem Confirmed|Windows 8 build 8095|8095.winmain_win8m3.110812-1840}}<br />
{{BLItem Confirmed|Windows 8 build 8100|8100.0.winmain_win8m3.110819-1727}}<br />
{{BLItem Confirmed|Windows 8 build 8101|8101.winmain_win8m3.110822-1905}}<br />
{{BLItem Leaked|Windows 8 build 8102.101#Updates|8102.0.winmain_win8m3.110823-1455}}<br />
{{BLItem Confirmed|Windows 8 build 8102 (winmain_win8m3_d)|8102.0.winmain_win8m3_d.110908-1930}}<br />
{{BLItem Leaked|Windows 8 build 8102 (winmain_win8m3_eeap)|8102.0.winmain_win8m3_eeap.110824-1030}}<br />
{{BLItem Leaked|Windows 8 build 8102.101|8102.101.winmain_win8m3.110830-1739}}<br />
<br />
=== Consumer Preview ===<br />
{{BLItem Confirmed|Windows 8 build 8108|8108.fbl_dnt2_wipdc.110902-1700}}<br />
{{BLItem Confirmed|Windows 8 build 8112|8112.0.winmain.110909-1742}}<br />
{{BLItem Leaked|Windows 8 build 8118|8118.fbl_core2_sfs.110921-1900}}<br />
{{BLItem Unconfirmed|Windows 8 build 8121|8121.winmain.110922-1933}}<br />
{{BLItem Leaked|Windows 8 build 8128|8128.fbl_core1_soc_partner.111005-1916}}<br />
{{BLItem Confirmed|Windows 8 build 8128 (winmain)|8128.0.winmain.1110??}}<br />
{{BLItem Confirmed|Windows 8 build 8130|8130.winmain.111006-1907}}<br />
{{BLItem Leaked|Windows 8 build 8133 (fbl_grfx_dev1)|8133.fbl_grfx_dev1.111012-1400}}<br />
{{BLItem Leaked|Windows 8 build 8133 (fbl_core2_sid_data)|8133.fbl_core2_sid_data.111012-1700}}<br />
{{BLItem Leaked|Windows 8 build 8133 (fbl_dnt2_bus)|8133.fbl_dnt2_bus.111012-1700}}<br />
{{BLItem Leaked|Windows 8 build 8133 (fbl_core2_sfs)|8133.fbl_core2_sfs.111012-1900}}<br />
{{BLItem Leaked|Windows 8 build 8133 (fbl_dnt3_wireless)|8133.fbl_dnt3_wireless.111012-1902}}<br />
{{BLItem Leaked|Windows 8 build 8140|8140.0.winmain.111020-1857}}<br />
{{BLItem Leaked|Windows 8 build 8148|8148.0.winmain.111103-1846}}<br />
{{BLItem Leaked|Windows 8 build 8155|8155.0.fbl_dnt3_wireless.111116-2000}}<br />
{{BLItem Confirmed|Windows 8 build 8156|8156.0.fbl_core1_soc.111117-1700}}<br />
{{BLItem Unconfirmed|Windows 8 build 8158|8158.0.winmain.111118-2210}}<br />
{{BLItem Leaked|Windows 8 build 8161|8161.0.winmain.111128-1254}}<br />
{{BLItem Confirmed|Windows 8 build 8165 (fbl_core2_sfs_dev2)|8165.fbl_core2_sfs_dev2.111203-22??}}<br />
{{BLItem Confirmed|Windows 8 build 8165|8165.fbl_fun_resp.111205-2000}}<br />
{{BLItem Unconfirmed|Windows 8 build 8172|8172.0.fbl_dnt2_bus.111214-1750}}<br />
{{BLItem Unconfirmed|Windows 8 unknown December 2011 build|817x}}<br />
{{BLItem Confirmed|Windows 8 build 8175|8175.fbl_dev_dp4.111216-2019}}<br />
{{BLItem Leaked|Windows 8 build 8176|8176.fbl_core2_sid_dev.120104-2026}}<br />
{{BLItem Unconfirmed|Windows 8 build 8180|8180.0.winmain.120109-1245}}<br />
{{BLItem Confirmed|Windows 8 build 8186|8186.winmain.120117-1707}}<br />
{{BLItem Confirmed|Windows 8 build 8192|8192.winmain.120125-1820}}<br />
{{BLItem Confirmed|Windows 8 build 8194|8194.winmain.120127-1917}}<br />
{{BLItem Leaked|Windows 8 build 8195|8195.fbl_dnt3_wireless.120201-1800}}<br />
{{BLItem Confirmed|Windows 8 build 8220|8220}}<br />
{{BLItem Confirmed|Windows 8 build 8225|8225.0.winmain_win8beta.120203-1918}}<br />
{{BLItem Leaked|Windows 8 build 8250|8250.0.winmain_win8beta.120217-1520}}<br />
<br />
=== Release Preview ===<br />
{{BLItem Leaked|Windows 8 build 8277|8277.fbl_dnt2_bus.120208-1700}}<br />
{{BLItem Unconfirmed|Windows 8 build 8302|8302.0.fbl_core1_soc.120319-1700}}<br />
{{BLItem Leaked|Windows 8 build 8305 (fbl dnt3 wireless)|8305.fbl_dnt3_wireless.120321-1800}}<br />
{{BLItem Leaked|Windows 8 build 8305 (fbl grfx dev1)|8305.fbl_grfx_dev1.120321-1830}}<br />
{{BLItem Leaked|Windows 8 build 8305 (fbl core2 sfs)|8305.fbl_core2_sfs.120321-1900}}<br />
{{BLItem Unconfirmed|Windows 8 build 8306|8306}}<br />
{{BLItem Confirmed|Windows 8 build 8309|8309.winmain.120327-1901}}<br />
{{BLItem Confirmed|Windows 8 build 8318|8318.fbl_core1_soc.120409-2355}}<br />
{{BLItem Leaked|Windows 8 build 8330 (fbl woa)|8330.0.fbl_woa.120424-2227}}<br />
{{BLItem Leaked|Windows 8 build 8330 (fbl grfx dev1)|8330.0.fbl_grfx_dev1.120425-1400}}<br />
{{BLItem Leaked|Windows 8 build 8330 (fbl ie longhorn)|8330.0.fbl_ie_longhorn.120425-2121}}<br />
{{BLItem Confirmed|Windows 8 build 8331 (winmain)|8331.0.winmain.120425-1916}}<br />
{{BLItem Leaked|Windows 8 build 8331 (fbl_loc)|8331.0.fbl_loc.120425-2034}}<br />
{{BLItem Unconfirmed|Windows 8 build 8331 (fbl_uex)|8331.fbl_uex.120425}}<br />
{{BLItem Confirmed|Windows 8 build 8333|8333.0.winmain.120428-1320}}<br />
{{BLItem Unconfirmed|Windows 8 build 8370|8370.winmain_win8rc.120428-1335}}<br />
{{BLItem Leaked|Windows 8 build 8375|8375.0.winmain_win8rc.120504-1900}}<br />
{{BLItem Confirmed|Windows 8 build 8377|8377.0.winmain_win8rc.120507-1903}}<br />
{{BLItem Confirmed|Windows 8 build 8382|8382.0}}<br />
{{BLItem Confirmed|Windows 8 build 8383|8383.0}}<br />
{{BLItem Leaked|Windows 8 build 8400|8400.0.winmain_win8rc.120518-1423}}<br />
<br />
=== Pre-RTM ===<br />
{{BLItem Confirmed|Windows 8 build 8422 (winmain)|8422.0.winmain.120524-1848}}<br />
{{BLItem Leaked|Windows 8 build 8422 (fbl woa)|8422.0.fbl_woa.120524-2000}}<br />
{{BLItem Confirmed|Windows 8 build 8422 (fbl core1 soc partner)|8422.fbl_core1_soc_partner.120525-1923}}<br />
{{BLItem Leaked|Windows 8 build 8423|8423.fbl_loc.120528-2000}}<br />
{{BLItem Confirmed|Windows 8 build 8424 (winmain)|8424.winmain.120529-1855}}<br />
{{BLItem Confirmed|Windows 8 build 8424 (fbl_woa_drop)|8424.fbl_woa_drop.120530-2000}}<br />
{{BLItem Confirmed|Windows 8 build 8431|8431.fbl_uex.120609-2000}}<br />
{{BLItem Unconfirmed|Windows 8 build 8432 (winmain)|8432.winmain.120611-1243}}<br />
{{BLItem Leaked|Windows 8 build 8432 (fbl loc)|8432.0.fbl_loc.120611-2000}}<br />
{{BLItem Confirmed|Windows 8 build 8432 (fbl_woa)|8432.0.fbl_woa.120611-2000}}<br />
{{BLItem Unconfirmed|Windows 8 build 8437|8437.0.winmain.120618-1325}}<br />
{{BLItem Leaked|Windows 8 build 8438|8438.fbl_ie_longhorn.120620-2000}}<br />
{{BLItem Leaked|Windows 8 build 8441|8441.0.winmain.120623-1614}}<br />
{{BLItem Confirmed|Windows 8 build 8508|8508.0.win8_rtm.120703-1900}}<br />
{{BLItem Confirmed|Windows 8 build 8509|8509.0.fbl_eeap.120708-0952}}<br />
{{BLItem Leaked|Windows 8 build 8513 (win8_gdr_soc_intel)|8513.0.win8_gdr_soc_intel.120710-2000}}<br />
{{BLItem Leaked|Windows 8 build 8513 (win8_gdr_soc_nv)|8513.0.win8_gdr_soc_nv.120710-2000}}<br />
{{BLItem Leaked|Windows 8 build 8513 (win8_gdr_soc_ti)|8513.0.win8_gdr_soc_ti.120710-2000}}<br />
{{BLItem Leaked|Windows 8 build 8518|8518.0.win8_gdr_soc_nv.120718-0003}}<br />
{{BLItem Leaked|Windows 8 build 8520|8520.0.fbl_eeap.120722-1632}}<br />
{{BLItem Confirmed|Windows 8 build 8523|8523.0.win8_rtm.120723-1815}}<br />
<br />
=== RTM Escrow ===<br />
{{BLItem Leaked|Windows 8 build 8888 (win8_gdr_soc_intel)|8888.16384.win8_gdr_soc_intel.120724-2000}}<br />
{{BLItem Leaked|Windows 8 build 8888 (win8_gdr_soc_ti)|8888.16384.win8_gdr_soc_ti.120724-2000}}<br />
{{BLItem Leaked|Windows 8 build 8888 (win8_gdr_soc_nv)|8888.16384.win8_gdr_soc_nv.120724-2107}}<br />
<br />
=== RTM ===<br />
{{BLItem Leaked|Windows 8 build 9200 (win8_rtm)|9200.16384.win8_rtm.120725-1247}}<br />
<br />
=== Post-RTM ===<br />
{{BLItem Leaked|Windows 8 build 9200 (win8_gdr_soc_ti)|9200.16384.win8_gdr_soc_ti.120725-2000}}<br />
{{BLItem Leaked|Windows 8 build 9200 (win8_gdr_soc_intel)|9200.16384.win8_gdr_soc_intel.120726-2000}}<br />
{{BLItem Leaked|Windows 8 build 9200 (win8_gdr_soc_nv)|9200.16384.win8_gdr_soc_nv.120726-2000}}<br />
{{BLItem Unconfirmed|Windows 8 build 9200.16456|9200.16456.win8_gdr_soc_intel.121112-2000}}<br />
<br />
==References==<br />
<references /><br />
{{Microsoft Windows}}<br />
[[Category:Windows versions]]<br />
[[Category:Versions of Microsoft Windows|8]]</div>Ovctvcthttps://betawiki.net/index.php?title=Redlock&diff=220396Redlock2022-06-28T08:49:02Z<p>Ovctvct: </p>
<hr />
<div>{{Infobox software<br />
| name = Redlock<br />
| logo = Redlock Icon.png<br />
| image = Redlock.png<br />
| imagecaption = Redlock running on [[Windows 8 build 8056]]<br />
| developer = lucasm and gus33000<br />
| os = Windows 8 builds from [[Windows 8 build 7779|build 7779]] to [[Windows 8 build 8121|build 8121]]<br />
| lr-version = 2020.12.31.86-9<br />
| lr-date = 2020-12-31<br />
| link = [https://cdn.discordapp.com/attachments/730486372808392804/794136955301396500/redlockT86-9.7z Redlock download link]<br />
}}<br />
'''Redlock''' is a tool developed by BetaWiki members and software developers lucasm and gus33000. The initial version was released on 29 January 2020. Its main goal is to replicate Microsoft's original Redpill implementation as closely as possible. It is in active development. Unlike the other enablers [[RedPill Enabler]] and [[Metro Unlocker]], the installer is completely text-based and written in C#.<br />
<br />
While the practice of disabling the Software Protection Service is still present, it differs in a multitude of areas. To keep the footprint minimal, the tool ships with only one shsxs.dll per architecture. The DLL's contents as well as registry and file tweaks performed upon installation are tailored on the fly, greatly improving compatibility. DISM is used to install the Immersive Browser. Unlike other unlock tools, Redlock's shsxs.dll has been built from scratch and is available as an open source project.<ref>https://github.com/thebookisclosed/shsxs</ref> Prior to this tool's release, it was common to borrow the one found in [[Windows 8 build 8102.101|Windows Developer Preview]].<br />
<br />
To demonstrate the accent capabilities of various early builds, it includes a copy of the [[Windows 8 build 8102.101|Windows Developer Preview]] accent modified in order to be colorizable on builds that support it. Redlock is notable for being the first Redpill tool to include support for builds before [[Windows 8 build 7927|7927]].<br />
<br />
Compared to the previous third party tools, Redlock has become the preferred tool for unlocking Metro due to its compact size, broader compatibility, and cleaner method of enabling the features.<br />
<br />
==Warning==<br />
Uninstalling Redlock in builds newer than [[Windows 8 build 8121|build 8121]] will cause a [[bugcheck]] with a <code>IRQL_NOT_LESS_OR_EQUAL</code>.<br />
<br />
==References==<br />
<references></references><br />
<br />
[[Category:Windows 8 Redpill unlockers]]<br />
[[Category:Community projects]]</div>Ovctvct