Shoutbox

quote:

---

Originally posted by YourNeibour
do you think my PC is upto snuff though?

---

as Shawnz asked above maybe a Ram stick is bad, i'd download a program such as memtest an run a memory test http://www.memtest86.com/

quote:

---

Originally posted by Jesus

quote:

---

Originally posted by ShawnZ
i believe you mean "youll have to run sysprep in the vm," which really isn't that much of a hassle.

---

that's what I meant, and most of the time you'll have to make (or at least customize) the sysprep file to do that. That's how it worked the last time I did this. Maybe it's possible to do this automatically by now.
Anyway, if you have a valid reason to do this it's not much of a hassle, but just to do a fresh install of an OS it's quite a hassle since that can be done in a much easier way.

---

correct me if i'm wrong but doing a system prep like that is for migrating from a vmdk file, i have done it plenty of time using the physical disk without a vmdk file and it worked 100% of the time with xp and ubuntu

quote:

---

Originally posted by Jarrod
correct me if i'm wrong but doing a system prep like that is for migrating from a vmdk file, i have done it plenty of time using the physical disk without a vmdk file and it worked 100% of the time with xp and ubuntu

---

The drivers will be the same whether it's a .vmdk or a physical disk.
Your system is probably one of the cases where the system is still bootable while using the drivers of the VM, but on other systems this is not always possible. I've tried it on my previous laptop and it gave me a BSOD if I tried to boot my VMware Windows XP installation from outside the VM.