Usage Conventions For

Your Network Configuration Files

Version 2.1
© 2004 Sony Computer Entertainment Inc.
Publication date: March 2004

Sony Computer Entertainment Inc.

1-1, Akasaka 7-chome, Minato-ku
Tokyo 107-0052, Japan

Sony Computer Entertainment America

919 E. Hillsdale Blvd.
Foster City, CA 94404, U.S.A.

Sony Computer Entertainment Europe

30 Golden Square
London W1F 9LD, U.K.

The Usage Conventions For Your Network Configuration Files manual is supplied pursuant to and subject to the terms
of the Sony Computer Entertainment PlayStation® license agreements.
The Usage Conventions For Your Network Configuration Files manual is intended for distribution to and use by only
Sony Computer Entertainment licensed Developers and Publishers in accordance with the PlayStation® license
agreements.
Unauthorized reproduction, distribution, lending, rental or disclosure to any third party, in whole or in part, of this book
is expressly prohibited by law and by the terms of the Sony Computer Entertainment PlayStation® license agreements.
Ownership of the physical property of the book is retained by and reserved by Sony Computer Entertainment.
Alteration to or deletion, in whole or in part, of the book, its presentation, or its contents is prohibited.
The information in the Usage Conventions For Your Network Configuration Files manual is subject to change without
notice. The content of this book is Confidential Information of Sony Computer Entertainment.

and PlayStation are registered trademarks of Sony Computer Entertainment Inc. All other trademarks are property
of their respective owners and/or their licensors.
Table of Contents

About This Document 5

About Version Control 5
Changes Since Last Release 5
Related Documentation 5
Typographic Conventions 5
Developer Support 6
Your Network Configuration Files 7
What Are Your Network Configuration Files? 7
Structure Of Your Network Configuration Files 7
Contents Of Your Network Configuration Files 9
Criteria For Creating Network Configuration Applications (Read Processing) 16
Displaying And Selecting Network Configurations 16
Using A Network Configuration To Make A Connection 16
Displaying And Selecting Hardware Settings 17
Using Hardware Settings To Make A Connection 18
Displaying And Selecting Internet Service Provider Settings 18
Using The Internet Service Provider Settings To Make A Connection 19
Errors During Reading Of Your Network Configuration Files 19
Criteria For Creating Network Configuration Applications (Write Processing) 20
Adding, Editing And Deleting Network Configurations 20
Adding, Editing And Deleting Hardware Settings 20
Adding, Editing And Deleting Internet Service Provider Settings 21
Saving To A Memory Card (PS2) 22
Saving To The Hard Disk Drive 22
Implementation Details 23
Redialing While Connecting 23
Connection Processing When The Hardware Types Are Inconsistent 23
Usable Characters 24

Usage Conventions For Your Network Configuration Files - Runtime Library Release 3.0.1
4 Table of Contents

Usage Conventions For Your Network Configuration Files - Runtime Library Release 3.0.1
 About This Document 5

About This Document

This document describes the contents of Your Network Configuration files. These are files provided by SCE
that are used to save information related to network connections. This document also describes criteria for
creating programs that use these files.

About Version Control

The Usage Conventions For Your Network Configuration Files, Version 2.1, is to be used in combination
with the TRC. Together they provide compulsory programming guidelines. This document is independently
version controlled.
The versions are numbered as follows:
Addition or Deletion of Regulations; increase the major number by one
Example: Version 1.0 Æ Version 2.0
Correction of Errors or Additional Explanation; increase the minor number by one
Example: Version 1.0 Æ Version 1.1

Changes Since Last Release

• None

Related Documentation
Note: the Developer Support Web site posts current developments regarding the Libraries and also
provides notice of future documentation releases and upgrades.

Typographic Conventions
Certain Typographic Conventions are used throughout this manual to clarify the meaning of the text:
Convention Meaning
courier Indicates literal program code.
italic Indicates names of arguments and structure
members (in structure/function definitions
only).
medium bold Indicates data types and structure/function
names (in structure/function definitions
only).
blue Indicates a hyperlink.

Usage Conventions For Your Network Configuration Files - Runtime Library Release 3.0.1
6 About This Document

Developer Support

Sony Computer Entertainment America (SCEA)

SCEA developer support is available to licensees in North America only. You may obtain developer support
or additional copies of this documentation by contacting the following addresses:
Order Information Developer Support
Attn: Developer Tools Coordinator E-mail: [email protected]
Sony Computer Entertainment America Web: https://www.ps2-pro.com/
919 East Hillsdale Blvd. Developer Support Hotline:(650) 655-5566
Foster City, CA 94404, U.S.A. (Call Monday through Friday,
Tel: (650) 655-8000 8 a.m. to 5 p.m., PST/PDT)

Sony Computer Entertainment Europe (SCEE)

SCEE developer support is available to licensees only in the PAL television territories (including Europe and
Australasia). You may obtain developer support or additional copies of this documentation by contacting
the following addresses:
Order Information Developer Support
Attn: Development Tools Manager E-mail: [email protected]
Sony Computer Entertainment Europe Web: https://www.ps2-pro.com/
13 Great Marlborough Street Developer Support Hotline:
London W1F 7HP, U.K. +44 (0) 20 7911-7711
Tel: +44 (0) 20 7859-5000 (Call Monday through Friday,
9 a.m. to 6 p.m., GMT/BST)

Usage Conventions For Your Network Configuration Files - Runtime Library Release 3.0.1
 Your Network Configuration Files 7

Your Network Configuration Files

What Are Your Network Configuration Files?

Your Network Configuration files are network configuration files that enable individual information that is
entered and set once by each user such as the hardware used for the network connection, access point of
the Internet service provider and user account, to be shared by various applications.
Because the file format is unified for the common network configuration library (netcnf) and specifics such
as save locations and the value range of settings are strictly defined, Your Network Configuration files can
easily be shared by multiple applications. Files that do not abide by the Usage Conventions, even if they
can be read/written by netcnf, are not Your Network Configuration files.

Figure 1

Network Library (libinet, etc.)

Common Network Configuration Library (netcnf)

Your Network
Configuration Files

Common Network Configuration File

Operations performed on Your Network Configuration files must be via the common network configuration
library (netcnf) and the common network configuration interface library (netcnfif). In addition, since Your
Network Configuration files are shared resources, an application that uses these files (hereafter referred to
as a network configuration application) must follow prescribed standards.

Structure Of Your Network Configuration Files

Your Network Configuration files consist of the following files.
• Configuration management file
• Network configuration file
• Hardware settings file
• Internet service provider settings file
In addition to these, device-related files that are required for each storage destination should also be
included. These storage devices include the memory card (PS2) and hard disk drive. Storage locations and
file configurations for each device are shown below.

Usage Conventions For Your Network Configuration Files - Runtime Library Release 3.0.1
8 Your Network Configuration Files

Table 1: When the storage device is a memory card (PS2)

Storage Location
/BWNETCNF

Table 2
File Type Maximum Size Maximum No. of Files Filename
Configuration 3K bytes 1 BWNETCNF
management file
Temporary file 3K bytes 1 BWNETCNF.tmp
Network configuration 3K bytes 6 net???.cnf
file
Hardware settings file 3K bytes 4 dev???.dat
Internet service 3K bytes 4 ifc???.dat
provider settings file
Icon file 34K bytes 1 SYS_NET.ICO
icon.sys 1K byte 1 icon.sys
File entries 9K bytes ((18+1)/2)
Directory entries 2K bytes

• The ??? of net???.cnf, dev???.dat, and ifc???.dat are automatically assigned by the common
network configuration library (netcnf).
• The temporary file is temporarily created by the common network configuration library (netcnf)
when manipulating Your Network Configuration files.
• The file entries and directory entries conform to the memory card library specification.

Table 3: When the storage device is the hard disk drive

Storage Location
/etc/network in __sysconf partition

Table 4
File Type Maximum Size Maximum No. of Files Filename
Configuration 17K bytes 1 net.db
management file
Temporary file 17K bytes 1 net.db.tmp
Network configuration 3K bytes 10 net???.cnf
file
Hardware settings file 3K bytes 30 dev???.dat
Internet service 3K bytes 30 ifc???.dat
provider settings file

• The ??? of net???.cnf, dev???.dat, and ifc???.dat are automatically assigned by the common
network configuration library (netcnf).
• The temporary file is temporarily created by the common network configuration library (netcnf)
when manipulating Your Network Configuration files.

Usage Conventions For Your Network Configuration Files - Runtime Library Release 3.0.1
 Your Network Configuration Files 9

Contents Of Your Network Configuration Files

The configuration information that can be saved in each of Your Network Configuration files is fixed and this
determines the settings that must be saved. This configuration information and the corresponding settings
are shown below.
The entries that appear in the Type column of the tables below have the following meanings.

Table 5
Type Meaning
Required A setting that is always entered or selected by the user and
must be set
Required/automatic A setting determined internally which must be set by the
network configuration application
Optional A setting that exists but doesn't get set unless it is entered or
selected by the user (it's also not saved if it isn't set)

In addition, the Applicable Keyword column shows the keyword provided by the common network
configuration library (netcnf) corresponding to that setting (for a description of keywords, refer to the
Common Network Configuration Library (netcnf) Overview).

Contents Of The Configuration Management File

The configuration management file contains information about the network configuration file, hardware
settings file, and Internet service provider settings file that are located in the directory where Your Network
Configuration files are saved together with the setting name of each file. This information is saved as text in
the following format.
file-type,1,filename,setting-name\n
(*) \n indicates a new line.
The user can specify the setting-name, using ASCII characters (excluding comma ','), hiragana, and
katakana. Please see the tables, "ASCII characters that can be used in Your Network Configuration files"
and "Hiragana and katakana that can be used in setting names" later in this document. The application
must prevent any other characters from being entered.

Contents Of The Network Configuration File

The following settings can be saved in the network configuration file.
Only ASCII characters are allowed.

Table 6: Network configuration file that contains combinations of hardware settings and Internet service
provider settings files
Type Setting Applicable Keyword
Required Combination of a hardware setting interface "ifc???.dat +
and Internet service provider setting dev???.dat" "ifc???.dat"
"dev???.dat"

Contents Of The Hardware Settings File

The following settings can be saved in the hardware settings file.
Only ASCII characters can be used in each entry. The application must prevent any other characters from
being entered.

Usage Conventions For Your Network Configuration Files - Runtime Library Release 3.0.1
10 Your Network Configuration Files

Also, because the vendor name and product name are used for the setting name, commas ',' cannot be
used.

Table 7: Settings when an Ethernet adapter manufactured by SCE is used for the connection hardware
Type Setting Applicable Keyword
Required/automatic Device layer type type nic
Required/automatic Vendor name vendor "vendor"
Required/automatic Product name product "product"
Required Operation mode of the One of the following
Ethernet hardware
Auto-detect phy_config auto
10Base-T Half-Duplex phy_config 10
10Base-T Full-Duplex phy_config 10_fd
100Base-TX Half-Duplex phy_config tx
100Base-TX Full-Duplex phy_config tx_fd

Table 8: Settings when a non-SCE Ethernet adapter is used for the connection hardware
Type Setting Applicable Keyword
Required/automatic Device layer type type eth
Required/automatic Vendor name vendor "vendor"
Required/automatic Product name product "product"
Required Operation mode of the One of the following
Ethernet hardware
Auto-detect phy_config auto
10Base-T Half-Duplex phy_config 10
10Base-T Full-Duplex phy_config 10_fd
100Base-TX Half-Duplex phy_config tx
100Base-TX Full-Duplex phy_config tx_fd

Table 9: Settings when a modem or terminal adapter is used for the connection hardware
Type Setting Applicable Keyword
Required/automatic Device layer type type ppp
Required/automatic Vendor name vendor "vendor"
Required/automatic Product name product "product"
Required Dialing type One of the following
Tone dialing_type tone
Pulse dialing_type pulse
Optional Additional AT commands chat_additional
"chat_script"
Optional Outside line outside_number
"outside_number" and
outside_delay
"outside_delay"
Required Line timeout (minutes) idle_timeout ?

• Although the line timeout setting is in units of minutes, the keyword that is defined by the common
network configuration library (netcnf) uses seconds as the units.

Usage Conventions For Your Network Configuration Files - Runtime Library Release 3.0.1
 Your Network Configuration Files 11

• It must be possible to set a value from 0 to 90 minutes for the line timeout. The application must
treat any other value as an error. A 0 entry means no timeout. The default value must be 10
minutes.

Contents Of The Internet Service Provider Settings File

The following settings can be saved in the Internet service provider settings file.
Only ASCII characters can be used in each entry.

Table 10: Settings when an Ethernet adapter manufactured by SCE is used for the connection hardware and
DHCP is not used
Type Setting Applicable Keyword
Required/automatic Device layer type type nic
Required Do not use DHCP -dhcp
Required IP address address "?.?.?.?"
Required Netmask netmask "?.?.?.?"
Required Default router route add -net 0.0.0.0
gw ?.?.?.? netmask 0.0.0.0
Optional Primary DNS nameserver add ?.?.?.?
Optional Secondary DNS nameserver add ?.?.?.?

• The IP address, netmask, default router, primary DNS, and secondary DNS are displayed in dot
format, which must be specified as follows.
num8.num8.num8.num8 (num8 is a decimal number represented as an unsigned 8 bit value)
• It must be possible to set values from 0.0.0.0 to 255.255.255.255 for the IP address, netmask,
default router, primary DNS, and secondary DNS. The application must treat any other value as an
error.
• For the IP address, netmask, and default router, 0.0.0.0 must be considered to be an error.
• For the primary DNS and secondary DNS, 0.0.0.0 must be either considered to be an error, or
treated as a specification for automatic acquisition.

Table 11: Settings when an Ethernet adapter manufactured by SCE is used for the connection hardware and
DHCP is used
Type Setting Applicable Keyword
Required/automatic Device layer type type nic
Required Use DHCP dhcp
Optional Primary DNS nameserver add ?.?.?.?
Optional Secondary DNS nameserver add ?.?.?.?
Optional DHCP host name dhcp_host_name
"host_name"

• The primary DNS and secondary DNS are displayed in dot format, which must be specified as
follows.
num8.num8.num8.num8 (num8 is a decimal number represented as an unsigned 8 bit value)
• It must be possible to set values from 0.0.0.0 to 255.255.255.255 for the primary DNS and
secondary DNS. The application must treat any other value as an error.
• For the primary DNS and secondary DNS, 0.0.0.0 must be either considered to be an error, or
treated as a specification for automatic acquisition.

Usage Conventions For Your Network Configuration Files - Runtime Library Release 3.0.1
12 Your Network Configuration Files

Table 12: Settings when a non-SCE Ethernet adapter is used for the connection hardware and DHCP is not
used
Type Setting Applicable Keyword
Required/automatic Device layer type type eth
Required Do not use DHCP -dhcp
Required IP address address "?.?.?.?"
Required Netmask netmask "?.?.?.?"
Required Default router route add -net 0.0.0.0
gw ?.?.?.? netmask 0.0.0.0
Optional Primary DNS nameserver add ?.?.?.?
Optional Secondary DNS nameserver add ?.?.?.?

• The IP address, netmask, default router, primary DNS, and secondary DNS are displayed in dot
format, which must be specified as follows.
num8.num8.num8.num8 (num8 is a decimal number represented as an unsigned 8 bit value)
• It must be possible to set values from 0.0.0.0 to 255.255.255.255 for the IP address, netmask,
default router, primary DNS, and secondary DNS. The application must treat any other value as an
error.
• For the IP address, netmask, and default router, 0.0.0.0 must be considered to be an error.
• For the primary DNS and secondary DNS, 0.0.0.0 must be either considered to be an error, or
treated as a specification for automatic acquisition.

Table 13: Settings when a non-SCE Ethernet adapter is used for the connection hardware and DHCP is used
Type Setting Applicable Keyword
Required/automatic Device layer type type eth
Required Use DHCP dhcp
Optional Primary DNS nameserver add ?.?.?.?
Optional Secondary DNS nameserver add ?.?.?.?
Optional DHCP host name dhcp_host_name
"host_name"

• The primary DNS and secondary DNS are displayed in dot format, which must be specified as
follows.
num8.num8.num8.num8 (num8 is a decimal number represented as an unsigned 8 bit value)
• It must be possible to set values from 0.0.0.0 to 255.255.255.255 for the primary DNS and
secondary DNS. The application must treat any other value as an error.
• For the primary DNS and secondary DNS, 0.0.0.0 must be either considered to be an error, or
treated as a specification for automatic acquisition.

Usage Conventions For Your Network Configuration Files - Runtime Library Release 3.0.1
 Your Network Configuration Files 13

Table 14: Settings when an Ethernet adapter is used for the connection hardware, PPPoE is used, and the DNS
server address is automatically obtained
Type Setting Applicable Keyword
Required/automatic Device layer type type ppp
Required/automatic Authentication name of peer_name "*"
connection destination
Required/automatic Authentication method allow.auth chap/pap
Required/automatic Do not use DHCP -dhcp
Required User ID auth_name "user_id"
Required Password auth_key "password"
Required Automatically obtain DNS want.dns1_nego
server address want.dns2_nego
Required/automatic Default router route add -net 0.0.0.0
netmask 0.0.0.0
Required/automatic Prohibit PFC negotiation -want.prc_nego
Required/automatic Prohibit ACFC negotiation -want.acc_nego
Required/automatic Prohibit ACCM negotiation -want.accm_nego
Required/automatic MTU and MRU setting mtu 1454
(1454 bytes)
Required Use PPPoE pppoe
Required/automatic Line timeout (minutes) idle_timeout 0

Table 15: Settings when an Ethernet adapter is used for the connection hardware, PPPoE is used, but the DNS
server address is not automatically obtained
Type Setting Applicable Keyword
Required/automatic Device layer type type ppp
Required/automatic Authentication name of peer_name "*"
connection destination
Required/automatic Authentication method allow.auth chap/pap
Required/automatic Do not use DHCP -dhcp
Required User ID auth_name "user_id"
Required Password auth_key "password"
Required Primary DNS nameserver add ?.?.?.?
Optional Secondary DNS nameserver add ?.?.?.?
Required/automatic Default router route add -net 0.0.0.0
netmask 0.0.0.0
Required/automatic Prohibit PFC negotiation -want.prc_nego
Required/automatic Prohibit ACFC negotiation -want.acc_nego
Required/automatic Prohibit ACCM negotiation -want.accm_nego
Required/automatic MTU and MRU setting mtu 1454
(1454 bytes)
Required Use PPPoE pppoe
Required/automatic Line timeout (minutes) idle_timeout 0

• The primary DNS and secondary DNS are displayed in dot format, which must be specified as
follows.

Usage Conventions For Your Network Configuration Files - Runtime Library Release 3.0.1
14 Your Network Configuration Files

num8.num8.num8.num8 (num8 is a decimal number represented as an unsigned 8 bit value)

• It must be possible to set values from 0.0.0.0 to 255.255.255.255 for the primary DNS and
secondary DNS. The application must treat any other value as an error.
• For the primary DNS and secondary DNS, 0.0.0.0 must be either considered to be an error, or
treated as a specification for automatic acquisition.

Table 16: Settings when a modem or terminal adapter is used for the connection hardware, and the DNS server
address is automatically obtained
Type Setting Applicable Keyword
Required/automatic Device layer type type ppp
Required/automatic Authentication name of peer_name "*"
connection destination
Required/automatic Authentication method allow.auth chap/pap
Required/automatic Do not use DHCP -dhcp
Required User ID auth_name "user_id"
Required Password auth_key "password"
Required Telephone number 1 phone_number0
??????????
Optional Telephone number 2 phone_number1
??????????
Optional Telephone number 3 phone_number2
??????????
Required Automatically obtain DNS want.dns1_nego
server address want.dns2_nego
Required/automatic Default router route add -net 0.0.0.0
netmask 0.0.0.0

Table 17: Settings when a modem or terminal adapter is used for the connection hardware, and the DNS server
address is not automatically obtained
Type Setting Applicable Keyword
Required/automatic Device layer type type ppp
Required/automatic Authentication name of peer_name "*"
connection destination
Required/automatic Authentication method allow.auth chap/pap
Required/automatic Do not use DHCP -dhcp
Required User ID auth_name "user_id"
Required Password auth_key "password"
Required Telephone number 1 phone_number0
??????????
Optional Telephone number 2 phone_number1
??????????
Optional Telephone number 3 phone_number2
??????????
Required Primary DNS nameserver add ?.?.?.?
Optional Secondary DNS nameserver add ?.?.?.?
Required/automatic Default router route add -net 0.0.0.0
netmask 0.0.0.0

Usage Conventions For Your Network Configuration Files - Runtime Library Release 3.0.1
 Your Network Configuration Files 15

• The primary DNS and secondary DNS are displayed in dot format, which must be specified as
follows.
num8.num8.num8.num8 (num8 is a decimal number represented as an unsigned 8 bit value)
• It must be possible to set values from 0.0.0.0 to 255.255.255.255 for the primary DNS and
secondary DNS. The application must treat any other value as an error.
• For the primary DNS and secondary DNS, 0.0.0.0 must be either considered to be an error, or
treated as a specification for automatic acquisition.

Usage Conventions For Your Network Configuration Files - Runtime Library Release 3.0.1
16 Criteria For Creating Network Configuration Applications (Read Processing)

Criteria For Creating Network Configuration Applications

(Read Processing)
The various kinds of processing performed by an application that reads and uses Your Network
Configuration files must be implemented according to the criteria described below.

Displaying And Selecting Network Configurations

Follow the criteria given below if processing for displaying and selecting network configurations is to be
implemented.
• When the user selects a network configuration, the hardware setting and Internet service provider
setting that are registered in the selected network configuration must be displayed. Furthermore,
when a network configuration is selectable in which either one or both of the hardware setting
and/or the Internet service provider setting are not registered (i.e. have been deleted), since the
respective settings do not exist, a message indicating that the network configuration is unavailable
must be displayed.
• When a network configuration that was saved on a memory card (PS2) is displayed, the setting
name (network configuration name) must be displayed in one of the following forms.
• "Network configuration 1" to "Network configuration 6"
• "Combination 1" to "Combination 6"
• "1" to "6"
• When a network configuration that was saved on the hard disk drive is displayed, the setting
name (network configuration name) must be displayed in one of the following forms.
• "Network configuration 1" to "Network configuration 10"
• "Combination 1" to "Combination 10"
• "1" to "10"
• It is advisable that all of the network configurations for the maximum number of files described
under "Structure Of Your Network Configuration Files" can be displayed and selected.
• When a network configuration that has been saved as the default data in individual data is
displayed, a check must be done to be sure that a network configuration with the same contents
is present in the directory where the original Your Network Configuration file is located. At the
same time, the presence of the hardware setting and Internet service provider setting that are
registered in the network configuration as well as their contents must also be confirmed.

Using A Network Configuration To Make A Connection

Follow the criteria given below if processing that uses a network configuration to make a connection to the
network is to be implemented.
• The user must not be able to select a network configuration for which either of the following
conditions is true, or, if such a network configuration is selected, a message must be displayed
that a connection cannot be established.
a. When the hardware that is described in the registered hardware setting is not physically
connected
b. When either or both of the hardware setting and/or Internet service provider setting that are
registered in the network configuration do not exist

Usage Conventions For Your Network Configuration Files - Runtime Library Release 3.0.1
 Criteria For Creating Network Configuration Applications (Read Processing) 17

• When a network configuration that has been saved as the default data in individual data is used
for the connection, a check must be done to be sure that a network configuration with the same
contents is present in the directory where the original Your Network Configuration file is located.
At the same time, the presence of the hardware setting and Internet service provider setting that
are registered in the network configuration as well as their contents must also be confirmed.
• When telephone numbers 1-3 have been set, there must be a mechanism to redial telephone
number 2 when telephone number 1 is busy, and to redial telephone number 3 when telephone
number 2 is busy.
• Make sure that the connection can be established even if the Internet service provider setting is
inconsistent for the type of Ethernet adapter as follows.
a. When an attempt is made to connect with an Ethernet adapter manufactured by SCE, and the
hardware setting is type nic, but the Internet service provider setting is type eth.
b. When an attempt is made to connect with a non-SCE Ethernet adapter, and the hardware
setting is type eth, but the Internet service provider setting is type nic.

Displaying And Selecting Hardware Settings

Follow the criteria given below if processing for displaying and selecting hardware settings is to be
implemented.
• It is advisable that all of the hardware settings for the maximum number of files described under
"Structure Of Your Network Configuration Files" can be displayed and selected.
• When displaying the hardware setting name on the screen, make sure that either the entire name
can be displayed or that at least 10 characters of both the vendor name and product name are
displayed.
• Predefined names of individual settings must be used for displaying the settings that are saved in
the hardware settings file (see "Contents Of Your Network Configuration Files", above).
• The minimum number of characters shown below must be displayed for the individual settings
that are saved in the hardware settings file.
Table 18
Setting Minimum No. of Characters to Display
Additional AT commands 32
Outside line 32

• When hardware settings that have been saved as the default data in individual data are displayed,
a check must be done to be sure that a hardware settings file with the same contents is present in
the directory where the original Your Network Configuration file is located.
• When displaying additional AT commands, the sceNetCnfConvS2A() function must be executed
first before displaying. This function is provided in the common network configuration library for
processing strings that are read from Your Network Configuration files. In addition, be sure to
provide a 256-byte buffer for the converted string, in order to avoid the
sceNETCNF_TOO_LONG_STR(-19) error.

Usage Conventions For Your Network Configuration Files - Runtime Library Release 3.0.1
18 Criteria For Creating Network Configuration Applications (Read Processing)

Using Hardware Settings To Make A Connection

Follow the criteria given below if processing that uses hardware settings to make a connection to the
network is to be implemented.
• The user must not be able to select hardware settings that describe hardware that is not
physically connected, or, if such settings are selected, a message must be displayed that a
connection cannot be established.
• When hardware settings that have been saved as the default data in individual data are used for
the connection, a check must be done to be sure that a hardware settings file with the same
contents is present in the directory where the original Your Network Configuration file is located.
• Make sure that the connection can be established even if the Internet service provider setting is
inconsistent for the type of Ethernet adapter as follows.
a. When an attempt is made to connect with an Ethernet adapter manufactured by SCE, and the
hardware setting is type nic, but the Internet service provider setting is type eth.
b. When an attempt is made to connect with a non-SCE Ethernet adapter, and the hardware
setting is type eth, but the Internet service provider setting is type nic.

Displaying And Selecting Internet Service Provider Settings

Follow the criteria given below if processing for displaying and selecting Internet service provider settings is
to be implemented.
• It is advisable that all of the Internet service provider settings for the maximum number of files
described under "Structure Of Your Network Configuration Files" can be displayed and selected.
• When displaying the Internet service provider setting name on the screen, make sure that either
the entire name can be displayed or that at least 20 characters are displayed.
• Predefined names of individual settings must be used for displaying the settings that are saved in
the Internet service provider settings file (see "Contents Of Your Network Configuration Files",
above).
• The minimum number of characters shown below must be displayed for the individual settings
that are saved in the Internet service provider settings file.
Table 19
Setting Minimum No. of Characters to Display
IP address 32
Netmask 32
Default router 32
Primary DNS 32
Secondary DNS 32
Telephone number 1 32
Telephone number 2 32
Telephone number 3 32
User ID 32
Password 32
DHCP host name 256

• When Internet service provider settings that have been saved as the default data in individual data
are displayed, a check must be done to be sure that an Internet service provider settings file with
the same contents is present in the directory where the original Your Network Configuration file is
located.

Usage Conventions For Your Network Configuration Files - Runtime Library Release 3.0.1
 Criteria For Creating Network Configuration Applications (Read Processing) 19

• When displaying the user ID, the sceNetcnfifConvAuthname() function must be executed on the
user ID and the result must be displayed on the screen.

Using The Internet Service Provider Settings To Make A Connection

Follow the criteria given below if processing that uses Internet service provider settings to make a
connection to the network is to be implemented.
• When Internet service provider settings that have been saved as the default data in individual data
are used for the connection, a check must be done to be sure that an Internet service provider
settings file with the same contents is present in the directory where the original Your Network
Configuration file is located.
• When telephone numbers 1-3 have been set, there must be a mechanism to redial telephone
number 2 when telephone number 1 is busy, and to redial telephone number 3 when telephone
number 2 is busy.
• Make sure that the connection can be established even if the Internet service provider setting is
inconsistent for the type of Ethernet adapter as follows.
a. When an attempt is made to connect with an Ethernet adapter manufactured by SCE, and the
hardware setting is type nic, but the Internet service provider setting is type eth.
b. When an attempt is made to connect with a non-SCE Ethernet adapter, and the hardware
setting is type eth, but the Internet service provider setting is type nic.

Errors During Reading Of Your Network Configuration Files

If any of the following errors occur while reading Your Network Configuration files, execute the error-
handling procedures as outlined.
• If an sceNETCNF_MAGIC_ERROR is detected, a message must be displayed indicating that the
Your Network Configuration file was created on another PlayStation 2 and that it cannot be used.
The user must then be asked whether or not to delete the configuration file. If the user chooses to
delete the configuration file, then the file must be deleted. If the user chooses not to delete the
configuration file, the file should be ignored from that point onwards.
• If an unrecoverable error such as an sceNETCNF_NG or sceNETCNF_SYNTAX_ERROR is
detected, a message must be displayed indicating that the Your Network Configuration file cannot
be corrected. Then the user must be asked whether or not to delete the configuration file. If the
user chooses to delete the configuration file, then the file must be deleted. If the user chooses not
to delete the configuration file, the file should be ignored fromthat point onwards.
However, note that SCEA/E titles that do not write to Your Network Configuration files should follow the
procedure below.
• If an sceNETCNF_MAGIC_ERROR is detected, a message must be displayed indicating that the
Your Network Configuration file was created on another PlayStation 2 and that it cannot be used.
The configuration file should be ignored from that point onwards
• If an unrecoverable error such as an sceNETCNF_NG or sceNETCNF_SYNTAX_ERROR is
detected, a message must be displayed indicating that the Your Network Configuration file cannot
be corrected. The configuration file should be ignored from that point onwards

Usage Conventions For Your Network Configuration Files - Runtime Library Release 3.0.1
20 Criteria For Creating Network Configuration Applications (Write Processing)

Criteria For Creating Network Configuration Applications

(Write Processing)
The various kinds of processing performed by an application that adds, edits and deletes Your Network
Configuration files must be implemented according to the criteria described below. For read processing, be
sure to follow the criteria described in the previous section.
The conventions described in this section do not apply to an application that does not perform the
functions discussed in this section, nor do they apply to an application that only uses Your Network
Configuration files that were created by another application.

Adding, Editing And Deleting Network Configurations

Follow the criteria given below if processing that adds, edits or deletes network configurations is to be
implemented.
• The common network configuration library (netcnf) must be used.
• The implementation must allow network configurations to be added and deleted, in addition to be
edited.
• Network configurations must be saved in the stipulated directory using valid filenames (see
"Structure Of Your Network Configuration Files", above).
• Make sure that not more than the stipulated maximum number of network configuration files can
be saved (see "Structure Of Your Network Configuration Files", above).
• All stipulated settings must be supported. Settings other than those which are stipulated must not
be saved (see "Contents Of Your Network Configuration Files", above).
• Hardware settings and Internet service provider settings that exist as files on different devices
must not be registered in network configurations.
• When saving a network configuration on a memory card (PS2), the setting name (network
configuration name) must have one of the following forms.
• "Network configuration 1" to "Network configuration 6"
• "Combination 1" to "Combination 6"
• "1" to "6"
• When saving a network configuration on the hard disk drive, the setting name (network
configuration name) must have one of the following forms.
• "Network configuration 1" to "Network configuration 10"
• "Combination 1" to "Combination 10"
• "1" to "10"
• If an unknown setting is encountered during editing, that setting must be saved unchanged.
• The same contents must not be saved within application-specific data for any purpose other than
making it the default data.

Adding, Editing And Deleting Hardware Settings

Follow the criteria given below if processing that adds, edits or deletes hardware settings is to be
implemented.
• The common network configuration library (netcnf) must be used.
• The implementation must allow hardware settings to be added and deleted, in addition to be
edited.

Usage Conventions For Your Network Configuration Files - Runtime Library Release 3.0.1
 Criteria For Creating Network Configuration Applications (Write Processing) 21

• Hardware settings must be saved in the stipulated directory using valid filenames (see "Structure
Of Your Network Configuration Files", above).
• Make sure that not more than the stipulated maximum number of hardware settings files can be
saved (see "Structure Of Your Network Configuration Files", above).
• All stipulated settings must be supported. Settings other than those which are stipulated must not
be saved (see "Contents Of Your Network Configuration Files", above).
• The settings name must be saved in the form below, using the vendor name and product name
obtained from the device driver.
vendor-name/product-name
• If an unknown setting is encountered during editing, that setting must be saved unchanged.
• Stipulated characters must be used. Inputting of characters other than those which are stipulated
must be prevented (see "Usable Characters", below).
• A 256-byte internal buffer must be provided for items in which strings are to be set to enable at
most 255 characters + "\0" to be read and written correctly (note that hiragana and katakana can
require up to 3 bytes per character). Also, a mechanism must be implemented for preventing input
that would exceed the size of the provided buffer.
• The application must allow additional AT commands to be entered, in either plain AT command
format or as CHAT script sequences (defined in the "Common Network Configuration Library
Overview"). The user input must be filtered with the sceNetCnfConvA2S() function provided by the
common network configuration library before saving the setting. If
sceNETCNF_TOO_LONG_STR(-19) is detected during the conversion, an error message must be
displayed indicating that the input contains too many characters.
• The same contents must not be saved within application-specific data for any purpose other than
making it the default data.

Adding, Editing And Deleting Internet Service Provider Settings

Follow the criteria given below if processing that adds, edits or deletes Internet service provider settings is
to be implemented.
• The common network configuration library (netcnf) must be used.
• The implementation must allow Internet service provider settings to be added and deleted, in
addition to be edited.
• Internet service provider settings must be saved in the stipulated directory using valid filenames
(see "Structure Of Your Network Configuration Files", above).
• Make sure that not more than the stipulated maximum number of Internet service provider
settings files can be saved (see "Structure Of Your Network Configuration Files", above).
• All stipulated settings must be supported. Settings other than those which are stipulated must not
be saved (see "Contents Of Your Network Configuration Files", above). Furthermore, it is only
necessary to be able to display the following settings. It is not necessary to allow them to be
added, edited, or deleted.
a. Telephone number 2
b. Telephone number 3
• If an unknown setting is encountered during editing, that setting must be saved unchanged.
• Stipulated characters must be used. Inputting of characters other than those which are stipulated
must be prevented (see "Usable Characters", below).
• A 256-byte internal buffer must be provided for items in which strings are to be set to enable at
most 255 characters + "\0" to be read and written correctly (note that hiragana and katakana can
require up to 3 bytes per character). Also, a mechanism must be implemented for preventing input
that would exceed the size of the provided buffer.

Usage Conventions For Your Network Configuration Files - Runtime Library Release 3.0.1
22 Criteria For Creating Network Configuration Applications (Write Processing)

• The same contents must not be saved within application-specific data for any purpose other than
making it the default data.
• When sceNETCNF_AOL_CONFIGURATION(-20) is detected, the Internet service provider setting
must not be added or edited.

Saving To A Memory Card (PS2)

Follow the criteria given below if processing that saves Your Network Configuration files to a memory card
(PS2) is to be implemented.
• The common network configuration library (netcnf) must be used.
• Your Network Configuration files must be saved in the stipulated directory using valid filenames
(see "Structure Of Your Network Configuration Files", above).
• Hardware settings files and Internet service provider settings files must be encoded before being
saved.
• Make sure that not more than the stipulated maximum number of settings files can be saved (see
"Structure Of Your Network Configuration Files", above). If an attempt is made to save more than
the maximum number, an appropriate message must be displayed indicating that the maximum
number of settings files has been reached.
• If there is less than 94K bytes of free space, an appropriate message must be displayed when
saving indicating that there is insufficient free space. Furthermore, since the configuration
management file is saved when the Your Network Configuration file is deleted, free space must
also be checked at that time.
• The specified files must be used for the icon file and icon.sys file.
• Other than the above, processing must conform to the TRC related to memory cards (PS2).

Saving To The Hard Disk Drive

Follow the criteria given below if processing that saves Your Network Configuration files to the hard disk
drive is to be implemented.
• The common network configuration library (netcnf) must be used.
• Your Network Configuration files must be saved in the stipulated directory using valid filenames
(see "Structure Of Your Network Configuration Files", above).
• Hardware settings files and Internet service provider settings files must be encoded before being
saved.
• Make sure that not more than the stipulated maximum number of settings files can be saved (see
"Structure Of Your Network Configuration Files", above). If an attempt is made to save more than
the maximum number, an appropriate message must be displayed indicating that the maximum
number of settings files has been reached.
• If there is less than 244K bytes of free space, an appropriate message must be displayed when
saving indicating that there is insufficient free space. Furthermore, since the configuration
management file is saved when the Your Network Configuration file is deleted, free space must
also be checked at that time.
• Other than the above, processing must conform to the TRC related to the hard disk drive.

Usage Conventions For Your Network Configuration Files - Runtime Library Release 3.0.1
 Implementation Details 23

Implementation Details

Redialing While Connecting

When a connection is made by a network configuration application, if telephone numbers 1-3 have been
set in a Your Network Configuration file, redialing must be attempted to telephone number 2 when
telephone number 1 is busy, and redialing must be attempted to telephone number 3 when telephone
number 2 is also busy. (Redialing is determined by the redial_string setting, which is defined in the dialing
definition file (DIAL_CNF) supplied with the modem driver.) However, just using sceNetCnfLoadEntry() to
read the Your Network Configuration file is insufficient to set redialing, as the setting described below is
also required.
• If while connecting, telephone numbers 1-3 had previously been specified, then the redial_count
member of the sceNetCnfInterface structure should be set to the value obtained by subtracting 1
from the total number of specified telephone numbers.
An implementation example is shown below.
sceNetCnfEnv_t env;
int i, redial_count;

// Execute sceNetCnfLoadEntry()
sceNetCnfLoadEntry("configuration management file name", type,
"setting name(network configuration name)", &env);

// Set redial_count
for(i = 0, redial_count = 0; i < sceNetCnf_MAX_PHONE_NUMBERS; i++)
{
if(NULL == (env.root->pair_head->ifc->phone_numbers[i]))
continue;
switch(i){
case 0: redial_count++; break;
case 1: redial_count++; break;
case 2: redial_count++; break;
}
}
env.root->pair_head->ifc->redial_count = redial_count - 1;

In addition, the redial_count value that is set by the processing shown above must not be saved to a Your
Network Configuration file. This should be implemented as processing that is performed only when making
a connection.

Connection Processing When The Hardware Types Are Inconsistent

In the following examples, the common network configuration library (netcnf.irx) specification will cause the
connection to fail because a valid hardware type is specified in the Internet service provider settings.
• When making a connection using an Ethernet adapter manufactured by SCE when the Internet
service provider setting is type eth and the hardware setting is type nic.
• When making a connection using a non-SCE Ethernet adapter when the Internet service provider
setting is type nic and the hardware setting is type eth.
To enable the connection to be established by a network configuration application even in the cases
described above, the following should be implemented.

Usage Conventions For Your Network Configuration Files - Runtime Library Release 3.0.1
24 Implementation Details

• When PPPoE is not used and the type for the Internet service provider setting is not ppp,
overwrite the type for the Internet service provider setting with the type for the hardware setting.
An implementation example is shown below.
sceNetCnfEnv_t env;

// Execute sceNetCnfLoadEntry()
sceNetCnfLoadEntry("configuration management file name", type,
"setting name(network configuration name)", &env);

// When PPPoE is not used and the Internet service provider setting
// type is not ppp, overwrite the type
if(env.root->pair_head->ifc->pppoe != 1 &&
env.root->pair_head->ifc->type != sceNetCnf_IFC_TYPE_PPP){
env.root->pair_head->ifc->type = env.root->pair_head->dev-
>type;
}

In addition, the value that is set by the processing shown above must not be saved to a Your Network
Configuration file. This should be implemented as processing that is performed only when making a
connection.

Usable Characters
The following table lists the characters that can be used in Your Network Configuration files. A network
configuration application must be able to handle the characters displayed here. Characters other than
those displayed here must not be saved to Your Network Configuration files.

ASCII characters that can be used in Your Network Configuration files

Table 20
Char Hex Char Hex Char Hex
(SPACE) 20 @ 40 ` 60
! 21 A 41 a 61
" 22 B 42 b 62
# 23 C 43 c 63
$ 24 D 44 d 64
% 25 E 45 e 65
& 26 F 46 f 66
' 27 G 47 g 67
( 28 H 48 h 68
) 29 I 49 i 69
* 2a J 4a j 6a
+ 2b K 4b k 6b
, (see Note) 2c (see Note) L 4c l 6c
- 2d M 4d m 6d
. 2e N 4e n 6e
/ 2f O 4f o 6f
0 30 P 50 p 70
1 31 Q 51 q 71

Usage Conventions For Your Network Configuration Files - Runtime Library Release 3.0.1
 Implementation Details 25

Char Hex Char Hex Char Hex

2 32 R 52 r 72
3 33 S 53 s 73
4 34 T 54 t 74
5 35 U 55 u 75
6 36 V 56 v 76
7 37 W 57 w 77
8 38 X 58 x 78
9 39 Y 59 y 79
: 3a Z 5a z 7a
; 3b [ 5b { 7b
< 3c \ (half-width) 5c | 7c
= 3d ] 5d } 7d
> 3e ^ 5e ~ 7e
? 3f _ 5f

Note: code 0x2c (",") cannot be used in setting names.

Hiragana and katakana that can be used in setting names

The table below shows hiragana and katakana that can be used by the user to specify setting names, as
well as ASCII characters displayed in the table 20 above. UTF-8 must be used as the character code. JIS,
SJIS and Unicode are provided for reference.

Table 21
Char UTF-8 JIS SJIS Unicode
ぁ e3 81 81 2421 829f 3041
あ e3 81 82 2422 82a0 3042
ぃ e3 81 83 2423 82a1 3043
い e3 81 84 2424 82a2 3044
ぅ e3 81 85 2425 82a3 3045
う e3 81 86 2426 82a4 3046
ぇ e3 81 87 2427 82a5 3047
え e3 81 88 2428 82a6 3048
ぉ e3 81 89 2429 82a7 3049
お e3 81 8a 242a 82a8 304a
か e3 81 8b 242b 82a9 304b
が e3 81 8c 242c 82aa 304c
き e3 81 8d 242d 82ab 304d
ぎ e3 81 8e 242e 82ac 304e
く e3 81 8f 242f 82ad 304f
ぐ e3 81 90 2430 82ae 3050
け e3 81 91 2431 82af 3051
げ e3 81 92 2432 82b0 3052

Usage Conventions For Your Network Configuration Files - Runtime Library Release 3.0.1
26 Implementation Details

Char UTF-8 JIS SJIS Unicode

こ e3 81 93 2433 82b1 3053
ご e3 81 94 2434 82b2 3054
さ e3 81 95 2435 82b3 3055
ざ e3 81 96 2436 82b4 3056
し e3 81 97 2437 82b5 3057
じ e3 81 98 2438 82b6 3058
す e3 81 99 2439 82b7 3059
ず e3 81 9a 243a 82b8 305a
せ e3 81 9b 243b 82b9 305b
ぜ e3 81 9c 243c 82ba 305c
そ e3 81 9d 243d 82bb 305d
ぞ e3 81 9e 243e 82bc 305e
た e3 81 9f 243f 82bd 305f
だ e3 81 a0 2440 82be 3060
ち e3 81 a1 2441 82bf 3061
ぢ e3 81 a2 2442 82c0 3062
っ e3 81 a3 2443 82c1 3063
つ e3 81 a4 2444 82c2 3064
づ e3 81 a5 2445 82c3 3065
て e3 81 a6 2446 82c4 3066
で e3 81 a7 2447 82c5 3067
と e3 81 a8 2448 82c6 3068
ど e3 81 a9 2449 82c7 3069
な e3 81 aa 244a 82c8 306a
に e3 81 ab 244b 82c9 306b
ぬ e3 81 ac 244c 82ca 306c
ね e3 81 ad 244d 82cb 306d
の e3 81 ae 244e 82cc 306e
は e3 81 af 244f 82cd 306f
ば e3 81 b0 2450 82ce 3070
ぱ e3 81 b1 2451 82cf 3071
ひ e3 81 b2 2452 82d0 3072
び e3 81 b3 2453 82d1 3073
ぴ e3 81 b4 2454 82d2 3074
ふ e3 81 b5 2455 82d3 3075
ぶ e3 81 b6 2456 82d4 3076
ぷ e3 81 b7 2457 82d5 3077
へ e3 81 b8 2458 82d6 3078
べ e3 81 b9 2459 82d7 3079

Usage Conventions For Your Network Configuration Files - Runtime Library Release 3.0.1
 Implementation Details 27

Char UTF-8 JIS SJIS Unicode

ぺ e3 81 ba 245a 82d8 307a
ほ e3 81 bb 245b 82d9 307b
ぼ e3 81 bc 245c 82da 307c
ぽ e3 81 bd 245d 82db 307d
ま e3 81 be 245e 82dc 307e
み e3 81 bf 245f 82dd 307f
む e3 82 80 2460 82de 3080
め e3 82 81 2461 82df 3081
も e3 82 82 2462 82e0 3082
ゃ e3 82 83 2463 82e1 3083
や e3 82 84 2464 82e2 3084
ゅ e3 82 85 2465 82e3 3085
ゆ e3 82 86 2466 82e4 3086
ょ e3 82 87 2467 82e5 3087
よ e3 82 88 2468 82e6 3088
ら e3 82 89 2469 82e7 3089
り e3 82 8a 246a 82e8 308a
る e3 82 8b 246b 82e9 308b
れ e3 82 8c 246c 82ea 308c
ろ e3 82 8d 246d 82eb 308d
ゎ e3 82 8e 246e 82ec 308e
わ e3 82 8f 246f 82ed 308f
ゐ e3 82 90 2470 82ee 3090
ゑ e3 82 91 2471 82ef 3091
を e3 82 92 2472 82f0 3092
ん e3 82 93 2473 82f1 3093
ァ e3 82 a1 2521 8340 30a1
ア e3 82 a2 2522 8341 30a2
ィ e3 82 a3 2523 8342 30a3
イ e3 82 a4 2524 8343 30a4
ゥ e3 82 a5 2525 8344 30a5
ウ e3 82 a6 2526 8345 30a6
ェ e3 82 a7 2527 8346 30a7
エ e3 82 a8 2528 8347 30a8
ォ e3 82 a9 2529 8348 30a9
オ e3 82 aa 252a 8349 30aa
カ e3 82 ab 252b 834a 30ab
ガ e3 82 ac 252c 834b 30ac
キ e3 82 ad 252d 834c 30ad

Usage Conventions For Your Network Configuration Files - Runtime Library Release 3.0.1
28 Implementation Details

Char UTF-8 JIS SJIS Unicode

ギ e3 82 ae 252e 834d 30ae
ク e3 82 af 252f 834e 30af
グ e3 82 b0 2530 834f 30b0
ケ e3 82 b1 2531 8350 30b1
ゲ e3 82 b2 2532 8351 30b2
コ e3 82 b3 2533 8352 30b3
ゴ e3 82 b4 2534 8353 30b4
サ e3 82 b5 2535 8354 30b5
ザ e3 82 b6 2536 8355 30b6
シ e3 82 b7 2537 8356 30b7
ジ e3 82 b8 2538 8357 30b8
ス e3 82 b9 2539 8358 30b9
ズ e3 82 ba 253a 8359 30ba
セ e3 82 bb 253b 835a 30bb
ゼ e3 82 bc 253c 835b 30bc
ソ e3 82 bd 253d 835c 30bd
ゾ e3 82 be 253e 835d 30be
タ e3 82 bf 253f 835e 30bf
ダ e3 83 80 2540 835f 30c0
チ e3 83 81 2541 8360 30c1
ヂ e3 83 82 2542 8361 30c2
ッ e3 83 83 2543 8362 30c3
ツ e3 83 84 2544 8363 30c4
ヅ e3 83 85 2545 8364 30c5
テ e3 83 86 2546 8365 30c6
デ e3 83 87 2547 8366 30c7
ト e3 83 88 2548 8367 30c8
ド e3 83 89 2549 8368 30c9
ナ e3 83 8a 254a 8369 30ca
ニ e3 83 8b 254b 836a 30cb
ヌ e3 83 8c 254c 836b 30cc
ネ e3 83 8d 254d 836c 30cd
ノ e3 83 8e 254e 836d 30ce
ハ e3 83 8f 254f 836e 30cf
バ e3 83 90 2550 836f 30d0
パ e3 83 91 2551 8370 30d1
ヒ e3 83 92 2552 8371 30d2
ビ e3 83 93 2553 8372 30d3
ピ e3 83 94 2554 8373 30d4

Usage Conventions For Your Network Configuration Files - Runtime Library Release 3.0.1
 Implementation Details 29

Char UTF-8 JIS SJIS Unicode

フ e3 83 95 2555 8374 30d5
ブ e3 83 96 2556 8375 30d6
プ e3 83 97 2557 8376 30d7
ヘ e3 83 98 2558 8377 30d8
ベ e3 83 99 2559 8378 30d9
ペ e3 83 9a 255a 8379 30da
ホ e3 83 9b 255b 837a 30db
ボ e3 83 9c 255c 837b 30dc
ポ e3 83 9d 255d 837c 30dd
マ e3 83 9e 255e 837d 30de
ミ e3 83 9f 255f 837e 30df
ム e3 83 a0 2560 8380 30e0
メ e3 83 a1 2561 8381 30e1
モ e3 83 a2 2562 8382 30e2
ャ e3 83 a3 2563 8383 30e3
ヤ e3 83 a4 2564 8384 30e4
ュ e3 83 a5 2565 8385 30e5
ユ e3 83 a6 2566 8386 30e6
ョ e3 83 a7 2567 8387 30e7
ヨ e3 83 a8 2568 8388 30e8
ラ e3 83 a9 2569 8389 30e9
リ e3 83 aa 256a 838a 30ea
ル e3 83 ab 256b 838b 30eb
レ e3 83 ac 256c 838c 30ec
ロ e3 83 ad 256d 838d 30ed
ヮ e3 83 ae 256e 838e 30ee
ワ e3 83 af 256f 838f 30ef
ヰ e3 83 b0 2570 8390 30f0
ヱ e3 83 b1 2571 8391 30f1
ヲ e3 83 b2 2572 8392 30f2
ン e3 83 b3 2573 8393 30f3
ヴ e3 83 b4 2574 8394 30f4
ヵ e3 83 b5 2575 8395 30f5
ヶ e3 83 b6 2576 8396 30f6
ー e3 83 bc 213C 815B 30fc

Usage Conventions For Your Network Configuration Files - Runtime Library Release 3.0.1
30 Implementation Details

Usage Conventions For Your Network Configuration Files - Runtime Library Release 3.0.1