Mustang's ATI plugin for Dell computer

Discussion in 'Acronis True Image Product Line' started by sarutaro, Nov 30, 2007.

Thread Status:
Not open for further replies.
  1. sarutaro

    sarutaro Registered Member

    Joined:
    Sep 26, 2005
    Posts:
    169
    I successfully created BartPE with Mustang's ATI (v. 10) plugin. This CD works nicely on my non-Dell computer. Restore time for ca. 10 GB tib was about 8-9 min. I am very happy with it.

    But it takes 1 hr 30-40 min on my Dell computer with the same BartPE CD and similar size of tib. But it takes about 11-13 min with ATI rescue CD on the same Dell computer. I repeated twice but I am getting the same results. I am wondering whether Mustang's ATI plugin needs a slight modification for Dell computers to expedite the restore time. I am not saying Mustang's plugin is wrong. It works but takes too long to complete the restore, which suggests that the plugin creates a speed bottleneck on Dell computer. I might be wrong on this one but I am getting the same resuls. Sarutaro
     
  2. mustang

    mustang Developer

    Joined:
    Apr 12, 2005
    Posts:
    905
    Code:
    It works but takes too long to complete the restore, which suggests that the plugin creates a speed bottleneck on Dell computer.
    That's not possible. When the Linux CD takes a long time to restore do you blame True Image or the driver support in Linux? I think you know the answer.
     
  3. sarutaro

    sarutaro Registered Member

    Joined:
    Sep 26, 2005
    Posts:
    169
    You migh have misinterpreted what I described. I would like to repeat again here: With the same Dell computer with the same tib, it takes about 10-13 min to restore with ATI rescue disk but it took 1.5 hr to restore with BartPE CD.

    On the other hand, it takes about 10 min with either ATI rescue CD or BartPE CD for non-Dell computer. This simple data led to the conclusion.

    The big advantage of using BartPE CD for me is that wireless laser keyboard (Microsoft model 6000 v.2) works nicely with it. For AT rescue CD, I got to use wired keyboard. Sarutaro
     
  4. MudCrab

    MudCrab Imaging Specialist

    Joined:
    Nov 3, 2006
    Posts:
    6,483
    Location:
    California
    I don't mustang misunderstood. What he's saying is that it's not the plugin that's causing the problem. All the plugin does is setup the program so it can run in BartPE (just as it would if installed in Windows).

    The problem you describe seems to be related to poor drivers. In this case the drivers on the TI CD are better optimized for your hardware than the ones that are on the BartPE CD. Have you tried adding updated drivers to your BartPE build to see if it helps?

    Are you restoring from an internal drive or a USB drive?

    When you're booted into Windows, how long does it take to Validate the image? When you're booted to BartPE, how long does it take to Validate the same image?

    If both Windows and BartPE are using the SAME drivers, then the results should be close, though Windows is usually some faster.
     
  5. sarutaro

    sarutaro Registered Member

    Joined:
    Sep 26, 2005
    Posts:
    169
    All of tibs are stored in the internal, D-drive which is a physically separate HD. Whenever I backup tib, I immediately performed validation. So for restore, I skip directly perform the restoration. I have been doing that for last 4-5 years without any problem. Sarutaro
     
  6. MudCrab

    MudCrab Imaging Specialist

    Joined:
    Nov 3, 2006
    Posts:
    6,483
    Location:
    California
    Understood, but it would be interesting to know the actual time differences between doing a Validation on the image in Windows and in BartPE. The Validation is just reading the image so it will let you know if BartPE is having a problem (slow drivers, etc.) reading the image.
     
  7. mustang

    mustang Developer

    Joined:
    Apr 12, 2005
    Posts:
    905
    I think it would be interesting to know how long it takes to copy a tib file from D: to C: under both Windows and BartPE.
     
Thread Status:
Not open for further replies.