Printable View
Running the latest version, v3.72, of uLE through a memory card exploit. I decided to try backing up a save game to my usb stick -- max memory usb stick -- and noticed that the supposed extra file was absent. I checked it on my pc and it was indeed missing.
For the record, the method I used was choosing copy on the save game directory under mc0:/ followed by mcpaste within mass:/
use MCpaste for both the MC and the mass: ...
and which is the extra file u're lookin for?
According to the filebrowser manual, in order to backup a gamesave I'm supposed to use the mcpaste command rather than the regular paste command. The reason being that this command will create an additional file to hold data about the gamesave itself which exists within the memory card but which would be lost when normally transferred to another device that isn't a memory card. Supposedly, that data is important for games or else they consider that the save is corrupt.
Then, when restoring the save into the memory card, mcpaste will take the data from that file and restore it to its proper place within the memory card.
That file is the one that is missing.
What are you saying ?Quote:
Originally Posted by xmod
He spoke of a single attempt to make a backup.
There is no way to use mcPaste twice in such an attempt.
What he described, using 'Copy' to get the paths into clipboard, and then browsing to the destination to start the copying with 'mcPaste' is absolutely correct.
I just think he misunderstood how mcPaste works, and that the extra attribute files are only created when entire gamesave folders are backed up this way. Separate files are not valid as PS2 gamesaves, and therefore don't merit any special attribute protection.
Edit:
The above was just an initial guess. I now believe that a pasting error occurred.
Best regards: dlanor
That is absolutely correct.Quote:
Originally Posted by Vey2000
This varies. Lots of games just ignore the special attributes, but some refuse to use saves that have incorrect attributes. The dependency on timestamps is more dubious (very hard to test for), but mcPaste preserves them too for safety.Quote:
Supposedly, that data is important for games or else they consider that the save is corrupt.
That is also correct.Quote:
Then, when restoring the save into the memory card, mcpaste will take the data from that file and restore it to its proper place within the memory card.
That's very odd indeed. I've never seen such an error before, neither in my own tests nor in any reports. Possibly it's some other error that causes the pasting to break off before reaching the point where the special file is written. (You should have seen a 'Paste failed' message then.)Quote:
That file is the one that is missing.
The only thing I know of that will cause this, is if the gamesave contains any file with a name that would be invalid on the destination filesystem.
Some very few such cases are known, including some that use 'backslash' in the filenames, which at present is only valid for use on MC and PS2 HDD, but not on mass: or host:. That problem will be fixed for mass: in the next version (I already have it working in my lab version), but it can't be fixed for host: as backslash is the path separator of most PC systems.
Another case where no 'extra' file will be created is if you merely copy the content of a save folder instead of the folder itself. Since files without a containing folder are not valid as PS2 gamesaves, mcPaste doesn't treat them as such.
Please check again if either of these things affect your backups, and also try it with some other folders (from other games or even homebrews), to ensure that it works normally for them.
Best regards: dlanor
i had similar errors. recently i tried to copy an .elf and a .scm(ROM file) to MC1 from HOST.
the copy failed, i believe due to not enough space, but i cant say for sure since the free space wasnt shown correctly a copple of times on uLe 3.72 on different devices. (MC & HDD)
I don't see why you call that case similar to the one of Vey2000.Quote:
Originally Posted by broodje
He has a problem specific to mcPaste backup of a gamesave from MC to mass:, whereas you describe copying of two homebrew files to MC from host:. Choosing mcPaste for such copying will have no effect different than normal Paste, so these error cases are not related at all.
Those free space display errors should no longer occur in the latest version, as I fixed those bugs in v3.72, for both the MC and HDD devices.Quote:
the copy failed, i believe due to not enough space, but i cant say for sure since the free space wasnt shown correctly a copple of times on uLe 3.72 on different devices. (MC & HDD)
Best regards: dlanor
Indeed u are right, i was reffering to his 'copy error'.
my knowledge of the english language may be some what limited, therefore i could only came up with the word similar.
to get back at that, i had those errors a copple of times, where files from different devices would not copy, altough i was succelsfully when i copied them liek this for instance:
HOST --> MASS = failure
HOST --> MC1 --> MASS = succes.
am sorry i do not have any specific details.,
All was done with uLe 3.72 with the sytem specs in my signature.
Well, this is even odder now.
First things first. I don't believe I saw any 'Paste failed' message at the time. I did actually try it with gamesaves of seven different games. Yes, I did save the folder, not individual files. No, none of them had any backslash characterrs.
That was yesterday around the time I posted here after my first failure. I just tried it again before replying, and it seems to have worked correctly. The special file was successfully created.
The only reason I can think of is that it was also yesterday that I had upgraded from v3.49 to v3.72. I can't remember right now if I had reset my ps2 between the time I upgraded and the time when I tried backing up gamesaves. I can say that I had never before tried backing up gamesaves with any other version, so I don't know if it it would've previously worked or not.
So, assuming that I hadn't reset, perhaps there was something left behind in ram that caused the problem. It's possibly a big assumption, as while I do remember resetting a few times, I don't remember if one of those was between upgrading and backing up. I had also been playing around with a few other things, such as applying a skin, etc.