SOLVED - Virtualbox won't boot

[Maurice]

I dual boot Pclinux with WindowsXP and have just installed Virtualbox. I used the default settings and the setup went fine. So I rebooted but when I pressed  'Start' I get the error message --

Could not read from the boot medium. System halted.

In my Boot menu I have Pclos as the default. I then set XP as default but that didn't help.

In the Vbox Settings I have hard disk set as the boot order and I/O apic enabled.

I did reboot after installing Vbox

Am I missing a setting somewhere?

[T6]

are you trying to use the xp partition from the dualboot on the virtual machine?

don't know if that is possible to do that way

what most users normally do is create a virtual machine and then in that virtual machine install xp or whatever you need

[Maurice]

are you trying to use the xp partition from the dualboot on the virtual machine?

don't know if that is possible to do that way

what most users normally do is create a virtual machine and then in that virtual machine install xp or whatever you need

Yes - I tried both XP and Pclos partitions.

Do you mean I have to install XP from the original CD?

[johnmart]

Yes, what T6 said. You have to create your virtual OS from an install medium. CD, DVD or ISO.
afik

[Maurice]

Yes, what T6 said. You have to create your virtual OS from an install medium. CD, DVD or ISO.
afik

Duh. I've just got to the part of the manual that explains that.  

But, if I put in my original XP disk, will it then reinstall XP and does that mean that I will lose my present XP with all my stuff on it?

[Xenaflux]

if I put in my original XP disk, will it then reinstall XP

If you mean re-installing the XP you had before you installed Virtualbos, the answer is no

If you install an operating system in virtualbox, either OS ( Windows or linux ) will see only one big file and they will not interfere with each other, unless you start up Vb and specificallly tell them to do so ( but not by default )

and does that mean that I will lose my present XP with all my stuff on it?

Again, it you refer to the XP which you had before you installed Virtualbox, no, it won't touch it. The two Xp's are separated things

I hope I understood your problem/dilemma correctly

[muungwana]

this is how virtual box works, atleast how most of use use it.

1. You install virtualbox on your computer and run it the same way you do with any other program on your computer.

2. You start virtualbox and then you install another operating system inside of it and then you use this installed operating system inside virtualbox and everything related to this installed system is contained within virtualbox. The operating system that runs inside virtualbox is called "guest" operating system and the one the computer was booted on is called "host" operating system.

In your case, you will have to start virtualbox and have virtualbox cd drive point to your windows cd and then let it install windows and then you will run this install of windows completely within virtualbox. Your windows partition is completely not touched. As a matter of fact, any other aspect of your host system will not be touched. VirtualBox will create a file and the entire windows install inside virtualbox will live in that file and the file will be like any other file on your system to the host system.

[Maurice]

Many thanks fellows for all your replies. I think I've got an inkling of an understanding.

However I've just got back from a rather bibulous dinner at my daughter's so, as this seems to be a somewhat thorny undertaking, shall wait for tomorrow before tackling it.

Actually all I use Windows for is a charting program for forex trading so all my 'stuff' on my present Windows is of no great importance. But VB will save rebooting from Linux to XP and back again.

Will let you know how I get on and thanks again

Maurice

[John Bee]

Hi Maurice;

 I just wanted to add this:  You can only install an MS OS to one machine, as per the license.

So if you install your XP in VBox, you can no longer use your other installation.

I mention this, in case you do install to VB and then activate XP in the VBox (which you will have to) and then try to use your original install, MS, can/will kill both installs, because you installed twice with the same key.

In other words, if you want to install XP to VBox, and not disturb your existing XP install, MS says buy a new XP. 

[Maurice]

Thanks for the reminder John.

I managed to get it working OK last night after all but the desktop overlapped the screen and I had to scroll down about 2 inches to see the panel at the bottom. My normal resolution is 1680x1050 but I tried various resolutions and still had to scroll.

I then downloaded Firefox. Rebooted. Reopened VB, Windows came up with its opening screen then a blue screen appeared

"A problem has occurred which seems to be caused by the file intelppm.sys.

The problem is still there when I booted this morning.

Any ideas please?

[muungwana]

Thanks for the reminder John.

I managed to get it working OK last night after all but the desktop overlapped the screen and I had to scroll down about 2 inches to see the panel at the bottom. My normal resolution is 1680x1050 but I tried various resolutions and still had to scroll.

install virtualbox guest additions and you will be able to set the resolution of virtualized system to that of virtualbox window.

more info at: http://www.virtualbox.org/manual/ch04.html

[muungwana]

is your computer using an AMD processor?

this link seem to discuss the problem you are seeing: http://www.runpcrun.com/0x0000007E

[John Bee]

Thanks for the reminder John.

No Problem, Maurice. I'd hate to see you lose your XP. 

[Maurice]

install virtualbox guest additions and you will be able to set the resolution of virtualized system to that of virtualbox window.

more info at: http://www.virtualbox.org/manual/ch04.html

Trouble is (because of the blue screen) I can't get into VB Windows to get into the Devices menu to install Guest additions. Catch 22 situation.

I have an Intel processor.

[muungwana]

did you update windows after you install but before you rebooted? that windows cd has what version of system pack? what version of virtualbox are you using?. Not everybody gets that error msg its probaby due to something unique on that windows installation image.