This actually has nothing to do with Multiman; it's just an app that attempts to open an eboot.bin using exitspawn2. Try growing a brain.
Printable View
This actually has nothing to do with Multiman; it's just an app that attempts to open an eboot.bin using exitspawn2. Try growing a brain.
That's exactly what I used to format, I just couldn't remember how to get around the 4GB limitation as I used it once on an old Maxtor drive. Btw, what firmware are you on?Quote:
Originally Posted by Comet
werent there compability issues with such big drives in the past? i think i remember readin ps3 wouldnt support 2tb (yet) not 100% sure tho.
but what you could try, is creating 1 "smaller" fat32 partition on that drive with max 1tb and see if it gets recognized by the ps3
I'm on 3.41 until multiMAN works 100% on 3.55cfw syscall.Quote:
Originally Posted by NeoKnight2k5
What exactly is the problem you're having?
Is your PS3 able to recognize your drive?
If you're having difficulties playing some games, you may need to split your 4GB files... try Split4G
I tried that, but it still doesn't get recognized.Quote:
Originally Posted by Apachai
The ps3 doesn't recognize the drive at all. I'm using an external drive built into an enclosure and I think this is one of the USB device sony black listed/block when they did the 3.50-3.55 update. Make sure you test your drive on a 3.55 PS3 before you update! :cry:Quote:
Originally Posted by Comet
Edit: It turns out this drive had problems working on the ps3 even before the 3.50 update. My ps3 slim wont recognize WD USB 3.0 external hard drive - AfterDawn: Forums
Edit: Edit: Problem solved! I forgot to set the partition to logical instead of primary. :oops: :facepalm:
Loads but not play backups, right?Quote:
I'm on 3.41 until multiMAN works 100% on 3.55cfw syscall.
What did I miss while sleeping last night? :chinscrat I thought the only working game backups are the very few reported that have the EBOOT.BIN files patched. I didn't think backups are actually working directly from MultiMAN or any other manager on 3.55 FW. :chinscrat
Hey, i have two questions:
1. Which route is the developer intending to take, is he going to change multiman's code so that is compatible with the new fluke's1 cfw or is he sticking with developing the mygame.pkg (also is it mygame.pkg purpose to make non-directboot games direct bootable)?
2. I have already installed the multiman from the 'list of 3.55 signed homebrew' thread, so i was wondering if that particular version has this 'clear loaded games history' function.
Thanks in advance.
Lots have happened. It's a mess now. Fella called Riku is patching eboots to play directly from xmb. Dean is experimenting with playing directly as well without the need for syscalls etc. But as usual though, place is full of knobs messing up threads and spamming to the fullest.Quote:
Originally Posted by tonybologna
I believe all backup managers will need to be re-coded to work with this news. It's not a matter of just patching EBOOT.BIN files for some games and launching from XMB.Quote:
Originally Posted by N3XuS
Sure, some games are working with patched EBOOT files by install package. Other than what dean reported yesterday with his testing then there are no managers working directly with backups. ;)
Knew about all that! I thought I had missed something! :pQuote:
Fella called Riku is patching eboots to play directly from xmb. Dean is experimenting with playing directly as well without the need for syscalls etc.
I wonder if dean is really planning on porting MultiMAN onto 3.55. I don't want to be stuck on 3.41, but I don't want to be on 3.55 without dean.