Windows XP SP3 - Image - BAD_POOL_CALLER error

[Anunes]

Hi,
Host OS: Windows 8.1 64-bit
VirtualBox Version : 4.3.12 r 93733
Guest as Image: XP - SP3 with all latest Drivers.


I can run the XP-image in safe mode but when starting it in Normal mode I keep getting the error BAD_POOL_CALLER inside the Guest XP, not on the Win 8.1.
I have disabled/Delete every "old" driver. Also I have disabled all "Startup" items as well all no-Microsoft Services.
I have tried everything I could/ I am aware but no luck.
Any Help?
Thank you
Regards

[Perryg]

Did the guest ever work properly?

[Anunes]

Did the guest ever work properly?

Yes, is still working without any problems on my other Laptop.
Well I must say the XP is some 5 years old installation and there are a lot of Apps installed.
Will it help (for sure) to remove all the Apps on the other Laptop an then make the image?

[noteirak]

So you copied the guest from a host to another - there are implications to that, especially if the CPU is different. I would assume the VM never worked on this host?

[Perryg]

Let me ask this another way. Has the Virtual Image ever worked in VirtualBox other than in safe mode?

[Anunes]

So you copied the guest from a host to another - there are implications to that, especially if the CPU is different. I would assume the VM never worked on this host?

I used some Software to do a Image of the HDD of the other Laptop. The other Laptop is 10 years old Hardware wiht Intel P4 cpu.
This Laptop is a Intel core i5.

Are you saying, it will not work making Images of HDD from a different Hardware to another?
Well , if so I am very sad, because I have Images of OS/2 Warp and I was planing to put them on P4 Laptop and make Images to run on the i5.
The P4 is my last chance to get OS/2 Warp again to live. I will not be able to install it from "fresh" on the new Hardware.

[mpack]

Now you have me confused. Perry asked you if this VM ever worked as a VM before today. Your last post makes it sound like a P2V project, not simply a problem of moving an existing VM from PC.A to PC.B.

Please clarify what this problem actually is.

If you are converting an old PC from physical to virtual then the task is called a P2V migration, and it will go a lot easier if you prepare the image somewhat first. Read this wiki article. You can ignore the obsolete "step by step" part - Disk2VHD is all you need.

I have a feeling that your problem will be the "intelppm.sys" issue - in which case all you need do is delete that driver file before imaging.

[Anunes]

Now you have me confused. Perry asked you if this VM ever worked as a VM before today. Your last post makes it sound like a P2V project, not simply a problem of moving an existing VM from PC.A to PC.B.

Please clarify what this problem actually is.

If you are converting an old PC from physical to virtual then the task is called a P2V migration, and it will go a lot easier if you prepare the image somewhat first. "wiki/Migrate_Windows]Read this wiki article". You can ignore the obsolete "step by step" part - Disk2VHD is all you need.

I have a feeling that your problem will be the "intelppm.sys" issue - in which case all you need do is delete that driver file before imaging.

I am sorry for my poor English. I am not English speaking.
Also I am very new to the Virtual Machines.
Well, yes it is a P2V migration project.
I will follow the steps you pointed me and post the result later today here.
Thank you for your help

[Anunes]

I did delete the AGP400.sys and INTELppm.sys from the XP installation and did a new P2V file.
Now I run the VB with XP_SP3 as Guest.
I did delte all Drivers from Device Manager.
I opened MSCONFIG and choose the option "Diagnostic Mode", so there will be no drivers installed, beyond the absoluty necessary for Windows. After that, opening Device Manager there no Drivers at all to see.
But still I get the BAD_POLL_CALLER error.
Any Ideia?
Or the only thing I can do is a system repair from Original CD?

EDIT: While running XP_SP3 as Guest and in Safe Mode, there are 2 Devices with Yellow Question Mark in Device Manager. One is for Video Device and the other is for a piece of System Device.
Do I need to install Drivers on the Guest for the Graphic Card Hardware of the Host?

[mpack]

Your English (in written form at least) seems fine to me.

Both of those "question mark" entries in the device list are harmless. I have them myself in a couple of working VMs. It just indicates the presence of plug and play hardware that XP doesn't have drivers for - and doesn't really need.

Bear in mind that there will be a limit to how far we can help you with getting XP to work - at this point it is no longer an VirtualBox issue.

Did you also run MergeIDE before imaging the XP system? That's very important too, as is choosing a IDE disk controller (not SATA) in the VM settings.

After that I would boot up in safe mode, get to prompt you before loading each driver, see how far you get.

Oh: and post a zip file containing your .vbox file and the Logs\VBox.log file. Make sure the VM is shut down (not running or suspended) before collecting these.

[Anunes]

After that I would boot up in safe mode, get to prompt you before loading each driver, see how far you get.

Hi mpack,
Thank you.
Can you explain how I get to prompt before loading each driver?

I also run Merge IDE.
I can always Boot in safe Mode even with Network support and I can access the Shared Folder.
I can do everything in Safe Mode.
Only Booting in Normal Mode I get this error. I tried everything I can /Windows is offering but no luck.
I am aware that a P2V Project is limited, it would be a "Wonder" if it was working just like that.
I am sending a Zip file with all .Vbox and Logs I have.

[mpack]

Actually no, I can't tell you - it's too long since I needed to use it last, and anyway that is a Windows support question. I might also be remembering Win98's safe mode.

But, if it boots for you in safe mode then that at least tells you something: your problem has to do loading a bad device driver, i.e. a driver that isn't designed for the virtual hardwre but also doesn't bother to check. You would have to look for non-MS hardware drivers in the original PC, and delete them.

[Anunes]

You would have to look for non-MS hardware drivers in the original PC, and delete them.

Hi mpack,
I did delete from the old Laptop all the specific drivers (PowerManagment, Mouse, LAN, WLAN,TV-Stick, a.s.o) and build a new P2V project and now I can boot in normal mode.
Great!
Now I have a 2nd problem: Windows want to Activate it again!
I have installed VB 4.3.12 and only the host drivers. Will I be able to Activate Windows XP SP3 from inside the VirtualBox?

Thank you!
VirtualBox is a great project. Congratulations to all of you.

EDIT** : I did not use MergeIDE neither I delete the AGP400.sys or INTELppp.sys. So, system works as Original.

[mpack]

Now I have a 2nd problem: Windows want to Activate it again!
I have installed VB 4.3.12 and only the host drivers. Will I be able to Activate Windows XP SP3 from inside the VirtualBox?

The hardware which the guest sees has changed radically, so a reactivation request is normal. And yes, you activate it from inside the guest just as if it was a real PC - which it is.

However - from experience I suggest that you postpone activation for as long as possible, until you have finished tweaking the VM - the goal being avoiding the need to activate the VM more than once. Microsoft doesn't like it when a license is activated more than once in any 120 day period.

I did not use MergeIDE neither I delete the AGP400.sys or INTELppp.sys. So, system works as Original.

If you already did these things for a previous attempt then the laptop was already permanently modified. You don't need to do it more than once, no matter how often you P2V the laptop.

Remember to install the Guest Additions. The VM experience will be much smoother when you do.

[Anunes]

Microsoft doesn't like it when a license is activated more than once in any 120 day period.

That is a very important thing I did not knew. Thank you for that.

I did not use MergeIDE neither I delete the AGP400.sys or INTELppp.sys. So, system works as Original.

If you already did these things for a previous attempt then the laptop was already permanently modified. You don't need to do it more than once, no matter how often you P2V the laptop.
Remember to install the Guest Additions. The VM experience will be much smoother when you do.

I had not modified the XP_SP3 installation with the MergeIDE. I have used MergeIDE inside P2V not on the Physical Machine.
Also, I did only rename the AGP400 and INTELppm drivers on the original XP_SP3 machine but somehow they appear with their original names back inside the P2V project. Seems Windows put them automaticaly back.
So it means that the XP-SP3 P2V project works without any modification.
For information: the Old Laptop is a Intel based PC (Cpu and Chip Set are Intel).
About Guest Additions, already done, works great.

Now, do I need to install the "Bridge Networking" drivers too? Or will the "Host only" LAN drivers do the job?