----- snip ----- re: suggestion of user defined title at top of screen
Sure, but that could come later. No need to do it all at once.
Indeed yes, but we are rapidly approaching the point where that will be necessary anyway.
Unfortunately, I would have to make a lot of changes to the CNF structure if I wanted to do it right.
"Yes, But No", is what I have to respond to that.
This is something I'm not really willing to do just yet. My reason is because it would require making a lot of changes to the CNF order within the CNF file through changes to config.c.
"Yes," we will have to make extensive changes.
"But No", we can no longer rely merely on the order of lines in the CNF file.
We will definitely need to add keywords and parse the CNF file for them, irrespective of the order in which the keyed lines occur. But doing so will also gain us far more freedom than anything discussed yet can allow, such as extensible menus (beyond those for programmed keys), and alternate launching methods (specified by different keywords).
Once we switch to a system of properly parsed keywords, a whole new vista of possibilities opens up.
Yes, of course we must expect initial bugs, and be prepared to fix them, but that really goes for any significant improvements.
It's most likely doable but at the cost of more interesting bug fixes and features.
For now, sure, that will do nicely. And there's no need to rush into further developments, but there's no need to hold back for too long either...
Personally I'm just happy with seeing which config was loaded with path on the top line below the version number. :)
----- snip ----- re: Your memory card problems.
I'm sorry to hear it, and I hope you won't lose any irreplacable saves in reformatting (as LaunchELF can't backup all special attributes). I have Several memory cards myself (3x 8MB, 2x 32MB, many PS1 cards) and I still get worried every time I have to reformat one of them, though I've never lost anything irreplacable yet (knock wood ;))
That is not a bad idea for a test tool, but getting it to a point where it can be used for reliable and practical testing would be a pretty big project all its own.
Perhaps a CRC file checker for the ps2 side. :)
And consistent behaviour is exactly what we can never expect from a bug... :(
This is where it would be good to know what is contributing to the bug but it's difficult if the bug can't be reproduced consistently.
Yes, but if/when we make a workaround for this in LaunchELF , we can easily add the same for ps2ftpd. For the moment I'm prepared to accept the renaming limitation in both of them.
Yeah I agree but the attribute issue for ps2ftpd.irx is probably supposed to be handled by the hdd driver. Another thing is that the rename function isn't implemented for ps2ftpd.irx either probably because the memory card mcRename function doesn't work anyway.
To me that entire method of getting the file attributes looks suspicious and I think it needs to be studied in detail. I know that this has worked differently in old versions of ExecFTPs, so it may be due to some struct definition relying on some HDD standard struct that may have been redefined since then. Whatever the true reason, it is clear that ps2ftpd, and recent versions of ExecFTPs, do use some bogus data for the file attributes, so we don't have much to lose by changing it. (Though we must still take some care, so as not to invalidate any folder structures.)
Nevermind I think I found it in FtpClient.c. Currently it does ----------, the else statement, for all files created on the hard drive. Any ideas as to what I should add to a new elseif statement or modify with the current if statement?
----- snip ----- re: code excerpt from ps2ftpd
Best regards: dlanor