4 ms·
Imagine if they made programmers put 64 bit DLLs in a "System32" directory and 32 bit DLLs in a "SysWoW64" directory. That would really keep 'em on their toes!
by jjoonathan 5y ago
Imagine if they made programmers put 64 bit DLLs in a "System32" directory and 32 bit DLLs in a "SysWoW64" directory. That would really keep 'em on their toes!
- eyegor 5y agoYou should look into the behavior of the /windows/sysnative link. It appears and disappears depending on whether your process is running as 32 bit or 64 bit.
- Karuma 5y agoProgrammers should never put DLLs in those folders... Or even ever touch them.
- mastax 5y agoExcept for \Windows\System32\drivers\etc\hosts, of course.
- jaywalk 5y agoI occasionally try to search for the reasoning behind the location of the hosts file in Windows, and I always come up blank.
- blincoln 5y agoMaybe it's from back before Windows had a built-in TCP/IP stack? If it were a third-party/optional driver, having files related to it in a path under system32\drivers would make sense.
- mjevans 5y agoBack around Win 95 when they added networking it was based off of (IIRC) BSD's TCP stack and related tools. They were an optional 'third party' driver of sorts, but shipped by the first party. I'm not positive about WinNT or Win3.11 (for workgroups?)
- mixmastamyk 5y agoI remember adding "trumpet winsock" to Win 3.x back in the day. Says '94 for that, and summer of '93 for NT 3.1 debut: https://en.wikipedia.org/wiki/Trumpet_Winsock https://en.wikipedia.org/wiki/Trumpet_Winsock https://en.wikipedia.org/wiki/Windows_NT_3.1 https://en.wikipedia.org/wiki/Windows_NT_3.1
- HideousKojima 5y agoThey originally copied BSD's network stack, IIRC
- jve 5y agohttps://superuser.com/questions/355297/why-does-windows-have-a-unix-style-etc-hosts https://superuser.com/questions/355297/why-does-windows-have...
- kevin_thibedeau 5y agoThey already hamstrung themselves with LONG because DWORD just wasn't good enough and now long can't be 64-bit either.