It is possible to install VS 6 on Win 10, it is a hack.
|
Just read through that article quick FurryGuy and I've gotta agree with you. I'm not sure I'd want to bother with it. I've the Enterprise Edition of Visual Studio 98, which, if I recall, was like an $800 or $1000 purchase (my old employer bought it for me). And unlike so many here, I'm not at all adverse to using old versions of things. I still mostly build with the x64 VC15 build chain which came with Visual Studio 2008. But I also test with VC19 on Windows 10. It doesn't make too much difference. Just more bloated binaries with each version Microsoft churns out, but that doesn't bother me as I use my own custom runtime which eliminates the bloat.
I'd be inclined to recommend to the OP to just download Microsoft's latest compiler and use that rather than fooling around with VC6. I mean, somewhere you've gotta 'draw the line' and move on, no matter how much one clings to older things. I finally had to give up on DOS, much as I hated to.
Place to begin likely would be converting all the floats in that program to doubles. Like I said, the compilers nowadays do internal calculations using doubles - that's why all those truncation warnings casting from doubles to floats. And when I did a test build with Mingw - GCC, I recall seeing a lot of the actual errors were 'ambiguous overload' errors involving C Runtime pow(), which takes type double parameters. In my coding career I've oftentimes switched between Microsoft's compilers and GCC. If I recall GCC tends to be stricter than MS and usually requires casts where MS compilers will let some stuff pass. Maybe that's changed with the newer MS compilers.
But if that code still has value and utility (it most likely does), it might be a better use of your time to update the code itself to build x64 on the newer compilers, rather than fighting trying to get VC6 to work on 2020 operating systems.