medor wrote:Replace Skaarj with EvilGrins
Something not very far, not very close. It was written about: "The better CPU = the better for game..." but that was the major goofing and a pretty much fake thing - a fantasy. This engine has hard-coded limits and not "computed limits" based on a benchmark at OS install or done in run-time 4 touchers, 10000000 iterations, 1000 paths, other arrays - these are the same in any CPU used, and then multi-core support is NONE, Calibrating to unpredictable CPU with speed stepping is also NONE. Only a single factor deviating execution in a new Kernel might go to a crash. Even if a last generation CPU is capable of a high speed processing UE1 will cap executions. If other stuff is based on the same "limits" we won't run everything in a new CPU and a new OS. More than that, programmers teams are changed as I can see so far, and these new dudes have mainly heads in clouds and don't have a clue about some base things, Internal sources from M$ were already speaking in private about problems and notice Higor's problems with compilers. Is not easy when Corporations are doing a mess with less skilled workers just for making money as a primary goal. I think in next 20 years in IT will be something like a chaos "Let's see if this do works" with very few exceptions. Look around and you can see some sudden self claimed "programmers" but having no clue what they do and finishing nothing - direct sample of evolution - start 100 things finishing nothing, or only one thing useless and borked in a self defaming spree.Red_Fist wrote:On the other side, did they write UT knowing to make it always work 20 years later ?
Red_Fist wrote:So by my estimation, if an old EXE can just be stripped of it's version, win7 64 would not know it was old, the same way UT still works.
On the other side, did they write UT knowing to make it always work 20 years later ?
I really don't see why every program since DOS or win 3.1 cannot just run, 16 bit, 32 bit, the CPU still takes the EXACT same commands built on the chip, like machine code, 100% the same for x86 and less of the same commands for 16 bit.
I think Sinclair Spectrum are on 8 bits using 64 kb. 16 bits goes to 640 kb base memory which is not that changed after all, those 640 kb are still a base for operations with memory if I'm not mistaking... the rest of memory was needing memory driver, read again, a memory driver called himem.sys... which I still have in WinXP dated 2008 else 2 GB memory probably would be a fantasy for use.Chris wrote: Heh.. 16 bits, can you imagine that? A limit of 64kb of memory space.
Sorry to correct you, but 16 Bit = 2^16 = 65536 has nothing to do with the 640k limitation. This limitation was caused by the designer of the early PC architecture, who decided to give the lower 640 kiB memory area to the user and reserve the reminding upper 384 kiB for the system. (See Wikipedia.)sektor2111 wrote:16 bits goes to 640 kb base memory
Later used CPUs had more than 20 address lines and offered also a Protected Mode which allows access to memory above that 1 MiB border. himem.sys was a software that could be used in real mode by several other programs to coordinate the access to that memory according the specification XMS.sektor2111 wrote:himem.sys
Users browsing this forum: Google [Bot] and 2 guests