What is ReactOS' memory limit and how can it be modified?

Ask your support questions in here

Moderator: Moderator Team

middings
Posts: 1073
Joined: Tue May 07, 2013 9:18 pm
Location: California, USA

Re: What is ReactOS' memory limit and how can it be modified

Post by middings »

demizen wrote:...hoping that all drivers will be rewritten...
Or look for products that were on the Microsoft Windows Server 2003 Hardware Compatibility List.
...at the market share inflection point.
What do you mean by that?

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.)
Last edited by middings on Fri Jul 28, 2017 10:13 am, edited 1 time in total.
erkinalp
Posts: 861
Joined: Sat Dec 20, 2008 5:55 pm
Location: Izmir, TR

Re: What is ReactOS' memory limit and how can it be modified

Post by erkinalp »

Russinovich wrote:The maximum 2TB limit of 64-bit Windows Server 2008 Datacenter doesn't come from any implementation or hardware limitation, but Microsoft will only support configurations they can test.
This is non-issue on ReactOS as anyone can test our code and fix it. Offending drivers need to be fixed one by one(you should really read your API docs thoroughly).
-uses Ubuntu+GNOME 3 GNU/Linux
-likes Free (as in freedom) and Open Source Detergents
-favors open source of Windows 10 under GPL2
demizen
Posts: 5
Joined: Thu Jul 27, 2017 4:28 pm

Re: What is ReactOS' memory limit and how can it be modified

Post by demizen »

dizt3mp3r wrote:
presonus firestudio and Cubase
Don't expect that to work.
it didnt.
demizen
Posts: 5
Joined: Thu Jul 27, 2017 4:28 pm

Re: What is ReactOS' memory limit and how can it be modified

Post by demizen »

middings wrote:
demizen wrote:...hoping that all drivers will be rewritten...
Or look for products that were on the Microsoft Windows Server 2003 Hardware Compatibility List.
...at the market share inflection point.
What do you mean by that?

there is a point when OS market share is large enough to attract enthusiast and hardware industry.
middings
Posts: 1073
Joined: Tue May 07, 2013 9:18 pm
Location: California, USA

Re: What is ReactOS' memory limit and how can it be modified

Post by middings »

demizen, thank you for explaining what you meant by "the market share inflection point".

Perhaps the "inflection point" is closer than we think. According to NetMarketShare the market share of Apple's Mac OS X 10.4 is within 3 significant digits of ReactOS's share today! (0.00%, ha ha) Microsoft Windows XP has an almost 7% market share (June 2017 data) whereas all species of Linux have only a 2.36% share. Perhaps this explains why the ReactOS Project gets heat from some Linux partisans.
erkinalp wrote:...anyone can test (ReactOS) code and fix it.
We wish that were so! "Anyone" can also update most of the ReactOS Wiki. There is "a parable about four people named Everybody, Somebody, Anybody, and Nobody". (The names are synonyms for everyone, someone, anyone, and no one.)
Last edited by middings on Sat Jul 29, 2017 10:59 pm, edited 1 time in total.
demizen
Posts: 5
Joined: Thu Jul 27, 2017 4:28 pm

Re: What is ReactOS' memory limit and how can it be modified

Post by demizen »

middings wrote:demizen, thank you for explaining what you meant by "the market share inflection point".

Perhaps the "inflection point" is closer than we think. According to NetMarketShare the market share of Apple's Mac OS X 10.14 is within 3 significant digits of ReactOS's share today! (0.00%, ha ha) Microsoft Windows XP has an almost 7% market share (June 2017 data) whereas all species of Linux have only a 2.36% share. Perhaps this explains why the ReactOS Project gets heat from some Linux partisans.
I sense some lack of faith here, but you are likely right. looking at the share hist, obviously not everyone works in the cloud yet. cloud(s) are vulnerable, one snip when shtf and cloud is no more. I use 3x magnifiers, galaxy note with logitech K780 for a big chunk of my work "at home or near home" but when datalink is gone that thing turns into a brick heavy ishuffle.

I don't know, i guess, but i think it will come down to the cloud development and the monies that pour into it, if cloud is more vulnerable than is the general belief today then reactos could grab quite a share. Its not just shtf, clouds are vulnerable for variety of reasons. Trade wars, security issues, economic espionage, fake news propaganda, you name it..

the reason why windows 7 an xp are still around is (justified) cloudophobia.
val
Posts: 69
Joined: Fri Feb 10, 2017 5:22 am

Re: What is ReactOS' memory limit and how can it be modified

Post by val »

. duplicate :(
Last edited by val on Sat Jul 29, 2017 3:37 pm, edited 1 time in total.
val
Posts: 69
Joined: Fri Feb 10, 2017 5:22 am

Re: What is ReactOS' memory limit and how can it be modified

Post by val »

erkinalp wrote:
Russinovich wrote:The maximum 2TB limit of 64-bit Windows Server 2008 Datacenter doesn't come from any implementation or hardware limitation, but Microsoft will only support configurations they can test.
This is non-issue on ReactOS as anyone can test our code and fix it. Offending drivers need to be fixed one by one(you should really read your API docs thoroughly).
hehe, I think you misunderstood Russinovich statement. Unless you mean you (or an average ReactOS user) can afford machines with the memory amounts even MS can't. :D
literally they mean: we could find a machine with 2 TB of RAM, that's the biggest one, so we tested it and we thus guarantee it works. for everything more, we haven't tested, can't guarantee.
Post Reply

Who is online

Users browsing this forum: Google [Bot] and 23 guests