[Solved] HDLD_SRV problem

[izdubar]

Ok ... so lately I wanted to test things on my HDD, and needed to add games.

As I don't need to add a lot of them, I don't want to remove the HDD from the PS2, and I used HDLD_SRV.

But the problem is that it doesn't work with my IPCONFIG.DAT !

My IPCONFIG.DAT is in mc0:SYS-CONF folder, I run hdld_srv 0.8.5 either from SYS-CONF, or BOOT folder, using uLE or PS2Link.

I always get the error "invalid configuration file format" and then hdld_srv use the default IP/MASK/GATEWAY which are not correct for my network.

Now I have checked many times the content of IPCONFIG.DAT, using uLE/Texteditor, and everything is ok. In fact every other program does work with this eaxct same file:

• PS2Link, ok
• OPL SMB, ok
• uLE PS2Net, ok

So what is the problem with this damn tool ?!

Does anyone have the sources of this program ? I've searched on ps2dev without luck ...

[offthewall]

I had a similar problem awhile ago, something was conflicting with it in the SYS-CONF folder. I copied the IPCONFIG.DAT to B*DATA-SYSTEM and HDLD_SVR was able to read my config fine.

[izdubar]

Desperating ...

Completely bugged tool ...

I moved the IPCONFIG.DAT from my SYS-CONF to BEDATA-SYSTEM folder.

Now it doesn't find it at all and tell me:

Use one of the following location to set IP address:
mc0:/BIDATA...
mc0:/BADATA...
mc0:/BEDATA-SYTEM/IPCONFIG.DAT <<< no really ?
mc0:/SYS-CONF/IPCONFIG.DAT

:-(

[redbeard]

I had a similar issue recently. Eventually I noticed a space (or another invisible) character at the end of the IP Address line. Removing that with ule text editor cured the problem.

[offthewall]

I moved the IPCONFIG.DAT from my SYS-CONF to BEDATA-SYSTEM folder.

Now it doesn't find it at all

That's weird...it should work. If what redbeard mentioned doesn't solve it, then I guess you could always just open the .elf with a hex editor, search for "192" and enter the info from your cfg.

[izdubar]

I had a similar issue recently. Eventually I noticed a space (or another invisible) character at the end of the IP Address line. Removing that with ule text editor cured the problem.

Ok that was it.

In fact it was a "00" character (another disturbing thing, is that uLE doesn't display this char, there was only CR/LF/EOF). And even if it shouldn't have disturb hdl_dump ... it does ...

However, if I can't fix hdl_dump without the sources ... I can fix the tool who created this "bugged" IPCONFIG.DAT ... as it is a bug in OPL

At least the problem won't appear anymore

Thanks for the help.

PS: @offthewall, I tried first to edit the binary ELF, but as it is packed you don't find anything in it

[dlanor]

Ok that was it.

In fact it was a "00" character (another disturbing thing, is that uLE doesn't display this char, there was only CR/LF/EOF). And even if it shouldn't have disturb hdl_dump ... it does ...

One problem with the 0x00 character is that it is not only the ascii NUL character (not intended for display), but it is also the standard string terminator for all C-related programming. So regardless of what other ascii codes a string contains, standard string functions in C code normally considers the string ended wherever there is an ascii NUL...

So if a line of text contains items separated by a NUL, then the items after it will most likely be lost.

However, if I can't fix hdl_dump without the sources ... I can fix the tool who created this "bugged" IPCONFIG.DAT ... as it is a bug in OPL

If you are sure that OPL created that config file, then yes.
But there are many different tools that use, and can create, that file.

Any one of them might be responsible for saving it with incorrect separator/terminator use.
But since OPL is the newcomer among them, I suppose we must suspect it first...

Best regards: dlanor

[izdubar]

If you are sure that OPL created that config file, then yes.
But there are many different tools that use, and can create, that file.

I'm more than sure, and especially the fact that the character was a "\0" put me on the track, I just had to verify the method in OPL which confirmed me the bug.

[dlanor]

I'm more than sure, and especially the fact that the character was a "\0" put me on the track, I just had to verify the method in OPL which confirmed me the bug.

Good. Then we'll be rid of it by the next beta, I assume.

Hmmm. I wonder if this could explain some of the problems some homebrew noobies have had with using OPL over LAN. Judging by the posts of some of them, this probably was their first efforts to use LAN with homebrews, so they are likely to have used OPL for the creation of that config file...

Best regards: dlanor

[izdubar]

Concerning the new user, I don't think it have an impact, except on HDLD_SRV. OPL, uLE/PS2Net, PS2Link have all succeeded to read and use the bugged IPCONFIG.DAT.

But of course if the trouble you speak/remember about was using HDLD to transfer games, then yes here it is clearly a no go.

Good. Then we'll be rid of it by the next beta, I assume.

Yes, I will give the info to Volca, as I don't have access to the official branch. he maybe even already saw the fix.