PS2 Dev News

[pixie2004]

@Pixel
Sorry, I assumed version 1.24b was newer than 1.24. Many people release software with version numbering like 3.9b or 3.9g with the 'g' signifying the 7th release of 3.9.

So, this aside... are you running yours from MC or HDD?

[Pixel]

I am running this using dms3's devolution mode, from MC.

[E P]

@E P
"Essentially the same" doesn't mean much when talking about a binary file; it's binary, they're either the same or they're not! The fact that one was compressed and other wasn't, is enough for there to be some difference in their execution, and I'm sure there is more than just the version string different, why else would there be a new version?

Well what did you want me to say that your ps2-unpacker sucks? No in all seriousness I know that your unpacker doesn't ever get you back the original binary elf. Your unpacker sometimes adds or takes away bytes at the end of the file and changes some near or within the ELF header. So I did some speculation on your unpacked ps2link binary. With Hex Workshop as my witness, I came to the conclusion that they are very close after unpacking your version and doing a compare with G's.

Sure lets play devils advocate and say they're totally different versions but that doesn't explain the fact that yours works for the most part as is. When uncompressed, it doesn't work just like G's only a black screen. The thing I don't get is I can't create a compressed ps2link-all-in-one with ps2packer that actually works unless you created your version with some other version of ps2packer. hum, funny indeed.

Oh and I use the exploit to run launchELF as my BOOT.ELF on an unmodified v4, System ROM Version 5.0 12/28/00 A. I tried running the all-in-one from memory card in BWLINUX directory through launchELF.

[Pixel]

Again, this is no new version. In 1.24b, the b standed for beta. We finally though the thing was stable enough, and renamed it to 1.24 when releasing it. So, again, between "my" previous 1.24b I linked there before, and the actual 1.24, there's strictly no code difference.

And, there may be troubles with the packer as well. I haven't done enough test to proove it 100% working. If you have troubles with the packed version, just use the original unpacked one.

[agentboolen]

@E P
"Essentially the same" doesn't mean much when talking about a binary file; it's binary, they're either the same or they're not! The fact that one was compressed and other wasn't, is enough for there to be some difference in their execution, and I'm sure there is more than just the version string different, why else would there be a new version?

Well what did you want me to say that your ps2-unpacker sucks? No in all seriousness I know that your unpacker doesn't ever get you back the original binary elf. Your unpacker sometimes adds or takes away bytes at the end of the file and changes some near or within the ELF header. So I did some speculation on your unpacked ps2link binary. With Hex Workshop as my witness, I came to the conclusion that they are very close after unpacking your version and doing a compare with G's.

Sure lets play devils advocate and say they're totally different versions but that doesn't explain the fact that yours works for the most part as is. When uncompressed, it doesn't work just like G's only a black screen. The thing I don't get is I can't create a compressed ps2link-all-in-one with ps2packer that actually works unless you created your version with some other version of ps2packer. hum, funny indeed.

Oh and I use the exploit to run launchELF as my BOOT.ELF on an unmodified v4, System ROM Version 5.0 12/28/00 A. I tried running the all-in-one from memory card in BWLINUX directory through launchELF.

I really can't understand why you would go to so much trouble to inspect those two binaries and complain about them if you could have simply taken the time to compile it yourself just like G said?

Some people that post here just don't make any sense!

[E P]

Whoa, agentboolen I'm not complaining I use the official ps2dev released binaries they work just fine. I was just interested in figuring out what the difference was with all-in-one not working. Call me a beta tester/ bug finder if you like but complaining come on I got better things to do with my time.

Maybe I really should compile it myself but I'm pretty sure I'll get the same result. I guess I need to get a dev environment setup but I've been too busy developing java programs anyway.

Believe me though when I really do complain you'll know it.

[pixie2004]

I've loaded the official ps2dev release of 1.24 on my MC and my HDD, and these are my findings:

loading mc0:/PS2LINK/PS2LINK.ELF:

Welcome to ps2link v1.24
Booting from mc dir (mc0:/PS2LINK/PS2LINK.ELF)
Initializing...
Could not find IPCONFIG.DAT, using defaults
Net config: 192.168.0.10 255.255.255.0 192.168.0.1
Failed to open extra conf file
Ready

loading hdd0:/__boot/PS2LINK/PS2LINK.ELF:

Welcome to ps2link v1.24
Booting from host (host:PS2LINK.ELF)
Could not find IPCONFIG.DAT, using defaults
Net config: 192.168.0.10 255.255.255.0 192.168.0.1
Initializing...

After about 10 seconds there's a brief flash of what looks like a register or stack dump and then a black screen.

Notes:
My IPCONFIG.DAT is in mc0:/SYS-CONF/, but the defaults are fine anyway.
I'm not sure if storing files on hdd0:/__boot is good or bad, but all the other programs I have stored there work fine.
I am using the exploit to load LaunchElf 3.11.
I find it interesting that the "Initializing..." message appears at a different point in the sequence depending on whether you load from MC or HDD.

@Pixel
I can probably capture the dump screen for you, I can just video capture the output of my PS2, let me know if you think its necessary.

[Pixel]

Okay, I think I understand.

ps2link can NOT load from hdd directly. I just think about it right now. Because the drivers (dev9.irx) will conflict. Since it is thinking it is booting from host, it doesn't behave the same way exactly. Blame fakehost on this one So, no need for the screen with the exception error, I think I solved that point. Have to tweak ps2link so it could natively load from hdd.

For the first try, it "seems" it is working, right ? Isn't your IP address pinging ? Is your network correctly set up ? If the answers are yes, please check the following:

-) when ps2link is booting, is there a delay between the "Initializing..." message and the "Could not find..." ? Like 1 second.
-) when ps2link says 'ready', is the ethernet link up ? that is, look behind your PS2, the smap adapter, and check the lights behind. Is the green one on ?

[pixie2004]

@Pixel
The first try, the official ps2dev release of 1.24 on my MC, works fine, I can execute .elf's from my PC using InLink 1.3.7. (Sorry, I should have made that clear)

Just to be doubly sure I loaded G's all-in-one 1.24 (not b) onto my MC and my HDD into a directories called PS2LINKA.

loading mc0:/PS2LINKA/PS2LINK.ELF:

Black screen and after about 1 second the analog led on my dual shock controller goes out.

loading hdd0:/__boot/PS2LINKA/PS2LINK.ELF:

Black screen and after about 1 second the analog led on my dual shock controller goes out.

In conclusion, there seems to be a problem running the official ps2dev 1.24 from HDD, and I cannot run G's single-file 1.24 from my MC or my HDD.
Could this be a conflict with LaunchElf 3.11, or maybe with my PAL SCPH-30004 and Messiah chip?

Lastly, it would be really nice if PS2LINK could check for IPCONFIG.DAT in mc0:/SYS-CONF/.