FreeFileSync v3.12 on Win XP SP3
I get error when sync'ing directories between two internal drives on same PC.
Log is below.
The problem file is a 192 GB disk image .tib created by Acronis Drive Image
Home 2010.
The sync stops after copying about 10% of the file.
In Windows Task Manager, paged Kernel memory starts around 105000 K and goes
up to 121000 K, much below the 160 MB level reported as problem in Microsoft
knowledgebase http://support.microsoft.com/kb/304101
Anyone else see this problem?
-----------------
Warning: Synchronization failed for 1 item(s):
Error: Error copying file:
"V:\Backup\Louise_ThinkPad\System_G_22_06_2010.tib" ->
"W:\V\Backup\Louise_ThinkPad\System_G_22_06_2010.tib"
Windows Error Code 1450: Insufficient system resources exist to complete the
requested service.
Error: Synchronization aborted!
You may try to synchronize remaining items again (WITHOUT having to re-
compare)!
Windows Error Code 1450: Insufficient ...
- Posts: 1
- Joined: 14 Dec 2010
- Site Admin
- Posts: 7279
- Joined: 9 Dec 2007
FFS uses Windows API function CopyFileEx (https://msdn.microsoft.com/en-us/library/aa363852%28v=vs.85%29.aspx) directly. So this issue probably
cannot be solved by FFS. Trying the info on knowledgbases may be the best
thing to do.
-Zenju
cannot be solved by FFS. Trying the info on knowledgbases may be the best
thing to do.
-Zenju
- Posts: 1
- Joined: 15 Feb 2011
I can confirm this is not a FFS issue. It happens in xcopy as well for
+50Gbytes.
My solution was in regedit, navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory
Management add/change PoolUsageMaximum DWORD to 60(decimal).
Remember to reboot...
(http://support.microsoft.com/kb/304101)
-tetzschner
+50Gbytes.
My solution was in regedit, navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory
Management add/change PoolUsageMaximum DWORD to 60(decimal).
Remember to reboot...
(http://support.microsoft.com/kb/304101)
-tetzschner
- Posts: 2
- Joined: 7 Oct 2003
I tried these options, but the problem persisted.
Finally, poking around the XP machine, I found the swapfile had been set to
Zero. Letting XP manage the swap file seemed to fix the problem.... for now.
Finally, poking around the XP machine, I found the swapfile had been set to
Zero. Letting XP manage the swap file seemed to fix the problem.... for now.
- Posts: 2
- Joined: 7 Oct 2003
Nah -- that didn't fix it either.