-
-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PS2Net not working #79
Comments
Try here |
It didn't exist in wLE_ISR's 945d787 commit and you told me here the issue had been fixed in a previous commit in the official wLE. |
Will that fix the FTP problem and is it a wLE official version or a wLE_ISR one? Also, will this ever be fixed? |
#62 is not something I can fix easily. that limitation is on |
What about the FTP problem? |
Very hard to debug without a devkit. will check it later |
I find it odd a previous commit didn't have it. |
Network was not touched. Try the test build I sent here before |
Then I don't know why I didn't have this issue and now I do. |
as I said twice already
and tell me if it works... |
SCPH-90008 > OpenTuna > BOOT.ELF > PS2Net > Total Commander FTP > Works well SCPH-90008 > OpenTuna > BOOT-EXFAT-DS34.ELF > PS2Net > Total Commander FTP > Works well |
Just tried that BOOT-EXFAT-DS34.ELF version and it works. Will this commit be released? What does "CDVD" mean, by the way? |
WTF This shit is insane |
What do you mean? |
Forget of fixing ps2net on official wLaunchELF. What I did that caused this issue was using latest CDFS.IRX to achieve freedvdboot compatibility. They will not fall back to the legacy one. Not sure how the hell a driver related to extending access to disc drive related features could impact negatively the network related stuff. Not to mention, no one will probably waste time on tracing that issue. |
And does the wLE version that comes with FDVDB have this PS2Net issue? I thought only the latest commits did. If so, you could discard FDVDB in the latest commits and fix the PS2Net problem and let users run FDVDB with a working PS2Net even if its wLE is obsolete. |
When running wLE_ISR on the PS2 and clicking on a folder ("mc0:/", for instance), it often opens it and immediately turns back, not to mention sometimes nothing happens after clicking a button (inside and outside wLE_ISR) or I have drift (outside wLE_ISR). I don't know if it's the DualShock 3's fault or Brook Super Converter's. I have to restart the PS2 when this happens. This might not exactly be related to wLE_ISR but it only happens there. |
That issue is already known and I don't know what's causing the issue |
So it's not Brook Super Converter's or DualShock 3's fault? Does it happen on the official wLE as well or only in any wLE_ISR version? |
It happens on wle Isr only, and I don't know why Or why it only happens on mc0 |
So, it only happens on wLE_ISR and only on mc0, not on wLE_ISR and mc1 or wLE and mc0? |
@israpps, what about this and this issue? They didn't exist before, they appeared in Latest development build. |
Impossible to track them down. 5 years passed between the build in Wich wLaunchELF Isr is based and latest wLaunchELF. Not only the changes to wLaunchELF itself can be responsible, the PS2SDK (toolchain, SDK, etc) changed a lot and also have influence. |
Checks
Console model
SCPH-70004
wLaunchELF commit code
e31a9a3
Describe the issue
PS2Net doesn't work in the BOOT-EXFAT-DS34.ELF version. Even though I insert the right IP address on FileZilla Client, it can't access the PS2.
The text was updated successfully, but these errors were encountered: