Guide to decrypt EDAT files

I have a problem after decrypt .edat it makes me that
LDR: E PPU[1] Thread (CPUThread)[0x02831160]EDAT: File has invalid NPD header.

What does that mean?

Nothing to worry about. The EDAT loader isn't fininished iirc. Hykem is the one working on that and he has some uncommited changes, so probably he will take care of that.

Little Off topic what is up with recomplier?

Nothing to worry about. The EDAT loader isn't fininished iirc. Hykem is the one working on that and he has some uncommited changes, so probably he will take care of that.

Ah, so have to wait? ^ ^

Nothing particularly good... *sigh*

(On June 27th): [DH]'s computer broke once again and he might rewrite it from scratch on other machine.

Uh... backups? Or why didn't he just commit each days work to a separate branch on github like Nekotekina did with the SPU recompiler? Acts like a backup, if need be people can test on more games than his hard drive can ever carry, and it stops people from constantly asking for an eta...

Uh... backups? Or why didn't he just commit each days work to a separate branch on github like Nekotekina did with the SPU recompiler? Acts like a backup, if need be people can test on more games than his hard drive can ever carry, and it stops people from constantly asking for an eta...

I totally agree. The data can still be retrieved (afaik the HDD is fine), so I assume the reason for rewriting the recompiler is avoiding mistakes done in the first implementation, but I think that even those "old mistakes" are relevant for the rest of developers as well. So yeah: In short, you are totally right, but I can't do anything about it. You guys can PM him about such things I guess.

Is he even on this forum? I assume you speak on IRC or Skype or something? You should tell him that even if the recompiler he has now is crap and just runs a single homebrew even slower than the interpreter, he should just put it up in a new branch. You can't keep that amount of code to yourself and spend half a year optimizing, rewriting, optimizing again and rewriting again, because he will never be finished.

Also, design mistakes in development can be avoided if other developers have access to the code and can review it...

Uh... backups? Or why didn't he just commit each days work to a separate branch on github like Nekotekina did with the SPU recompiler? Acts like a backup, if need be people can test on more games than his hard drive can ever carry, and it stops people from constantly asking for an eta...

I totally agree. The data can still be retrieved (afaik the HDD is fine), so I assume the reason for rewriting the recompiler is avoiding mistakes done in the first implementation, but I think that even those "old mistakes" are relevant for the rest of developers as well. So yeah: In short, you are totally right, but I can't do anything about it. You guys can PM him about such things I guess.

Is he even on this forum? I assume you speak on IRC or Skype or something? You should tell him that even if the recompiler he has now is crap and just runs a single homebrew even slower than the interpreter, he should just put it up in a new branch. You can't keep that amount of code to yourself and spend half a year optimizing, rewriting, optimizing again and rewriting again, because he will never be finished.

Also, design mistakes in development can be avoided if other developers have access to the code and can review it...

+1 but if you notice your code is basically shit then you probably want to just start over with something more malleable.

I think the reason he didn't push changes to a public branch is so people would not get hyper and bug him about it or compile it and complain about things not working or merge it or whatever when it's not even finished. That's perfectly understandable.

He should have had a backup of the branch somewhere online, though.

Uh... backups? Or why didn't he just commit each days work to a separate branch on github like Nekotekina did with the SPU recompiler? Acts like a backup, if need be people can test on more games than his hard drive can ever carry, and it stops people from constantly asking for an eta...

I totally agree. The data can still be retrieved (afaik the HDD is fine), so I assume the reason for rewriting the recompiler is avoiding mistakes done in the first implementation, but I think that even those "old mistakes" are relevant for the rest of developers as well. So yeah: In short, you are totally right, but I can't do anything about it. You guys can PM him about such things I guess.

Is he even on this forum? I assume you speak on IRC or Skype or something? You should tell him that even if the recompiler he has now is crap and just runs a single homebrew even slower than the interpreter, he should just put it up in a new branch. You can't keep that amount of code to yourself and spend half a year optimizing, rewriting, optimizing again and rewriting again, because he will never be finished.

Also, design mistakes in development can be avoided if other developers have access to the code and can review it...

+1 but if you notice your code is basically shit then you probably want to just start over with something more malleable.

He should have had a backup of the branch somewhere online, though.

This I agree with.

I think the reason he didn't push changes to a public branch is so people would not get hyper and bug him about it or compile it and complain about things not working or merge it or whatever when it's not even finished. That's perfectly understandable.

Maybe so, but as we have seen people will ask about it all time time anyway...

Uh... backups? Or why didn't he just commit each days work to a separate branch on github like Nekotekina did with the SPU recompiler? Acts like a backup, if need be people can test on more games than his hard drive can ever carry, and it stops people from constantly asking for an eta...

What do you want, test every single broken commit with no reason?