RandomGuy2024
Member
Every time I run wLE 4.43a c46c88c's PS2Net, it always freezes at "Loading NetFS and FTP Server Modules...".
EDIT: I checked wLE 4.43a f213b31's PS2Net and it doesn't freeze at "Loading NetFS and FTP Server Modules..." but now FileZilla Client can't access the PS2. It says "Could not connect to server".
EDIT 2: I'll use wLE_isr latest automated build's PS2Net since it works (if not using the NO_NETWORK builds, of course) unlike wLE 4.43a latest development builds'. I find it odd wLE 4.43a 41e4ebe's PS2Net works when that wLE version was out on 14/01/2019.
EDIT 3: If running any wLE_isr build with MX4SIO support, "mc1:/" doesn't appear in the FileBrowser.
EDIT 4: I was told in Reddit that the MX4SIO driver denies access to the MC on mc1 and it's a mandatory side effect. I'll use wLE_isr latest automated build's BOOT-EXFAT-DS34 since it doesn't have this issue.
EDIT 5: After clicking "mc0:/", wLE_isr latest automated build's BOOT-EXFAT-DS34 opens it and sometimes immediately exits out of it as if I had pressed the "Triangle" button. I have to restart the PS2 when I have this problem and run wLE_isr latest automated build's BOOT-EXFAT-DS34 again.
EDIT 6: It seems it's a known issue that hasn't been fixed yet and it only affects wLE_isr builds with DualShock 3/4 support. Since I use a DualShock 3 wirelessly via Brook Super Converter I don't need them and so I'll use wLE_isr latest automated build's BOOT-EXFAT. Also, after running wLE_isr BOOT-EXFAT-DS34's PS2Net, FileZilla Client still can't access the PS2. It says "Could not connect to server".
EDIT 7: If running any wLE_isr build from mc1 with a MC inserted in mc0, changing wLE_isr's IP address in "Network Settings..." and clicking "Save to "mc1:/SYS-CONF/IPCONFIG.DAT", it says "Saved Failed". I have to take the MC inserted in mc0 for the "IPCONFIG.DAT" file to be created if not wanting to take the FMCB MC which was inserted in mc1 and from which I ran wLE_isr.
EDIT 8: Now, wLE_isr latest automated build supports MMCE. I downloaded wLE_isr latest automated build's BOOT-EXFAT-MMCE and I'll use it from now on.
EDIT 9: I got rid of Brook Super Converter's USB Y-cable by mistake and so I can't use DualShock 3 wirelessly on the PSC (only on the PS2 or wired on the PSC thanks to AutoBleem). I'm having a lot of trouble finding Brook Super Converter for sale again.
EDIT 10: After finally finding Brook Super Converter for sale again, I got another product with the same name (eBay showed a picture from the previous Brook Super Converter I got) and it only worked on the PSC when not using its external HDD so it's not worth it since I can't run AutoBleem because it's there. I ordered an USB-Y cable which fit on the previous Brook Super Converter but it still didn't work.
EDIT 11: I bought a Wingman PS2, updated it and it lets me use a DualShock 3 wirelessly on the PS2, not to mention it's cleaner than Brook Super Converter.
EDIT 12: I bought a 8BitDo USB Wireless Adapter 2, updated it and it lets me use a DualShock 4 wirelessly on the PSC with AutoBleem on the console's external HDD unlike before after connecting the 8BitDo USB Wireless Adapter 2 to a PSC front port, clicking its pair button and pressing the DualShock 4's "SHARE" and "PS" buttons until the controller makes noise.
EDIT 13: When trying to connect to the PS2 by FTP using FileZilla Client in Windows 11 and wLE_isr latest automated build's BOOT-EXFAT-MMCE's PS2Net, FileZilla Client no longer says "Could not connect to server" but now it says:
"Status: Connection established, waiting for welcome message...
Status: Plain FTP is insecure. Please switch to FTP over TLS.
Status: Server does not support non-ASCII characters.
Status: Logged in
Status: Retrieving directory listing...
Status: Directory listing of "/" successful"
Below "Remote site:", Filezilla Client only shows a mount point called "/" and below "Filename" it only shows one called "..". I've tried other wLE and wLE_isr builds and FTP programs (including Windows 11's File Explorer) and they don't work too. This is odd since it was working before in the previous wLE_isr automated build so maybe the latest (which has the 74550d8 commit) is the culprit. This also happens in wLE_isr latest automated build's BOOT-EXFAT-DS34.
EDIT 14: I tried wLE 4.43a 41e4ebe and it doesn't have this problem so wLE_isr's latest automated build (which has the 74550d8 commit) really is the culprit. Anyway, I think I'll be using USB devices from now on in wLE_isr latest automated build's BOOT-EXFAT-MMCE when wanting to copy files from there to the MCs or just run them from the USB devices until a new wLE_isr automated build without this problem is out (if it will ever be).
EDIT 15: Now, the DualShock 3's battery is draining fast.
EDIT 16: I ordered a DualShock 3 battery from Amazon but I couldn't unscrew 3 of the 5 screws so I got help and they were able to change the battery with difficulty.
EDIT: I checked wLE 4.43a f213b31's PS2Net and it doesn't freeze at "Loading NetFS and FTP Server Modules..." but now FileZilla Client can't access the PS2. It says "Could not connect to server".
EDIT 2: I'll use wLE_isr latest automated build's PS2Net since it works (if not using the NO_NETWORK builds, of course) unlike wLE 4.43a latest development builds'. I find it odd wLE 4.43a 41e4ebe's PS2Net works when that wLE version was out on 14/01/2019.
EDIT 3: If running any wLE_isr build with MX4SIO support, "mc1:/" doesn't appear in the FileBrowser.
EDIT 4: I was told in Reddit that the MX4SIO driver denies access to the MC on mc1 and it's a mandatory side effect. I'll use wLE_isr latest automated build's BOOT-EXFAT-DS34 since it doesn't have this issue.
EDIT 5: After clicking "mc0:/", wLE_isr latest automated build's BOOT-EXFAT-DS34 opens it and sometimes immediately exits out of it as if I had pressed the "Triangle" button. I have to restart the PS2 when I have this problem and run wLE_isr latest automated build's BOOT-EXFAT-DS34 again.
EDIT 6: It seems it's a known issue that hasn't been fixed yet and it only affects wLE_isr builds with DualShock 3/4 support. Since I use a DualShock 3 wirelessly via Brook Super Converter I don't need them and so I'll use wLE_isr latest automated build's BOOT-EXFAT. Also, after running wLE_isr BOOT-EXFAT-DS34's PS2Net, FileZilla Client still can't access the PS2. It says "Could not connect to server".
EDIT 7: If running any wLE_isr build from mc1 with a MC inserted in mc0, changing wLE_isr's IP address in "Network Settings..." and clicking "Save to "mc1:/SYS-CONF/IPCONFIG.DAT", it says "Saved Failed". I have to take the MC inserted in mc0 for the "IPCONFIG.DAT" file to be created if not wanting to take the FMCB MC which was inserted in mc1 and from which I ran wLE_isr.
EDIT 8: Now, wLE_isr latest automated build supports MMCE. I downloaded wLE_isr latest automated build's BOOT-EXFAT-MMCE and I'll use it from now on.
EDIT 9: I got rid of Brook Super Converter's USB Y-cable by mistake and so I can't use DualShock 3 wirelessly on the PSC (only on the PS2 or wired on the PSC thanks to AutoBleem). I'm having a lot of trouble finding Brook Super Converter for sale again.
EDIT 10: After finally finding Brook Super Converter for sale again, I got another product with the same name (eBay showed a picture from the previous Brook Super Converter I got) and it only worked on the PSC when not using its external HDD so it's not worth it since I can't run AutoBleem because it's there. I ordered an USB-Y cable which fit on the previous Brook Super Converter but it still didn't work.
EDIT 11: I bought a Wingman PS2, updated it and it lets me use a DualShock 3 wirelessly on the PS2, not to mention it's cleaner than Brook Super Converter.
EDIT 12: I bought a 8BitDo USB Wireless Adapter 2, updated it and it lets me use a DualShock 4 wirelessly on the PSC with AutoBleem on the console's external HDD unlike before after connecting the 8BitDo USB Wireless Adapter 2 to a PSC front port, clicking its pair button and pressing the DualShock 4's "SHARE" and "PS" buttons until the controller makes noise.
EDIT 13: When trying to connect to the PS2 by FTP using FileZilla Client in Windows 11 and wLE_isr latest automated build's BOOT-EXFAT-MMCE's PS2Net, FileZilla Client no longer says "Could not connect to server" but now it says:
"Status: Connection established, waiting for welcome message...
Status: Plain FTP is insecure. Please switch to FTP over TLS.
Status: Server does not support non-ASCII characters.
Status: Logged in
Status: Retrieving directory listing...
Status: Directory listing of "/" successful"
Below "Remote site:", Filezilla Client only shows a mount point called "/" and below "Filename" it only shows one called "..". I've tried other wLE and wLE_isr builds and FTP programs (including Windows 11's File Explorer) and they don't work too. This is odd since it was working before in the previous wLE_isr automated build so maybe the latest (which has the 74550d8 commit) is the culprit. This also happens in wLE_isr latest automated build's BOOT-EXFAT-DS34.
EDIT 14: I tried wLE 4.43a 41e4ebe and it doesn't have this problem so wLE_isr's latest automated build (which has the 74550d8 commit) really is the culprit. Anyway, I think I'll be using USB devices from now on in wLE_isr latest automated build's BOOT-EXFAT-MMCE when wanting to copy files from there to the MCs or just run them from the USB devices until a new wLE_isr automated build without this problem is out (if it will ever be).
EDIT 15: Now, the DualShock 3's battery is draining fast.
EDIT 16: I ordered a DualShock 3 battery from Amazon but I couldn't unscrew 3 of the 5 screws so I got help and they were able to change the battery with difficulty.
Last edited:
