PS3 Filezilla problem (Solved)

Giaggio96

Member
Hello people,
I'm going crazy because of this problem I'm experiencing. I'm trying to transfer a game that I keep saved as a backup copy on my pc to my ps3, using the filezilla client via ethernet. The upload process runs smoothly up to the last remaining 1.4 GB to be transferred, because from here the link is always interrupted by magic on the same point. The game weighs about 10 GB and of course on my ps3 there is more than enough space to transfer it. What could it be? So far I have always transferred files even over 20 GB without the slightest problem. How can I solve this problem?
 
If it stops EXACTLY in the same place, then files on HDD can be corrupted, or one of files can have name that PS3, filezilla, or PC is not able to handle.
 
If it stops EXACTLY in the same place, then files on HDD can be corrupted, or one of files can have name that PS3, filezilla, or PC is not able to handle.
Sorry, but I don't get it.. Something like my PS3 HDD is damaged or what? Yes, the transfer stops right at the exact point every time, but my PS3 works just fine, how can this be?
 
No, file that you have on PC can be corrupted.
Got it.. But, even if the file is corrupted, what should it have to do with filezilla? I mean, filezilla should not just transfer files as generic STUFF, not caring that they are functional or not? :confused3:
 
Got it.. But, even if the file is corrupted, what should it have to do with filezilla? I mean, filezilla should not just transfer files as generic STUFF, not caring that they are functional or not? :confused3:
Yes, but it might not be readable due to corrupt filename for example or bad sector on PC hard disk

Easiest solution is probably to rip the game again to PS3 HDD. :)
 
Solved just ripping the game again... I'm not sure if it was truly damaged the previous file I uploaded to the console, but it works now, so who cares? :victorious:
Anyway, thanks for the help
 
Filezilla does a few things in the background, and I think it somehow processes the files internally before transfer from the way it acts/handles. If you have a weird file, ripped incorrectly or if perhaps one bit was in a bad sector, it can cause weird issues like this even with cpu to cpu transfer. Generally speaking, i've also found it more probable to happen when more transfers are enabled. Dropping this to 6 or less usually solves that issue (the number of available SPU, as 1 is disabled and the other is used for system).

Also, i've found it helps keep connection faster if you keep the screen from dimming on the ps3. Usually by a keypress or move a joystick or something. Can also notice minor issues if playing a larger game while transferring as well...

Hopefully some of this experience helps you :)
 
Back
Top