i suspect that windows' low-level timekeeping is not based on time_t, the way unix is. windows has a bunch of stuff like the SYSTEMTIME struct that does not ex

i suspect that windows' low-level timekeeping is not based on time_t, the way unix is. windows has a bunch of stuff like the SYSTEMTIME struct that does not exist on unix-like operating systems and doesn't have the same vulnerabilities. so windows-only software is less likely to exhibit this problem. macosx/linux/unix is much more severely affected. however, microsoft's c/c++ compiler does indeed recognize time_t and related functions. any software that uses them will be subject to the 2038 problem.