Running an XP Partition (SP3) in Ubuntu 9.04

[vboxuser31]

I am having a small problem with running my XP Partition off my Hard Drive in Ubuntu 9.04 using VirtualBox. I am unsure of my version of VirtualBox, but I my Ubuntu is FULLY updated and I downloaded my VirtualBox via Synaptic Package Manager, thus, it is most likely the latest version of VirtualBox. Ok, now onto my problem. Here's the steps I did up until the point of my problem.

*All of the File Uploads are in consequential order of the processes in which took place*

[vboxuser31]

Continuation...

[vboxuser31]

Continuation...

[vboxuser31]

Continuation...

[vboxuser31]

Continuation...

[vboxuser31]

Sorry for so many posts, I can only upload 3 images per post. Anyways, as you can see, Step 13 or the last image is the problem I am running into. I tried to boot up my Linux Mint as well, and it seemed that the cursor refused to work in the virtualization. If you have any insight of what might be a possible solution, that would be a great help.

Thank you
vboxuser31

[Sasquatch]

Check the wiki Editions Page. It says that RAW Disk Access is for the PUEL version ONLY. It's also in the manual. So you need to change that version, as you're using the OSE one.
After you changed that, check the howto in the Windows Guests forum.

[peter_altherr]

and by the way, referring to your first statement: installation via synaptic ensures to have the lastest version. this is definitely wrong. i thought the same until i found out it is not that way. for instance: if you have vb 2.2.0 installed via synaptic and vb 2.2.2 is available i had to manually start synaptic and search for vb recognizing there is a new version. so i choosed the new version which caused the old one to be removed. i have no idea why it is working this way. maybe the vb guys have not really learned the version management under debian or they want to have it this way for whatever reason.

regards

peter

[Sasquatch]

and by the way, referring to your first statement: installation via synaptic ensures to have the lastest version. this is definitely wrong. i thought the same until i found out it is not that way. for instance: if you have vb 2.2.0 installed via synaptic and vb 2.2.2 is available i had to manually start synaptic and search for vb recognizing there is a new version. so i choosed the new version which caused the old one to be removed. i have no idea why it is working this way. maybe the vb guys have not really learned the version management under debian or they want to have it this way for whatever reason.

regards

peter

Updating 2.2.0 to 2.2.2 using the repo is not the issue. The repo is working just fine. Your problem is upgrading to a new major version. That is under a new name. Upgrading from VB 2.1.4 to 2.2.0 means installing a new package, because they are listed as VirtualBox-2.1 and VirtalBox-2.2.

But that's off-topic here.