When I say non-os I really mean just some executable code
of my own.

My scenario is:
x86_64 processor, standard hard drive.
I want to create a blank partition and boot into my executable on it.
I'm thinking to use grub as a boot loader but not sure what to
do with my code to make that executable -

Can anyone talk me through how to configure my code so grub
can find and run it? Must I use a header such as ELF - if so what is the minimum I must do - or can I do it as a simple executable without that?

also can I get grub onto a drive before there is any other OS on it?
Or can I get a simpler solution than grub in the first place?

Yes, however without an OS you can not use standard libraries or functions etc. In 16 bit real mode you can use the built in BIOS functions for keyboard and writing to the screen. I would guess you do not have enough programming experience to be able to do this so tell us what are you trying to accomplish so we can offer you some different ideas.

http://www.codeproject.com/Articles/...bly-and-C-Part

Thanks michael

All I was trying to do was exactly as described.

I've been around the block a few times. This is just something I've never done.
It turns out reading the grub docs had persuaded me this was a lot more complicated
than it is but thanks again for the suggestions anyway.

You just need to have executable code which matches the arch of the machine. The first bits of bootloader code are an example of that.

Here is a library where you can make a C++ program that runs without any OS. And you can use standard library functions:


http://www.includeos.org/

[QUOTE=Guttorm;5622619]Here is a library where you can make a C++ program that runs without any OS. And you can use standard library functions:


That web page has the word "cloud" on it. At which point I stop reading.

Again thanks - but I'm all sorted now anyway.
A dozen lines of fasm and it's done.

Personally, what I would do is to strip Linux to its very-bare minimum, customized for exactly your hardware, and use it as the underlayment of your application.

There are also various non-Linux OSes that are specifically targeted at device-control applications . . .

In short, if it were me, I would not "blur the line" between "your application" and "the system-control program, whatever it may be." I would not merge this concern into "your application."

If you wish it to be, the Linux kernel can be "pretty damned small."