I don't have a 100MG reserved partition on this system.
Also, I found this other KB article:http://www.terabyteunlimited.com/kb/article.php?id=411
I've had some success, but I think it's not complete yet. Hopefully TB (David) can chime in, because I'm kind of stuck at this point.
Here's what I did.
- I kind of followed that article, copy the \Boot directory, bootsect.bak, bootmgr, ntldr, and ntdetect from the ACER-1 (XP) partition to the Win7 partition.
- I then setup a new boot item, with just the Windows 7 partition in it, and used BING BCD Edit to delete the "Earlier version of WIndows" item
- I can now boot directly into Windows 7 from BING boot menu, and I *think* that the Windows 7 partition is no longer depending on anything on the XP partiton (ACER-1).
The problem that I'm left with is booting to the XP (ACER-1) partition. It feels like that (booting to XP) is still tied to something on the Windows 7 partition.
The reason that I think that is that I left the original XP boot item in the BING Boot menu. That has, for partitions:
 Acer recovery
 ACER-1 (XP) partition
 Windows 7 partition
And, using this original XP boot item, I can boot, what it appears to be, directly into XP from BING.
HOWEVER, I tried creating a new "XP only" boot item, where it only has:
 ACER-1 (XP) partition
When I booted into that, it said it couldn't boot. I figured it was because the boot.ini on the ACER-1 partition had "partition(2)", which is the Windows 7 partition (the 3rd partition, counting from 0), so I changed the boot.ini in the ACER-1 partition to "partition(0)", since, for the "XP only" boot item, I had only the ACER-1 partition in slot 0 of the boot menu.
Then, when I tried to boot the "XP only" boot item from BING, I get an error saying that it can't find <Windows root>\system32\hal.dll !!!
I checked the ACER-1 partition, and in the <Windows>\system32\ directory, there IS a hal.dll, so I'm kind of stumped at this point, and can't understand what's going on. It almost seems like when I boot to the "XP only" boot item, it's looking for the hal.dll on the partition(s)???
Now, on the ACER-1 partition, there's apparently still a BCD (the BCD Edit still shows up in BING properties), but I thought that XP doesn't use BCD for booting (it was only used from Vista onwards??). Also, I have to admit that I don't quite understand BCD (the old boot.ini was a lot simpler), but I *did* check BCD edit on the ACER-1 partition, and that DOES look "ok", i.e., the Boot setting says "HD-0" and "ACER-1".
So, any ideas WHY, when I set up the "XP only" boot item in BING, and then adjust the boot.ini on the ACER-1 partition to "partition(0)", it can't find the hal.dll?
Should I just blow away the BCD stuff on the ACER-1 partition, and if so, how do I do that?
Thanks and hopefully TB/David will chime in!!
P.S. I think that I'm ok for now, in that I can boot XP and WIn7, but I don't like the way that this is working, i.e., it looks like if I change the relative positions of the 1st 3 partitions (Acer recover, followed by ACER-1, followed by Windows 7), something would break.