Hi KevinG,

Thanks for the reply. Yes, I have read the documents. However, the hard disk is a 120GB WDC1200JD. This is an SATA drive so this should not be a SCSI issue. Now, the error message implies that it at least make an attempt to read the MBR which is on the first hard disk, ie. my Windows Hard Disk. Could the problem be something else?

Cheers

Petr,

Thanks. The problem was me not making the boot partition available to VMware.

I am, however, still unable to boot successfully. After I select Windows in GRUB and after I choose my VMware profile in Windows, the following error message is displayed and the virtual machine shuts down:

"A problem has been detected and Windows has been shut down to prevent damage to your computer.

If this is the first time you've seen this stop error screen, restart your computer. If this screen appears again, follow these steps:

check for viruses on your computer. Remove any newly installed hard drives or hard drive controller. Check your hard drive to make sure it is properly configured and terminated. Run CHKDSK /F to check for hard drive corruption, and then retstart your computer.

Technical information:

*** STOP: 0x0000007B (0xF7B8524, 0xC0000034, 0x00000000, 0x00000000)"

I can boot my Windows partition with no problem. There is no viruse on my machine. Not knowing much about Windows, I am not sure how to proceed.

Petr,

I got some time to look for some online documentation about this error. The documents suggested that in my VMware hardware profile, I need to change my IDE controllers from third party to Standard Dual channel PCI IDE controller. So these are the steps I took:

1. Booted natively to Windows XP
2. Created a copy of the original hardware profile. Let's call it VMware profile
3. Rebooted natively back to Windows XP, but chose the VMware profile.
4. Opened the Device Manager and selected the IDE Controller
5. Updated both hard disk drivers to Standard Dual Channel PCI IDE controller.
6. Booted natively into Linux.
7. Started VMware and ran Windows XP as guest.
8. Selected VMware profile.

However, I am still seeing the same STOP 0x0000007B problem.

Petr,

Yes, I am using raw SATA. I even mentioned it on my Sep. 10th post. So what is it that I need to do?

Thank,
Nader

Nader, before copy-pasting continuum solution please make sure you remove spurious spaces from it - unfortunately it seems that current Jive version puts spaces to its output randomly

To bad - that doesn't help either - looks good in edit-mode but once posted the linebreaks are unpredictable.

Is it possible to quote something that needs to be exactly like the original???

Well this is strange - if you mark the quote and copy it to a new file the linebreak disappear but leave spaces.

Message was edited by:
continuum

Hi Nader
When you find "lsilogic" in the raw-disk descriptor, this means that the VMware_XP uses the disk as a SCSI-disk.
You are lucky - my computer uses the same SATA-controller - so I know that you can uses this one in VMware without having to tweak anything.
You just have to change the raw-disk descriptor so that I says 'ide' instead of 'lislogic'.

So I would recommend to create a new XP-VM with default settings - that means you will get a standard-IDE-disk. Nect thing to do is exchange the new blank disk with the raw-disk that you have already created and edited.

Then I would add the line
scsi0.present = "FALSE"
to your vmx-file (that's the file that you can double-click to start the VM - and that is used to order the ingredients of your VM-pizza)

After that your VM-XP should be able to boot. It will reboot 2 or 3 times until it has found all the new hardware. Then it will ask you to reactivate with Microsoft and once that is done it should work.

Ulli