Sorry, what do you mean with "partitioned"? I'm totally noob at this.
Good, then you couldn't have possibly made a "queer" partitioning, but you can still tell us if you had before 1 or 2 volumes visible (or 3 - which I doubt at this point see below).
A "volume" is the *whatever* that normally gets a drive letter, i.e. did you have C: and D: or C: only or C:, D: and E: as drive letters?
I tried what you suggested; a window opened: http://img43.imagesh...3/6080/l0wm.jpg
Strangely enough, this is good news.
It means that you have a recovery partition (created by the manufacturer) and that then it was ALREADY hidden.
Must I follow instructions and see what happens?
That (if it works) will restore the OS "as it was" (and you will lose all data).
Revert the change you made:
then issue the following:
It should boot alright.
That PC is a laptop and the manufacturer has made a "recovery" partition on it.
That partition is (and should be) "hidden", but even if hidden remains first partition on disk.
The grub4dos command "find --set-root /boomgr" scans ALL partitions (no matter if hidden or not) for file /bootmgr, since the recovery partition is evidently Windows PE based, actually more likely Windows RE based (both use BOOTMGR as OS loader, like Windows 7 install does) the first found file is on the first partition (but this is the one that is hidden and not actually the one that should be booted).
Spyhunter (or some other software that *somehow* installed grub4dos) has a "standard" menu.lst (grub4dos menu) that looks for BOOTMGR on first partition first, and this creates the issue.
Report what happens, then if hopefully successful we'll talk about how to "fix" the issue.