----- snip ----- re: problems with recompiled myPS2 binaries
Good. Then I'm very interested in seeing your sources.
Originally Posted by Thumps
But perhaps it would be best (before diving into those sources) for me to test one of your recompiled binaries, to ensure that it does work properly in my PC LAN as well as in yours.
It's the same for me, though I do take every PS2 homebrew I find for a spin or two. But the Samba implementation is something I'd like to port into uLaunchELF as well, which is the main reason I've invested quite some time in experiments with myPS2.
The whole reason I wanted to play with myPS2 in the first place is for samba.
I don't run linux myself, but I did get the original myPS2 Samba implementation to talk to my Windows PCs without problems (one WinXPpro and one Win2K).
I have 2 linux servers that offer several samba mounts. So all my mp3's, photos, personal work is only available to samba or NFS.
----- snip ----- re: modchip boot methods for MC (Dev1) and HDD (Dev2)
As long as you have an HDD and networking, there's little real need for CD-R/DVD-R access, which is the main contribution of a modchip. The only things you'd really need it for are a few emulators that need ROM data files on CD, and a few games that don't work from HDL (so not really dev-related).
Ahh ok, I wondered about that. I don't have a modified ps2 myself. I loaded the exploit onto my memory card using the AR network update method. I have the mod chips sitting on my desk but never installed them because all I wanted was the ability to really play with my ps2 from a developers point of view.
----- snip ----- re: problems I had using +MYPS2 partition for booting myPS2
I see, and I also noted your later post where you verified having found code that checks this identity correctly. That's very good, of course, though I must add that it didn't work for me, but that was quite a while ago, so possibly the code has been changed since then. Once I got it working with two separate partitions, I stopped experimenting with just a single one.
Yeah I was wondering about that myself. It wouldn't be the first time I've taken the hard route to get something done :banghead: . Although in my case it seems to work perfectly, I can access the other mount points using the pfs1..pfs2 and the myPS2 partition is mounted on pfs0 without any issues.
----- snip ----- re: booting other launcher on MC to start myPS2 from HDD
I know, and in the case of myPS2 even packing is no big help, as it requires a whole folder tree besides the binary, and packing that stuff is out of the question as the program needs it unpacked. I never even considered putting this stuff on my own MC (even though it's a 32MB type), so I never used it from any other media than HDD.
I just wanted to have it on my hard drive and not the memory card considering that I didn't use a packer while recompiling myPS2 the binary is over 3 megs and I would like to have game saves on my memory card not just myPS2.
Actually a boot from HDD will often be much slower than a boot from MC, even though HDD is the faster medium. This is because an HDD boot requires loading drivers and scanning the partitions, and if you have a lot of games installed (like most people do ;)) the latter will take a lot of time. So for these cases an MC boot will be much faster.
I can understand the need for Dev2 booting. It would be much nicer to boot directly then stick a CD in the ps2 or having to boot from the memory card.
I'm not sure if you've followed recent discussions in the uLaunchELF forum, but some of the latest changes allow you to program all menu buttons of uLE, so that you can remove access to both FileBrowser and configuration menu from the main menu. This leaves the kids only with those launch key buttons that you have chosen for them (using it as mc1 in your own PS2 to set it up of course).
I have considered doing something similar for my kids ps2, I dont really want to allow them access to the elf launcer.
Doing this will require modifying the CNF file in a text editor, but that should be no problem for you.
That is to be expected. We do the same kind of stuff for uLaunchELF too, since we have no way to update the SVN with some needed changes.
And yes I have support for Samba on my compiled version of myPS2, but it did require me to recompile the entire ps2sdk and supporting irx's.
I haven't done much work on unix systems myself, but I've been around long enough to have a decent grip on most of this stuff too. So it should be enough for me if you explain any changes you made to the setup as supplied by ntba2.
Although having been working with GCC for over 10 years on the unix side of the world, I'm no stranger to makefiles or build environments.
Also, as I mentioned above, a good starting point for me is to simply test one of your recompiled binaries. Just to ensure that its Samba routines can talk to the PCs on my LAN, since that's what failed to work with those I recompiled.
Best regards: dlanor