I get a error message since update to 3.13 (Win 7 x64, portableapps.com)

233 views
Skip to first unread message

Ʈǿʍɨ Ʈąřƙɨɲ

unread,
Mar 29, 2016, 5:22:15 PM3/29/16
to FastCopy bulletin board
Hello!

The error message I keep getting now is this: "Can't continue - Can't alloc memory(fileStatBuf)(There are no more files.18) :" and sync activity of Fastcopy stops there. Is there a way solve this?

kind regards,
Tomi

Hiroaki SHIROUZU

unread,
Mar 29, 2016, 10:39:36 PM3/29/16
to FastCopy bulletin board
It indicates too many files in one diretory direct(=except subdir's files), so it can't allocate the area for file attributes.

The most easy way is changing FastCopy(x86) version ->  FastCopy(x64) version.

But if your OS is 32bit, try this.

FastCopy2.ini
 [main]
  max_attrsize = 268435456; (=256MB or 402653184=384MB)

32bit OS user address space is only 2GB and it is used for stack/heap/share memory.
If you change max_attrsize, I suggest not to use big number for main buffer size.
Otherwise, you get allocating error for main buffer.

Ʈǿʍɨ Ʈąřƙɨɲ

unread,
Mar 30, 2016, 1:28:53 PM3/30/16
to FastCopy bulletin board
My OS is Win7 x64 and Task Manager showed that portableapps.com had launched the Fastcopy64.exe file accordingly. I had problem first making Fastcopy load my new edited fastcopy2.ini file, because I had another copy elsewhere on the same disk and Fastcopy took the settings from there, which was quite strange, because they were not connected in anyways before, but the other copy was a backup from another disk. Eventually I put the old version inside a .rar file and Fastcopy started using my new edited version. Seems your advice has fixed the issue now. Thank you, Hiroaki!

Hiroaki SHIROUZU

unread,
Mar 31, 2016, 2:43:18 AM3/31/16
to FastCopy bulletin board
max_attrsize is 1GB(1073741824) in FastCopy x64 version.

Did you have used x86 version? (and old ini still work...)
Reply all
Reply to author
Forward
0 new messages