There is just so much wrong with this. Let's go through it step by step:
ComputerMail wrote:
I only need to r/w in 64go RAM
What unit is 'go'? Google doesn't really give me an answer. There are bits: they are single binary digits. A byte is essentially nothing but a 8-digit binary number. All the prefixes are just the regular metric prefixes, i.e. a power of ten. The slightly changed ones (e.g. Kibibyte) are far less common and based on powers of two. Long story short: 8 bit = 1 byte, 1000 bytes = 1 KB, 1024 bytes = 1 KiB.
ComputerMail wrote:
Also i do not really need to understand how do all that work
This is the wrong mindset altogether. As someone (I honestly don't remember who) said, osdev is 90% research. Lazy design and bad code will bite you really badly at some point down the road.
ComputerMail wrote:
i would just use RAM in faster mode for given example in assembly language (nasm) if it is easier to answer.
There probably is no general answer to this, as this depends on many aspects of the CPU and RAM. You should have a good idea of what you're targeting, as the very first line of your code is completely arch-dependent. You should pick whatever platform you want to run your OS on. There are multiple factors here, e.g. if you want to use more than 4 GiB of memory, you have to go with 64-bit. If you want to use Virtual 8086 Mode, you'll have to go with 32-bit.
Although I don't really get what you're trying to say about PAE, but I can tell you that there's a catch: you can only use (as in page) 4 GiB of memory at a time, as virtual addresses are still locked to 32-bit (hence the name 'Physical Address Extension').
While it's not my job to do this, I really have to ask you this: have you read
Beginner_Mistakes and
Required_Knowledge?
Edit: I found the
quote:
eryjus wrote:
I would characterize writing a Hobby OS more of a research project than a coding project.