1
Setup & Installation / Target 64Tb of memory, not one less.
« on: June 23, 2024, 10:57:19 am »
For the future and other follies
I have doubts, I read that the OS/2 could manage in Voice.
"In theory the 386 processor allows for 64 terabyte of virtual memory."
http://www.os2voice.org/VNL/past_issues/VNL0708H/feature_3.html
This is something that has been around my head for some time.
And it will not be that the maximum theoretical memory is always 4GB, but that it rotates in almost endless cycles, so that for example
You have 13GB = (4GBX3)+1GB available, it will show you 1GB, but that 1GB, if spent it appears as 4GB, are spent and ... re -empecing.
If this were so, it would be good to find that number that multiplies by 3 or whatever. Somehow I think I should
exist.
Another example, it can be like if you enter a building, on the ground floor you have 4gb,
but if you go up to the first floor you have another 4gb = 8gb keep going up floors and imagine a skyscraper
of 100 floors = 400gb
It could also be that the memory begins at the top of the building, and goes down the way,
without the need for a floor number. Until it runs out.
If someone would tell you today, create a 64Tb memory, and you can only direct 4gb, how would you do it?
Could it be that we are only seeing the memory that is on one floor of the building?
To help understand the memory I use the freemem.exe program, the information it provides is not valid.
But it can help to understand what I say, and also the operation of the applications, how much memory they use,
When they use it, when an application is loading, when it is dead, etc ... in real time.
This program is freemem.exe very old, and I have seen it rotate many times.
And everything continues to work. By watching it rotate I mean having 100mb of memory and going through 4gb,
and then 3.8g....
Could it be so?
What if we are putting memory limitations where they do not exist?
I mean: If you create a program and tell it to look at the memory and close it if it's insufficient,
why not let the system decide whether or not it's insufficient.
I leave you a screenshot, you can see used 2297mb, and simultaneously 2819mb free according to Vmem = 5116mb
Here I am using the memlinit in 4095, and because it won't let me put twice as much on it. Limits!!!!
All run nice.
Saludos
** Ian has removed the attachment for the ebay listing **
I have doubts, I read that the OS/2 could manage in Voice.
"In theory the 386 processor allows for 64 terabyte of virtual memory."
http://www.os2voice.org/VNL/past_issues/VNL0708H/feature_3.html
This is something that has been around my head for some time.
And it will not be that the maximum theoretical memory is always 4GB, but that it rotates in almost endless cycles, so that for example
You have 13GB = (4GBX3)+1GB available, it will show you 1GB, but that 1GB, if spent it appears as 4GB, are spent and ... re -empecing.
If this were so, it would be good to find that number that multiplies by 3 or whatever. Somehow I think I should
exist.
Another example, it can be like if you enter a building, on the ground floor you have 4gb,
but if you go up to the first floor you have another 4gb = 8gb keep going up floors and imagine a skyscraper
of 100 floors = 400gb
It could also be that the memory begins at the top of the building, and goes down the way,
without the need for a floor number. Until it runs out.
If someone would tell you today, create a 64Tb memory, and you can only direct 4gb, how would you do it?
Could it be that we are only seeing the memory that is on one floor of the building?
To help understand the memory I use the freemem.exe program, the information it provides is not valid.
But it can help to understand what I say, and also the operation of the applications, how much memory they use,
When they use it, when an application is loading, when it is dead, etc ... in real time.
This program is freemem.exe very old, and I have seen it rotate many times.
And everything continues to work. By watching it rotate I mean having 100mb of memory and going through 4gb,
and then 3.8g....
Could it be so?
What if we are putting memory limitations where they do not exist?
I mean: If you create a program and tell it to look at the memory and close it if it's insufficient,
why not let the system decide whether or not it's insufficient.
I leave you a screenshot, you can see used 2297mb, and simultaneously 2819mb free according to Vmem = 5116mb
Here I am using the memlinit in 4095, and because it won't let me put twice as much on it. Limits!!!!
All run nice.
Saludos
** Ian has removed the attachment for the ebay listing **