Memory Card Annihilator coded by ffgriever, gfx by Berion

PS2 Memory Card Annihilator v2.0a (a new version after more than 11 years!) 2.2.0

v2.0a introducing errors in English language file:

Code:
LNG_OPER_PSX_MEMORY_CARD="PS1 Memory Card"
Should be: PSX Memory Card... :P

Code:
LNG_OPER_QUESTION_UNFORMAT_DATA_LOST="Are you sure you want to unformat the memory card?\n\nUnormatting will destroy all the data stored on the card!"
Should be: Unformatting.

Code:
LNG_INFO_UNIT_KB="KB"
This was corrected actually from "kB" to "KB" but just like in "MB" case, should be "KiB" and "MiB" to follow proper units, not related to SI (as kilo is 1000 not 1024).
 
Code:
LNG_OPER_PSX_MEMORY_CARD="PS1 Memory Card"
Should be: PSX Memory Card... :P
This is a PSX (which supports PS and PS2 MCs):
upload_2022-6-16_1-41-48.png

This is a PlayStation (PS):
upload_2022-6-16_1-42-16.png

And this is a PSone (PS1):
upload_2022-6-16_1-42-38.png

But, ffgriever said "For me PlayStation is PSX. PS1 is PSone. The DVD recorder was not released anywhere in the west, no one knows about it, no one thinks about the DVR when they hear PSX" and since he does not wants to dragged into a PS-whatever naming war, I asked him "Tell me which one should I use and I will use it, since it is your software. PSX, PS-X, PS1 or PS?" and he said "PSX", so here we are. Anyway, I left what translators picked in their translations. Some went with PSOne, some went with PS, some with PSX and some with PS1. If a Brazilian feels that PSOne fits more natural to the Brazilian (since they might not know the PSX acronym, then OK). If ffgriever, the developer, feel sthat PSX will fit more to an English audience, then it is OK to me!

Code:
LNG_OPER_QUESTION_UNFORMAT_DATA_LOST="Are you sure you want to unformat the memory card?\n\nUnormatting will destroy all the data stored on the card!"
Should be: Unformatting.
Fixed!

Code:
LNG_INFO_UNIT_KB="KB"
This was corrected actually from "kB" to "KB" but just like in "MB" case, should be "KiB" and "MiB" to follow proper units, not related to SI (as kilo is 1000 not 1024).
"1 KB" means 1024 bytes (as Windows would report it, traditional usage)
"1 kB" means 1000 bytes (as Mac OS would report it, IEC usage)
"1 KiB" means 1024 bytes (it is used only in Germany and France, it mean Kibibyte, not Kilobyte. 1000 KiB = 1024 KB. So 1 KiB = 1024 bytes = 1 KB and so 1 KiB = 1,024 KB)
We will use KB...

I pushed a silent update to the download site.
 
Now look not at the MFs in Sony who exploited the sentiment but on executable header. What You can see there? :P

- - -

About size nomenclature: this thing was broken by design since the beginning as people using SI units in IT which is wrong. Later was introduced proper convention but old is so much rooted that none of the OS or desktop environment following it (maybe except Cinnamon which shows size in KB, as it should (which I don't like, but this example shows that not only Berion is a heretic ;p)). What You said is (at least I think it is :P) actually partially wrong because:
  • 1KiB = 1024 bytes
  • 1KB = 1000 bytes
 
Now look not at the MFs in Sony who exploited the sentiment but on executable header. What You can see there? :P
What I read there is "50532D58" aka "PS-X", with an "-" which stands for "PlayStation eXecutable", two words, separated by "-" since the usual "·" used to separate two words in Katakana does not exists in the ANSI charset...

  • 1KiB = 1024 bytes
  • 1KB = 1000 bytes
Nope, that statement of yours is wrong. Me and ffgriever just digged into that kB vs KiB vs KB malarkey...

In fact, we where ready for this:
upload_2022-6-16_3-18-7.png


So... just let it be...
 
I have a clone momery card 64MB that sometimes shows up, sometimes it doesn't . If i format it as 8MB will it avoid those bad blocks ?
I'm available for testing if you have something beta . Such a card works better with FMCB or Fortuna ?
 
@HWNJ Question for you... I would like to know if it's possible to have memory card annihilator run off of smb and have it look for the language file in a folder in you memory card, like for instant SYS-CONF?
Thanks
 
MCA reading language file from place where it was launched, and it will not see it on SMB.
Yes, I understand that, but I prefer running the app from SMB and would like to know if it was capable to have the app look for the language file on a different path.
Thank You
 
Not possible. MCA is closed source and ffgriever don't want involve much in the scene. So chances that he would add SMB etc. are near zero. Or maybe it is already some prioritizing path in resources seeking about which I don't know (e.g "mc0:/SYS-CONF/lang.cfg" first, then appdir, just an example of idea).

Try dropping language file to: "mc0:/MCA/", "mc0:/SYS-CONF/" or "mc0:/SYS-CONF/MCA/". Maybe some of them will work?
 
@HWNJ Question for you... I would like to know if it's possible to have memory card annihilator run off of smb and have it look for the language file in a folder in you memory card, like for instant SYS-CONF?
Thanks
The language file is only read from next to the ELF and the application has no drivers for SMB and no code to connect to it, so, no... it will not work.
 
The language file is only read from next to the ELF and the application has no drivers for SMB and no code to connect to it, so, no... it will not work.
Thanks Everyone, I was just hoping it had a language path to MC0 built-in.
 
So I'm running this on a 30001 fat PS2. I've got FHDB set up just fine, and while MCA works just fine, despite having the English .LNG file right next to the mca .ELF that I'm running, it's always in Polish. I've opened the .LNG file to verify that, yes, it's english, but I'm baffled as to why this isn't working?
 
Back
Top