Ok, looking at your image and rereading your description, it seems to me that you will have to do a "manual" edit of your Boot.ini in XP Pro to pick up the XP Home install. This is not necessarily a "bug" per se, but is the manifestation of you MOVING the HDD to a secondary controller and it no longer being the "active" HD on the system.
I believe a manual edit of the Boot.ini would fix this - but please wait for additional guidance on this, as we don't want to jump to conclusions just yet.

http://www.pronetworks.org/forum/viewtopic.php?t=78102

JabbaPapa wrote:

http://www.pronetworks.org/forum/viewtopic.php?t=78102

hey, i don't think that applies to me Jabba Pappa, as i've got all those files on my main drive and all my drive letters match the ones in VBP.

can someone confirm what kd1966 (is that a reference to the english world cup win by the way? ) was saying?

at the moment i only have the XP Pro install in my boot.ini on my C drive and only the XP Home install in my boot.ini on my F drive.

is this the problem? when i tried adding the XP Home install to my boot.ini on my C drive it just created a second old style boot menu that appeared after i selected either of the non-vista OSs.

thanks again and apologys if i'm being slow here.

Another option would be to create the XP Home entry in VBPro as a new legacy OS entry

No, nothing to do with you Splog ...

...

In order not to confuse things any further, I will pursue the XP VBP bug issue in a separate thread.