The above video goes away if you are a member and logged in, so log in now!
and the freezing issues 99% of people are experiencing? whats that about.
Install msysgit so you can use git in msys.
Originally Posted by FarenHeit
TBH though, you are better off with the ubuntu virtualbox.
I have always used dev_hdd0/GAMES for my backup folder and have edited the source for managers as such (except for BM1.0 which I had to edit the eboot.bin for that). I did this so I can add/remove managers without deleting games.
Originally Posted by h0bbit
Yep I can completely understand this.
Originally Posted by h0bbit
The only reason I ran into this issue was because I installed GAIA and was trying to use the /dev_hdd0/BDRIPS or /dev_hdd0/GAMEZ directory. My reasons for this are simple, I don't want to have to mess around moving stuff around on the HDD if I decide to use a different backup manager. It's also useful if I ever want to uninstall a particular backup manager as I know that it will only remove the backup manager files and nothing else.
Perhaps this is something that has to be thought about. I guess GAIA could always be changed to use a different path, but it would be nice if it wasn't inside it's own install directory for obvious reasons.
When you talk about the dev payload having elevated issues, I assume you mean full /dev_hdd0 read and write access, not elevated permissions or weirdness due to the hermes payload. I could see this being useful for some people, but I have to ask the million dollar question:
If you're going to do this on the dev payload, and there is nothing to stop people from using that payload, what's the point?... Wouldn't it be easier to keep PL3 consistent and ensure all payloads have the same permission set? People should be aware of the risks, if they screw it up they only have themselves to blame.
Just something to think about I suppose.
I have to personally disagree with this "permission logic" -- I mean the who point of "Jailbreak'ing" a PS3 is to give you PERMISSION to DO WHAT YOU WANT, kick Sony out the door, and give you total freedom. -- But then you have a Jailbreak payload, that says to you, sorry you as an user is JUST PLAIN DUMB, therefore we only going to give you a tiny-crack in the opened door, so you can peek over to the left, but don't you dare try opening the door more, or we will slam it shut in your face!
Originally Posted by lombers
What we going have to do? - Jailbreak the Jailbreak? -- You as the user are trading Sony lock&rule for the Jailbreak's own version of lock&rule!
I don't know, just my personal 2 cents on the matter, I mean if the user going to Jailbreak his PS3, he got to take the risk and understand the machine, not be controlled or limited by someone's idea of what is enough power to give to the user, because they "might" do something "wrong"?
This is my own personal opinion on this matter, no offence is directed towards any of the great work the payload developers have done so far!
Good point garyopa.
I see both sides of the fence, but your point definitely has more strength behind it. Everybody knows there is a risk to jail breaking their console, the responsibility is ultimately theirs.
There is already an example of stuff not working because of this (GAIA installing to /dev_hdd0/GAMEZ) which was previously fine under other payload versions. Taking features away that people were previously using is not a good outcome for anyone.
Having said that I understand that with development there will always be bugs, and people unfortunately are going to have to live with that...
I think your looking at the situation wrong. The main reason for having that payload be default is for compatibility reasons. When your running a game in non-JB mode, it doesnt have escalated permissions. When you want to JB your PS3 for playing games, you dont need escalated permissions either. You still have full access to the game folder, the save game, the trophies, etc. There is no change. Now what this means as far as compatibility is concerned at this point, who knows. It would have to take some more testing to see, but one thing is for sure. Installed games with the PL3 payload will work when your system is booted in non-JB mode (if you have the disc that is). This is not the case with Hermes payload.
Originally Posted by garyopa
Now if you want to do custom configurations , homebrew, or just want to store things somewhere else, build the dev version of the payload. They're all included in the git repository and its a simple flag in the build process. Not like it needs to be maintained differently.
Now of course you look at this situation like "omgz i want full access, just cause i can". When in reality this concept of thinking is why the JB is not as complete as it could be. By opening up everything and giving full access could potentially be whats causing some of these games to not work. There could be checks going on that are looking for things to fail in code, but are not failing because everything is enabled.
Teensy 2.0 - Fat PS3 & 3.41fw
The user should not have to build payloads based on their own configuration. The payload should be universal, simple. No ifs, no buts.
Originally Posted by h0bbit
In an ideal world ! and time usually helps
Originally Posted by JonahUK
Anyway if people only care about game backup compatibility stick to Hermes, relax it's a marathon not a sprint, from the sounds of it everyone bitching should just go stick to Hermes and return when the effort and point of PL3 comes to fruition (greater compatibility, saves working with actual disc versions to - you remember the ones you bought - compatibility across different PS3 versions/Payloads etc.
Anyway people saying they're going back to hermes well cool do it ,PL3 devs have always said stick with what works for you !
The permission although not 100% I believe is not meant to restrict you it is trying to make greater cross compatibility as working the same way the un-JB PS3 does
Well i installed Gaia manager, and the pl3 on my minimus v1 and it failed to work.
So i reflashed my minimus v1 with hermes v4b
http://psx-scene.com/forums/f6/herme...eleased-68928/ (Hermes V4B released)
and had mem patch on and now it all works great.
How do i copy this onto my external harddrive?? it has files over 4gb right? what do i need to do to run it off my external?
Also does this hermes V4b payload work with all the other games iv'e cureently ripped with a different payload?
i must say it will e a bitch if for different games we need to keep flashing different payloads, hope not.