Or look for products that were on the Microsoft Windows Server 2003 Hardware Compatibility List.demizen wrote:...hoping that all drivers will be rewritten...
What do you mean by that?...at the market share inflection point.
Realistically, the memory limits for Microsoft Windows XP 32-bit are due to the constraints of the legacy hardware and software that Microsoft strives to remain compatible with. ReactOS faces many of the same constraints because of the same legacy problems. In the pure open source world, if your new whiz-bang OS distro with the hot new Linux kernel crashes, go patch (if you can). Or ask the author of the open source application or driver that balks on the new OS to please, please fix his software--if you can't fix it yourself. That's one of the reasons Linux hasn't mastered the desktop.
Mark Russinovich wrote a series of articles for Microsoft TechNet titled "Pushing the Limits of Windows". The first article in the series, "Pushing the Limits of Windows Physical Memory", is probably the one most applicable to the matter of ReactOS's memory limits.
I found the article from a link in one of the comments to a Raymond Chen article at his blog, The Old New Thing. The article's title is "It's the address space, stupid". (Look for Raymond's remarks in some of the comments.)