I need help playing over Ethernet with the OPL 0.8 and 0.9 versions

[tomstone]

I seriously need some help to get the newer OPL versions to work over Network. Something important changed after version 0.7 and I cannot get the newer versions to connect. I can play just fine with the old OPL, but when I try to boot up OPL 0.8 it doesnt show me any list and in 0.9 it shows me Error 302. The Hard drive I am sharing is named and shared by PS2SMB, the port is 445(Same as configured in 0.7), and the filesharing is not password protected. I am using Windows 7 to do this. Any ideas what I am doing wrong?

Thanks in advance.

[slntw]

I seriously need some help to get the newer OPL versions to work over Network. Something important changed after version 0.7 and I cannot get the newer versions to connect. I can play just fine with the old OPL, but when I try to boot up OPL 0.8 it doesnt show me any list and in 0.9 it shows me Error 302. The Hard drive I am sharing is named and shared by PS2SMB, the port is 445(Same as configured in 0.7), and the filesharing is not password protected. I am using Windows 7 to do this. Any ideas what I am doing wrong?

Thanks in advance.

Try to defrag the HDD and test it again, if it doesn't work, change the name to SMB only.

Edit: Your problem is related to the Shared Folder name:

* Minor GUI changes (deferred error message display, small optim for main loop)
* provide Error messages for network startup

On error when starting the network, you will have a message with an error code, which correspond to

#define ERROR_ETH_NOT_STARTED 100
#define ERROR_ETH_MODULE_PS2DEV9_FAILURE 200
#define ERROR_ETH_MODULE_SMSUTILS_FAILURE 201
#define ERROR_ETH_MODULE_SMSTCPIP_FAILURE 202
#define ERROR_ETH_MODULE_SMSMAP_FAILURE 203
#define ERROR_ETH_MODULE_SMBMAN_FAILURE 204
#define ERROR_ETH_SMB_LOGON 300
#define ERROR_ETH_SMB_ECHO 301
#define ERROR_ETH_SMB_OPENSHARE 302

If you have an error 300, it means OPL fails connecting to your SAMBA/CIFS serveur, so it can be due to:
* bad IP address for your PC
* bad port
* false crendential (or guest account not allowed)

If you have an error 302 is when the share name is invalid.

Finally, YOU CAN RE-TRY NOW TO CONNECT AS MANY TIMES AS NEEDED (until successful connection).

To do so, try connecting, check the error code, go to network settings, change them, go back to your menu list and HIT REFRESH ("select" button) OR WAIT FOR AUTO-REFRESH IF ENABLED. OPL will try to connect again.