PS3 webman not mounting ps3 isos

hipvic18

Forum Noob
So ive been struggling with this for the last couple of days but i copied over an old backup from an old ps3 kingdoms hearts 1.5 over to my fat silver ps3 over ftp. but now when i go to webman and try to mount the iso file to play it it first shows the icon for when its in the process of doing so and then it says loaded and right after it says error with the game name and serial number but no actual error codes. my fat ps3 is an evilnat CEX CFW 4.91. ive also updated webman on the ps3 itself with the update option please help a noob out thanks
 
So ive been struggling with this for the last couple of days but i copied over an old backup from an old ps3 kingdoms hearts 1.5 over to my fat silver ps3 over ftp. but now when i go to webman and try to mount the iso file to play it it first shows the icon for when its in the process of doing so and then it says loaded and right after it says error with the game name and serial number but no actual error codes. my fat ps3 is an evilnat CEX CFW 4.91. ive also updated webman on the ps3 itself with the update option please help a noob out thanks

First, check that other games work, either physical or digital. Then, try to rip the game again.
 
Some reasons that could produce that error:
- The game could have been renamed, moved or deleted after the games have been scanned. Run prepISO to re-scan the games.
- The storage device could have been removed or changed from port (e.g. USB0 to USB1). Plug the external HDD and run prepISO.
- The CFW syscalls could have been disabled (e.g. pressed R2+TRIANGLE). Reboot to re-enable CFW syscalls.
- The ISO file could have been corrupted due a file system corruption (e.g. cross link). The storage may need rebuild the file system.
- Storage device fault due damaged sectors or physical damage in the plates or electronic components. Try copying the game to internal HDD or another storage device.
 
First, check that other games work, either physical or digital. Then, try to rip the game again.
i backuped a copy of armored core 4 answer using webman vhs menu and rescanned but when i went to launch it i got the 80010017 error for the first time

all my other games work that i have installed on my xmb

Some reasons that could produce that error:
- The game could have been renamed, moved or deleted after the games have been scanned. Run prepISO to re-scan the games.
- The storage device could have been removed or changed from port (e.g. USB0 to USB1). Plug the external HDD and run prepISO.
- The CFW syscalls could have been disabled (e.g. pressed R2+TRIANGLE). Reboot to re-enable CFW syscalls.
- The ISO file could have been corrupted due a file system corruption (e.g. cross link). The storage may need rebuild the file system.
- Storage device fault due damaged sectors or physical damage in the plates or electronic components. Try copying the game to internal HDD or another storage device.
i did copy the game to my internal hdd and i also ran prep iso after i moved the game to my internal but i dont think it did anything
one thing i am certain the is i definetely had syscall disabled was that why i wouldnt work?
 
Last edited by a moderator:
i backuped a copy of armored core 4 answer using webman vhs menu and rescanned but when i went to launch it i got the 80010017 error for the first time

all my other games work that i have installed on my xmb

You didn't answer me. I've told you to try a disc game to discard if the console has a hardware or a software issue. Running what's already installed doesn't hint anything to make a diagnose.
 
You didn't answer me. I've told you to try a disc game to discard if the console has a hardware or a software issue. Running what's already installed doesn't hint anything to make a diagnose.
im not 100% sure what you mean when you say discard

First, check that other games work, either physical or digital. Then, try to rip the game again.
all of my physical games work on disc if thats what you mean
 
Last edited by a moderator:
Software issue most likely, because that error, 80010017, usually occurs when it can't decrypt the game. Something must've happened while dumping.
 
when i went to launch it i got the 80010017 error for the first time

Error 80010017 = Failure in authorizing SELF. Program authentication fail (Error starting BluRay game). It normally can happen:
- if the ISO image is still encrypted (e.g. downloaded pirated redump ISO)
- if the EBOOT is signed with incorrect keys (e.g. downloaded pirated games patched for 3.55)
- if the game data in HDD is corrupted or has missing files
- if the backup of the disc was made without remove the encryption layer
 
Error 80010017 = Failure in authorizing SELF. Program authentication fail (Error starting BluRay game). It normally can happen:
- if the ISO image is still encrypted (e.g. downloaded pirated redump ISO)
- if the EBOOT is signed with incorrect keys (e.g. downloaded pirated games patched for 3.55)
- if the game data in HDD is corrupted or has missing files
- if the backup of the disc was made without remove the encryption layer
ah so no piracy then haha
 
Error 80010017 = Failure in authorizing SELF. Program authentication fail (Error starting BluRay game). It normally can happen:
- if the ISO image is still encrypted (e.g. downloaded pirated redump ISO)
- if the EBOOT is signed with incorrect keys (e.g. downloaded pirated games patched for 3.55)
- if the game data in HDD is corrupted or has missing files
- if the backup of the disc was made without remove the encryption layer
ok so i have Armored core For Answer on disk backuped the game to my hdd using the vhs menu from webman but im still getting the error code 80010017 i tried enabling syscalls using create syscalls using the cobra tools menu but its still not working still getting the error
 
ok so i have Armored core For Answer on disk backuped the game to my hdd using the vhs menu from webman but im still getting the error code 80010017 i tried enabling syscalls using create syscalls using the cobra tools menu but its still not working still getting the error
This may be a stupid suggestion, but try restarting the system. This in case the syscalls weren't reenabled.
 

Similar threads

Back
Top