Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon.

Pages: 1-

Finding of Fact - Microsoft and 64-bit

Name: Anonymous 2012-10-03 6:44

Microsoft is refusing to tell the truth that they are obsessed with 64-bit - they only mentioned older hardware timers being no longer supported, and the kernel in the 32-bit x86 version, despite using 64-bit RAM access, the RAM limit is intentionally lowered to 4GB to make people think it still uses 32-bit RAM access,but now in even the 32-bit x86 version of Windows 8, everything except the code form is 64-bit (which in the x86_64 version EVERYTHING is 64-bit), in which Windows 8 dropped support for older, 32-bit only, MOTHERBOARDs with HAL_INITIALIZATION_FAILURES, forget about 32-bit only CPUs. the kernel in the 32-bit x86 version, despite using 64-bit RAM access, the RAM limit is intentionally lowered to 4GB to make people think it still uses 32-bit RAM access, but now in even the 32-bit x86 version of Windows 8, everything except the code form is 64-bit (which in the x86_64 version EVERYTHING is 64-bit), in which Windows 8 dropped support for older, 32-bit only, MOTHERBOARDs with HAL_INITIALIZATION_FAILURES, forget about 32-bit only CPUs.

Does /tech/ agree with this?

Name: Anonymous 2012-10-07 23:41

the 32-bit x86 version cannot access 64-bit RAM, I don't know what you're smoking OP, but even while high I know that 64-bit is vastly superior, not only for RAM access speeds & size, but for data security both in protection and retention (checksums).

Four years ago I would have agreed that 64-bit doesn't have much use, but these days we've finally managed to make most things 64-bit compatible across several operating systems.

Name: Anonymous 2012-10-08 12:06

[spoiler]nigger[spoiler]

Name: Anonymous 2012-10-08 13:25

.Net maximum object size is limited by a 32 bit pointer. So is WinRT.

Where is your god now?

Don't change these.
Name: Email:
Entire Thread Thread List