SATA Driver Slipstreaming w/nLite + VMWare = BAD_POOL_CALLER

Rebooter

Rebooter

New member
I'm upgrading my system soon (new MB/Mem/CPU). I'm having problems slipstreaming SATA drivers into a Win XP install disk. I use nLite, but when testing in VMWare, I keep getting BAD_POOL_CALLER errors just when setup tries to access the virtual harddrive.

The test in VMWare isn't for the SATA drivers, but for the rest of the install. I know that VMWare machines don't support SATA, but in the past it would just skip the SATA drivers and work. If I redo the ISO with nLite without the SATA driver integration, it works fine. I have also tried different ISOs as the base for the nLite ISO and with different options (install modes, no OEM install), same deal: They only work if the SATA drivers aren't part of it.

I have created slipstreamed SATA setups before and they tested OK in VMWare, but now I keep getting these errors no matter how I try it.

I can try using the F6/Floppy method, or use native IDE when running setup and trying to change it to SATA later, but I'd like to have a proper SATA install from the CD if possible.

Has anyone had this issue with VMWare + SATA slipstreamed XP setup? Is it just an issue with VMWare, and it'll work with the actual hardware? I'm just trying to iron out all the software details before I start the hardware upgrade. I'm going to do a dual boot with XP 32-bit and Windows 7 64-bit.
 
Try a different VM say... Virtual Box, which has an option for emulation of a SATA and IDE hard disk. To be honest, I'm not sure that's good idea testing on VMs as they act vastly different than hardware does.
 
FiggyG said:
Try a different VM say... Virtual Box, which has an option for emulation of a SATA and IDE hard disk. To be honest, I'm not sure that's good idea testing on VMs as they act vastly different than hardware does.
Click to expand...
I couldn't disagree more.

Rebooter, have you included the VMware drivers (scsi, etc.) in the image as well? Are you using SCSI, SAS or IDE controller in your VM?
 
caveman-jim said:
I couldn't disagree more.

Rebooter, have you included the VMware drivers (scsi, etc.) in the image as well? Are you using SCSI, SAS or IDE controller in your VM?
Click to expand...

Using IDE controller in the VM. I didn't know about vmware drivers for the image, haven't really needed them before. As this worked for an ISO I made a year or more ago, it just seems strange that I always get the BAD_POOL_CALLER now. Maybe they changed something in VMWare... I'll try the disc made from the ISO Thursday or Friday with the real hardware. Maybe it's an nLite problem. The disk that worked was made with an earlier version. I wish I could just drop XP, but I have some games/apps that don't like 7 64-bit.

The BAD_POOL_CALLER BSOD seems like windows setup is trying to load one of the drivers even though it's not needed (the wmware machine is IDE).
 
caveman-jim said:
I couldn't disagree more.

Rebooter, have you included the VMware drivers (scsi, etc.) in the image as well? Are you using SCSI, SAS or IDE controller in your VM?
Click to expand...

Does the VMware driver act exactly like the piece of hardware that the driver is designed to use? AFAIK, they use generic "hardware" as possible for the guest OS to install without any fuss. Would you disagree with this?

Rebooter, what SATA driver are you slipstreaming into XP?
 
FiggyG said:
Does the VMware driver act exactly like the piece of hardware that the driver is designed to use? AFAIK, they use generic "hardware" as possible for the guest OS to install without any fuss. Would you disagree with this?

Rebooter, what SATA driver are you slipstreaming into XP?
Click to expand...

The intel SATA textmode drivers.

The setup behavior in vmware before was that it would iterate through the drivers before it tried to access the virtual IDE HD. I can see the driver I added flash as it scans the list, but since it wasn't needed for the virtual ide, it was just skipped (which is what I expected) and the install proceeded. Now it seems that either it's trying to force the driver to load which then fails because the hardware isn't there, or maybe the nLite integration is bad somehow.

Maybe this is how it's supposed to be? Like if you add the driver, it's expected to be needed and loaded regardless? With earlier versions of nLite/vmware this didn't seem to be the case, maybe it's been changed...
 
Bhahaha :lol:

I've spent 6 years tweaking network, iSCSI and ZFS. Sometimes one has got to do it good and proper, science style :D
 
You must log in or register to reply here.
Back
Top