This time though, I am using Linux (gcc, etc) instead of Windows (visual studio) as my development environment. This resulted in changing all of the inline assembly in my kernel to the GCC AT&T format, not difficult but time consuming. The kernel now compiles. Haven't been able to run it yet though, because of boot problems. Originally, I was linking to a binary because my custom-built boot loader expects a PE and I'm no longer using Windows as a development environment. So I just made a slight modification to the boot loader to load a flat binary. Problem was it didn't work, and I figured out that it was due to 16-bit addressing restrictions, the kernel was coming out as a 90kB file... So I have spent the last few days unsuccessfully trying to get grub to work, but it won't recognize my multiboot header for whatever reason. I don't know why, it occupies the first 12 bytes of the file (now an ELF file) and contains everything it should have for GRUB legacy as far as I can tell. Then I realized that the ELF file was only 5kB! All I have to do is get my working boot loader to parse ELF files and its all good . No need to figure out grub and I am back to 100% my own software. Shouldn't be too difficult to program, my kernel already has a working ELF loader, I did it once, I can certainly do it again. Jacob
(VS is a decent IDE, for all sorts of things, but most osdeving sites assume that you're on a UNIX-like environment.
(I am still struggling with binaries. 
)