Linked by Thom Holwerda on Fri 21st May 2010 12:45 UTC, submitted by martini
OS/2 and eComStation After god knows how many years, it's finally here: the final release of eComStation 2.0. We first reported on eComStation 2.0 back in December 2005, when the first beta was released, and between then and now, we've seen countless betas and release candidates come and go, but the wait is finally over.
Permalink for comment 426064
To read all comments associated with this story, please click here.
RE[4]: Hmm
by Bill Shooter of Bul on Sat 22nd May 2010 15:50 UTC in reply to "RE[3]: Hmm"
Bill Shooter of Bul
Member since:

I am not a typical user. I am a power user. As such, there are several applications i use that consume a large amount of memory.

Virtual machines ( yes I typically run two or three vms at once )
open office

I actually do know how well that workload works on a 2000 era computer: Not good. You can do the same things but you have to close one app to open another. It takes longer. I'd also have to have separate physical machines to replace the virtual machines.

Win 32 bit didn't support the PAX extensions that allow you to use more than ~3 GB. Mac/linux/ win32bit servers did. It used that as a product differentiator to get people to pay for server OSes. however it would limit each process to ~3gb. Making it unsuitable for really memory intensive apps ( databases and the like).

There have been 64 bit architectures that don't have a 32 bit version. Like Itanium. Though yo could really point to that lack of legacy support as a reason for its relative failure to meet its expectations.

Ram isn't the only reason for the change to x86_64. There are a lot of other changes in the instruction set that make it a better choice. I'm not an expert on them, but I know they exist. But those are specific to one implementation of 32 vs 4 bit that would not pertain to other instruction sets like POWER.

Reply Parent Score: 2