There are locations in memory that have defined purposes, for example 0xb8000. After I enable paging, is it the physical location 0xb8000, or the virtual location 0xb8000 that gets displayed to the screen?

The graphics controller only ever sees physical memory addresses. The paging MMU is buried deep inside the CPU and external devices can't see it.

Thanks revolution. I didn't think of descriptor tables in my original post, are their positions affected automatically after I enable paging, or do I have to reload their locations?

For example, I have GDTR(the actual register, not the common label name) pointed at 0x100, but I have 0x100 mapped as 0x1000, does GDTR now point to 0x1000, or must I reload it with the location mapped to 0x100? Are tables affected at all by paging?

All the locations used are just theoretical.

Tyler: Did you download the Intel/AMD documents I suggested? Read the Intel manual volume 3A, chapter 3: "PROTECTED-MODE MEMORY MANAGEMENT". You can find all the gory details of exactly how it works. With pictures and diagrams and things also.

It wasn't working when I checked last night, it is today though.

Last night, I clicked on the support page link, it stalled until my connection timed out multiple times, but it's good now.

GDTR point to linear memory.
TR points to descriptor in GDT as a segment registers (because it is a segment).
etc...

you have the chance to speak and read english, down the manuals and read them.

Paging-wise, virtual B8000 remainst mapped to physical B8000. But the northbridge sends accesses to it to Video RAM, instead of regular RAM. This is set by VGA and chipset register.