m sry if i offended u
I'm not offended. Just plain annoyed that you ignored the "Read me" link and "posting rules" thread even after being pointed at it
i wasnt sure abt it as it wud shut my system down
that was *not* what you asked.
back to the link (I really urge you to read it thoroughly as well as the other 90% of that document):
More generally, if you write like a semi-literate boob you will very likely be ignored. So don't use instant-messaging shortcuts. Spelling "you" as "u" makes you look like an semi-literate boob to save two entire keystrokes. Worse: writing like a l33t script kiddie hax0r is the absolute kiss of death and guarantees you will receive nothing but stony silence (or, at best, a heaping helping of scorn and sarcasm) in return.
(...)
Often, people who need technical help have a high-level goal in mind and get stuck on what they think is one particular path towards the goal. They come for help with the step, but don't realize that the path is wrong. It can take substantial effort to get past this.
Stupid:
How do I get the color-picker on the FooDraw program to take a hexadecimal RGB value?
Smart:
I'm trying to replace the color table on an image with values of my choosing. Right now the only way I can see to do this is by editing each table slot, but I can't get FooDraw's color picker to take a hexadecimal RGB value.
--------------------------
So far the rant, now to your 'problem':
It will more likely reboot, but I guess that's not your real question either...
Grub loads all its file from disk, and so does windows/linux. If you want to mess up any existing OS you must change those things that
1) affect them
2) persist even when you disconnect power
Unless you blow up your hardware (which is very unlikely) that means that you must have made changes to the hard disk.
Since starting a write to disk is harly anything that happens by accident, it simply means that when you do not include any code that accesses the hard disk, your existing setup will be pretty much safe. The only fried setups I ever had was because of a broken
windows installler without me noticing the error in time (128G will always be enough?
)
The tutorial does not really create a 'flat' binary, but instead a multiboot image. GRUB is one of the bootloaders capable of booting such images. There are more, but they're non-standard and even self-written bootloaders are more abundant. If you want to go all the way, you can drop the multiboot format and write your own bootloader, or even a mixture of both. The wiki has the so-called babystep tutorial that deals with bootloaders.