ps2link on ps2link

mharris · Post by **mharris** » Tue Feb 10, 2004 9:32 am

Now that there's a new version of ps2link out, I'd like to give it a try. Is it possible to execute the new version of ps2link via my existing ps2link (on the memory card -- independence exploit) ?

Are any pksh changes needed to take advantage of the new features?

thx

(sorry if this is OT, this forum seemed like the closest match)

Post by **TyRaNiD** » Wed Feb 11, 2004 4:26 am

If you go to the Makefile in the ee dir there is a setting called LOADHIGH. Set this to 1 and rebuild. That should allow you to run ps2link over ps2link.

Note: I have not tried this personally, just from what I have heard. If it doesnt work it isn't my fault ;)

You will need a upgraded version of pksh to run things like host directory listing though it is apparently abit of a hack atm and might not work on anything other than linux. You can use the latest version of pksh with the older ps2link though so there is no reason not to upgrade I guess.

Post by **ooPo** » Wed Feb 11, 2004 5:24 am

Take a look at ps2client, the latest version has support for the new directory functions and should compile fine under any unix-like environment.

Post by **blackdroid** » Wed Feb 11, 2004 8:01 am

yes ooPo it compiles but it doesnt work, casting int fd to DIR is a hack, and does not work on all unixes. same goes for pksh it compiles but opendir, closedir, readdir does not work on all unixes as it is atm, I intend to fix this ASAP but im swamped with $$$ work atm :(

For the other new features like dumpmem, dumpreg, start/stop vu, execgs you probably will need pksh for the moment, but im sure inlink and ps2client will incorporate that functionality.

adresd · Post by **adresd** » Wed Feb 11, 2004 8:50 am

I can verify that the LOADHIGH option does work as advertised.
I used it extensively in testing.

You can also have a highload version and load the low (normal) one with it, it works both ways.

Post by **ooPo** » Wed Feb 11, 2004 8:56 am

Hacks aside, it ran fine on cygwin, linux, and osx when I tested it. Which unixes won't it work on?

I can't fix a problem I can't see, man! Feed me! :)

Post by **blackdroid** » Wed Feb 11, 2004 9:07 am

adresd wrote:I can verify that the LOADHIGH option does work as advertised.
I used it extensively in testing.

You can also have a highload version and load the low (normal) one with it, it works both ways.

but fresh from cvs it doesnt matter if you do LOADHIGH or not, ps2link will load from mc atm because of the argc != 1 check.

nevermind.. my old pksh that fucked it up.

Post by **blackdroid** » Wed Feb 11, 2004 9:13 am

ooPo wrote:Hacks aside, it ran fine on cygwin, linux, and osx when I tested it. Which unixes won't it work on?

I can't fix a problem I can't see, man! Feed me! :)

it doesnt work properly on my cygwin machine though ( returns nothing ).. anyway the DIR struct on FreeBSD doesnt get initialized correctly with just a cast. The better thing to do would probably to have a DIR array and do a fd = dirfd(DIRptr), send that fd, and compare the fd in readdir, closedir to what we have in the DIR array to get the correct initialized struct for that given fd.

Post by **blackdroid** » Wed Feb 11, 2004 10:16 am

ok I take everything about (int)(DIR *) back.
I screwed up. ( I hereby grant #ps2dev to use that against me at any time :)

Post by **ooPo** » Wed Feb 11, 2004 10:41 am

Uhhh, ok. Does this mean you're still getting nothing from ps2client?

Post by **ooPo** » Wed Feb 11, 2004 10:42 am

Oh, while you're around... can you give a quick comment on those new commands you added, what they do, and are they in ps2link cvs yet?

Post by **blackdroid** » Wed Feb 11, 2004 10:54 am

ooPo wrote:Uhhh, ok. Does this mean you're still getting nothing from ps2client?

I should try again on my win machine, which I dont have where im at.

As for the new commands, yes they are in cvs both for ps2link side and pksh.

execgs = basically a one dmapacket size buf that will get sent to gif via dma channel 2, takes a file and size as argument
start/stop vu = takes 0 or 1 as argument to start/stop vu0 or vu1.
dumpmem = dumps mem, takes file, start and size as arguments
dumpreg = dumps registers, argument is a file and an integer wich describes what type of registers you want dumped or all, basically it is for dumping dma, gif, vif etc registers.

the foremost reason for me adding these commands is for wxVU,
although dumpmem and dumpreg can be quite handy at times when debugging in general.

adresd · Post by **adresd** » Thu Feb 12, 2004 10:33 am

wow, sounds like you are not having fun at all.

args that stop working, then start working again

first its a hack then its not.. lol :)

hope the confusion clears soon :)

btw, ps2client works here on cygwin, but does have some log issues, which oopo is aware of.