error message

Have "Iomega Automatic Backup Pro Software" and the Iomega 80gb usb external hard drive . This software works great for backing up data
. The only way I can get it to work for a complete system restore on my C/Drive is in safe mode!
Otherwise I Keep getting error message \.\C: failed to backup, error code: Insufficient system resources exist to complete the requested service. (0x00517913, 0x0051526C, 0x20005900, 0x20005900) Have tried msconfig selective start, nothing running in back round. Spent 3 days with Iomega support with out any positive results.
Tried it on another computer had same problem. One of the computers has Windows Xp Pro (media adtion) the other windows XP home.The Windows Pro is HP that has the recovery backup on seperate partion D/Drive , installed as fat32,. Normal system is on C/drive . I can do a back up the on the D/drive Fat32 but not the C/drive which is NTFS.

This appears to be great software very simple to use only problem it doesn't work for doing a complete system backup. (The reason I bought it)

Was wondering if anyone has used this software and had similar difficulties ? Or if anyone has any idea what could be causing the problem?

Thank you

I have exactly the same problem with Iomega's Backup Pro ver. 3.2.0.17 on a new 80G ext. HD. The backup works fine in XP's Safe mode only. I have run MSConfig>Startup tab and disabled all Startups per Iomega's suggestion; no help. Next suggestion is to "Stop" the 'Services' running programs, one by one. (rt.MyComputer, L. Manage, L Service & Apllications, L. 'Services') and test at each step if Backup Pro will run. I have not worked this step yet as there are about 70 programs showing in the "Status' column that are auto or manually running.
Any suggestions or help would be greatly appreciated....
David

Please search for my orginal posting under this topic.
Backup Pro will only run under XP's Safe mode. Normal running comes back with an out of resources error code before it even gets started to do a backup. Iomega has not been much help after 4 converstations. Again, please see my post under Skywagon for mored details and what they want me to try next.
Thanks.....

I have FOUND the problem with my Backup Pro that would not do a system backup and keeps stopping with error codes of limited system resources......

It is caused by Norton's "Go Back" program that came with my recent version of Norton System Works (a wonderful diagnostic program by the way).
I don't use "Go Back" so it was easy to uninstall it the usual way via the Control panel. As soon as that program was uninstalled and the system re-booted, then Iomega's Backup Pro worked just as advertised.
Just for the readers interest.... I also tried via the Startup tab disabling most of the programs. That did not help. Also, tried Stop(ing) all programs running under Services and that did not help. It looks like Norton's GO Back can only be disabled permanently via an uninstall. Hope this helps others with the same problem.
Skywagon

Hi all,
This type of problem has occured many times with Norton's programs. The problem comes about because when you install a Norton program onto your HD it moves Window's "cache" file... then.. your computer "runs out" of system resources when attempting to do memory intensive (ie. high resource) activitys like backups..etc. Essentially, Windows & sometimes other programs can't find the cache file to use it.. so it just KR*PS out/crashes.
Unfortunately, about the only solution (like Skywagon found out) is to uninstall the Norton product.
Hope this helps,
RGPHNX

Thanks for the info Skywagon.

Let us know if we can help further in the future!

This thread has been Resolved and Locked to prevent other users hijacking the thread and to help others know which threads have been Resolved and which are still being worked on.

If you started this thread and the problem returns or the case has not been properly Resolved, please send a Private Message to a Moderator of this forum to have the thread opened again. If you have a different problem, please start a new thread.