Fritz

OK, ever since yesterday I have been having this problem as discussed in this thread.

The problem was somewhat solved using a format either through XP's Explorer, or through StorageTools; but upon testing and verifying with larger files, this is what I get:

1) Copied a 13MB dummy zip file from desktop to Ax's internal memory: no problem
2) Move the same file from Ax into SD: no problem
3) Tried moving the same file from SD back into Ax, got dialogue box titled "Action Failed" with message:

"Cannot move file 'dummy.zip'. There is not enough space on the storage device.
Press 'Yes' to continue."

Repeated process with file size 12.3MB and got same findings.

Tried with 11.6MB file and it worked (and subsequent smaller files were also fine).

FYI, there was 22MB of internal Ax storage allocated for this battery of tests -- coincidently that is relatively twice the storage space required for the 11.6meg file.

Can anyone duplicate this on their Ax? Or am I the only one with this problem?

Cheers.

__________________
"To be, or not to be is true." -- Boole

Mike C

If it creates a copy file and a destination file that could take up (file size) x 2.

__________________
Persistence can pass for brilliance
FFR Roadster on order for 04/3/04.
Mike

Fritz

But I'm just cutting and pasting (moving) it tho...? So you're saying it firsts allocates X-megs for copying in RAM; and then writes X-megs, hence the 2X?

Cheers.

__________________
"To be, or not to be is true." -- Boole

Mike C

The file system in ppc02 has some odd behavior at times, but I'm still learning.
It just seems like a coincedence the way the numbers add up.

__________________
Persistence can pass for brilliance
FFR Roadster on order for 04/3/04.
Mike

Fritz

Yeah I went and double checked allocated 26megs -- and guess what? The 13 meg dummy file copied no problem!

__________________
"To be, or not to be is true." -- Boole

b9_2mr

Remember, this is a Windows-based product... That means there will be problems. If it's anything like the way Windows downloads files, first it creates a temporary file somewhere, then when the temporary file is finished copying, then it copies the temp file to the intended target file. In other words, you need 2x the space that the file takes up. Now, I believe this is only the case for FTP files in Windows 9x/2k/xp, but who knows with PPC? Could be the same way there too:(