lawson23's Posts

two questions. 1. Is there a way to convert this disk to a IDE disk before I get the blue screen of death? I can't find anyway to work around this issue with my configuration. 2. If 1 can't be done. How do I take my current vm6 install and either 1 install vm 5.5 so I can use both. This would allow me to create a image and once it is created use it in vm6 or convert all my existing vm files down to 5.5 so I can uninstall 6 and go to 5.5 because I need this function.

The attached suggested method problem is that once all the files are copied and it tries to boot I get a blue screen of death. So yes it gets me past the first issue but then it doesn't allow me to boot the system.

FYI for an update I just wanted to let everyone know I just did a repair install of win2k3 and this fixed the problem for now. Thanks for everyones help. Now I have to figure out how to get my other drives into the virtual machine. Drive E and F which are physical drives that need to become either part of the VMDK or different vmdk files.

Took a screen shot: 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 controllers. Check your hard drive to make sure it is properly configured and terminated. Run CHKDSK /F to check for hard drive corruption, and then restart your computer. Technical information: \*** Stop: 0x0000007B (0xFA0D2A98, 0xC0000034, 0x00000000, 0x00000000)

I'm going from memory but if it serves me correct I can't boot into safe mode which is consistent with a HAL.DLL issue. Which is common when you swap a motherboard or something. Basically I think it is using a different hal that what the VM sets for hardware.

Ok I did this but here is my problem I'm not getting a blue screen when booting into the install. Here are a few items to note and I can always go back and rebuild the VMDK file if I did something wrong. This is installed in Linux and I had to install the grub installer on the original disk containing the 2k3 install. So what I did was build the vmdk and remove grub by booting into recovery console and running: FIXBOOT C: FIXMBR BOOTCFG /rebuild I don't think it is an issue with the bootloader as it starts to boot windows but quickly gives blue screen. I think this is more of a hal issue. Any ideas?

Ok I understand it. One question. run the vdiskmanager with -r option and convert into a split disk we safe in Q:\ Why do you use the Split option? Also will this (vmdk) be the size of the used space or of the entire drive?

check out this post: http://www.vmware.com/community/thread.jspa?messageID=187305&#187305 And this one: http://www.vmware.com/community/thread.jspa?messageID=349340&#349340 W2K, NT - workstation loses connection to Domain After a Revert (and/or Discard) loses those VM the connection to the domain. Why? To the Authentifizierung between PC and server (domain) so-called machine account password is used. This changes itself for safety reasons cyclically. If VM by means of Revert on one old conditions is put back, is not correct the password PC any longer with that the server. With the following Registry key one switches that automatic changes of this password off: HKEY_LOCAL_MACHINES\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters DisablePasswordChange REG_DWORD 1 If the password ran off once, helps in short removing of the VM from the domain and after the restart a renewed Take up to the domain! Then equal the above Registry keys change and one new Snapshot make! The above is a poor translation from German to English but some have said this works. I will be trying this out on my next build attempt.