Testing: wLaunchELF_v4.43a (Build-9c18290-2018-11-03)

There is some weird font text shown in the following places:

Navigate to:
wLE > Settings > Screen Settings > (place cursor next to the following items - don't need to run them:)

• Skin Settings
• Load Skin CNF
• Save Skin CNF

If you look in the footer, there is some weird font text shown for the button options.

Also...

wLE > Settings > Startup Settings > (place cursor next to the following items - don't need to run them:)

• Number of CNF's
• Initial Delay:
• Default Timeout

If you look in the footer, there is some weird font text shown for the button options.

I have attempted several times to transfer a large number of files from USB to HDD with WLaunchElf (latest version), and WLE silently fails. Here's the repository I'm trying to transfer for OPL:

https://github.com/Tom-Bruise/PS2-OPL-CFG-Database

It contains about 14,000 extremely small .CFG files, of which belong in OPL's "CFG" folder. It will fail every single time after a few hundred, but it will not report any errors, it'll simply close the transfer. You'll have to watch it to see what happens.

Are you guys able to host your own precompiled binarys on a release page.
https://help.github.com/articles/creating-releases/

Psx-Scene is currently down (http://psx-scene.com/forums/official-ulaunchelf-forums/) so unable to grab a new realese, I'm running on the old 2013 release.

Checks

• I have checked existing issues for duplicates and found none

Describe the issue

Simply launching the 2021-10-16 build specifically breaks a fresh FHDB installation.
I had to image the HDD to reinstall.

Then I made a prepared multi-install memory card that I would use to boot from and restore for regular testing, opening the older 2019 version of LaunchELF, formatting the entire HDD, then launching FHDB Installer from mass to restore and boot just from that device later.

Deleting the FHDB CNF file or copying and pasting an old one to the same location would not help.
I changed other various FHDB settings like default browser mode and the OSDSYS options using the configuration, launching other programs, powering off and on completely frequently between each action, and none of those would cause the issue.

LaunchELF PS2 partition defaults:

  __mbr               128Mb       (Reserved for system)
  __net               128Mb
  __system            256Mb
  __sysconf           512Mb
  __common            1024Mb

I would add homebrew to the HDD under __common in a new folder and run from there. Some place I heard running homebrew from a mass storage device directly may be problematic, but I think has worked fine for me before, and also from the memory card, although I don't want to alter any data on those anymore, especially the one with the FMCB multi-install.

I just copied 2GiB of data from the beginning of my SATA Toshiba 80GiB HDD that I am using inside my older fat model PS2 with the HDD-Network adapter that should cover all of the relevant partitions, although I suspect an issue with the first, most important one, both before and after using the issue-causing wLF build. When running cmp -l, I see these changes:

      3073   0 260
      3074   0 113
      3075   0 371
      3076   0  15

When I take the first 1MiB from the 'before' data file and reapply that to the HDD, FHDB boots successfully again.

Console model

SCPH-39001

hi

I made an ISO for ulaunchelf and burned in dvd, created a LAUNCHELF.CNF and inserted in the same directory where elf is

But when I load the DVD the CNF isn`t loadead

What I have to do to load the cnf in this case?

Disclaimer
Issue reports for app version which were not downloaded from the official GitHub repo or were not compiled from this Github repo are not accepted.
Before posting the issue confirm that you meet the below requirements.

• I have checked existing app issues for duplicates and found none
• I am using either app beta version or app stable version, or version compiled by me

Describe the issue
Built from source using latest ps2-dev, when I press jgpviewer in MISC menu, ulaunchelf freezes. Trying to boot with a jpg set in cnf results in a black screen. Reverting to build of ule bundled with ule themes will load jpgviewer and the image in question. I have fully rebuilt ps2-dev and repulled latest commit here before making issue.

Configuration (please complete the following information):

• Console Model: PCSX2 v1.7.0-dev-1670-gc93692a77
• App revision (or commit) 5c5e75c

To Reproduce
Steps to reproduce the behavior:

1. Build source
2. open jpgviewer

Expected behavior
view a jpg

As was reported in this PSX-scene thread, current versions of uLE (including 4.43a, though I have not built a HEAD build to check it hasn’t been fixed since!) don’t work with PSX memory cards or PocketStations, as of WIP6.

This is exhibited as PSX memory cards and PocketStations appearing to have 0 bytes of available space, and the memory card directory listing not being readable.

uLaunchELF v4.42d works as expected.

Infinite pasting when copy (cut) then paste a folder into itself.
(e.g.: pasting "mc1:/APPS" into "mc1:/APPS/" causes infinite loop!!)

It may fatal. (I hope no one trying this😅)

Hello AKuHAK,

Please accept the file https://github.com/marcelocripe/pt-br.lng-for-wLaunchELF-pt-br.lng-para-wLaunchELF/blob/main/pt-br.lng.
The 'pt-br.lng' file is a contribution from Venão (Hardlevel) on 08-12-2020 and revision of marcelocripe on 08-11-2021 for the translation of wLaunchELF into Brazilian Portuguese.

Note: The original lang.h file does not recognize character accents (ç, ~, ^, `, ´, etc), so it was not inserted into the 'pt-br.lng' file, the file encoding is ANSI, should be encoded in UTF-8.

Thanks for programming and maintaining wLaunchELF.

marcelocripe

Olá AKuHAK,

Por favor, aceite o arquivo https://github.com/marcelocripe/pt-br.lng-for-wLaunchELF-pt-br.lng-para-wLaunchELF/blob/main/pt-br.lng.
O arquivo 'pt-br.lng' é uma contribuição do Venão (Hardlevel) no dia 12-08-2020 e revisão do marcelocripe no dia 11-08-2021 para a tradução do wLaunchELF para o idioma Português do Brasil.

Nota: O arquivo original lang.h não reconhece a acentuação de caracteres (ç, ~, ^, `, ´, etc), por isso não foi inserido no arquivo 'pt-br.lng', a codificação do arquivo é ANSI, deveria ser codificado em UTF-8.

Eu agradeço por programar e manter o wLaunchELF.

marcelocripe

We have a topic at ps2-home.com where 3 different bugs were reported when mounting a VMC with wLE and doing some functions.

See thread: https://www.ps2-home.com/forum/viewtopic.php?f=16&t=9003

Let me know if you have any questions or something isn't understandable.

P.S. I believe one of the reported bugs has been reported before: #28

Could someone please upload the keyboard map files to this repository or link to a download service.?

It seems that there were posted on psx-scene.com and this site is since dead and wayback time machine doesn't have links to them.

I am hoping some people have these in their possession.

The details of the files are as follows:

https://web.archive.org/web/2010103...ead-ulaunchelf-support-files-46447#post328313

Keyboard_US.zip == The original US map, useful as starting point for new work.
Keyboard_SE.zip == Swedish key map, by me (dlanor).
Keyboard_FR.zip == French key map, by Polo35.

Or

https://webcache.googleusercontent....iewtopic.php?t=5210+&cd=1&hl=en&ct=clnk&gl=au

uLE_Keyboard_US.zip
uLE_Keyboard_SE.zip
uLE_Keyboard_FR.zip

We have a member at PS2-HOME reporting a possible bug when using wLE with FHDB. http://www.ps2-home.com/forum/viewtopic.php?f=16&t=6519

When he wants to setup a shortcut button on wLE for the following path: MISC/OSDSYS -- He gets this error: mc:/BAEXEC-SYSTEM/osdmain.elf is Not Found.

So it seems the issue is that wLE is looking for it under MC and not under his HDD (FHDB) setup.

Is this a known issue or a new bug for FHDB users and wLE?

This demo was working with uLaunchELF 4.40 but wLaunchELF breaks it: https://www.pouet.net/prod.php?which=10435
It fails somewhere after switching video modes, and it happens both when launching from mass and cdfs

SMB2/3 network filesystem support would be very nice to avoid having to use clunky usb sticks to copy
files to/from the ps2.

Libsmb2 is a high performance, small footprint smb2/3 client that can be ported to almost any platform that has berkley socket support. It supports up to smb3.1.1 as well as signatures and encryption.
It interoperates with Windows, MacOS, Samba, EMC, NetApp, linux-cifsd kernel server and Azure.
https://github.com/sahlberg/libsmb2

I have ported libsmb2 so it builds on PS2 EE and it works.
I have build small test applications based on ps2sdk/samples/network/tcpip-basic
to connect to shares and access them.

It would be awesome to have smb2 support in the launchelf filemanager.
I tried to do it myself, copying code from working examples into wlaunchElf with no success,
I can't even get the ethernet link to become active, and not even getting to calls to socket() to succeed when I try to put this code into wlaunchElf :-(.
So this is way too hard for me to do, which makes me sad :-(

But if anyone wants to attempt it, I can share the setup code I have so far, working examples based on
ps2sdk/samples/network/tcpip-basic and any help you would need for the libsmb2 api. I willing to work with you.

I think it would be really really nice to have smb2/3 support to be able to copy files from/to modern windows and other smb2/3 server.

Hey, with newest wLE (for me that is), commit: 970ca99

I have the following issues:

1. Unstable FTP and lack of permissions even when given
2. A bit more stable HOST however I need lotsa resets to make it connect, and even when it connects it can freeze console while copying
3. CDVD support, doesn't load config from disc and often hangs while copying files (I just tested it) and loading elfs from it

And possible (?) features:

1. Lack of detecting if device has enough space to copy/paste there
2. Removal of graphical glitch when long file name expands window and next is shorter - space under long window is blank and 'cuts' file names till it finishes operation

I think I can predict answers but I needed to try asking. :)

I noticed that when we compile wLE, we get two ELF files:

BOOT.ELF (not packed)
ULE.ELF (packed)

The issue is that the packed version is ULE.ELF and that is the one we tend to share so users can place that file inside the BOOT folder in their MCs for FMCB and etc. The issue is that we have to rename it to BOOT.ELF so it follows the standard filename that we are mostly accustom to.

So I was thinking, wouldn't it be best to reverse the two filenames, so the one that gets packed should be already renamed to BOOT.ELF? This way it is easier for us to share it, without having the task of having to rename it prior to sharing it? For convenience purposes only?

In the Makefile (LINE 6), this can be done like this:

FIND:

EE_BIN = BOOT.ELF
EE_BIN_PKD = ULE.ELF

REPLACE, WITH:

EE_BIN = ULE.ELF
EE_BIN_PKD = BOOT.ELF

Your thoughts?

With sendspace being broken, where can current versions be downloaded?

Trying to upgrade in hopes of creating a partition larger than 128gb. Using v4.43a

In lastest release, it doesn't have elf release, just source code.

Faced strange bug, which is not presented in earlier ps2toolchain versions. When I launch the current development build from a USB stick, then I cannot launch apps from the internal HDD anymore (just return back to OSD browser). This bug only appears if launched from mass, if I launch from MemoryCard or from HDD itself, then I can load elfs from HDD with no problem. Can't figure out where is the problem, but it seems that this is not wlaunchELF problem. If someone can test if OPL has a similar issue? @rickgaiser can it be related to the changes in ps2toolchain?

@sp193

This new version has a new bug. If we try to run some MISC commands -- sometimes it will freeze up the PS2 console.

The previous uLe version [wLaunchELF v4.43a (Build-2017-06-21)] prior to this one did not have this bug.

More details: http://www.ps2-home.com/forum/viewtopic.php?f=16&t=3762

Could add support for .ttf fonts and fix the character bug as ç,ã,é in the Portuguese of brazil.

Checks

• I have checked existing issues for duplicates and found none

Describe the issue

I have a strange issue with recent builds (e.g. 3ac1a36).
I mean when I turn off my PS2 (SCPH-50004) via PS2PowerOff in MISC
my HDD gets corrupted.

It will not launch FHDB anymore. All I can hear is my HDD stuck in a loop tries to power on,
but after a few seconds it shuts down. It does not even reach FMCB logo.

This happens only when wLe is launched from HDD e.g. hdd0:/__sysconf/FMCB/BOOT.
On a flip side when I launch wLe from a MC or a USB device everything is fine.

When I insert a MC with FMCB, launches PlayStation 2 HDD checker I get this notification:

After repairing errors everything seems is back to normal and FHDB launches without any problems.

This issues does not happen with e.g. 41e4ebe or an "ancient" uLe 4.42d.

Console model

SCPH-50004

Describe the issue
wLaunchELF doesn't load config files from it's launch directory (in my case, mass:/wLaunchELF/LAUNCHELF.CNF)

Configuration:

• Console Model: SCPH-77004
• App revision: Both latest release (41e4ebe (14\01\2019)) and latest commit (5c5e75c)

To Reproduce
Steps to reproduce the behavior:

1. Launch wLaunchELF
2. Configure something using the configuration utility
3. Exit configuration utility to save configuration (wLaunchELF shows message "Saved Config mass:/wLaunchELF/LAUNCHELF.CNF")
4. Exit wLaunchELF
5. Start wLaunchELF again

Expected behavior
I expect my just created config file to load

When using boot.elf downloaded from the auto bot, PS2 freezes when in file browser after a few seconds.

@sp193 -- We have a bug report at PS2-HOME: http://www.ps2-home.com/forum/viewtopic.php?f=16&t=6346

Where the user wants to setup his wLE page to adjust buttons to quickly launch ELF files that are exist inside his INTERNAL HDD using FHDB. It seems when he tries to save his BUTTON settings, he gets this error: “Failed To Save LAUNCHELF.CNF”

Example:
(assign the SQUARE button to launch the following ELF file within this path)
hdd0:/__sysconf/FMCB/PS2Restart.ELF

Can you tell us if this is a common bug with FHDB not allowing to do this with wLE or simply a bug in wLE?

Or can you browse the help topic to see what he is doing wrong?

He eventually was able to set up wLE by editing the LAUNCHELF.CNF file, by adding the links to the ELF files, by using NOTEPAD++ (-- FYI: earlier in that thread, he reported he couldn't do that, since he was using Windows Notepad -- and we all know that utility causes issues with encoding formats. But once he switched to NOTEPAD++ he was able to workaround this bug.)

But yet, if he tries to adjust his buttons settings within the wLE settings page, he can't. The only links he can setup are the functions found within wLE's /MISC folder.

NOTE: this doesn't happen to wLE when using it with FMCB, so we assume it maybe a FHDB and wLE conflict?

If wLE is placed in a separate partition (in my case, PP.wLaunchElf), trying to save the network settings fails. If you copy IPCONFIG.DAT from another configuration (or maybe just create the file?) to the partition, then it works

There is a buffer overflow vulnerability in the loader.c file. This is in regards to both the s variable and the partition variable.

The partition variable contains argv[1] which is user controlled as displayed below:
https://github.com/AKuHAK/uLaunchELF/blob/75b22d9b0d5a23f4b758d6498e6e7a185b744523/loader/loader.c#L126

This variable has a size of 128 characters, making it simple to overflow:
https://github.com/AKuHAK/uLaunchELF/blob/75b22d9b0d5a23f4b758d6498e6e7a185b744523/loader/loader.c#L51

Running with argv[1] = A * 400 (400 A's) will make the application crash. This weakness may be used to change the intended execution flow of the program.

Tested on uLaunchELF 4.43a 41e4ebe and latest commit

The MISC menu has every option of the R1 menu available

I've already solved this on my wLE mod so I'll leave the link here
israpps@0d4f675

Currently wLaunchELF can only supports static address:

Is there any chance to also add DHCP?

Is there a way for wLe to enter shared folder without e.g. Rad Host Client 1.8a?
Something like in OPL, where games can be listed but instead of that I can use for example "wLe" share not "PS2SMB"?

Checks

• I have checked existing issues for duplicates and found none

Describe the issue

Squares are shown as marks, I know I have screen from fork but identical issue exists with this official version. No matter settings saved or without loaded LAUNCHELF.CFG. When I'll find the time I'll replace pic with official version.

Console model

39004/50004/70004/77004/90004

Launching OPL via uLE (wLE 4.43a - commit d7c7459) causes issues for both Internal HDD and SMB users. See this report: http://www.ps2-home.com/forum/viewtopic.php?f=16&t=5790

Okay, now testing the new fixes done for Issues #25 and #26 (commit: ff91651 )

And I am using FMCB v1.965 (2018/11/03) and loading BOOT.ELF from MC 1.

I now got a new bug with this wLE version.

NOTE: I've compiled this version with the latest changes made to PS2SDK: ps2dev/ps2sdk@fbc3945

If I try to go into SETTINGS in wLE and then simply press the TRIANGLE (Return), I get a black screen.

Before, when pressing that button, it should bring me back to wLE main page to select File Browser or etc.

It also gives me a black screen after I select OK or Cancel in the SETTINGS page.

The way I discovered this bug, is that I wanted to verify that the weird font issue was fixed in Issue #26 -- which it was. But now this new bug came about.

This didn't happen prior to when I reported that bug, so at least we know it was a recent update that caused it?

Refer to: ps2homebrew/Open-PS2-Loader#298

The very same automatic release might be implemented here as well.

It would be great if using the file browser I could open text files by pressing O

Currently I have to open the text editor, press R1, choose open, find the file.

Specifically useful for CHEATS.TXT

if i shut down my console from uLaunchELF while the HDD isnt active (tested on 4.43a 41e4ebe and 4.43a_KHN) the HDD is turned on less than one seccond before shuting down the console.

https://github.com/AKuHAK/uLaunchELF/blob/8d4a0c28f336395d42fe43ddc981cac11ce0ea5f/main.c#L2115

Since this location is hard coded for memory card location only and FreeHDBoot users have their osdmain.elf stored at "hdd0:/__system/osd/osdmain.elf", misc/osdsys does not work.

A easy solution to this might be to add an if / else statement here to allow both locations to be usable. The "else" will still default to the original coding if osdmain.elf is not found on hdd. This would make things more compatible without compromising original design.

Something similar to this, but in proper syntax of course:

If "hdd0:/__system/osd/osdmain.elf" exists
    sprintf(default_OSDSYS_path, "hdd0:/__system/osd/osdmain.elf");
Else 
    sprintf(default_OSDSYS_path, "mc:/B%cEXEC-SYSTEM/%s", rough_region, file);

@sp193, just testing: Update 2018/11/03: v0.984 (FMCB v1.965) re-released. Which includes: wLaunchELF_v4.43a (Build-9c18290-2018-11-03)

I think something changed in the way now that the USB HDD module loads via FTP using wLE's PS2NET.

Before, when I would run it, through my FTP client I can see both the MC's and also the USB HDD (mass) connected to the PS2 unit.

Now with all the latest changes, it will not. It will only see the MCs, but not the USB HDD. It will only see it if I navigate (using the File Browser) to the mass directory, then when I refresh my FTP client, I can finally see the USB HDD folder contents (mass).

Is this a bug? If not, could you make PS2NET automatically scan and run the USB MODULE, this way we don't need to do so many steps in order for our FTP clients to see the USB HDD?

wLaunchELF v4.43a

Version Fri jan 11 18:41:39 2019 commit: 41e4ebe

SELECT: Configure > Network Settings...

Extreme slowdown when the save path is "hdd0:/__sysconf/FMCB/IPCONFIG.DAT"

I think that the date in the About page in uLE can be misinterpreted because it's based on when the ELF was compiled and not really representing if any new core (code) changes were really added to it--since it sports a newer date.

Please go to this post to read more about this wishlist: http://www.ps2-home.com/forum/viewtopic.php?f=16&t=4847

Hello, it is possible to disable the HDD modules loading at startup?? So that the HDD would be powered-on only if/when needed (like it was in Ulaunchelf 4.42 and previous). Maybe there's an option that escapes me?

In the mist of refactoring the code to use only fileXio, I found that uLaunchELF will change the timestamps for files after copying. However, the code for doing so for a PFS destination was commented out, saying that it doesn't work.

So did it never work? Does anyone know what actually happens? Or was it already fixed, but just not enabled within uLaunchELF?
Right now, I have re-enabled the code. If it is a problem with PFS, then PFS should be looked at. Or if it wasn't ever a feature that PFS was meant to have (and it also comes with some ill effects), then it should be re-disabled within uLaunchELF with the appropriate comments.

There seems to be an odd bug when enabling Progressive in TV MODE in uLE Settings. Testing this version of uLE: v4.43a 2018-06-18 commit: d7c7459 -- also updated to latest version of FMCB v1.961

It seems to not take affect when launching uLE for the first time from either the PS2 Browser or etc.

It only seems to take affect when you happen to have a multiple page uLE Skin and you have also adjusted those pages with Progressive Mode enabled.

So it seems that the first page, it doesn't turn on Progressive mode on the TV, but until you switch to a different page within uLE. And then when you return to the first page, it then is in Progressive Mode.

I've scan my two memory cards (NOTE: I launch FMCB via my 2nd SLOT) or my USB HDD to see if I happen to have another CNF file (LAUNCHELF.CNF) anywhere else, but no, nothing that it could be overriding my settings.

I haven't yet tested this bug without a skin, so perhaps that might be the issue? But I did go through each page and made sure to enable progressive mode for each page and etc. So something is amiss here.

I'll report back once I test this without a skin. The skin I am testing is the one found here: http://www.ps2-home.com/forum/viewtopic.php?f=60&t=2211 -- and like I said before, I made sure to go through each different page (it only has 5 CNF pages) and enable Progressive mode per page via uLE -- not NOTEPAD++ or etc.

P.S. I've created a tutorial to teach others about this new feature: http://www.ps2-home.com/forum/viewtopic.php?f=60&t=5785

UPDATE:

Bug still occurs without a skin.

Checks

• I have checked existing issues for duplicates and found none

Describe the issue

Since my controller broke long time ago and I had a spare ir remote, I tried to use it but when I try to navigate the menu you bring up with R1 I can't navigate it because the d-pad input doesn't work even though it works perfectly fine outside of wlaunchelf

Console model

SCPH-70001

The rename function doesnt do nothing when used with VMCs.

Tested with wLaunchELF v4.43a wed oct 31 16:52:25 2018 commit: 66ca9b2 and previous versions of wLaunchELF.

When the copy process encounters a long folder name that it has to truncate, the copy process fails to copy any files after that.

examples:

• SLPM_860.80.Jun Classic C.C. & Rope Club
• SLUS_009.57.Metal Gear Solid - VR Missions

could you make it posible??
mostly because it is annoying to go back to misc every time that i want to edit title.cfg files from hdd0:/+OPL/APPS/

I don't know how or when it happened, but PS2Net completely broke for FTP purposes between at least commit 41e4ebe and the current dev release. I tested and confirmed this myself, though I cannot say when exactly, or how.

It would greatly improve usability if the position of that cursor persisted between uses of the onscreen-keyboard.

Expected:

• press select to open onscreen-keyboard
• type $
• press select to hide onscreen-keyboard
• move around document
• press select to open onscreen-keyboard
• cursor is at $

Actual:

• press select to open onscreen-keyboard
• type $
• press select to hide onscreen-keyboard
• move around document
• press select to open onscreen-keyboard
• cursor is at A

On wLaunchELF trying to rename the __.POPS partition fails, however it does work on uLaunchELF 2TB Edition.

The last version of wLE that I can compile is commit: 763495f (Aug 27, 2017)

But then that got broken starting with this commit: b950488 (Feb 18, 2018)

... and pretty much to any commit after that, gives me the same general error -- even the most current commit: b4f8a48 (Aug 11, 2018 )

I get the following error at the end of the compiling:

In file included from launchelf.h:8,
                 from main.c:4:
githash.h:1:20: warning: extra tokens at end of #ifndef directive
githash.h:2:17: warning: extra tokens at end of #ifndef directive
githash.h:2:1: unterminated #ifndef
githash.h:1:1: unterminated #ifndef
main.c: In function `Show_About_uLE':
main.c:296: `ULE_VERDATE' undeclared (first use in this function)
main.c:296: (Each undeclared identifier is reported only once
main.c:296: for each function it appears in.)
main.c:298: `GIT_HASH' undeclared (first use in this function)
make: *** [main.o] Error 1

Unless, I am using the wrong command? I use the make rebuild command. -- Please advise?

UPDATE:

If I revert only the changes made to this commit: b950488 (Feb 18, 2018)

I can then compile the latest wLE version: b4f8a48 (Aug 11, 2018 )

But it won't have the data that is generated inside the About page of wLE. :-(