I doubt it would be hard, but I don't see why anyone would bother. At my last job, we would occasionally need to dig up old code because Microsoft finally remo

I doubt it would be hard, but I don't see why anyone would bother. At my last job, we would occasionally need to dig up old code because Microsoft finally removed something they had deprecated several years before. I think it was always amusing. One case that stands out was a utility program that would update data for our users each month. I needed to change something about the string handling. After updating the data, the program would enumerate all running software and kill any copies of our program (so that they would need to read the new data on startup). I noticed that we went through the trouble of enumerating 32-bit and 16-bit programs. Since we hadn't shipped a 16-bit version of our software since the '90s, and we had changed our data format significantly since then, I happily ripped that code out. I don't think you can find information on 16-bit Windows on MSDN anymore. I guess, to put it another way, who's shipping 16-bit programs?