Quote:
For nethostfs support, it's a bit more complicated as it involves networking configurations. After unzipping the nethostfs archive to your PC (both Windows & Linux are supported), you can launch it as follows:
nethostfs usage:
Usage: nethostfs [options] rootdir
rootdir: The defined dir will be used as root dir for PSP. Use /cygdrive if you want the PSP to see all drives in your PC.
Options:
-p port : TCP port number
-l login_password : Password for client PSP to login
-h : Print this help messages
Example
nethostfs -p 7513 -l mypass /cygdrive
This will allow your PSP to access all drives in your PC. You'll also need to configure the following under iR Configurator.
- XMB Network for NetHost: Choose the network entry which you've defined under XMB Infrastructure Network Settings.
- NetHost IP/Name (AP): This is the IP address of Domain Name of your PC to provide nethostfs access.
- NetHost IP (Adhoc): This is only used for Adhoc WiFi PC connection as discussed in the next paragraph.
- NetHost Port: The TCP port to be used, such as 7513 in the example above.
- NetHost Password: The password to access nethostfs service on the PC, example mypass.[/code]
Adhoc WiFi PC Configuration:
----------------------------
The PSP firmware 1.5 does not allow your PSP to connect to a PC via Adhoc WiFi, the Adhoc WiFi connection only supports PSP to PSP communication. To connect your PSP to your PC, you'll normally need an Infrastructure Access Point. However, iR Shell utilizes a little trick by using the network drivers from firmware 1.0 to allow you to connect your PSP to your PC via Adhoc WiFi.
To use adhoc PC connection, follow these procedures below.
1. Place the following PRX modules from a 1.0 firmware dump. These files are not included with iR Shell distribution for legal reasons. It doesn't matter whether the files are encrypted or decrypted. Encrypted files are smaller in size.
ms0:/IRSHELL/SYSTEM/pspnet.prx
ms0:/IRSHELL/SYSTEM/pspnet_apctl.prx
ms0:/IRSHELL/SYSTEM/pspnet_inet.prx
ms0:/IRSHELL/SYSTEM/pspnet_resolver.prx
2. From your XMB, goto Network Settings->Infrastructure Mode.
- Enter a connection name with "adhoc" as prefix (case insensitive). Example, "Adhoc PC1". The adhoc prefix tells iR Shell this is an adhoc entry. Without adhoc prefix, iR Shell will treat it as a regular Infrastructure settings for Access Point only.
- Enter the SSID name for your adhoc network. Don't use Scan as it won't allow you to scan adhoc networks.
- Use WEP encryption to your preference.
- Choose Custom under "Address Settings", then choose "Manual IP Address Settings". Enter IP address manually, example "192.168.100.2". For "Default Router" entry, type your PC's IP Address, example "192.168.100.1". Enter an arbitrary DNS address.
- For Proxy Server, choose "Do Not Use". Then save settings and skip test connection.
3. Goto iR Configurator, select the appropriate XMB Network Config entry. Then, enter your PC IP Address under "NetHost IP (Adhoc)" entry. This PC IP Address is used for adhoc connections. For infrastructure connections, iR Shell uses the IP Address/Name defined under "Nethost IP/Name (AP)". The reason for having 2 different entries is to avoid making changes to your configurator when switching from AP to Adhoc.
4. Done. You can now use nethost0 via Adhoc mode under iR Shell. If you enable to option "Allow Adhoc PC Connection for Homebrew" under iR Configurator, this will even allow your existing Infrastructure WiFi homebrew applications to use Adhoc WiFi to a PC.
So far so good, but what exactly does nethostfs do? Any idea? Also i'm not sure if i can configure wlan under OSX the same way i can with XP. I could start the macbook with xp but this is not what i want!