Here's what I remember from the old 3.1 days. We had our own DLL loader to keep from getting "Out of memory" errors. It was based on a solution from MSDN magazine, to give you an idea of how common the problem was. The Microsoft/Sybase database client could become corrupted if other code was doing TCP/IP activity. File Manager and Program Manager were jokes. The default MS TCP/IP stack would occasionally stop working. I could never figure out how to reenable it without reinstalling Windows. (I eventually went to another stack, which worked flawlessly.) Windows 95 had a much smarter loader, so we didn't need our custom loader anymore. TCP/IP was reliable. And we could go 32 bit, which solved our database client issue. I don't see similar technical issues for moving to Windows 8.