I wasn't trying to be rude, I was just strongly encouraging you to invest in yourself, learning the grub os is a great investment. As a side note in the linux console as root type "grub", that will enter you into the grub enviorment, which has all it's own commands just like dos, to exit just type "quit".
title Linux Mint, kernel 2.6.22-14-generic
kernel /vmlinuz-2.6.22-14-generic root=/dev/sdc3 ro quiet splash
The line root, above is for grub to read, it tells grub where the kernel is located, that is not necessarily your /(root) partition, this address is in grub terms because grub is reading it. If you have /boot on a separate partition then the kernel is there, after the kernel loads, grub is no longer running, so the kernel line has another address pointing it to the /(root), this address is in linux terms because linux is reading it, not grub.
but the first command is "root (hd2,1)". Is that telling GRUB where my root partition is?
No, it's telling grub where your kernel is. Normally the kernel is in the same folder as /grub/.
But how does it know where my boot partition is?
Ok when you install grub, there's actually two installations, the first is into your Host OS, in this case Linux, that allows grub to run at other times then boot. Then grub can/is run ether with an install script or manually. At that time it searches/creates for/a /boot/grub/menu.lst, it also maps the system and creates some stages files, such as stage1.5. Then it inserts a complete system onto the MBR, which knows where /boot/grub/menu.list is and those stage files.
If it couldn't find these files you would get other errors, that is not the case.
Grub is also doing another interesting thing in your case, I have one box doing this also.
title Windows Vista/Longhorn (loader)
map (hd0) (hd2)
map (hd2) (hd0)
Grub is remapping your system. Windows will not boot in drive D: position, so grub is swapping the drives making it appear to the bios as drive C: before it passes it off to windows. Notice the two map lines. If windows was in the primary master position it would only have one map line.
I do see your windows partition is 100 and some odd gb big. Your bios has some limitations, if your second partion is beyond the bios limitations, grub won't be able to read it. It's sort of strange the boot strap process, I don't know all the technicole side of it. But to make it short and sweet.
The bios starts the PC, runs some checks, then passes off to the bootloader, this is done in an easy sort of way grub using some of the bois knowledge to start., then the bootloader runs and passes it off to the OS, again sort of easly, the reason for two different address lines in the stanza.
I've had occassion where grub loaded fine then was unable to finish due to driver issues and limitations. Some large drives play tricks on the bios to see that large drive, those tricks getting dropped have way through somehow.