The above video goes away if you are a member and logged in, so log in now!
New Awesome Mount Point Manager - NZHawkPS3
New Awesome Mount Point Manager - NZHawkPS3 –
NOW AVAILABLE for DOWNLOAD
Awesome MountPoint Manager 1.01
NZHawkPS3 known for his Awesome Peek Poker (NZHawk's Awesome Peek Poker - Dumps live PS3 ram!) & Awesome MountPoint Manager 1.0, tweeted this earlier.
New Awesome Mount Point Manager by the end of today. sycall35 ftw!
Awesome MountPoint Manager 1.01 now discards the crappy syscall36 and makes use of the far superior syscall35! NZHawk | PS3
I will update the entire program in the next few days.. Needs a lot of work on the GUI side of it....
Source: NZHawk (NZHawkPS3) on Twitter
As well as add support for any folder to any folder redirect support.. Bare with me peeps. 1.01 only has support for dev_bdvd and dev_flash
Get it here: NZHawk | PS3
Last edited by vettenstein; 10-16-2010 at 01:41 AM.
Reason: now available for download
Now Available for download
sorry noob question, whats the point of the new syscalls
cool thanks for the info, so i should be using this instead of hermes v3 then?
Well, if you want to use it currently, you have to switch to Gaia Manager for it, as OM 1.16 doesn't support the new syscall yet. So, that choice is up to which manager you're currently using. My guess is that everything will start switching this way, so if you're currently using Hermes v3 and OM v1.16, you may want to wait till moh updates his manager if you perfer it, but Gaia is based off of his code directly.
Originally Posted by lenskip
ah i c, i just updated my max avr stick with the hex from this site Maximus AVR USB Blog
Originally Posted by chesh
is that the hex with the new syscall? if it is i'll switch managers, does this improve compatibility?
nevermind, how do u use this Awesome MountPoint Manager 1.01
Originally Posted by lenskip
Nice, hopefully the peek poker will get one soon as well. Because the last time I tried it, I was not getting genuine memory readings (if you're getting all "FF"s then something's wrong).
The simple fact is, with syscall_35, enabling backups becomes the responsibility of the app, not the payload. No more cracking, no more legal issues for the payload coders, and more flexibility because apps are free to use whatever they want, not just what the payload defines for them. Basically, PSJailbreak screwed up big time by using syscall_36 to tie the payload to the BM in the first place, this just fixes it and unties a messy knot that need not exist. Just like the new version of PS3JB for the TI separates the payload and compatibility descriptors from the main app and eliminates the need to recompile it. It just makes things easier and less complicated all the way around, once everyone gets behind it anyway. And it's a good, solid concept, so I think most developers will support it.