New
#21
Hi there
I suggest you re-read my previous post again -- PHYSICAL memory extension is handled as I pointed out in my post --what isn't true please.
There is another implementation that IBM used to use on its older MVS /370 systems was called SWAPPING when you had loads of TSO (Time Sharing Option) users.
What this did was every so often swap out the entire user's address space to a reasonably fast disk (used to be called Drum storage on those days) and allow another user to be "swapped in" to use the same address range that the "swapped out" user had.
Paging is a different methodology -- The system (OS) task dispatcher knows what it needs to do next. It takes a pre-defined order of tasks in the system and determines if it can suspend (temporaily) an active task or take and suspend a non critical low priority inactive task. It then saves the REAL memory slots that that task uses and assigns those to the "waiting" task. A Dispatcher interrupt will then signal to the CPU / I/O system / graphics or whatever that this task is ready to resume its processing.
The algorithm the task dispatcher uses is or can be hideously compicated and this will make or break the efficiency of the OS. You'll need a serious course on Windows internals to make head or tail of this but you can look at the kernels of various Linux distro's if you are interested in this. The Task dispatcher is a critical element in ANY OS.
However you cut it the virtual memory still has to be matched to REAL memory and without the PAE hardware / system 4GB is your lot.
Please also suggest any other method of actually adressing more than 4GB PHYSICAL (Not Virtual) memory with a 32 bit adress scheme.
The physical restriction is still the maximum address that RAM could address and whichever way you turn it on EVERY planet in the known universe 2 ** 32 is 4GB.
Please if you refute something POST what's wrong
Or are odours of Troll beginning to seep up into the atmosphere here.
Cheers
jimbo.