You're the one claiming that Steam is affecting Windows .dlls and all that shady shit. The burden of proof is on you.
Attacking the person asking you for it doesn't help much to your argument's credibility.
NORMAL API LIBRARY FUNCTION IN KERNEL32.DLL
766049BF - 8B FF - mov edi,edi
766049C1 - 55 - push ebp
766049C2 - 8B EC - mov ebp,esp
766049C4 - 83 7D 08 00 - cmp dword ptr [ebp+08],00
766049C8 - 53 - push ebx
766049C9 - 56 - push esi
766049CA - 57 - push edi
766049CB - 74 17 - je 766049E4
766049CD - 68 F8496076 - push 766049F8 : ["twain_32.dll"]
766049D2 - FF 75 08 - push [ebp+08]
766049D5 - E8 30000000 - call 76604A0A : [->76FDC7D9]
766049DA - 59 - pop ecx
766049DB - 59 - pop ecx
766049DC - 85 C0 - test eax,eax
766049DE - 0F84 6EEE0200 - je 76633852
766049E4 - 6A 00 - push 00
766049E6 - 6A 00 - push 00
766049E8 - FF 75 08 - push [ebp+08]
766049EB - E8 F5FEFFFF - call 766048E5 : [->74BB2CCC]
766049F0 - 5F - pop edi
766049F1 - 5E - pop esi
766049F2 - 5B - pop ebx
766049F3 - 5D - pop ebp
766049F4 - C2 0400 - ret 0004
STEAM GAME RUNNING SAME LOCATION:
766049BF - E9 06B70F00 - jmp 767000CA
766049C4 - 83 7D 08 00 - cmp dword ptr [ebp+08],00
766049C8 - 53 - push ebx
766049C9 - 56 - push esi
766049CA - 57 - push edi
766049CB - 74 17 - je 766049E4
766049CD - 68 F8496076 - push 766049F8 : ["twain_32.dll"]
766049D2 - FF 75 08 - push [ebp+08]
766049D5 - E8 30000000 - call 76604A0A : [->76FDC7D9]
766049DA - 59 - pop ecx
766049DB - 59 - pop ecx
766049DC - 85 C0 - test eax,eax
766049DE - 0F84 6EEE0200 - je 76633852
766049E4 - 6A 00 - push 00
766049E6 - 6A 00 - push 00
766049E8 - FF 75 08 - push [ebp+08]
766049EB - E8 F5FEFFFF - call 766048E5 : [->74BB2CCC]
766049F0 - 5F - pop edi
766049F1 - 5E - pop esi
766049F2 - 5B - pop ebx
766049F3 - 5D - pop ebp
766049F4 - C2 0400 - ret 0004
NOTE THE CHANGE HERE:
766049BF - E9 06B70F00 - jmp 767000CA
which goes here:
767000CA -E9 21F258E8 JMP gameover.5EC8F2F0
then points to a function in this steam .dll
gameover.dll
which you can look at the list of things that steam says is 'ok' to be running on your cpu (like the punkbuster .dll's, etc.)
5EC8F369 8B3D C8A1CA5E MOV EDI,DWORD PTR DS:[<&KERNEL32.GetModu>; kernel32.GetModuleHandleA
5EC8F36F 68 04E7CA5E PUSH gameover.5ECAE704 ; ASCII "pbcl.dll"
5EC8F374 FFD7 CALL EDI
5EC8F376 85C0 TEST EAX,EAX
5EC8F378 75 33 JNZ SHORT gameover.5EC8F3AD
5EC8F37A 68 F8E6CA5E PUSH gameover.5ECAE6F8 ; ASCII "pbcls.dll"
5EC8F37F FFD7 CALL EDI
5EC8F381 85C0 TEST EAX,EAX
5EC8F383 75 28 JNZ SHORT gameover.5EC8F3AD
5EC8F385 68 ECE6CA5E PUSH gameover.5ECAE6EC ; ASCII "pbcag.dll"
5EC8F38A FFD7 CALL EDI
5EC8F38C 85C0 TEST EAX,EAX
5EC8F38E 75 1D JNZ SHORT gameover.5EC8F3AD
5EC8F390 68 E0E6CA5E PUSH gameover.5ECAE6E0 ; ASCII "pbcags.dll"
5EC8F395 FFD7 CALL EDI
5EC8F397 85C0 TEST EAX,EAX
5EC8F399 75 12 JNZ SHORT gameover.5EC8F3AD
5EC8F39B 68 D4E6CA5E PUSH gameover.5ECAE6D4 ; ASCII "pbsv.dll"
and sets up an error here:
5EC8F3C7 FF15 D8A0CA5E CALL DWORD PTR DS:[<&KERNEL32.SetLastError>] ; kernel32.SetLastError
and crashes your game if something steam doesn't 'like' happens
and then otherwise, backtracks back to the windows system api after hooking it.
if you have any tools, and can actually get them to access the game without it crashing, then you can see that this is true..
there is ZERO DOUBT steam is hooking api's in the kernel32.dll WINDOWS SYSTEM .DLL
PERIOD..