Project Artemis

[LiquidManZero]

This is a little confusing.

Any copy of 0.5, release or built off the repository code, does not have functional networking... Except for the ps2rd-0.5-nosms.zip build Misfire posted earlier in this thread. Do I understand correctly that the issue here is that the client coding just needs to be updated? ...if that's the case, then how exactly did you guys discover that the new networking code does faster transfers?

And for that matter, why was the incompatibility never mentioned anywhere?

[jimmikaelkael]

I don't know of which module your talking about...

But if it's of the last "net" module I wrote:
FYI, it will allow to replace SMAP/SMSTCPIP, taking only 12Kb compiled. It has been tested on both FAT/Slim and works as it should.
However, communication with old clients is broken for now, the time "adb" module is being developed.

[LiquidManZero]

It's starting to look quite a bit like 0.5+ only works correctly not on a fat ps2, with those new fancier networking modules. I wonder why...

[Agent Moose]

I've got a question. Why does the game (Ratchet: Deadlocked) freeze when I try to connect online? No matter which version I try, it freezes.

[Ishtar]

Yes I have the problem with every game I have tried...

I tried the ps2rd-0.5-nosms version and it works fine on my network! no problems with ip/gateway config

[misfire]

Ishtar, I attached a build of ps2rd 0.5 with the standard network modules. Try if it works for you. Note that game compatibility isn't as good as with the SMS modules.

[misfire]

Actually, MySifRebootIop() is called on every IOP reset, not only when running the second ELF from a game.

I'm using a crossover cable myself. If the gateway isn't set correctly in the new SMAP driver, we definitely need to fix it. Do you have this problem with every game?

[Ishtar]

I have been looking at the code and trying to hardcode the ipconfig just to get it to work with my network but I am getting more confused the more I test...

so far I know it loads the correct settings from ee/debugger/debugger.c in MySifRebootIop

I tried to modify the smap driver /iop/smsmap/main.c _start to return hard coded ip values different from the config and again it only works when MySifRebootIop gets called (booting second elf)... I then tried to hard code SMapInit with the same results... the hard coding works it overides the config but only when MySifRebootIop gets called

where/how does it first load the smap driver or is it using some other smap driver when first loaded? or am I missing something because everything I touch only seems to work when MySifRebootIop gets called (loading a second elf) its annoying me cause when I set everything back to normal and use defaults it works with a crossover cable I can change the ip in the config and it works but as soon as I try and change the gateway it fails until MySifRebootIop gets called...

[Agent Moose]

I always had used the default one, but the game I try it on is a multi-elf, and it doesn't want to stay connected in ps2cc past the title screen.

[Ishtar]

I didn't add a space I moved a space... but thats not whats causing my problem

I don't know why but on my ps2 it only sets the gateway address from the config if it loads a second elf meaning I am stuck using a crossover cable that works all the time with default ip settings or if its a multi elf game after the second elf loads it works with my network setup...

Is anyone else having trouble like this?
Does it work for anyone else with a diffrent gateway address from the default one?

[Agent Moose]

He just added a space in it.

I don't think one space inside of parentheses would fix it.

[misfire]

"GW.addr = inet_addr (ppcArgV[ 3 ] );" should be "GW.addr = inet_addr( ppcArgV[ 3 ] );"

Ehm, those lines are identical. I don't see the fix.

[Ishtar]

I have tried both ps2cc and ntpbclient the problem seems to be more network related somewhere I get no ping reply I don't even see any arp response on the network for the ip in the config that I am trying to connect too.

[edit]
I was able to get it connectiong I used a crossover cable into a laptop with all default settings I can get it to change ip but its not using the gateway address from the config or something goes very wrong when I change the gateway address so I am stuck with 192.168.0.1 and thats why it fails on my network!

Anyway thanks for your help if I get a chance I will look the code over I am sure it won't be too hard to fix.

[edit2]
I had a look at the code and found the problem simple typo in iop/smsmap/main.c


int _start ( int iArgC,char** ppcArgV ) {

IPAddr IP;
IPAddr NM;
IPAddr GW;

if ( iArgC >= 4 ) {

IP.addr = inet_addr( ppcArgV[ 1 ] );
NM.addr = inet_addr( ppcArgV[ 2 ] );
GW.addr = inet_addr (ppcArgV[ 3 ] );

} else {

...


"GW.addr = inet_addr (ppcArgV[ 3 ] );" should be "GW.addr = inet_addr( ppcArgV[ 3 ] );"

[edit3]
Bleh I am still having issues after that it seems to only be setting the right ip config if a second elf is loaded thats a bit of a problem for single elf games so I guess I am stuck using a crossover cable for now at least that works.

[misfire]

Hm, my first thought was that the changes we made to the network modules and your Ethernet adapter don't play well together. But now you're saying that Open PS2 Loader works for you. That's strange cause it uses almost the same drivers...

Can you ping the PS2 in-game? And are you using ps2cc? Please try it out with ntpbclient too.

[Ishtar]

I would also like to know...

I have tried everything I can think of its either not binding the ip/netmask in the config or its got some issues with my hardware...

I assume v0.5 works for others so then I am thinking its a bug with ip config somewhere thats just effecting me or a hardware issue but thats unlikly since sms and open ps2 loader both work on the same setup and they seem to use the same or very similar smap drivers...

I just got a ps2 dev environment setup again but I don't have time to do much just yet
I will let you know if I figiure out whats wrong but would appreciate any help as I don't have much spare time atm...