Windows drive letters are not limited to A-Z
https://www.ryanliptak.com/blog/windows-drive-letters-are-not-limited-to-a-z/
#ycombinator #zig #win32 #windows
Windows drive letters are not limited to A-Z
https://www.ryanliptak.com/blog/windows-drive-letters-are-not-limited-to-a-z/
#ycombinator #zig #win32 #windows
Microsoft Post-Quantum Crypto APIs Are Now Generally Available
buff.ly/C05hqD2
#pqc #windows #dotnet #apis #win32 #cryptography #bcrypt #ncrypt
Microsoft Post-Quantum Crypto ...
Draft PR for GLFW:
glfwWaitEvents (and glfwWaitEventsTimeout) which only return if GLFW events are encountered (or timeout).
This resolves issues with these functions returning early when they shouldn't. I use these to implement Avoyd's power saving for example.
Since my Mac died I've not yet implemented the Cocoa backend, but will likely rent some remote desktop time at some point to add this. Cross platform open source can get expensive!
#Microsoft, your MSIX tooling is abysmal.
Why can PackageManager.StagePackageAsync freeze randomly?
Is it "lighted up" or "lit up"?
"Cool API you wanna use there, would be a shame if it doesn't work on half your target systems" - #Microsoft, with the #WinRT PackageManager API.
Fuck you.
If anyone is using GLFW on Windows with raw mouse motion you might want to test a PR branch we're considering merging. It adds buffered raw mouse reading, which can lower the event loop timing considerably when used with high poll rate mice:
https://github.com/dougbinks/glfw/tree/pr-2750-win32-buf-raw-m
I'd like to get a bit more testing on this before I merge, any help appreciated. Original PR: https://github.com/glfw/glfw/pull/2750#issuecomment-3464783371
One Open-source Project Daily
Yori is a CMD replacement shell that supports backquotes, job control, and improves tab completion, file matching, aliases, command history, and more.
https://github.com/malxau/yori
#1ospd #opensource #cmd #commandline #shell #terminal #win32 #windows #yori
Cursed #Python on #Windows fact:
It is possible to create a file on a system where Long Paths are enabled that is entirely valid, but which `open()` cannot read.
I don't think I've ever stumbled on it, but each "component" (thingy-between-backslashes) in a Windows path is separately limited, usually to 255 bytes.
It is definitely possible to make a file with a filename longer than this through the GUI (i.e. copy 'a'*1024 onto the clipboard, "New File", and paste), but I don't know how this works in the #Win32 API. Maybe the "real" component is the equivalent "short" name and there's some metadata storing the pretty version.
Edit: here's a program that demonstrates that these files cannot be created by Python, although it doesn't show off the inability to open a file created by other means:
Okayokay #Microsoft, how can you fuck up #Windows so badly?
User complains "Task Manager autostart settings have no effect on your application"
User checks HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
And both keys, SupportFullTrustStartupTasks and EnableFullTrustStartupTasks, are missing.
Recreates it, and autostart works again.
In fact, everything except "HideFastUserSwitching" and "DisableAutomaticRestartSignOn" were missing.
HOW!?
quicktipp #104: opening the classic Windows notepad.exe on Windows 11 (instead of the new modern Notepad app) with `classic.exe`.
https://github.com/christian-korneck/classic-windows-notepad
#windows11 #windows #win32 #notepad #app #apps #uwp #metro #modernapp #microsoft #windows10
In a multithreaded application, when I have a double-checked lock without using atomic (because the type I'm using doesn't support that), does atomic_thread_fence even make any difference?
I.e. PerformOperation mutates the variable-by-ref.
atomic_thread_fence(acquire)
if (condition) {
lock_guard;
atomic_thread_fence(relaxed)
if (condition) {
PerformOperation(variable-by-ref)
atomic_thread_fence(release)
}
}
@wyatt I still have 3 gripes with what #Microsoft calls #WSL:
1. It's not a "#Windows Subsystem for #Linux", but a "Linux Subsystem for Windows". The real #WindowsSubsystemForLinux is called #Wine, as it provides #Win32 & #Win64 calls on Linux!
2. The "#Unix Subsystem for Windows" aka. "Unix Services for Windows" were to a degree better.
3. "WSL" is less of a compatibility layer and more of a #HyperV - #VM, which also results in issues with #VMware / #VMwareWorkstation and #VirtualBox.
In an early episode of #StarTrekDiscovery, soon after Burnham arrives on the eponymous starship, a computer display shows code that she's tasked with fixing.
An experienced programmer would quickly recognize the code being displayed: it's a list of #Win32 function declarations! Most likely taken from a #Windows SDK header file.