Jump to content

- - - - -

[LODR - U] VMware Converter 3.0.3 (coldclone)

  • Please log in to reply
3 replies to this topic

#1 joakim


    Silver Member

  • Team Reboot
  • 912 posts
  • Location:Bergen

Posted 29 August 2009 - 10:35 AM

Here's a slightly modified version of a LODR package I made some months ago;


The last free version capable of coldcloning. No need for rebuildt iso, just hotplug this package to a running PE-environment. Works similar to other packages by me, with one exception. It no longer requires a given directory tree, and can now be placed inside any folder. Included as usual, is a tool to prepare the files.

Some screenshots from different boot environments;

Posted Image

Posted Image

Posted Image

Posted Image

From the readme;

VMware Converter 3.0.3 - LODR package for The last free coldclone supported version

The prepare the files required either use Converter303_Preparation.exe. Just launch once and it will download, unpack installe and copy required files into a subdir named "VMware-Converter-3.0.3".


Download file from&#59; http://download3.vmware.com/software/converter/VMware-converter-3.0.3-89816.exe and use batch get_files_converter303_ripp_installer.cmd

Place Converter303_Coldclone_LODR.exe inside the directory "VMware-Converter-3.0.3" where the converter files are.

To use LODR package, place the directory "VMware-Converter-3.0.3" somewhere you have access to from a booted cd. Then just execute Converter303_Coldclone_LODR.exe. It will setup everything and launch converter.exe in coldclone mode when finished. 


Sometimes, converter will complain about not being able to connect the local agent when executed the first time. If so, then just cancel and abort the process and restart in coldclone mode. Then it should work.

Shortcut directly to coldclone mode is generated on desktop and in startmenu. 

Path to main executable (converter.exe) in this LODR package can basically be anything (in contradiction to earlier LODR packages by me). Ie, 







#2 Lancelot


    Frequent Member

  • .script developer
  • 5013 posts
  • Location:Turkiye/Izmir
  • Interests:*Mechanical stuff and Physics,
    *LiveXP, BartPE, SherpyaXPE,
    *Basketball and Looong Walking,
    *Buying outwear for my girlf (Reason: Girls are stupid about buying bad stuff to make themselves uglier :))
    *Girls (Lyric: Girl,...., You will be a womann, Soon)
    *Answering questions for "Meaning of life",
    *Helping people,

    Kung with LiveXP, Fu with Peter :)

Posted 29 August 2009 - 11:11 AM

Thanks a lot joakim :ermm:

#3 NeBlackCat

  • Members
  • 2 posts

Posted 18 October 2009 - 12:38 PM


Had mixed results with this, having made it in C:\LODR\VMware-Converter-3.0.3\ then copied it's output to a folder on my WS2003/SP1-based UBCW4Win (latest version as of today) boot media.

I could not get anything other than the "can't communicate with service" type of error when booting the CD and running Converter303_Coldclone_LODR.exe (twice, as suggested).

I was able to get it past that by running converter.cmd then coldclone_mode.cmd, but that got me to "cant determine type of system" errors. I can sometimes get around those by de-assigning C: from the system disk (it's a laptop dual-booting vista and xp) in disk manager, but I couldn't do that as it turns out that converter.cmd actually hardcodes paths from where it was created (C:\LODR\...) hence the services were being run from there, hence C: was locked.

So I made a modified temp version of converter.cmd, pointing to the correct folder on the boot cd, but still couldn't get past the "cant determine type of system" converter error.

The strange thing is, at one time I did get past that error (using the same cd, having run various things from your lodr's folder on it) to the point where I could choose a partition to convert, but I can't remember what I did and can't get it to work again!

Any ideas?

#4 joakim


    Silver Member

  • Team Reboot
  • 912 posts
  • Location:Bergen

Posted 18 October 2009 - 01:35 PM

See answer at the sanbarrow forum.

Could you also tell your directory structure from where the LODR package is placed and the path to the loader. Is the loader put inside the directory as generated by the preparation tool?

In any way, it will not work if executed from a network share.


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users