39,327
edits
DOS 4 GW: Difference between revisions
m
update links
(clean up) |
m (update links) |
||
Line 10:
DOS/4GW kernel was loaded ''before'' the main program started, and it displayed its banner on loading, ensuring that ''anyone'' who ever played [[Doom]] would have it burned into their brain. Additionally, when the game or app crashes, the kernel would usually plaster error messages all over the screen without any regard for what was going there before and certainly without clearing it, which could result in [[Nightmare Fuel]] for those who played a good old game that had crashed right in front of their eyes. This also tended to reinforce the popular memory of what else would've been just a footnote in a history of computing.
Flash forward to [[The New Tens]], and strangely enough, the problem of "not enough memory" has occurred once more. While the norm has adopted 64-bit versions of operating systems, extending the amount of available memory to 2^64 bytes ( or 16 exabytes, which is 16 trillion trillion bytes), many programs are still run in 32-bit compatibility mode. In Windows, it allows for 2GB of memory available to 32-bit programs by default. A few games (notably ''[[The Elder Scrolls V: Skyrim]]'') have exceeded this limit occasionally resulting in a crash. The only way to get around this is to recompile the program with a flag that tells Windows to make the entire 4GB of 32-bit space available.
{{reflist}}
| |||