hdld_svr.elf not showing up under mc0: but shows up under mass:

[BobBorakovitz]

has anyone encountered this issue before? I did a search in the ulaunchelf forums, but came up with nothing.

I'm using a Memor32 FWIW. I also tried to put the file in all caps and put it as BOOT2.ELF to auto-launch it with Memento but neither wouldn't read it.

I can run it fine with the USB plugged in but it's not really ideal, is there a different version that works from MC0:? or can it be hex-edited to run from MC0:?

thanks for reading

[dlanor]

Originally Posted by BobBorakovitz

has anyone encountered this issue before? I did a search in the ulaunchelf forums, but came up with nothing.

Of course not, because what you are describing is not uLE-specific. It is some problem with your usage of Memor32/Memento.

I'm using a Memor32 FWIW. I also tried to put the file in all caps and put it as BOOT2.ELF to auto-launch it with Memento but neither wouldn't read it.

What do you mean by "neither wouldn't read it" ?
To me that sentence makes no sense.

If you mean that Memento wouldn't read or use the file, I still don't see how that is an uLE-related problem. And though I'm not familiar with Memento myself, I have a strong hunch that you've simply misread its instructions. For an 'auto-launch' I can't imagine that they would hardcode a name like "BOOT2.ELF", since the "2" implies some way of selecting between different elfs, which is not relevant to an 'auto-launch'.

I can run it fine with the USB plugged in but it's not really ideal, is there a different version that works from MC0:? or can it be hex-edited to run from MC0:?

There is absolutely no problem using uLE from or 'on' mc0:, and no modifications are needed for it. It is the preferred uLE launch device of most uLE users, whether the booting is done by modchip Dev1, MrBrown exploit, or the new FMCB methods. They can all use mc0: without problems, and I'm sure the same can be done with Memento as well, once you do it correctly. But since I have no Memor32 myself, nor the docs for it, I can't help you with that.


Edit:
I just checked out a doc on Memento, and apparently it does NOT implement any aúto-boot of homebrew elfs, as you always have to press one of the gamepad buttons R1,R2,L1,L2 in order to boot any elf. So if you installed the file "mc0:/BOOT/BOOT2.ELF" then you will need to press R2 at power-on or reset, to make Memento boot the selected elf. It will never do it automatically, without button pressing, no matter what filename you use.

Edit2:
I just realized that your problem could also be that Memento might not be compatible with launching the hdld_svr elf. If so the obvious solution is to boot uLE instead, and then use uLE to launch the server. That eliminates the Memento launcher from direct contact with the server, hopefully eliminating all compatibility problems.

Best regards: dlanor

[suloku]

Originally Posted by dlanor

Edit2:
I just realized that your problem could also be that Memento might not be compatible with launching the hdld_svr elf. If so the obvious solution is to boot uLE instead, and then use uLE to launch the server. That eliminates the Memento launcher from direct contact with the server, hopefully eliminating all compatibility problems.

Best regards: dlanor

That might not be the case, as some programs like ps2link doesn't work after booting ule with fmcb (dunno with memento) even with an iop reset.

It's a memory allocation problem, there's a ps2link version out there modified by lucas (sorry, I think this isn't the correct spelling) which allocates itself on another place and works ok with fmcb.

Anyway it's worth trying, if not, you can always run it from an iso image trhough hdloader.

[BobBorakovitz]

apparently my question wasn't clear enough at all. I was trying to provide enough info to get some help and ended up rambling as usual.

I load ulaunch from memento by holding R1 while booting. I can see & run hdld_svr.elf without a problem in ulaunchelf from mass:, but when I copy the file to mc0: within ulaunch it doesn't even show up on the list. When I hook up the memory card to the computer and pull the "boot" folder off hdld_svr.elf is there where it should be!

I was just wondering if anyone has seen this before, as I haven't had any other programs not show up on the file list that are actually there.

suloku: thanks for the suggestion about running it off the hdd i may try that so I don't have to have my usb card plugged in. Also, you're probably right about it being a memory allocation issue.

Please go easy on me, I'm kind of a noob at PS2 but I do research first and only ask for weird stuff like this....or something I'm totally stuck at. Thanks.

[dlanor]

Originally Posted by BobBorakovitz

I load ulaunch from memento by holding R1 while booting. I can see & run hdld_svr.elf without a problem in ulaunchelf from mass:, but when I copy the file to mc0: within ulaunch it doesn't even show up on the list.

Please clarify this one point again:
Are you saying that uLE itself is unable to show the file in "mc0:/BOOT/" in a FileBrowser directory listing, even directly after copying it to that "mc0:/BOOT/" location ?

If so that is a truly unique error which I've never heard of before.

Best regards: dlanor

[suloku]

Strange, it is there but it can't be listed by ule.

Try editing ule's cnf file with the server path and make ule launch it. If the elf runs it means it really is there and ule can't see it, which is really weird.

How long have you had your memor32? Maybe some problem happened when dealing with windows, usb and the card, causing the error (file is written but not listed in the toc, but still windows can see it, maybe because of mementos software that reads the card).

[TnA]

Does uLE maybe have an issue, while trying to access the "corrupted FAT"-FS from Memento?

[dlanor]

@TnA & suloku:
Let's avoid speculating too much about the possible causes until we know for sure whether uLE can show the file in the FileBrowser or not, which he still has not clarified.

Best regards: dlanor

[BobBorakovitz]

hey all, thanks for the replies!

yes, that is exactly the problem, I can copy the file to MC0: and even retreive the file back from it. But it doesn't show up on the ulaunch file list under MC0:
When I copy it to mass: (for example) the file appears no problem and I can run it.

I'm thinking it's a problem with Memor32 for some reason, not really ulaunch due to the fact that it wouldn't boot with Memento's launcher either after renaming it to boot2.elf.

I don't have any time to test this right now, but will test further first thing tomorrow morning. I will try to edit ule's cnf file with the server path and make ule launch it. (thanks for the suggestion, suloku!) I'll also back up my game saves and format the card, just in case it is a TOC error or something.

thanks for your patience guys

[TnA]

Might you able to copy your osdmain.elf to USB-Stick?
Then format and create folders again and paste back to MC?
Does Memento still works then, or not?

[dlanor]

Originally Posted by BobBorakovitz

hey all, thanks for the replies!

yes, that is exactly the problem, I can copy the file to MC0: and even retreive the file back from it. But it doesn't show up on the ulaunch file list under MC0:

I find it hard to understand you.

You say that you can copy it to MC, presumably using uLE, even though uLE never shows it as having arrived at the destination. How then do you know that it was correctly copied ? You also say that you can retrieve it, which is definitely impossible to do in uLE, if the file is not visible.

The only conclusion I can draw from this is that you are not using uLE for the copying, even though you earlier said that you did so (a few posts ago) in the following phrase:
"when I copy the file to mc0: within ulaunch"

That should mean that the copying was made using the uLE FileBrowser, but the new info in your current post disproves that. So I now assume that you used some Memento tool to copy the file to the MC, and if it doesn't show up for other tools like uLE, then the tool you used is definitely bugged.

I suggest that you stop using that non-uLE tool for copying to the MC, and instead use uLE to copy the "mass:/BOOT/" from your USB drive to the MC, where it will then appear as "mc0:/BOOT/". Then you can test that the files in that folder are also visible from the Memento tool. If so, then it proves that it is uLE that does this correctly.

I'm thinking it's a problem with Memor32 for some reason, not really ulaunch

I agree with that, though I was confused earlier when I thought you used uLE for all the copying.

due to the fact that it wouldn't boot with Memento's launcher either after renaming it to boot2.elf.

If you really did what you say here, then that is an entirely different issue.
"boot2.elf" is the wrong name, the correct one being "BOOT2.ELF" (all upper-case).

You must never mix up what character case you are using for files on the PS2, neither in real file operations nor in the bug reports you make about those files. In PS2 file operations filename character case is always significant.

I don't have any time to test this right now, but will test further first thing tomorrow morning. I will try to edit ule's cnf file with the server path and make ule launch it. (thanks for the suggestion, suloku!)

I doubt that it will work. If uLE is unable to find the file in making a directory listing, then it should also be unable to find the same file for launching.

I would rather that you did the experiment I mentioned above. Copy the "BOOT2.ELF" file from "mass:/BOOT/" to "mc0:/BOOT/" using uLE FileBrowser, and check if it is then visible both to uLE (thus also to other homebrew programs) as well as to the Memento tool.

I'll also back up my game saves and format the card, just in case it is a TOC error or something.

That is always a good idea.

Best regards: dlanor

[remax]

dlanor>just don't forget that the Memor32 has an USB output so that you can transfer file from and on the PC using the Memor32 SaveGame Manager.

So he can easily see in SGM if the file has been copied to the MC or not (about "How then do you know that it was correctly copied?").
Besides, i use this software and i have never had any troubles with it. Neither i had any problems like files that don't show up in uLE when i used the memento FW.

But i agree he has to be extremly precise about which method he used each time.

[Testoverride]

I have had a problem with memor32 "corrupting". I would suggest reformatting the memory card with your PS2, flashing with the memento firmware and see how it goes. I had to do this before because my boot folder got corrupted (before FMCB).

I would also buy a regular memory card (not memor32) and put FCMB on it and keep the memor32/memento for an emergency.

[dlanor]

Originally Posted by remax

dlanor>just don't forget that the Memor32 has an USB output so that you can transfer file from and on the PC using the Memor32 SaveGame Manager.

I'm well aware of that, but that is not what he said he was doing.

So he can easily see in SGM if the file has been copied to the MC or not (about "How then do you know that it was correctly copied?").

I don't see how that is relevant when he said that he was doing the copying within uLE. If the program doing the copy can't even see the result of its own work, then we can take it for granted that the copy is not healthy, even if some other tool can see it.

Besides, i use this software and i have never had any troubles with it. Neither i had any problems like files that don't show up in uLE when i used the memento FW.

And since you, having the same stuff he has, don't get the same problem, this points more to some kind of error specific to his setup. I'd guess that either his Memor32 has some hardware/format problem, or his firmware program may be damaged.

But i agree he has to be extremly precise about which method he used each time.

Yes, otherwise any attempt to debug gets hung up on trying to guess what the bug report was really trying to say.

Best regards: dlanor

[Northbear]

Originally Posted by Testoverride

I have had a problem with memor32 "corrupting". I would suggest reformatting the memory card with your PS2, flashing with the memento firmware and see how it goes. I had to do this before because my boot folder got corrupted (before FMCB).

I would also buy a regular memory card (not memor32) and put FCMB on it and keep the memor32/memento for an emergency.

Sorry for the late post but i would recommend what Testoverride suggested. I had trouble with my Memor32 too. Some files will not be correctly loaded if Memento firmware is installed.
Some homebrew seem to fail even if loaded through ULE.


(In Additon: users who wants to use the Action Replay Max series will get problems with Memor32. Everytime you load AR MAX your Memor32 will get corrupted and you will loose all your data. I personally encountered this problem, i lost my high level character from PSU: Ambition of the Illuminus.)

best regards
Northbear

(again sorry for the late post )