Linked by Thom Holwerda on Wed 27th Mar 2013 10:45 UTC
General Development "Programming is hard. Don't ever feel bad because you aren't as good at 'just googling it' as the person next to you. Don't ever let hackathon snobs talk you out of creating the next Twitter for cats or Yelp for public washrooms. Even the dumbest ideas (like trying to make animated polygons disappear and reappear) will help you improve as a programmer. Learning to program is largely about learning to learn - and the best way to learn is to do." For some reason, I love this short story.
Permalink for comment 557136
To read all comments associated with this story, please click here.
RE[6]: Only natural to improve
by f0dder on Fri 29th Mar 2013 21:21 UTC in reply to "RE[5]: Only natural to improve"
Member since:

"Did something actually happen with Vista that broke TP executables? Or did the programs break because you got a fast machine, and ran into the CRT delay-calibration divide by zero issue?"

I know what your talking about, I vaguely recall an official patch for the divide by zero bug on fast machines, no?

That's indeed what I was thinking about - dunno if there was any official patch, but I recall there was a tool that would fix up executables, as well as a source code patch for people to recompile CRT with.

Actually though they stopped working because AMD64 broke backwards compatibility with VME (virtual mode extentions) which is required to run 16bit code under protected modes. This means that 16bit code can no longer be virtualized and must be emulated, and microsoft chose not to support it at all.

So the breaking deal is Long Mode not supporting VME, rather than Vista breaking anything? AFAIK 32bit versions of Vista (and Win7 for that matter, dunno about win8) still has NTVDM?

I'm curious since I haven't heard about Vista breaking DOS stuff, and DOYC knows it's been blamed for a lot ;) (I've been running 64bit since XP64, so my DOS apps broke before Vista).

Reply Parent Score: 2