Converter 3.0.1 to Workstation 6.0 - converter has no 6.x option

[walhub]

I would like to convert a physical machine to VM workstation 6.0, since that's the only version I have. But I don't see a 6.x version option.

Should I use 5.x ??? What do I not get in doing so?

[mikefoley]

Two things... Use the built-in converter of WS6 or convert to 5 and "upgrade"

the VM when you open it with WS6.

WS6 will open and run 4, 5, and 6.

mike

[walhub]

Mike thanks for the tip.

I used the WS 6.0 built-in (Import) converter.

But it gets to 97% complete and hangs.

It looks like many others have the same problem.

Any ideas on that?

[mikefoley]

If I could solve the 97% error, I'd be a hero.

[gautam]

Try using Converter 3.0.1 to create a WS 5 VM and then open this in WS6. Converter 3.0.1 probably won't fail at 97% and if it does fail, it might provide more information as to why it failed.

[walhub]

Yes you would be.

[walhub]

Actually I tried 3.0.1 before, and it also failed ... at 97%

It's the reason I was headed down this path.

But thanks.

[admin]

What OS is your physical machine?

Also, are you resizing any partitions?

What OS is Converter or Workstation 6 installed on?

[walhub]

Physical OS is W2k sp4

Resizing from ~27gb to 31gb.

WS6 is installed on the local physical machine,. W2k sp4

Destinations have been a usb hard drive and a network drive, with the same result.

[admin]

So you are trying to convert the local machine, and no password is needed?

1. Make sure you are logged in as a local administrator.

2. Verify that your boot.ini is not read-only.

[walhub]

Correct - local machine, no p/w required.

1. yes

2. boot.ini is NOT read only, just archive check marked.

[admin]

How long does the progress take before reaching 97%? A few minutes or half an hour?

[walhub]

Over an hour, probably almost 2hrs

[admin]

Then the problem is more likely something to do with the configuration at the end of the process to change the drivers within the cloned VM. It could be a case where the registry could not be updated...a line in the error log would say something to the effect of not enough space to update the registry, or too many serial devices. A detailed error in the log file can provide more details as to why the process failed.

[walhub]

Thanks.

I think I already trashed old logs.

So I'll be on the look-out for that as I try again.