The 1.09 will also include a patch against the 1.08 "multiple haloloop attacks" exploit.
Printable View
The 1.09 will also include a patch against the 1.08 "multiple haloloop attacks" exploit.
I read that post, Roger mentioned you :D
And Omega where's that updated version changer for Halo CE
*stern look* :)
Why would someone use a 64bit operating system if they used that small amount of ram?Quote:
Originally Posted by Hunter
32bit os have a limit around 3.75Gb's where as 64Bit have around 128Gb's.
64-bit allows up to 17.2 billion gigabytes mister. 32-bit allows up to 4GB, but under Windows it is recommended to not go below 1GB of reserved kernel memory (leaving 3GB for applications)Quote:
Originally Posted by =sw=warlord
And then there's PAE, giving you 64GB when properly implemented (ie, Linux is good, but BSD doesn't have full support and OS X only does 32GB, and only datacenter versions of Windows 32-bit support PAE properly)...Quote:
Originally Posted by Kornman00
Glad to see Sawnose is still doing small patches for HPC. I wasn't surprised to see Modacity members chiming in with their thoughts on the whole deal.
Is it just me or is it that every time an OS release is due out, a new patch for the game wonders into the picture http://kornnersoftware.com/trillian/rec0.gif?
You happen to have release dates around the 2 sections of the year Roger does things for Halo PC.Quote:
Originally Posted by Kornman00
Nay! It's the other way around ;_;
For my 64 bit pc, console doesn't work, the resolution is locked at 1024x768, and it tears ALL OVER no matter what I do.Quote:
Originally Posted by Yuki
E: All my tearing and artifacts are fixed, my resolution it no longer locked at 1024x768 (now OTHER resolutions including 1440x990 show up in options), and now console works fine. :neckbeard:
2nd edit: Oh bitterbanna's thrid FOV isn't working like it did in halo v 1.08 :ohdear: