Remind me again why native xphome defragger bad with FDISR?

Discussion in 'FirstDefense-ISR Forum' started by Horus37, Oct 28, 2007.

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

    Horus37 Registered Member

    Joined:
    Jan 4, 2007
    Posts:
    328
    Someone explain to me what the problem is with using just the native xp defragger and FDISR? Do you have to exclude the isr bin file with it as well? I'm assuming when they built FDISR they built it knowing the native defraggers would be use so I'm surprised at how many people opt for different defraggers.
     
  2. Acadia

    Acadia Registered Member

    Joined:
    Sep 8, 2002
    Posts:
    4,048
    Location:
    SouthCentral PA
    To the best of my knowledge there is NO conflict between the XP defragger and FirstDefense. I believe that I remember receiving that info from Raxco tech support a couple of years ago.

    Acadia
     
  3. Peter2150

    Peter2150 Global Moderator

    Joined:
    Sep 20, 2003
    Posts:
    17,039
    I don't think the issue is FDISR. I just don't like the XP defragger.
     
  4. TonyW

    TonyW Registered Member

    Joined:
    Oct 12, 2005
    Posts:
    2,633
    Location:
    UK
    I might be wrong, but I don't think it's as critical to exclude the $ISR 0 folder now.
     
  5. Peter2150

    Peter2150 Global Moderator

    Joined:
    Sep 20, 2003
    Posts:
    17,039
    Correct. I tested O&O's new one, and I didn't exclude anything. NO problems.
     
  6. tradetime

    tradetime Registered Member

    Joined:
    Oct 24, 2006
    Posts:
    1,000
    Location:
    UK
    I've never had a problem, so you've lost me.
     
Thread Status:
Not open for further replies.