BrokenThorn Entertainment

So I setup a page-fault handler, but after the page-fault occurs and my handler runs a GPF occurs. Is this happening because the page isn't properly mapped? Also, if you have a non present page stored in a page file, how do figure out where in the page file is the page you want to map when a page fa...

I think the problem may be in display.c, change: case 'i': { c = va_arg (args, int); char str[32]={0}; itoa_s (c, 10, str); Puts (str); i++; // go to next character break; } to case 'i': { c = va_arg (args, int); char str[32]={0}; itoa (c, 10, str); Puts (str); i++; // go to next character break; }

Thanks that cleared that up!

On PTEs and PDEs the bits reserved for the frame address are only 20-bits. So you can really only represent addresses up to 1MB. So is the frame address really multiplied by 4K to get the physical address? So like if the frame address is 1 it represents the page at 4096-8191?

I don't see a memory hole between 15-16MB? 0x0-0x9f000 (total size 0x9f000) 0x9f000-0xa0000 (total size 0x1000) non contiguous by 0x48000 bytes 0xe8000-0x100000 (total size 0x18000) 0x100000-0x7ff0000 (total size 0x7ef0000) non contiguous by 0xf7fd0000 bytes 0xfffc0000-0x100000000 (total size 0x4000...

Thanks! I have a question about the memory detection though. What is it really detecting? I thought it was detecting the total amount of RAM installed in the system, and then certain areas were available and some were reserved (as designated by the memory map). But it seems that it's getting some ra...

Lol...ok, can anyone look at that memory problem though?

Yeah. EDIT: Fixed it...set the present bit in the GDT entries...not sure why that's a problem though. The tutorial describes that bit as only being used in Virtual Memory and just to ignore it and set it to 0. Oh well. Although, I'm having a problem with the memory maps , if anyone could take a look...

Ok. from gdt.h // gdt entry structure struct gdt_entry { unsigned short limit_low; unsigned short base_low; unsigned char base_middle; unsigned char access; unsigned char granularity; unsigned char base_high; }; // pointer to gdt (needed for lgdt instruction) struct gdt_ptr { unsigned short limit; u...

Ever since I put in code for the GDT I've had problems. Eventually I decided, temporarily, it'd just be easier to use the GDT setup by the bootloader. But now I'm coming towards the point where having a GDT is necessary, but I just don't know what's going on. I tried using the GDT code from the demo...

I see. Well for whatever reason I seem to be getting the amount of memory in bytes, no biggie lol. EDIT: Nevermind...I have no idea what I'm getting. I just realized Bochs default memory is 32MB, and Virtual Box's is 64MB, and it was reporting around 38MB of RAM...also noticed that the amount of ava...

Oh right, I remember I had a similar problem on hexadecimal numbers, thanks Andy. I still have some questions. Is the memory being returned in KB or bytes, because the amount seems too big to possibly be in KB. And also, how come in 14th demo (with the virtual memory manager) we initialize the physi...

I'm using the code from the tutorials to get the amount of memory on the system, but it's returning a negative number:
Any idea on what's going on?

After a long discussion with Andy we fixed the problem! Woot haha.