Steam On Linux Use Ticked Higher In May, 25% Of Linux Gamers Are Using The Steam Deck

[avis]

The source code of Windows is licensed out to governments and other parties who are able to submit corrections back to Microsoft.

oiaohm, is there anything to back it up? You've already shat the bed with "14000 hypervisors for CSGO", now this? I asked you twice to provide citations authored by Valve, you said "I Googled up incorrectly"? Are you serious? Is this a kindergarten?

Also, the Windows source code is not licenced out to governments and other parties. It's just shared under a strict NDA: "for reference (e.g. when developing complementary systems), for review and auditing from a security perspective (mostly wanted by some large corporations and governments), and for development (academic institutions, OEMs, individual developers)". More info here: "Source-code modification or distribution is not allowed under these Shared Source programs."

I know for a fucking fact that there are people in Microsoft who document everything in regard to their APIs including Win32. I can dig up a ton of posts on blogs.microsoft.com which is an official resource unlike your unsubstantiated statements. There are multiple posts made my Microsoft employees on Twitter and news.ycombinator.com as well.

Sorry, I'm 100% sure you've got nothing and you're just blatantly making things up just like Mr. Weasel who keeps talking about completely tangential things and claims those things are right. They are. They just have zero relationship to what I said.

<offtopic>I say sugar is sweet which is backed up by everything. Mr. Weasel intervenes, screams, swears, "But but but fucking sugar is mostly made of sugar beet which is often fucking acid!!!" (mimicking the style of his posts where he couldn't stop swearing as if it made him right - no, if anything it made him look pathetic and horrible. When you're right, you simply lay out facts to prove your PoV. The problem is he chose the PoV that was again 100% tangential to what I said).</offtopic>

Microsoft major update screw ups like triggering massive self deletes of file systems

Show me screws up in relation to their APIs for Christ's sake. You continue to make stuff up.

Sometimes I respect you for your deep knowledge but in this topic you continue to make statement after statement without a single proof or citation. There's no need to be a buffoon. Mr. Weasel does it so much better.

err:ntdll:RtlpWaitForCriticalSection << attempting to make me laugh. That not win32

This has nothing to do with drivers. Wine barely has any. Please stop. It's not even funny any more. In fact if you Google this error up, actually you don't need to, Wine bugzilla literally has over a hundred open bug reports and many hundreds closed, you'll barely find a single post in relation to "drivers".

It's an issue with proper Win32 emulation under Wine which is "fucking nothing" according to Mr. Weasel and "it just works". Wine does nothing. The kernel doesn't execute anything. Yeah, right.

Unlike you, I've been closely following Wine development for over 25 years now. I'm a very active bug reporter as well. 308 filed bug reports, 58 of them are still open. But of course, I'm a "fucking idiot" as Mr. Weasel said.

You and Weasel put yourself over me. That's not what intelligent people do or even think about.

Don't bother posting a rebuttal or a reply unless you have solid sources to back it up. Not hearsay, not random Internet posts.

I loved your previous posts in regard to X.org/Wayland/etc when you were able to dig up the facts that I'd never known about. Unfortunately in this discussion you don't dig up stuff, you make it up.

Have a nice day.

[oiaohm]

oiaohm, is there anything to back it up? You've already shat the bed with "14000 hypervisors for CSGO", now this? I asked you twice to provide citations authored by Valve, you said "I Googled up incorrectly"? Are you serious? Is this a kindergarten?

That is not what I said at all. Lets stop at this point. Quote my lines of text you have based this on and read them this time. You asked for CSGO I said VAC. I never said the answer could be found by google.

"VAC documents at last count 14000 hypervisors they have to check for that cheaters have made all have windows claiming secureboot is enabled. Cheat developers are very active people."

Read this line carefully. Lets say I said "clamav documents x number of a particular type of virus where would you look for the count the signature files right" Yes googling for answer to clamav document x numbers of something would also be a dead end. VAC the program is really a form of locally running anti-virus style program looking for cheats.

Basically you attempted to google something that never had a google answer.

Also, the Windows source code is not licenced out to governments and other parties. It's just shared under a strict NDA: "for reference (e.g. when developing complementary systems), for review and auditing from a security perspective (mostly wanted by some large corporations and governments), and for development (academic institutions, OEMs, individual developers)". More info here: "Source-code modification or distribution is not allowed under these Shared Source programs."

is what you wrote 100 percent correct? sorry its not depends on how much of a weasel you are with legalities..

What license do you need for windows 12 IoT core for embedded usage that need customization to run on platform like you use todo with CE and you email [email protected] to ask about that problem what do you think the answer is?
https://www.microsoft.com/en-us/shar...g-program.aspx << Its this one. The one that allows modification.

https://en.wikipedia.org/wiki/Windows_IoT

Yes windows Iot replaced "Windows Embedded Compact" and Microsoft has not updated the license agreement to reflect the change on the website when you come to in fact signing that agreement with microsoft that document is updated. Yes funny that you click on the windows embedded compact link in the contract and today you end up at bing with no results.
Windows IoT core does not have the win32 userspace but you have the ntdll and the core OS kernel. Yes Windows IOT has the same kernel core as your desktop versions.

There is more shared source license agreements than what are documented on the Microsoft website and Microsoft has not kept their shared source public pages 100 percent up to-date.

How would anti-cheat company get able to use a CE License to work on IoT. Simple looking at the possibility of making own game console using windows as core as excuse of course that allows them to submit patches up stream. Of course with the CE license they can submit changes upstream to Microsoft for possible include in new version of windows. Lets just say anti-cheat companies are not the only ones using this licensing loop hole.

err:ntdll:RtlpWaitForCriticalSection <<avis you were only looking at wine. This error shows up under windows event logs when programs don't work under Windows as well.

Its a generic error it can be drivers it can be software to software. You get that error under windows or wine lots of debugging ahead. The Hundreds of bugs reports in wine is not strange with this error.
https://learn.microsoft.com/en-us/wi...tion-time-outs That error is a trap in the windows nt design to go off when there is possible a dead lock due to waiting on a critical section for too long.

err:ntdll:RtlpWaitForCriticalSection with timeout after it means nothing that is problem because this has follows windows nt-12 kernel behavior exactly as Microsoft has defined to raise this error. People ask how to fix this. Something has gone wrong before you got to err:ntdll:RtlpWaitForCriticalSection to cause a critical section not to be acquirable in a suitable amount of time because the critical section lock has not been released.

Yes critical section timeout are part of windows design. Microsoft documents how to debug RtlpWaitForCriticalSection time outs under driver section of windows documentation even that you can have problem happen software to software.

err:ntdll:RtlpWaitForCriticalSection with timeout after it=critical-section-time-outs they are the same thing. Wine calls it one thing and windows in the eventlog calls it a critical section time out. Programs operating correctly critical section time outs should not be happening but they are in Windows NT-12 as safe guard against dead lock..

Notice how you said it had nothing do with drivers. Problem is how to debug err:ntdll:RtlpWaitForCriticalSection/critical-section-time-outs is only in the driver section of the Microsoft documentation even that problem just need two userspace threads using a(as in single) critical section and one not releasing as it should.

Get it yet err:ntdll:RtlpWaitForCriticalSection under wine or "critical section time outs" appearing in windows event logs contains nothing useful for how you end up at this point. All it tells you is that you have a deadlock event with a critical section that been caused by something that happened before that point. Neither message is a bug.

It is one of the issues I do have with wine. Messages that are absolutely correct behavior like the err:ntdll:RtlpWaitForCriticalSection timeout messages are mixed with err messages of known broken behavior.

Yes by windows NT design you with issues you should have a number of err:ntdll:RtlpWaitForCriticalSection/critical-section-time-outs as part of normal system operations. This is the fun part lot windows systems you check eventlog and you see critical section timeout messages and the computer appears to be operating normally.

Please note issues coming from ntdll with windows the solution more often than not will be in the driver documentation not the win32/win64 documentation because this is windows nt native problem. Native problems fall under drivers by NT design(this is Microsoft windows NT design for you sometimes it head scratching). This is why thinking ntdll is part of win32 is a problem causes you to look wrong place in Microsoft documentation for solutions.

err:ntdll:RtlpWaitForCriticalSection/critical-section-time-outs under wine/windows is a message you can get when program is working perfectly as expected. Debugging is required to work out if this is harmless normal behavior caused by holding critical sections little too long or deadlock. Yes NT design this message appears after the deadlock has possible been happening for 60 seconds. Lot of stuff can happen in 60 seconds.

https://www.howtogeek.com/658194/windows-10s-new-update-is-deleting-peoples-files-again/

Microsoft has had a string of updates that nuked peoples files.