Shut them Down

[WilliamP]

I just wanted to pass along this information. Shut down your AV . PG . and as I found out last night Online Armor. I have NOD32, Process Guard and Online Armor. I also have Ewido but keep the guard inactive. I had forgotten to shut down OA and had errors.

[ronjor]

Snapshot errors? I've had none with NOD running.

[WilliamP]

I don't think I have had any caused by NOD, but I know that the other two can cause errors. Love them but I guess that is just the way it is.

[ronjor]

Can you explain the errors?

[Acadia]

I never shut down ANYTHING when updating a Snapshot (or creating, at those very rare times), BUT I do not have PG or Online Armor (yet) ... I do have NOD, but have never needed to shut down ANY anti-virus that I have ever had when updating or creating Snapshots.

Do you have the latest update for the latest version? The latest update fixed a reoccurring error of some sort.

Acadia

[Peter2150]

I would shut down AV just from a speed point of view. FD is accessing files, and you av will try and scan. PG did lock files and the dat files wouldn't be copied if you didn't disable. I've not had any problems with OA,Safe'nSec, and Ghost Security Suite.

Pete

[ronjor]

NOD definitely scans the files. Not much speed loss and no errors noted.

[Skytrooper]

I use NOD32, ProcessGuard, and Online Armor. The only program I need to disable in order to make error-free FD-ISR snapshots is ProcessGuard. I haven't noticed any conflicts between NOD32 and Online Armor with FD-ISR.

[hollywoodpc]

Me too . Only shutdown PG .

[Peter2150]

One strange thing with PG, is that when refreshing snapshots I never got errors with PG disabled. But once I started with the archives I started getting occasional errors even with PG disabled. Only by chance when I had PG removed did I notice the errors never returned.

[crofttk]

FYI, Raxco does call out "Known Issues with 3rd Party Software", here: http://www.raxco.com/support/windows/SupportOptions.cfm?product=fdisr&ProductVersion=fd and Process Guard is among those mentioned.

[WilliamP]

I have duplicated the errors with OA and have figured out the problem. OA has been updated during the day and the computer hadn't been rebooted. When this happens I get errors. If I reboot then no errors.