Thanks. What version of ghost32 are you running - you can find out with the following command line: "ghost32 -ver"?
When ghost32 is operating on vmdk files it needs exclusive access to them, so it could be worth checking that the vmdk file(s) are not part of a VM currently running in VMware and are not mapped as a drive letter.