HP t1000 T1500/T1510 Windows-based Terminal Network Installation Guide - Page 28

NOSWAP, REFLASH, MF_DIR, Setup | Connectivity | Internet | DNS | Hosts

Get HP t1000 - Terminal Thin Client PC PDF manuals and user guides View all HP t1000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 28 highlights

14 Chapter 2 (Windows server) is //machine/share[/directory], where machine is a DNS resolvable machine name, share is the share name, and path is an optional path within that share. For name resolution, an entry in the terminal's host file (Setup | Connectivity | Internet | DNS | Hosts) qualifies. For NFS, the directory MUST be exported with read/write/execute permissions and with root mapping to root, not to nobody. For SMB, the server's guest account needs to be activated and guest users need to be able to connect to that share for full control. The network services tree is automatically included as part of the network boot tree, so network services are not required here, but can be used to share the load between multiple servers. If large pages are to be printed, it is recommended that local-boot terminals use network services to provide space for the spool files. NOSWAP Normal behavior for the terminal is to allow swapping via NFS (network services or network boot), although not activating this ability. Setup provides the ability for a terminal to turn on swapping and specify the size of the swap file. Because of the server resources required to support swapping (20+ MB per terminal that can swap), the NOSWAP DHCP option allows the network administrator to override what is configured in setup, to protect the disk space capacity on his server. For Option 18 or 128+, this is a string 0080_NETSVC=YES. For Option 43, it is a field with one byte of data. The data is ignored; however, including the option prevents swapping. REFLASH Normal behavior is to bring up the terminal's user interface in a network-boot environment. If this option is provided, the flash build utility is brought up and the terminal is put in a special mode, designed to reprogram itself or to program cards. Normally, this option is used only for the terminal's Boot Server feature, which allows one terminal to be used to provide resources for other terminals to reflash themselves. For Option 18 or 128+, this is a string 0080_NETSVC=YES. For Option 43, it is a field with one byte of data. The data is ignored; however, including the option prevents swapping. MF_DIR When using the flash build utility, this option provides the network services-style path to the directory where the images to be programmed reside when shortcuts are used by the flash build utility. The syntax for NFS is machine:/path, where machine is the IP address or DNS-resolvable machine name for the server, and path is the full pathname. The syntax for SMB (Windows server) is //machine/ share[/path], where machine is a DNS resolvable machine name, share is

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
14
Chapter 2
(Windows server) is
//machine/share[/directory],
where
machine
is a
DNS resolvable machine name,
share
is the share name, and
path
is an optional
path within that share. For name resolution, an entry in the terminal's host file
(
Setup | Connectivity | Internet | DNS | Hosts
) qualifies. For NFS, the directory
MUST be exported with read/write/execute permissions and with root mapping to
root, not to nobody. For SMB, the server's guest account needs to be activated and
guest users need to be able to connect to that share for full control. The network
services tree is automatically included as part of the network boot tree, so network
services are not required here, but can be used to share the load between multiple
servers. If large pages are to be printed, it is recommended that local-boot
terminals use network services to provide space for the spool files.
NOSWAP
Normal behavior for the terminal is to allow swapping via NFS (network services or
network boot), although not activating this ability. Setup provides the ability for a
terminal to turn on swapping and specify the size of the swap file. Because of the
server resources required to support swapping (20+ MB per terminal that can
swap), the NOSWAP DHCP option allows the network administrator to override
what is configured in setup, to protect the disk space capacity on his server. For
Option 18 or 128+, this is a string
0080_NETSVC=YES
. For Option 43, it is a field
with one byte of data. The data is ignored; however, including the option prevents
swapping.
REFLASH
Normal behavior is to bring up the terminal's user interface in a network-boot
environment. If this option is provided, the flash build utility is brought up and the
terminal is put in a special mode, designed to reprogram itself or to program cards.
Normally, this option is used only for the terminal’s Boot Server feature, which
allows one terminal to be used to provide resources for other terminals to reflash
themselves. For Option 18 or 128+, this is a string
0080_NETSVC=YES
. For Option
43, it is a field with one byte of data. The data is ignored; however, including the
option prevents swapping.
MF_DIR
When using the flash build utility, this option provides the network services-style
path to the directory where the images to be programmed reside when shortcuts
are used by the flash build utility. The syntax for NFS is
machine:/path
, where
machine
is the IP address or DNS-resolvable machine name for the server, and
path
is the full pathname. The syntax for SMB (Windows server) is
//machine/
share[/path]
, where
machine
is a DNS resolvable machine name,
share
is