win95 exe's jump to win2000 - (Painful)
-
We have win95 exe's written in c++ & mfc...these work well on win95, but keep blowing up with "Abnormal Terminations" on win2000. How best can I migrate my VC5 & MFC code to Win2000 ????? Would a win2000 dev pc with devStudio install & a recompile do any good? Cheers Gerry.
-
We have win95 exe's written in c++ & mfc...these work well on win95, but keep blowing up with "Abnormal Terminations" on win2000. How best can I migrate my VC5 & MFC code to Win2000 ????? Would a win2000 dev pc with devStudio install & a recompile do any good? Cheers Gerry.
I'm not expert in these things, but let me share my experience. From my personal experience, you need to work it(compile ... devet.. testing) on a nt or 2k machine. The problem is most of the code would work without a hickup in 95/98 but almost always will end up blowin up in NT / 2K. Most of the problem could be to do with uninitialized memory (in my case that was the problem) so while do the debugging in NT/2K machine ... you have more chances of spotting the bug. Cheers Kannan
-
We have win95 exe's written in c++ & mfc...these work well on win95, but keep blowing up with "Abnormal Terminations" on win2000. How best can I migrate my VC5 & MFC code to Win2000 ????? Would a win2000 dev pc with devStudio install & a recompile do any good? Cheers Gerry.
Generally speaking, there's probably a bug in your code that isn't showing itself in Win95. This might be because you're relying on the way Win95 returns or processes data, which is different under NT. Or it might simply be because NT and Win95 create different kinds of call stacks and therefore exposes a bug that just happened to work under 9x. In any case, you should debug on the platform you're trying to target.
-
I'm not expert in these things, but let me share my experience. From my personal experience, you need to work it(compile ... devet.. testing) on a nt or 2k machine. The problem is most of the code would work without a hickup in 95/98 but almost always will end up blowin up in NT / 2K. Most of the problem could be to do with uninitialized memory (in my case that was the problem) so while do the debugging in NT/2K machine ... you have more chances of spotting the bug. Cheers Kannan
moral of the story is always init your ptrs to NULL in your constructors and test for NULL before using them kidz ;) --- "every year we invent better idiot proof systems and every year they invent better idiots"