3 ms·
I remember learning about the Win32 API, and then proceed to delete/move UI elements of other Window using VB. I immediately tried to move the "continue" button
by wolpoli 4y ago
I remember learning about the Win32 API, and then proceed to delete/move UI elements of other Window using VB. I immediately tried to move the "continue" button of WinZip. Does anyone know if these APIs are still allowed or are they locked behind the UAC prompt now?
- jdsfighter 4y agoYou're bringing back waves of nostalgia. I used to frequently read AllAPI.net and come up with mischievous implementations for my own amusement. A quick Google Search netted the following project (https://github.com/microsoft/CsWin32 https://github.com/microsoft/CsWin32). Looks like my evening is gone.
- brewmarche 4y agoCool find! I’ve only known <https://github.com/dotnet/pinvoke https://github.com/dotnet/pinvoke> which offers ready-to-use NuGets for various Win32 APIs.
- deleted 4y ago[deleted]
- jchw 4y agoAs far as I know, most of this stuff still works. There might be some security boundaries that apps can opt into, but most of them do not. So something running as your user, you can probably manipulate the UI of. There's been some amusing ones even not so long ago, like this one: http://kylehalladay.com/blog/2020/05/20/Rendering-With-Notepad.html http://kylehalladay.com/blog/2020/05/20/Rendering-With-Notep... edit: Bad example, they are using WriteProcessMemory. Still a lot of fun, but not the same. I was thinking of this: https://twitter.com/steveklabnik/status/1263190719721766918 https://twitter.com/steveklabnik/status/1263190719721766918
- Pathogen-David 4y ago> Does anyone know if these APIs are still allowed or are they locked behind the UAC prompt now? For better or worse this sort of thing still works just fine for apps which still use Win32 controls. All that's really changed with regards to UAC is non-privileged apps can't mess with privileged ones.
- haimez 4y agoAs a remember as a teenager I wrote a program that would constantly call the beep function (read: loud squeals from your motherboard speaker, if you had one, and not affected by volume controls so you couldn’t turn it off easily) and then that program would use the Win32 APIs to also poll for any task manager windows you might launch and minimize them immediately so that you couldn’t kill the process. I sent beep.exe to some of my friends on AIM at the time and they ran it (it was a simpler time) and were not amused- even after I told them they could just restart their computer to make it stop. (I had a version that added itself to the registry to auto run at startup, but even my teenage self thought that was a bit too far).
- art0rz 4y agoI used to work tech support for a DSL company. The tools used to log customer interactions were slow and buggy. I taught myself VB to fix a lot of issues in the UI, and automate a large part of my job. I taught a coworker (who had never touched any code before) some of it. After a few months he moved on to do data entry for another company. When I saw his title on LinkedIn change to "automation engineer" after a while I was curious and had to ask what happened. He had automated most of his data entry job. The bosses got curious and asked to share his secret which he did, got a fat raise and a nice title. Sadly, most of his team was let go, but I'm happy I helped him become a programmer.