The above video goes away if you are a member and logged in, so log in now!
My question is pretty simple,
How does host: work?
Do I hook my PS2 up to a PC with an ethernet cable? Does it have to be a cross-over cable? Can I plug it into a router?
Basically right now, all I know is that my slim PS2 has an ethernet port, I have a PC and a router, and both uLaunchELF and SMS let you browse to host:
So, if anyone can explain to me how host: works and what I have to do to get it working, please let me know! Thanks
cheers, i'll give it a look
Originally Posted by djflexmaster79
Ok so, I've got my PS2's IP set up correctly, it's plugged in to my router, so is my PC, I can ping the PS2 and I get a response, but when I start the net service in uLE or SMS and then run RadHostClient here, I drop files into RadHostClient and nothing shows up under host: on the PS2. RadHostClient even has a green icon to show that it is connected to my PS2. Anybody got any ideas?
P.S. I'm using RadHostClient because PS2ClientLoader doesn't like my 64-bit Vista.
I think you may not be doing this properly.
Originally Posted by quid
This is done as follows:
1: On the PC, launch RadHostClient (or PS2ClientLoader)
2: On the PS2, use uLE FileBrowser to browse "host:/" (showing only an empty folder)
3: (automatic) as a result of step 2 uLE opens the HOST server
4: (automatic) as a result of step 3 RadHostClient opens a HOST server-client session
5: On the PS2, use uLE FileBrowser to again browse "host:/" (showing PC shares)
Note that the browsing in step 2 above is only used to open the host: server, and the intention is that this should be detected by RadHostClient (or PS2ClientLoader) as the server replies to its pings, at which that client program will make its HOST connection attempt.
A common mistake is to use the MISC/PS2Net command, which is intended for FTP protocol and not at all for HOST. Doing so will cause the PS2 to start replying to any incoming pings even though the HOST server is not open, and that will cause the resulting HOST connection attempt of RadHostClient (or PS2ClientLoader) to fail. Sometimes (but not always) it helps to then terminate the client program, browse uLE to "host:/", and then restart the client program on the PC again. But it is obviously better to do it right from the start, as described in the 5-step list above.
Once you have established communication this way once in a uLE session you will not need to do so again, even if you have left the FileBrowser. For the rest of the session the host: device will work like the native PS2 devices, accessible by normal browsing as easily as any of them.
With SMS the HOST protocol is used differently in that the HOST server is opened independently of the browsing, so that no 'extra' browsing is needed in order to get the HOST contents displayed. In uLE on the other hand the loading of optional device drivers is always controlled by the user's attempts to access them (eg: if you never browse to hdd0: then no time is wasted on loading HDD drivers etc) and that is why it works the way it does in uLE.
Best regards: dlanor