Yesyesyes... you do browse the host from PS2... !!!Originally Posted by zabolyx
That was a major reason for my adding 'host:' to uLaunchELF.
Most people are confused by the '3-point startup' needed to get host: operational. This is mainly because it relies on a 'server' program on the PC, though that program was designed as a 'client' program for PS2Link on the PS2. This makes it necessary to use a peculiar procedure to browse host:
1: In LaunchELF, attempt to browse to host: (times out to empty dir)
-- This sets up the PS2 end of the host interface, similar to PS2Link launch
2: On PC, start "ps2client.exe -h YOUR_PS2_IP_NUMBER listen"
-- Use either a dos command, batch file, or an edited shortcut for this
-- It sets up "ps2client" to run in 'listen' mode, as a host: server
3: In LaunchELF, make a new attempt to browse to host:
-- This will now establish contact and show the host: root directory.
-- Exactly what that means is described further below in this text...
The good thing about this method is that after connecting successfully once, you only need to repeat steps 2 and 3 above for future connections (of the same PS2 uLaunchELF session), and each new connection can have an entirely different host: root directory. It's all up to you, as described below.
If that had been the extent of it, there would have been no point at all in adding it to uLaunchELF...if I am correct that uses a script file for playing roms with Emus that use inlink....
The 'script' file you mention is simply a text file named "elflist.txt", defining extra files and paths that should be made visible in host:. It would be more correct to call it a 'link' file, since it contains links but no script commands.
If that file is present then each line in it defines a symbolic link to a file or folder anywhere in the PC filesystem. Regardless of where they are really stored (no need to be on the same drive) they will be presented as part of the content of the host: root directory, as seen in uLaunchELF on the PS2. This restricts access only to named files and folders, plus any content of such folders (including subfolders, recursively). But if you so wish it, this also allows access to the entire machine, as you are allowed to specify just a drive (like "C:") to allow access to the entire contents of its root directory. So you can do this for all drives you have, making each available as a pseudo-folder of host:.
If the link file does not exist, then the work directory of the server on the PC (usually "ps2client.exe") will be used as root directory for host:. This will allow access only to that folder, plus any content of it (including subfolders recursively). This limits access to a single PC drive, but can still be convenient to use, since ps2client can be made to use any 'work directory', not just the one where the program itself resides. (I use drag-drop to batch files, to control this myself.)
With FTP, that's one way to do it, though uLaunchELF also supports the same mount and unmount commands as used with ExecFTPs and the PS2OS FTP server. (All three programs use ps2ftpd.irx)you use the filebrowser to mount the HDD partition that you want to view on the PC
If you have the PS2 and PC on the same desk, then it's most convenient to just pick up the PS2 controller and browse to the partition you want in PFS for FTP. But if the PS2 and PC are separated by some distance, you'll find it more convenient to use the FTP 'site' commands instead.
Best regards: dlanor