User talk:EvoAndОбзорщик

Language

Please consider using English in your future edit summaries so that people can more easily understand what you're saying. Overdoze (talk) 11:36, 29 October 2022 (UTC)

Good, I will try write in English... EvoAndОбзорщик (talk) 09:32, 13 July 2023 (UTC)

A feedback

The language that you are using is Russian, which is the rest of this wiki user don't know. I think can you please spend some time to learn English before contribute again? —— Preceding SIGNED comment added by insomnia {{ talk • contribs • email me }} 11:49, 29 October 2022 (UTC) (last updated on 10:31, 10 November 2022 (UTC))

(translate):Язык, который вы используете, — русский, которого остальные пользователи вики не знают. Я думаю, не могли бы вы потратить немного времени на изучение английского, прежде чем снова внести свой вклад?

Builds Windows Longhorn

I don't understand some things.. Why are windows longhorn builds that are found in other vista builds as separate files, programs, and program extensions not accepted as potential non-expired windows Longhorn builds? EvoAndОбзорщик (talk) 09:12, 13 July 2023 (UTC)

They are not notable 37.231.218.129 09:17, 13 July 2023 (UTC)

To be exact, .NET file versions do not count. NaraInsider1694 (talk) 09:20, 13 July 2023 (UTC)

Ok... And what about build 4026. What didn't suit there because the build tag was already present there? EvoAndОбзорщик (talk) 09:30, 13 July 2023 (UTC)

Windows longhorn 4060

All hi! I just now detect files Windows longhorn build 4060. These files are mentioned in build 4093. Here is his tag: 6.0.4060.0 built by: private/Lab06_dev(skatari). EvoAndОбзорщик (talk) 09:58, 13 July 2023 (UTC)

Path: %Windir%\WINDOWS\System32 Files: BRCOINST.DLL, hpgt21/33/42tk.dll, hpgtmcro.dll, hpojwia.dll, hpsjmcro.dll EvoAndОбзорщик (talk) 10:03, 13 July 2023 (UTC)

File versions are not notable, and driver versions like these almost certainly do not correspond in any meaningful way to an actual build of Windows. Hounsell (talk) 10:55, 13 July 2023 (UTC)

windows build 3680

Happy Metallurgist's Day to everyone! Going through the windows longhorn 4029 lab06 files, I found in the file cnbjmon.dll mention of a certain build of Windows 5.2.3680.0 (Lab03_dev(skatari).020509-1043). What kind of windows do you think it belongs to? — Preceding unsigned comment added by EvoAndОбзорщик (talk • contribs)

As I expected, another non-notable build that is only mentioned in one file. NaraInsider1694 (talk) 08:44, 16 July 2023 (UTC)

Warning

Looking over your previous edits, we appreciate your efforts to improve BetaWiki. However, we are unable to deem these contributions as acceptable for the following reasons:

• Bad grammar and mechanics. I understand that you may not be a native speaker of English but take the effort to improve it.
• Adding non-notable builds based on file versions or stock references in source code files. Please review the Guidelines to see what we deem as notable and what not. Not every single build with a reference is worth adding here.

This is a warning to ensure that you improve your edits. Failure to comply can result in being unable to edit the pages for a period of time. BF10 (talk) 12:22, 21 July 2023 (UTC)

Then what's the point of introducing new information about some builds? You might as well cut out a significant chunk of the entire site... EvoAndОбзорщик (talk) 18:33, 21 July 2023 (UTC)

"what's the point of introducing new information about some builds"... So if a file has a version close to a Windows build number, to you that means it's an unleaked build... Do you actually realise that this wiki would be bloated to death with all of them? Half of the wiki would just be "version x.x.xxxx.x found in file xyz.zyx". --Tobi (talk) 08:49, 22 July 2023 (UTC)

I understand perfectly well that it is not necessary to pollute the site with useless garbage, unconfirmed assemblies with a mention in the assembly file. although I don't really agree about the 4026.lab06 build, but... Oh my God! Why were ALL Windows XP builds removed from sdx.PM ? Okay, if there were reasons to delete, but NO. I didn't find that! EvoAndОбзорщик (talk) 14:07, 25 July 2023 (UTC)

sdx.pm is just one file and you don't know how the contents of the file are actually laid out. NaraInsider1694 (talk) 11:10, 25 July 2023 (UTC)

Because it's just a list of individual changes that were forward/reverse-integrated into different branches, and that alone isn't enough to merit new pages. It doesn't imply that the builds themselves exist either, for all we know; it could very well be some few Microsoft developers' personal FIs/RIs into mainline. - pivotman319 (📫) 11:48, 25 July 2023 (UTC)