it took 22 yrs 2 get from 528 to 10240 its only taken 5 more 2 get 2 20xxx windows build nos r a 16bit wordstarting 2 wonder what happens @ 65535
It took 22 years for Windows NT build numbers to get from 528 (Windows NT 3.1, in 1993) to 10240 (Windows 10 Threshold, in 2015). It's only taken five more (well, six by the time it's released) to get from 10240 to the 20xxx range (as it appears Windows 10 21H1/Iron will be). Now Windows build numbers are stored as a 16-bit WORD - it's hardcoded into the Ver*() functions, and always has been - so, as @bfoos points out, this (assuming unsigned*) has a limit of 65,535 decimal. So I'm starting to wonder.... what happens when Microsoft hits 65,535? * I further wonder how many poorly-coded applications treat it as a signed value, and will break at 32,767? good enuff 4 ya @windows builder ? dat took me like 20x as long 2 type as the originl
TechBench new show up the 2004 but file not available Windows 10 Education 2004 [ID: 1625] Windows 10 2004 [ID: 1626] Windows 10 2004 Home China [ID: 1627]
Off topic on --- > >dat took me like 20x as long 2 type as the originl = Your ( time is ) worth 20 times more than other peoples ? < ---- Off topic off
For those who don't speak sUp3r 1337 h4x0r 7r0ll language. And it only took me... what... 30 seconds? Reading your... "post", on the other hand...
I tried them, and I was having a lot of stutters on AC Odyssey, however, I got 3 FPS more on average, multiple times tested with Hardware accelerated GPU scheduling enabled. What is your experience and results so far? P.S, 450.99 have been released recently, and I haven't tried them.
@ this point I'm getting TDR a few times a day no mattrer what driver I use but it worked well for me before that tbh