Ok, noob uLE question

[Racer]

I have it installed on my memory card and that is all working. I setup my network config. I just use the default of 192.168.0.10 which the address is available on my network.

When uLE starts up, it does not activate the network. My router light does not come on. I know the network is working, I can play online games.

Am I missing something? I checked the docs and everything but did not find anything that I needed to do. It says a FTP server runs quietly in the background.

Thanks

[dlanor]

I have it installed on my memory card and that is all working. I setup my network config. I just use the default of 192.168.0.10 which the address is available on my network.

When uLE starts up, it does not activate the network. My router light does not come on. I know the network is working, I can play online games.

This is normal. Without user action uLE will not initiate any network traffic at all, nor will it start any of its internal servers until a specific request is made to do that. So without such commands from the user the network drivers are not even started, though they are embedded in the program and ready to be started at user request.

One reason for these methods is that uLE may be used to launch software that is incompatible with some of the device drivers which uLE may also use. So if we loaded every device driver that uLE is able to use, by default just because uLE is booted, then uLE would lose the ability to run lots of software due to compatibility problems.

Because of this we defer loading most device drivers until the user indicates the need for a particular driver, either by a specific command, or simply navigating the FileBrowser to a device whose driver was not already loaded. That will then cause the needed driver to be loaded, after which it will remain resident for the rest of the session.

Am I missing something? I checked the docs and everything but did not find anything that I needed to do. It says a FTP server runs quietly in the background.

That last is only true *AFTER* that server has been started, which is optional to do. And the same goes for the other built-in server for the HOST protocol (a MUCH faster way of transferring files to/from a PC).

The FTP server can be started (like many built-in programs) by navigating the FileBrowser to the pseudo-device MISC/ and choosing the correct program link from that directory. For the FTP server that would be "MISC/PS2Net". Doing so will launch the FTP server after loading all drivers it may need. The normal sequence of events for this is thus:

1: On PS2, Navigate to "MISC/" and launch the subprogram "PS2Net"
2: On PC, start your FTP client and log in to the uLE FTP server


The HOST server is started simply by navigating the FileBrowser to the "host:" device. The first time in a session that you do this it will start the server, along with all drivers it needs, but there will be no resulting file list. That can only be produced when browsing to host: *after* a client program on the PC has contacted the server, so the proper sequence of events for this is as follows:

1: On PS2, Navigate FileBrowser to host:, and then 'back' to the root
2: On PC, launch a HOST client (eg: RadHostClient.exe or ps2client.exe)
3: On PS2, Navigate FileBrowser to host:, displaying the shared PC content

The main advantage of the HOST protocol is that the speed is appx 1450 kByte/s, as compared to the appx 200-300 you may get in FTP. Another thing making it more convenient than FTP is that you can browse normally between different PS2 HDD partitions without the need for 'mount' or 'unmount' commands that you'd use in FTP.

The downside (as some see it) is that you have to do all browing from the PS2 side. Personally I prefer that when copying stuff to the PS2, but I know many people differ in this.

Best regards: dlanor

[Racer]

Hey thanks for the quick reply.