

- PS4 FIRMWARE 3.55 UNABLE TO RE INITIALIZE DRIVE ARCHIVE
- PS4 FIRMWARE 3.55 UNABLE TO RE INITIALIZE DRIVE FULL
- PS4 FIRMWARE 3.55 UNABLE TO RE INITIALIZE DRIVE CODE
- PS4 FIRMWARE 3.55 UNABLE TO RE INITIALIZE DRIVE PC
- PS4 FIRMWARE 3.55 UNABLE TO RE INITIALIZE DRIVE PS2
updated cue2pops.exe with a compiled version of 2.3 to prevent virustotal reporting false positives in the file

changed the cue file validator to check for double quotes around the bin file as cuetopops 2.3 reports the cue as invalid if double quotes are not present app will delete the working directory even if debugging is enabled
PS4 FIRMWARE 3.55 UNABLE TO RE INITIALIZE DRIVE ARCHIVE
changed 7z to extract all files inside the working directory instead of keeping the archive folder structure due to windows having a 260 character path limit
PS4 FIRMWARE 3.55 UNABLE TO RE INITIALIZE DRIVE FULL
working directory for each file is now always a random 6 digit string instead of the full path of the source file due to windows having a 260 character path limit wrote and compiled binmake 1.0 for converting disk images to cue/bin files added support for disk images (bin, img, iso, mdf, nrg) Rename "conf_elm.cfg" to "conf_apps.cfg"). (To use it with Official Beta revisions release or latest stable OPL 0.9.3

If you are using OPL Daily Builds you can use this tool to generate a "conf_elm.cfg" file that can be used to play PS1 games directly from OPL.
PS4 FIRMWARE 3.55 UNABLE TO RE INITIALIZE DRIVE PS2
PS4 FIRMWARE 3.55 UNABLE TO RE INITIALIZE DRIVE PC
Is your PC getting a good signal? If the signal quality is substandard, then packet loss is not out of the question and perhaps that is why OPL is having problems with connecting.īut i actually thought that packages where sort of "checked" upon arrival ? I don't recommend that you use wireless though, since wireless can add onto the latency and packet loss, just due to how wireless technologies are. Did you set your firewall zone to "Home"? Although I would have expected it to not even connect if the firewall was the problem.
PS4 FIRMWARE 3.55 UNABLE TO RE INITIALIZE DRIVE CODE
157128/9 User: philippeb (05-16-2017, 04:04 PM)ģ02 is the error code that is displayed when OPL tries to (but fails to) send an echo to the server, to test that the connection was established properly. Is your PC getting a good signal? If the signal quality is substandard, then packet loss is not out of the question and perhaps that is why OPL is having problems with connecting. 157128/8 User: SP193 (05-15-2017, 10:49 PM) 302 is the error code that is displayed when OPL tries to (but fails to) send an echo to the server, to test that the connection was established properly. I thought it was something with my connection setup, but it seems to be somewhere else ? I actually assumed that one of you would go like "DUUUDE, why the hell is setting x set to y ?, out X instead of A and problem is solved".Īnyway, i get error 302 when trying to connect. I am pretty sure that a newer version past v0.9.3 will not help, particularly if it is a user error. He did not give any information on what the problem was, so we can only guess.
