You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After installing ARK-4 via the FasterARK method and running it, ARK-4 often crashes in the "#ChovyProject" part with a C1-2858-3 error message, and when it doesn't, it often crashes when running PSP ISOS with a C1-2858-3 error message.
I have this issue if ARK-4's "Memory Stick Speedup" is set to "Always" (it's set as such by default). If set to "Disabled", I don't have it. Also, this setting is set to "Always" by default.
USB Charge
Disabled
Overclock
Disabled
Power Save
Disabled
Balanced Energy Mode
Disabled
Autoboot Launcher
Off
Disable PSP Go Pause
Off
Unlock Extra Memory
Disabled
Memory Stick Speedup
Disabled
Inferno Cache
Off
Skip Sony Logos
Off
Hide PIC0 and PIC1
Off
Hide MAC Address
Off
Hide DLC
Off
Turn off LEDs
Disabled
Verification of form.
I agree that I properly filled out the items listed above.
The text was updated successfully, but these errors were encountered:
PSP/Vita Model
Any
ARK Version
4.20.69 Rev 1
Homebrew/GAME (if applicable)
No response
Plugins ( if applicable )
No response
Steps to reproduce
After installing ARK-4 via the FasterARK method and running it, ARK-4 often crashes in the "#ChovyProject" part with a C1-2858-3 error message, and when it doesn't, it often crashes when running PSP ISOS with a C1-2858-3 error message.
I have this issue if ARK-4's "Memory Stick Speedup" is set to "Always" (it's set as such by default). If set to "Disabled", I don't have it. Also, this setting is set to "Always" by default.
USB Charge
Disabled
Overclock
Disabled
Power Save
Disabled
Balanced Energy Mode
Disabled
Autoboot Launcher
Off
Disable PSP Go Pause
Off
Unlock Extra Memory
Disabled
Memory Stick Speedup
Disabled
Inferno Cache
Off
Skip Sony Logos
Off
Hide PIC0 and PIC1
Off
Hide MAC Address
Off
Hide DLC
Off
Turn off LEDs
Disabled
Verification of form.
The text was updated successfully, but these errors were encountered: