xp home native defragger and fdisr233-Files to exclude?

If one uses xp home's native defragger with fdisr233, do you need to manually exclude some files like you do with raxco's perfect disk defragger or? I don't see a way of manually excluding files with xp home's native defragger. Did leapfrog design fdisr to only work with raxco's perfect disk defragger or what?

 

As Peter said, everything is OK with the Windows XP defragger. I emailed the head man at Raxco tech support a few years ago when Raxco still sold the excellent original FirstDefense and he gave me a rather detailed explanation of how the defrag process worked and how Windows defragger would not hurt FirstDefense. Unfortunately I no longer have those emails to forward or prove it to you so all I can state is this: the built-in WindowsXP defragger will not mess up FirstDefense. Just think how many tech support calls Raxco would have received it the XP defragger had messed up FirstDefense, after all, the majority of folks using FirstDefense were probably using the built-in Windows defragger. Only some third-party defraggers from a few years ago could mess you up. If you are using a "modern" original copy of FD with the built-in XP defragger you have nothing to fear, my wife's pc is set up that way.

Acadia

 

Whilst it's true you don't need to exclude anything now, it seems PerfectDisk still does:

 

So Pete, i assume that when using PerfectDisk (v.2008 or v.10) and/or iobit SmartDefrag nothing need to be excluded?

So defragmentation in FD-ISR no longer is a problem in any way?

Is this case with all defrag tools that nothing should be excluded?

Is this a new way in functioning with new releases of FD-ISR?

- Renegade

 

Thanks Pete.

It's has been quite a long since i have used FD-ISR and i have been absent from FD-ISR forum.