"vmware-ufad.exe died on startup, check your %TEMP% setting"

[adcockc]

I am trying to clone several old NT hosts using the Cold Clone CD and I always get this message:"vmware-ufad.exe died on startup, check your %TEMP% setting"

-Is there something obvious I am doing wrong?

Thanks

[admin]

How much memory is available on these machines? The cold clone CD launches Converter in memory in a RAM disk.

[adcockc]

Smallest was 1 gig. The others have 2 & 4.

[admin]

What version of NT 4.0? SP4 and higher?

[adcockc]

Yep. I have SP6 on all these guys.

[theanykey]

i would recommend doing a hot conversion with NT4 machines.

also, do you by chance have special characters in your environment variables for both TMP and TEMP? if so, make new ones following the basic english charset

[adcockc]

My settings were:

TEMP: %SystemDrive%\TEMP

TMP: %SystemDrive%\TEMP

I changed them to:

TEMP: SystemDriveTEMP

TMP: SystemDriveTEMP

and tried it again and got the same error. -Thanks for the idea though.

I will try to get the warm-converter software and try that.

[theanykey]

Can we try:

TEMP: %USERPROFILE%\Local Settings\Temp

TMP: %USERPROFILE%\Local Settings\Temp

after saving, look again - any special characters as in language characters like ä å é ç ... ect

you can leave it as it was if % was the only thing you saw

TEMP: %SystemDrive%\TEMP

TMP: %SystemDrive%\TEMP

[Natiboy]

I've run into this and used an smb mount point (my VC Server) over the network to fix the issue. It has something to do with the P2V Cold boot setup.

Check under the network configuration and see if the checkbox for "use this disk for a temp directory is checked" I created a temp path on my VC server with a drive letter (F:\) and another on my NAS Device (G:\) in the configuration and my Cold boot completed well.

[scerazy]

As said by Natiboy, use network share for the temp

Your error means that the ramdisk did not initialize OK

Should not happen with original CC ISO

Seb