After getting off my arse lately and actually coding, I decided to finish off the improvements I had been making to ps2client. The main difference is the use of threads for the networking code. It should be snappier than ever before.
The other big difference is the dropping of ps2netfs support. That's not to say ps2netfs is bad - in fact I like it a lot. It just doesn't fit into what ps2client was supposed to be and was always kinda wedged-in. It really needs a good gui client written for it and unfortunately that isn't my specialty.
So anyway, the changes are in cvs. If anyone can grab it and give it a try, I'd appreciate it.
Impending ps2client v3.0.0 release.
-
Guest
Re: Impending ps2client v3.0.0 release.
Hah! Thats a good one! :)ooPo wrote:After getting off my arse lately and actually coding, I decided to finish off the improvements I had been making to ps2client. The main difference is the use of threads for the networking code. It should be snappier than ever before.
I totally disagree with removing ps2netfs and that it doesnt fit (even
if you decide to remove it, atleast make a branch/tag of the code in the cvs
so you can grab 2.0 without any trouble)
I used it all the time for data syncing to the hdd when i coded the demo.
I had a set of script files i just ran to sync the data over to the hdd.
If you want gui you can just load ps2ftpd instead and use your fav ftpclient.
.emoon
if you decide to remove it, atleast make a branch/tag of the code in the cvs
so you can grab 2.0 without any trouble)
I used it all the time for data syncing to the hdd when i coded the demo.
I had a set of script files i just ran to sync the data over to the hdd.
If you want gui you can just load ps2ftpd instead and use your fav ftpclient.
.emoon
emoon: maybe you missed it or he changed his mind, but earlier oopo mentioned removing ps2netfs support and giving it it's own program... which makes sense to me.
I do agree... I don't want to see only gui clients, though having a gui client would be spiffy.
I do agree... I don't want to see only gui clients, though having a gui client would be spiffy.
Shoot Pixels Not People!
Makeshift Development
Makeshift Development
I've been always annoyed with a small "problem". I know there's quite nothing to do about it, but, well :)
It happens me all the time to let a ps2client running into the background, then I switch the console off and on 'coz my software hung it up, and then I run another ps2client. The problem is it can't open the tty since the udp port is still occupied by the previous one. Well, what would be good is that instead of only warning that it can't open the udp port for that, it should generates an error and exit. Or maybe offering that as an option.
It happens me all the time to let a ps2client running into the background, then I switch the console off and on 'coz my software hung it up, and then I run another ps2client. The problem is it can't open the tty since the udp port is still occupied by the previous one. Well, what would be good is that instead of only warning that it can't open the udp port for that, it should generates an error and exit. Or maybe offering that as an option.
pixel: A mischievous magical spirit associated with screen displays. The computer industry has frequently borrowed from mythology. Witness the sprites in computer graphics, the demons in artificial intelligence and the trolls in the marketing department.
oog, argh, gragh!
emoon: Yes, v2.0 has been tagged in cvs since its release. I use ps2netfs a bit myself for putting things on memorycards. Good to finally hear I'm not the only person using it. :) Like I said, though... I'll probably whip up a separate client for it soon enough.
pixel: instead of exiting the program, it should just keep going if it can't open that port? hmm...
lukasz: bugs! help missing! they'll be fixed! :)
At home I use 192.168.100.10, so when I chopped it off for the commit I left the wrong number there. Oops. :)
emoon: Yes, v2.0 has been tagged in cvs since its release. I use ps2netfs a bit myself for putting things on memorycards. Good to finally hear I'm not the only person using it. :) Like I said, though... I'll probably whip up a separate client for it soon enough.
pixel: instead of exiting the program, it should just keep going if it can't open that port? hmm...
lukasz: bugs! help missing! they'll be fixed! :)
At home I use 192.168.100.10, so when I chopped it off for the commit I left the wrong number there. Oops. :)
Ive compiled the updated version and it works much better than the 2.0.0 version, it now captures this
Earlier when I reset, I sometimes wouldn't be able to execute directly afterwards because the PS2 wasn't "ready" yet and I would never get the IOP cmd thread started etc. output
What I am trying to say is, nice job ooPo :)
Code: Select all
ps2client reset
ps2client -t 3 execee host:playsample.elf
tty mounted
host: mounted
IOP cmd thread started
Naplink thread started
loadmodule: id 29, ret 0
open name mc0:conf.dat flag 1 data 41378
open fd = -19
EE: Cmd thread
What I am trying to say is, nice job ooPo :)
I finally got around to start with ps2netfs support. It is in cvs now and untested because my ps2 was hooked up to the hdtv for some Tekken 5 action on the weekend and I'm too lazy to move it. :)
The ps2client project now contains two clients: ps2client and fsclient. Commands (copyto/etc) should work like they did before.
Feel free to test and post what I've broken.
If not, I'll do it myself tomorrow anyway.
The ps2client project now contains two clients: ps2client and fsclient. Commands (copyto/etc) should work like they did before.
Feel free to test and post what I've broken.
If not, I'll do it myself tomorrow anyway.