Omg.i changed scsi0.present from TRUE to FALSE and that solved the issue!!!! No more BSOD. vmx file of your VM and manually changeĬhange scsi0:0 = “FALSE” OR add the line if it does not exist at all.Īlso as a side note, some will not PXE boot so this line also is a life saver: The way we configure our VM's for creating and testing deployments for XP is to go into the. VMWare Workstation likes to default to ACHI and not make it very easy to change. Just don't understand why storage drivers would be "wrong" for those two?
So the only want to install the lat d531 and vmware workstation is to deploy using win xp setup files with the drivers injected using the selection profile. Same method above, I also found that the latitude d531 BSOD too. Uses a win xp 32 bit wim and associated that task sequence with the profile in the "inject drivers" section. Created a selection profile called "vmware workstation win xp 32 bit" and associated the OOB driver folder with it. I created an OOB driver folder called "vmware workstation win xp 32 bit" and import the drivers. Just to backtrack, I did a partial #3 total control method. Regards, Vik Singh "If this thread answered your question, please click on "Mark as Answer" How have you created your folder structure and what was entered in DriversPath? So, you used the Total Control menthod by Johan's Blog. Stop 7B in this case is surely a driver problem and definitely storage drivers for VMWare.