WOW!!! A non-corrupted image.........

Discussion in 'Acronis True Image Product Line' started by Cat-21, Apr 25, 2006.

Thread Status:
Not open for further replies.
  1. Cat-21

    Cat-21 Registered Member

    Joined:
    Feb 7, 2005
    Posts:
    60
    I recently got the time to add TI 9.1WS b3567 to my BartPE Disk and I finally created a working image. To all wondering how this feat occurred, build yourself a Reatogo or XPE version of the Bart CD as the standard NU2Menu shell didn't work for me. Add Mustang's TI driver, run the auto-driver and you should be all set. I haven't tested across a wide range of hardware, so I'm unsure if it's going to be a reliable solution for me and others yet, but hopefully it can help those who were stuck in corruption land.

    This success motivated me to test furthur so I rebuilt the plugin using TI 9.1 b3534 as I was curious to see if the newer version had actually fixed the problem and to my surprise build 3534 can also create and restore as well, keep in mind that this computer previously failed with corrupt images both in Windows and with Acronis' Bootable Media (both builds). So now I tried to restore an older image that verified corrupted and I could not restore it with the BartCD. Now I flipped it and tried to restore my good image with the Acronis Bootable Media that did restore with my BartCD and it failed restore saying it was corrupted. I then rebooted with the BartCD and now the image was corrupted and unrestorable.

    This leads me to believe the crazy notion that somehow TI is more stable on Bart than it is in either Windows or it's Linux-based bootCD. This is about as tricky as it gets. My only guess is that:
    1. Corruption occurs on the Windows side because of some type of conflict with software/drivers/Windows as my BartCD could image and restore the machine, hardware not stopping things.

    2. Corruption occurs on the bootable media side due to limitations of the Linux-based Bootable Media. Also if you have seen other Linux builds out there, you'll know that Acronis' Linux build is very limited and not quite as robust as other Linux distributions like Mepis, Knoppix, etc. so it makes sense why users have USB related issue that other distros don't have.

    So in the end my opinion is that my BartCD stikes a perfect balance between stability and compatibility. Less intensive imaging without Windows in the way, yet better hardware compatibility as well as PNP USB support from BartPE, unlike the shaky Linux build that TI is using. Has anyone had a better experience using BartPEo_O
     
  2. Cat-21

    Cat-21 Registered Member

    Joined:
    Feb 7, 2005
    Posts:
    60
    Just to keep you all updated I have tested across a wider range of hardware. My results are mixed creating\restoring images. I had some success and still some PC's with corrupted images. Just to add the BartPE method worked best for me as compared to in-Windows images and Acronis' native bootable media which didn't work for me. I figure the final fix for these corrupted images will be coming so at this point I would say to all who are having corrupted images to try the BartPE method first and if it doesn't work, your only choice is to wait for a future build. I will not be testing any furthur for my clients, but I will post here if a permanent fix comes along so others can benefit from the information.
     
Thread Status:
Not open for further replies.