OpenPS2Loader - It is not saving IP configuation?

[versatileninja]

Here is the situation that might be easily fixed. If I go into OpenPS2Loader, and when I make a change to my computers IP address and go to save configuration, upon reboot of the PS2, it does not retain the value.

It always defaults back to 192.168.0.2, and disregards my previous change. What gives?

[Bootlegninja]

use uLaunchELF to create the needed IPCONFIG.DAT in your SYS-CONF folder on your card. once in uLE, press select and then go into the network config section. there, you can set your IP, subnet, and gateway and have the program save that.

[Scooter]

SMS (simple media system) can also be used to set up your address as well and its a bit more user friendly for new comers..
Ither homebrew works though..

[The_Reaper_CooL]

Hello there!

I have the same problem, and I think you've misunderstood versatileninja.

So when I open up OPL, I always have to set my PC's IP Setting there, because when I want to save the settings, it always says: ERROR WRITING SETTINGS.

So it doesn't make an usbld.cfg or conf_opl.cfg or whatever.

Can we make a file like that manually?
If so, how does it look like (could you post yours for OPL 0.7)?
Where do we need to copy it so that it will load it?

I looked like everywhere to solve this problem, and...
a. Didn't find any solution
b. Noone helped
c. Those who "helped" said that you guys can help me

Thanks in advance (and if I can ask someone to REALLY upload their file with instructions on how to use them, then please do so. It's not like I can hack into your system with that...)

[dlanor]

Hello there!

I have the same problem, and I think you've misunderstood versatileninja.

So when I open up OPL, I always have to set my PC's IP Setting there, because when I want to save the settings, it always says: ERROR WRITING SETTINGS.

So it doesn't make an usbld.cfg or conf_opl.cfg or whatever.

Hmmm, I haven't tried installing from scratch in a long time, and I guess there may be some trouble with it, and one obvious source of trouble is of course the storage location.

You absolutely MUST have an MC connected, with free space on it, and for an original save from scratch it really should be in the first MC slot (so mc0: as seen in uLE FileBrowser).

You should use the uLE FileBrowser to inspect your MC to see if it contains a folder named "OPL" and if not then perhaps it will help if you create that folder manually.

Those things were to help ensure that the main config of OPL has somewhere to 'live', but you also need to do the same for the basic IP config stored in a file named "IPCONFIG.DAT" in the standard MC folder "SYS-CONF" used for a large number of homebrew configs (it is the default location for uLE's config file "LAUNCHELF.CNF", for example.

I you just make sure that the MC in the first slot has a folder named "SYS-CONF", then any of the homebrew programs with ability to choose IP addresses should also be able to save a proper "IPCONFIG.DAT" file(such as uLE in its network config submenu, or OPL in its equivalent menu).

If you create folders on your own to accomplish the above, using the uLE FileBrowser, then they will be shown (falsely) as corrupt if you view them in the Sony browser, which doesn't really matter. But you can fix that in uLE if you wish, by browsing into each such folder and there using the "New Icon" command. You then get to enter two short texts one of which will become the Icon title in the Sony browser and the other becoming graphic text on the Icon image. After this that home-made folder will be shown properly in the Sony browser, so you can stop worrying about claims of corruption.

Can we make a file like that manually?

Making the config files of OPL is far too risky to do by hand.
Just try to make sure that the program has what it needs for a successful save.
(MC inserted in slot 0, free space on it, and SYS-CONF folder existing (maybe OPL folder too))

Best regards: dlanor

[The_Reaper_CooL]

"MC inserted in slot 0"

Yes, it is in slot 0, but I tried it even in slot 1 (so it's in MC0, and then I tried it in MC1)

"free space on it"

It has 7.8 megs free space on it

"SYS-CONF folder existing (maybe OPL folder too)"

Both folders exist, but no matter that EVERYTHING is working (or everything is okay that is said above), but it DOESN'T WORK

Any other solutions? Maybe upload yours (or someone upload theirs)?

EDIT:
I am so desperate that this isn't working, and it's like a very simple thing, and it annoys me.
I even tried to Hex Edit the file, Unpack then Repack it, now I want to recompile it, and while there's a great tutorial, I know I'll fail.

So please someone help me (not with the compiling stuff, the saving stuff)

[dlanor]

"MC inserted in slot 0"

Yes, it is in slot 0, but I tried it even in slot 1 (so it's in MC0, and then I tried it in MC1)

"free space on it"

It has 7.8 megs free space on it

"SYS-CONF folder existing (maybe OPL folder too)"

Both folders exist, but no matter that EVERYTHING is working (or everything is okay that is said above), but it DOESN'T WORK

Hmmm, I just realized that you should be using a public version of OPL, the latest being v0.7, and as far as I can recall, the OPL folder had not yet been implemented back then. Most of us who are into the beta testing use newer versions, and the config methods have changed for these.

But if you are using the public v0.7, then that changes everything.

So that version must still be using the old "usbld.cfg" file, which could be stored in different locations, both in "mc0:/SYS-CONF/" and in "mass:/" the latter being the root of a USB drive. And I have a vague memory of some problem saving correctly when there were multiple versions present. The loading would be from one file, but the saving would be to another, so the new saved settings were never loaded next time. And that does seem to match your symptoms, don't you agree ?

So you should double-check that there is not a usbld.cfg stored either in a second MC or on a connected USB drive, to mess things up for you. Since you probably have a USB drive connected for running games from, that location is my prime suspect. And if you find a usbld.cfg there, try simply copying it to the SYS-CONF folder on your MC, and then delete it from the USB drive. Then you have the kind of setup I have when using v0.7, with usbld.cfg in "mc0:/SYS-CONF/" and none on the USB drive. And that should allow you to save the config normally.

Any other solutions? Maybe upload yours (or someone upload theirs)?

OK, the attached ZIP contains both "IPCONFIG.DAT" and "usbld.cfg" exactly as working on one of my consoles with OPL v0.7. The files are stored in a "SYS-CONF" folder that you can copy to your MC with uLE, so that these two files mingle with any others you may have in your own "SYS-CONF" folder (overwriting if you have any with the same names).

But this setup will definitely not work for you without editing, as I use non-standard LAN addresses, and have network as the defult game list always active. So you will have to edit the setup before it can be used properly.

Best regards: dlanor

[The_Reaper_CooL]

Thanks for the attached file, but here's a VERY odd problem:
I can't copy files into my SYS-CONF folder (it doesn't work from uLE, and it doesn't work with ExecFTP either).

And no, I play games via LAN with PS2SMB stuff, I think it's way faster. And yes, this is a public version that has the saving issues you remember.

Any ideas why I can't paste stuff into SYS-CONF folder? If that can be solved, then I think everything will be solved... wait! Maybe that's why it can't create the stuff because it has problems with it!

So again: Any ideas regarding this? (Using FreeMCBoot 1.8, LaunchElf v4.39)

[dlanor]

Thanks for the attached file, but here's a VERY odd problem:
I can't copy files into my SYS-CONF folder (it doesn't work from uLE, and it doesn't work with ExecFTP either).

You should be more specific. When you say 'can't' does that mean that the "Paste" command is not available or that it somehow fails to work ? And if it fails, then HOW does it fail ? Does it show any prompts, status messages, anything at all ? And exactly what kind of copying did you attempt here ? What was the source device, and how was that prepared ? (We already know that the destination was "mc0:/SYS-CONF/". Right ?)

Also, can you copy stuff at all using uLE, when the destination is some other folder ?
And are you well familiar with how file copying in uLE should work ?

Having read the rest of the post below this point now, I must say it looks very bad, and is probably not fixable by any methods discussed so far, like normal file copying of any kind.

And no, I play games via LAN with PS2SMB stuff, I think it's way faster.

Yes, it is, when it works, but even so one of the default storage locations always remains "mass:/" regardless of where you use your games from, so if a USB drive is connected it can have the effect I spoke of, even if you make no attempt to use it in OPL.

And yes, this is a public version that has the saving issues you remember.

Good. It is always best to know clearly which version we're talking of, but if it is not v0.7, then all bets are off as the others are obsolete.

Any ideas why I can't paste stuff into SYS-CONF folder?

I'm only aware of two cases where that may happen. One is when MC is full and the other is when MC is corrupted, so that space allocation fails even though the indication still shows space available.

If that can be solved, then I think everything will be solved... wait! Maybe that's why it can't create the stuff because it has problems with it!

That is indeed very likely. Any error preventing uLE from pasting files to MC would also prevent other programs from creating new files on MC, as that is essentially the same operation.

So again: Any ideas regarding this? (Using FreeMCBoot 1.8, LaunchElf v4.39)

The programs themselves are not suspect in any way, but their handling sometimes is, especially when it comes to FMCB installs. Some people have reported odd problems in making their installs (mainly caused by odd methods for starting their first homebrew, so as to manage the installs), and sometimes having to abort an install without waiting for the correct completion message. And then they say that their install is working only to suffer weird problems sometime later.

If there were any such problems during your own FMCB installation, then I would suspect that this has caused some corruption, whose effects have gradually grown (through various MC work) until it now blocks write operations even though some space should be free.

But either way, even without any known cause for it, some corruption is still what I suspect to be causing all he write failures, both for uLE and for OPL.

The best thing to do then, is to use the existing MC only for booting uLE and then use it to launch the FMCB installer from a noobie package on USB drive, to make a new FMCB installation on a fresh MC. Using the same old MC as target for a new install could be fatal, if reformat and/or new install fails on it, leaving you with no way to boot homebrew. So use a new card for it.

And after you have a new boot MC working, then backup the data from your old MC and try reformatting it for a new FMCB install (with a new boot MC available this is no longer risky).

Sorry, but there is also significant risk that your old MC may not recover, if the reason for the corruption is more hardware-related than software-related, which remains to be seen.

All I can add at this point is: "Good luck!"
I hope you can repair your setup...

Best regards: dlanor

[The_Reaper_CooL]

Thanks for the info. I can save stuff on my MC card with games, but I can't save into that folder.

So even if I try to paste into it, it says "Paste failed". Like it's write protected or something.

I don't know if I should do this or not, but I'll save all my stuff onto my PC via ExecFTP, or via uLE to USB, then I format my MC and reinstall FMCB. If all else fails, then I need to get a new MC (which is bad :\ )