Sorry if I came across a bit harsh there in my previous post, I hope you'll try Linux again sometime soon.
I have lots of time to help someone who really wants to learn, just no time for people who come to ridicule Linux and GRUB and don't really want help.
I thought you might have been a trouble maker here to try us out, giving us your problem but not enough info to solve it, then blaming Linux and GRUB.
Now I see that you have another thread here and you might be a person genuinely wanting to learn and needing a way to get started.
I'll try to explain a few things, it might help you or someone else.
I'm not sure what went wrong with your installation, but for most of us, the installer gets it right, and Mint will be installed and the boot loader set up automatically to boot either Windows, (if you have it), or Mint, plus any other operating system that might be detected in the computer.
Probably the most important information that boot loaders need is the information from the BIOS about what hard disk(s) your computer has.
After that, the partition information in the partition table of each hard disk(s) MBR is needed.
Most computers come with Windows in them when they are bought from the store, and the great majority of people don't know any better.
If you have only ever run one single installation of Windows in your computer, you probably think Windows is in 'Drive C:'.
It may never have occurred to you to question that.
Your 'A:' drive is your floppy disc drive if you still have one, and 'Drive B:' is reserved for those old 5 1/4" floppy discs that hardly anyone has anymore.
'D' drive is probably your CD/DVD drive, unless you have a logical data partition.
Windows XP has a boot loader called NTLDR, which is good for booting one Windows installation.
NTLDR can be configured to boot more than one Windows installation, but it's a little bit complicated to use. You need to be able to edit a file called boot.ini, which is a hidden, read-only, system file in most Windows systems.
To get boot.ini to tell the boot loader, NTLDR, which hard disk and which partition Windows is in, you need to know the hard disk number and the partition number.
If the partition number or hard disk number for Windows gets changed accidentally, or Windows is copied to a different partition somehow, you can't boot Windows.
But if you edit boot.ini with the right hard disks and partition numbers, you can fix the Windows boot loader to boot Windows XP in any partition or hard disk.
Now you can forget about any 'Drive C:' and other drive letters, those are only for people in computer user land, and drive letters don't have any real meaning as far as any boot loaders are concerned. Hard disks are numbered counting from 0 (zero), and so are partitions.
Most Windows boot error messages can be cured by editing the boot.ini file, and/or by running CHKDSK.
Examples of Windows boot loader error message are like 'autocheck program not found - skipping autocheck', 'hal.dll is missing or corrupt', and 'NTLDR is missing, press any key to restart'.
Those are normally caused by Windows not being able to find it's own files.
A typical boot.ini file looks like this, (above), note the hard disk number is zero, (for 'first hard disk), but the partition number is 1, (for first primary partition).
Hard disk and partition numbers are really simple, hard disks are numbered 1, 2, 3 and 4 and so on.
Normally they are numbered automatically by the computer's BIOS, depending on the way they are plugged in to the motherboard and how the jumpers are set.
The computer's BIOS always looks at the first hard disk's MBR for a clue about where to find a boot loader.
The MBR's job is to direct the BIOS to the first sector of a partition (boot sector), or to a boot loader itself.
The MBR contains a little boot loader code, and the partition table to help it find the operating system, as the operating system could be anywhere in the hard disk.
Once the boot loader is engaged, if all goes well, the boot loader will find the operating system's kernel and load it into the computer's memory and the operating system will boot.