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

[dlanor]

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]

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]

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 )