Thanks Simon Bridge & syg00
Surely this is a problem with the way the VM is set up in Virtualbox
This would not surprise me because I had to glean fragments from many different places to get this far.
This is how this partition is booted native.
From grub menu.lst
title XP Home testing installation
map (hd0) (hd1)
map (hd1) (hd0)
Then it hits longhorn as pointed out by syg00
From boot.ini located in the C:\ of the partition
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="XP Home test install" /fastdetect /NoExecute=OptIn /bootlog /sos
C:\CMDCONS\BOOTSECT.DAT="Microsoft Windows Recovery Console" /cmdcons
Then xp comes up in it's malfunctioning state.
The last line is the recovery console and as I understand it the '/cmdcons' is some kind of pointer to a file buried in windows somewhere that tells the boot loader where and how to boot it.
check the message at failure.
The only message I get when I try to launch the vm is about the host os, Debian Lenny, sound system not working which may cause the guest os sound apps to hang. If I reset the vm I don't get that message. In either case the vm just sits there with a black screen and my processor is at 100%.
The command I used to create the vmdk image (if image is the right word).
VBoxManage internalcommands createrawvmdk -filename /home/rbees/.VirtualBox/VDI/WinXP.vmdk -rawdisk /dev/hdb -partitions 2 -relative -register
I guess I can make a vmdk that points to the whole drive my understanding is that they don't take up very much space because they only hold the wright through information. Doesn't take very long either about a minuet or so.
If that boot sector record is invalid, it doesn't matter what you use - even ntldr.
An invalid boot sector would not surprise me either. The short version; Windows did bsod, bsod said cause may be hard drive, did complete reinstall including rc partition, still bsod, installed new master hard drive moved old drive to slave installed to master, still bsod, windows on slave not boot either, told wife she would have to deal with it, booted into Etch problem cured. Stupid windows.
That was a couple of years ago. Now that the vm's have gotten to a more useable state I decided to get that non booting partition to boot in a vm, then my wonderful wife could run her windows dependent bowling league and book keeping programs without having to boot into windows.
Would looking at the boot sector of that partition tell me anything?
How do I look at it?