bubach wrote:
What executable format is your kernel, PE-EXE, ELF, flat binary, else?
Flat Binary
bubach wrote:
At what address do you what it loaded?
Since the code will be used to load two files (the stage 2, then the kernel) at two different addresses, I would like the Fat32 code to only refer to variable names, and then these variables would be assigned values in the code calling it (the stage-1 then the stage-2, respectively)
bubach wrote:
It the second stage loader supposed to do something else, like entering protected mode, gathering information about available RAM, set a video VESA mode?
Yes, but I can take care of that. Right now I'm really struggling with the FAT32 code.
bubach wrote:
What kind of budget are we talking about?
$400CND
bubach wrote:
What OS will you use it from, so tools to automate the process can be included or at least instructions?
It will be compiled on a Windows PC using NASM. It will run in a virtual machine with no OS.
bubach wrote:
Also, you could include an image file of the USB drive freshly formatted with FAT32 and it will include everything needed to complete the task.
Yes, I will provide all information requested by the person helping me.