----- snip ----- re: PSXMemTool problems with multi-slot saves
I've experimented a bit with this problem myself tonight, and I have to agree with you that PSXMemTool is completely unsuitable for working with multi-slot saves.
That is only because ".GME" is a full memcard file type. You get the same result with any other full card type, like ".mcr" or similar. The problem appears to be that Simon didn't implement routines to reassign slot positions and recreate directory headers for non-first slots of a save.Quote:
Originally Posted by alkarl
Let's clarify that a little:
In the case of a three-slot save, for example, the header from the ".mcs" file must be modified to indicate which slot is to be the second of this save (depends on what is free at import time), before that header can be placed in the directory section. Then a middle-slot header must be created for that 2nd slot, and it must in turn indicate which the third slot is, and that must be given a final-slot header in the directory section. And of course, for a four-slot save there would be two middle-slot headers instead of just one, and so on for larger saves.
Actually I think that Simon Mallion has dropped development of this tool. Version 1.19b has been around for quite a while now, and I know that he is aware of the lacking support for multi-slot saves, because if you try to export a multislot save you get an error message stating that this simply isn't supported for multi-slot saves yet.Quote:
if somoene can confirm that and maybe report the bug.
PSXRC is not at fault, can't fix the problem.
the most unbelievable thing is how can that bug hasn't been reported yet. :mad:
But the behaviour for import of such saves is indeed a bug, as the program clearly ignores the save size field in the header structure. It should at least have detected the size and refused the import, if he couldn't implement it properly at that time.
To change the subject to something brighter, I was wondering if you'd consider making a commandline version of your conversion tool, simply accepting a normal commandline argument for the name of the file to be converted.
My point in asking for this is that it would then be very easy to write a small BAT file which could then be used as target for mouse drag-drop of files. So I could simply pick up a file from a window with the mouse, and by dropping that on the BAT file (or its shortcut), it would invoke your conversion tool with the correct work directory and filename, without me having to type anything by hand.
I use this method a lot to make use of command line tools more convenient, and I'm sure it could work well for your tool as well. It's sort of like a "poor man's GUI", and without requiring any deep Windows-specific coding ;)
Best regards: dlanor