PS3 black screen SMB loading on new OPL builds

[igordimovski]

Hi

I have problem with newer OPL builds, my last working version over SMB is r323, but all of the latest version I have compiled r404 r399 r386 ... don't work with same symptoms ... connection to PC is OK, list of games is OK but NO games loading ... after I press X for game to load there is just black screen ... no debug colors ...

I am using yoshi's last vm for compiling

My setup
60 GB PS3 model CECHA01
Swap Magic 3.6
Wired connection to PC

EDIT:
I have just compiled latest version r422 and same problem NO game loading just black screen

[aginor37]

I have no idea if this will be any help, but have you changed the username/password in network config to match a user account with full access on the PC? I feel somewhat certain that somewhere in that time frame they started moving away from the GUEST logon.

Other than that i have no idea, as I don't know how/if things work any differently on a PS3.

[igordimovski]

I have no idea if this will be any help, but have you changed the username/password in network config to match a user account with full access on the PC? I feel somewhat certain that somewhere in that time frame they started moving away from the GUEST logon.

Other than that i have no idea, as I don't know how/if things work any differently on a PS3.

Yes, and it is same with username/password or GUEST/no-password, what is strange is that I can start network and see list of games, so network config is OK, but I can not start any game ...

[dlanor]

Yes, and it is same with username/password or GUEST/no-password, what is strange is that I can start network and see list of games, so network config is OK, but I can not start any game ...

Even if everything is perfectly setup for GUI access to the game list, it could still fail due to missing permissions of the game files themselves.

What is made visible inside a directory is based not on the file permissions set, but on the permissions of the fileshare/folder used. But in an access involving the file content, as when running a game, it is not just the permissions of the fileshare but the permissions set for the individual file that matter.

Being able to see all games, but getting stuck in a white screen at launch is typical of one permission error, where the logged on user has access permission to the folder, but no permission at all for the file(s) of that game.

Similarily being able to see all games, but getting stuck in black screen at launch is typical of another permission error, where the logon user has permission to access the folder and also the game file(s), but only read permission when trying to run the game with VMC. (write permission only matters with VMC choice activated for a game ).

You should double-check the fileshare settings to make sure that each file has the access settings needed. Note that this concerns not only the "Sharing" tab of the property dialog for the fileshare folder, but also the "Security" tab of the property dialog for each game file.

If you use an SMB logon that is the same username and password as you use on your computer/NAS normally when creating files etc, then the file permissions should be OK, but for VMC use you should also set the folder "Sharing" permissions to include "Full Control" for that user. Even when it is the same logon that you use on the computer, amd recognized as such when it comes to the file security settings, the fileshare must still be given a separate confirmation that write on this fileshare is acceptable (by that user).

Perhaps you are right and your setup really is good as-is, with some unknown weirdness messing it up for you, but what I described here are some of the stumbling blocks that others (including myself) have had problems with in the past, so it's worth the time to check if any of them apply to your own problems.

Edit: Almost forgot: My references to dialogs and 'tabs' relate to WinXP pro SP3, so your methods may vary in other OS variants.

Best regards: dlanor

[igordimovski]

Even if everything is perfectly setup for GUI access to the game list, it could still fail due to missing permissions of the game files themselves.

What is made visible inside a directory is based not on the file permissions set, but on the permissions of the fileshare/folder used. But in an access involving the file content, as when running a game, it is not just the permissions of the fileshare but the permissions set for the individual file that matter.

Being able to see all games, but getting stuck in a white screen at launch is typical of one permission error, where the logged on user has access permission to the folder, but no permission at all for the file(s) of that game.

Similarily being able to see all games, but getting stuck in black screen at launch is typical of another permission error, where the logon user has permission to access the folder and also the game file(s), but only read permission when trying to run the game with VMC. (write permission only matters with VMC choice activated for a game ).

You should double-check the fileshare settings to make sure that each file has the access settings needed. Note that this concerns not only the "Sharing" tab of the property dialog for the fileshare folder, but also the "Security" tab of the property dialog for each game file.

If you use an SMB logon that is the same username and password as you use on your computer/NAS normally when creating files etc, then the file permissions should be OK, but for VMC use you should also set the folder "Sharing" permissions to include "Full Control" for that user. Even when it is the same logon that you use on the computer, amd recognized as such when it comes to the file security settings, the fileshare must still be given a separate confirmation that write on this fileshare is acceptable (by that user).

Perhaps you are right and your setup really is good as-is, with some unknown weirdness messing it up for you, but what I described here are some of the stumbling blocks that others (including myself) have had problems with in the past, so it's worth the time to check if any of them apply to your own problems.

Edit: Almost forgot: My references to dialogs and 'tabs' relate to WinXP pro SP3, so your methods may vary in other OS variants.

Best regards: dlanor

I finally got time to double check network and sharing setup on PC side, Win XP SP3, and I can't see anything wrong ...
again if I use "older" r323 OPL version everything is OK, this is my last compiled version without username/password in network config,
then if I use "newer" version of OPL ( I have compiled only this r386 r399 r404 and r422 ) with username/password in network config, if I enter username=GUEST and "blank" for password in network config list of games is OK but can not start any ( I think that this time OPL is connecting to PC in same way as in "older" r323 with GUEST account so PC sharing config should not be a problem ) ...
I will try to compile r361 which I think is first version with username/password in OPL network config and check again ... than again maybe there is problem with PS3 PS2 backward compatibility and "newer" builds of OPL ...

and thanks again to All for this super program

EDIT:
OK so I compiled every version from r359 to r369 and here is the result

r359 r360 r361 are OK and SMB game loading is OK

r362 r363 ... r369 NO SMB game loading

r362 changeset description on bitbucket is "EE core: added a ResetSPU() in LoadExecPS2 hook "
then I commented line 267 ResetSPU(); in loader/syshook.c:
after this again compiled r362 and tested this modified version on my PS3 CECHA01 and now SMB game loading is OK and working as before ...
so why is this ResetSPU(); function freezing my PS3 PS2 backward compatible hardware ...
I will try now to compile the latest version and see if this will help ...

[igordimovski]

I have just compiled and tested r426 with commented line 276 ResetSPU(); in loader/syshook.c:
and SMB game loading is working with this change on my PS3 CECHA01 ...

[gamer76]

Thanks igordimovski. That worked for me