DT-900

DT-900
UPLOAD/DOWNLOAD UTILITY
LMWIN TCP/IP
MANUAL
(Version 3.01 for Windows 95/98 Windows NT)
CASIO Computer Co., Ltd.
Copyright © 2003. All rights reserved.
January 2003
Table of Contents
Chapter
Chapter
Chapter
Chapter
Chapter
Chapter
Chapter
Chapter
Chapter
Chapter
Chapter
Chapter
1
2
3
4
5
6
6.1
6.2
6.3
6.4
7
7.1
8
8.1
8.2
8.3
8.4
8.5
9
9.1
9.2
9.3
9.3.1
9.3.2
9.4
9.4.1
9.5
9.5.1
9.5.2
9.5.3
9.5.4
9.6
9.7
9.8
10
10.1
10.2
10.2.1
10.2.2
10.2.3
10.2.4
10.2.5
10.2.6
10.2.7
10.2.8
10.2.9
10.2.10
10.2.11
10.2.12
10.2.13
10.2.14
10.2.15
11
12
Editorial Record ...........................................................................
Introduction ................................................................................
Terminology/Nomenclature ........................................................
System Architecture ...................................................................
Environments and Interfaces .....................................................
Functionality ...............................................................................
System Configuration .................................................................
Connection of Satellite Cradle through RS-232C .............……
Direct Connection of DT-900 through RS-232C ...................…….
Connection of Master Cradle through SCSI …....................……
Connection of Master Cradle through TCP/IP ………………….
Error Information .........................................................................
Error Codes .........................................................................…….
Installation ...................................................................................
Version-up …………………….......................................................
Uninstallation …………………………………………………………
Syntax of Installer Command ………………………………………
Starting up LMWIN ……………………………………………………
Closing LMWIN ………………………………………………………..
Manu Layer …………....................................................................
Screen Transition of Upload/Download Utility (GUI) ................
Main Menu Screen ......................................................................
Script Menu .................................................................................
Script File Editor ………………………………………………………
Open ..............................................................................………….
Configure Set Menu ……..............................................................
Communication Setup Screen (RS-232C) ..…….........................
Execute Menu …….......................................................................
Server Mode …………...................................................................
Command Execute …………........................................................
Script Execute …………...............................................................
Abort …………...............................................................................
Help …….......................................................................................
Status Display .............................................................................
Error Message Display ................................................................
Command Interface …………………………………………………..
Single Shot Mode/Batch Mode ……………………………………..
Command Detail ……………………………………………………….
Send ……………………………………………………………………..
Receive ………………………………………………………………….
Append File Send ……………………………………………………..
Append File Receive ………………………………………………….
File/Directory Delete ………………………………………………….
Move/Rename ………………………………………………………….
Buzzer ……………………………………………………………………
Time Date Set …………………………………………………………..
Character String Display ……………………………………………..
Session Termination ………………………………………………….
Child Process Execution …………………………………………….
Drive Information Fetching ………………………………………….
File Information Fetching ……………………………………………
File Information Setting ………………………………………………
Format …………………………………………………………………...
Syntax of Script File Commands ................................................
Configuration Set File .................................................................
2
4
5
6
7
8
9
10
10
11
12
13
14
15
17
17
17
17
18
18
19
19
21
21
22
23
25
26
27
28
29
31
32
33
34
35
36
36
37
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
54
Chapter
Chapter
Chapter
Chapter
Chapter
Chapter
Chapter
Chapter
Chapter
Chapter
Chapter
Chapter
13
14
14.1
14.2
15
15.1
15.1.1
15.1.2
15.1.3
15.2
15.3
15.4
15.4.1
15.4.2
15.4.3
15.4.4
15.4.5
16
16.1
16.1.1
16.1.2
16.1.3
16.1.4
16.2
16.2.1
16.2.2
16.2.3
16.2.4
16.2.5
16.2.6
17
17.1
17.1.1
17.1.2
17.2
18
18.1
18.2
18.3
18.4
19
20
20.1
20.2
20.2.1
20.2.2
20.3
20.4
21
21.1
21.2
22
23
23.1
23.2
24
Format of LMWIN.INI ...................................................................
RS-232C Interface ........................................................................
Notes about the Installation …………………………………………
Limitation ……………………………………………………………….
SCSI Interface ………………………………………………………….
Installation ………………………………………………………………
Setup Conditions ……………………………………………………..
DIP Switch Setting on Master Cradle …………………………….
Note about the Installation ………………………………………….
SCSI Cable ……………………………………………………………..
Bootup …………………………………………………………………..
Function and Operation ………………………………………………
Overview ………………………………………………………………...
Selection and Setup for SCSI Interface ……………..……………
Specifying Command Execute/Script Execute
………………
Abort ……………………………………………………………………..
Session Establishment ………………………………………………
TCP/IP Interface ……………………………………………………….
Installation ……………………………………………………………..
Required Environment ……………………………………………….
Number of Master Cradles ………………………………………..
Limitation on Simultaneous Communication ……………………
Setup of “ini” File ……………………………………………………..
Function and Operation ……………………………………………..
Overview ………………………………………………………………..
Selection and Setup for TCP/IP Interface …………………………
Specifying Command Execute/Script Execute ………………….
Abort …………………………………………………………………….
Session Establishment ………………………………………………
Cradle Monitoring Panel ……………………………………………
Other Errors ………………………………………………………….
Errors under SCSI and TCP/IP Interfaces ………………………..
Errors Caused by Simultaneous Communication .……………..
Other Errors ……………………………………………………………
Year 2000 Compliance ……………………………………………….
< File Check Utility >
File Check Utility .........................................................................
Development Concept ....................................................……......
Purpose ...............................................................................……..
Scope ..................................................................................……...
Terminology ........................................................................……..
Operation Environment ...............................................................
Function ...........................................................….........................
Operation Procedure ................................……............................
Detailed Functions ...........................……....................................
List File Creating Function ………………………………………….
List File Comparison Function ……………………………………..
Format of List File ……................................................................
Common Specifications to Each Function .......……..................
Screen Images of Operations .....................................................
List File Creation ......................................…….............................
List File Check ..........................................……...........................
Syntax Analysis of Script Files ...................................................
Installation Method of File Check Utility ....................................
For Host PC .......................................................................……....
For DT-900 .................................................………………………....
Error Messages/Codes from File Check Utility .........................
3
55
56
56
56
57
57
57
58
58
58
59
59
59
59
60
61
61
62
62
62
62
62
63
65
65
65
66
67
67
68
69
69
69
69
71
71
71
71
71
72
73
74
74
75
75
77
79
79
80
80
81
83
85
85
85
88
Editorial Record
Manual
Version no.
1.01
Date edited
Page
1999
January 2003
All
Content
Original.
Descriptions about DT-900M60E,DT-900M61E models have
been added to all relative descriptions.
No part of this document may be produced or transmitted in any form or by any means, electronic or
mechanical, for any purpose, without the express written permission of CASIO Computer Co., Ltd.
in Tokyo Japan. Information in this document is subject to change without advance notice. CASIO
Computer Co., Ltd. makes no representations or warranties with respect to the contents or use of this
manual and specifically disclaims any express or implied warranties of merchantability or fitness for
any particular purpose.
© 2003 CASIO Computer Co., Ltd. All rights reserved.
4
1. Introduction
This document is the User Manual for the Windows 95 Upload/Download utility software, TCP/IP
version 3.01, for the DT-900 system. It describes the operation, screen installation and configuration
of the system. It also describes the application programming interface (API). The version 3.01 of the
Manual includes the descriptions for the RS-232C, SCSI and TCP/IP interfaces. The object of the
Upload/Download utility software is to perform the following functions:
•
•
•
Send and Receive files between the Host PC and the DT-900.
Remote two-way and one-way command execution (buzzer activate, format)
Script file execution on the Host PC
2. Terminology/Nomenclature
Download
Transfer of files/data from the Host PC to the DT-900
Upload
Transfer of files/data from the DT-900 to the Host PC
Cradle
A device which acts as the interface between the Host PC and the DT-900. This device can be a
Master Cradle or a Satellite Cradle.
Master Cradle
A Cradle which connects to the Host PC through a SCSI link or TCP/IP link. A Master Cradle has
protocol translation capability, from SCSI or TCP/IP to IrDA, and can support up to a maximum
of 8 Satellite Cradles through RS-422 links.
Satellite Cradle
A Cradle which is connected to a Master Cradle through RS-422 link or a Cradle which can be
connected to the Host PC through an RS-232C link. It basically acts as a protocol converter from
RS-232C to IrDA.
Script File
An application specific batch file which is prepared on the Host PC, consisting of a number of
commands to be executed in sequence. This file can be prepared on the Host PC using the
Environment Setup Tool (part of the Upload/Download utility) or a Text Editor. This file can be
designed to execute on the Host PC or the DT-900. The script files shall have an extension
of .SCR. The utility will not recognize any other extensions as script file.
Session
The activity between the Host PC and the DT-900 from the start of a request by the DT-900 to the
termination of the activity is called a session.
5
3. System Architecture
User Application
Program
GUI
File Transfer
Engine
File Transfer
Commands
Communication Driver Functions
Communication
Layer
Communication
Drivers
(for RS-232C, SCSI, TCP/IP)
To Cradle with DT-900
Fig. 3.1
The Upload/Download System architecture is as shown above. It consists of the following
components:
GUI
This is a Graphical User Interface of the Upload/Download utility. It consists of the following
sub-systems:
- A script file editor which enables the user to create and edit script files in wizard form.
- A configuration file editor which enables the user to select the communication interface
between the Cradle and the Host PC and also to configure the settings (COM port, baud
rate, etc. ). These settings and selections are stored in the Configuration file DEVICE.INI.
- A Command Execution Screen which enables the user to start and stop the utility and to
issue commands (send, receive, format, etc.).
User Application Program (optional)
This is an optional facility by which the user can make use of the File Transfer utility APIs to
develop their own applications or user interfaces. This product provides a standard User
Interface (GUI), but the user has the option to develop other interfaces or enhance the existing
interface.
File Transfer Engine
This sub-system implements the File Transfer Protocol, and may be considered as the engine
which carries out all file transfer and other commands.
6
Communication Layer
This layer provides a common interface between the various communication drivers ( RS232C, SCSI and TCP/IP) and the File Transfer Utility layer. The objective of this is to provide
a single application programming interface between the utility and the drivers.
Communication Drivers
This layer implements the communication drivers for RS-232C, SCSI and TCP/IP. This is the
lowest layer which interfaces directly between the hardware on the Host PC and an Cradle.
7
4. Environments and Interfaces
The Upload/Download utility host program is available under the following operating
environments.
IBM compatible PC AT
CPU
: Pentium
Clock
: 100 MHz (minimum)
Memory Capacity
: 16 Mbytes RAM or more
Display
: Minimum size 800 x 600 dots (16 colors)
Free space
: 10 Mbytes required for storage of this utility software (Also, area
for data storage is required.)
Available OS
: Windows 95, Windows NT Workstation 4.0,
Windows NT Server 4.0, Windows 98
OS language
: The LMWIN is designed and developed for the OS of other
languages as well as English language.
However, to use this software under other language, be sure to
check the operability first.
The Upload/Download Utility Host Program can be used with the following specific interfaces.
RS-232C interface (refer to Chapter 14 in this manual.)
SCSI interface (refer to Chapter 15 in this manual.)
TCP/IP interface (refer to Chapter 16 in this manual.)
8
5. Functionality
The Upload/Download utility provides the following functions between the Host PC and the
DT-900.
1.
2.
3.
4.
5.
6
7
8
9
10.
11.
12.
13.
14.
15.
File Send
File Receive
File Send and Append
File Receive and Append
Buzzer activate
Format Disk
Set Time and Date
Delete
Move/Rename
Fetch Disk Information
Fetch File Information
Set File Information
End Session
Execute Child Process
Display Character String
9
6. System Configuration
6.1 Connection of Satellite Cradle through RS-232C
Satellite Cradle can be connected to the Host PC through an RS-232C serial link. The Satellite
Cradle may be daisy-chained to other Satellite Cradles (maximum of 8 units ) through RS-422 serial
links, as shown below, or may be stand alone.
IrDA
Satellite
Cradle
Host PC
RS-232C
RS-422
Satellite
Cradle
IrDA
DT-900
DT-900
RS-422
Satellite
Cradle
IrDA
RS-422
Maximum 8 units of Satellite Cradle
Fig. 6.1
10
DT-900
6.2 Direct Connection of DT-900 through RS-232C
A direct connection between the Host PC and the DT-900 can be possible.
Host PC
RS-232C
DT-900
Fig. 6.2
11
6.3 Connection of Master Cradle through SCSI
Host PC
SCSI
Master
Cradle
ID0
IrDA
DT-900
RS422
RS422
Satellite
Cradle
IrDA
Satellite
Cradle
IrDA
DT-900
DT-900
SCSI
7 x Satellite
Cradle (max.)
Master
Cradle
ID1
IrDA
DT-900
RS422
SCSI
RS422
Satellite
Cradle
IrDA
Satellite
Cradle
IrDA
DT-900
DT-900
7 x Satellite
Cradle (max.)
Master
Cradle
ID2
IrDA
DT-900
RS422
RS422
Master Cradles (ID0 to ID6) can be connected.
Fig. 6.3
12
Satellite
Cradle
IrDA
Satellite
Cradle
IrDA
DT-900
7 x Satellite
Cradle (max.)
DT-900
6.4 Connection of Master Cradle through TCP/IP
Host PC
TCP/IP
Master
Cradle
IrDA
DT-900
RS422
RS422
Satellite
Cradle
IrDA
Satellite
Cradle
IrDA
DT-900
DT-900
7 x Satellite
Cradle (max.)
Master
Cradle
IrDA
DT-900
RS422
RS422
Satellite
Cradle
IrDA
Satellite
Cradle
IrDA
DT-900
DT-900
7 x Satellite
Cradle (max.)
Master
Cradle
IrDA
DT-900
RS422
Maximum 254 units of Master Cradle can be connected.
RS422
Satellite
Cradle
IrDA
Satellite
Cradle
IrDA
DT-900
DT-900
7 x Satellite
Cradle (max.)
Fig. 6.4
Note:
Depending on the performance of the Host PC and the quality of network, the number of Master
Cradles that can be communicated simultaneous may vary.
13
7. Error Information
The Upload/Download System identifies, logs and displays the following types of errors:
Communication errors
File Transfer Utility or Protocol Errors
User Command Syntax Errors
Error Messages are displayed in Error Message Dialog boxes. A maximum of 8 dialog boxes can
be displayed on the screen simultaneously. If there are more error messages, the last Error
Message box will display a message “ More Errors Exist -- See Error Log for details”.
When an error occurs start the session from the beginning. If the same error continues, reset the
parameters such as baud rate to other values or check conditions set for each interface port. Or, start
up the LMWIN again. Refer to Chapter 17 “Other Errors” also.
All the errors are logged in the Error Log file (ERROR.LOG) in the directory specified in the
DEVICE.INI file (configuration file). The Error Log file has the following information about the
errors:
Cradle number in the table below is always 1 for the RS-232C interface, or a SCSI-ID number of
Master Cradle for the SCSI interface, or a control number of Master Cradle for the TCP/IP interface
(Refer to Chapter 16 “TCP/IP Interface”.).
Table 7.1 Content in Error Log file
Cradle no.
0
0
0
Session no.
0
0
0
Date
6-9-1997
6-9-1997
8-9-1997
Time
17-44-46
18- 1-24
11-53-29
14
Error code
0x00 0x01
0x00 0x05
0x04 0x05
Description
Undefined function code
Communication error
Command timeout error
7.1 Error Codes
The following is a list of error codes and descriptions for errors returned by the File Transfer
Protocol layer. These errors are returned to the application by the FTP API.
Table 7.2
Error Code
0x00
0x00
0x00
0xDC
|
|
0x00
0xF5
0x00
0xF6
0x00
0xF7
0x00
0xF8
Error Message
NormalEnding
ADriverFormatNotice
|
ZDriveFormatNotice
PowerOffEndingNotice
ResetEndingNotice
BreakKeyInterruptEndingNotice
0x00
0x01
0x02
0x03
0x04
0x05
0x06
0x07
0x08
0x10
0x12
0x13
0x15
0x15
0x16
0x17
0x18
0x19
0x02
0x03
0x0B
0x0F
0x10
0x11
0x12
0x13
0x14
0x15
0x17
0x19
0x1A
0x1B
0x1D
0x1E
0x1F
0x01
0x01
0x01
0x01
0x01
0x01
0x01
0x01
0x01
0x01
0x01
0x01
0x01
0x01
0x01
0x01
0x01
0x01
0x02
0x02
0x02
0x02
0x02
0x02
0x02
0x03
0x03
0x03
0x03
0x03
0x03
0x03
0x03
0x03
0x03
UndefineFunctionCode
UndefineSubFunctioncode
NotExecuteCommand
CheckSumError
CommandSequenceError
SequenceNumberError
OtherProtocolError
ParameterError
TimeoutError
DataLengthError
ProtocolVersionDifferenceError
MemoryAllocationError
FileSizeError
DateError
TimeError
FileAttributeError
OverwriteOptionError
EOFFlagError
FileNotFound
PathNotFound
InvalidFormat
InvalidDiskDrive
DeleteRequestisCurrentDirectory
NotSameDisk
FileNothing
WriteProtectError
UnknownUnit
DriveNotReady
DataError
SeekError
UnknownDiskFormat
SectorNotFound
WriteError
ReadError
UnknownError
0x20
0x21
0x03
0x03
FileShareError
FileLockError
15
Description
Normal end
Notification of format on Drive A
|
Notification of format on Drive Z
Notification of ending power shut down
Notification of ending reset
Notification of ending interruption by
user
Protocol error (function code)
Protocol error (sub-function code)
Command not executed
Checksum error
Command sequence error
Sequence number error
Illegal protocol
Parameter error
Timeout error
Protocol error (DATA LEN)
Protocol version not miss-matched
Memory allocation not possible
Protocol error (file size)
Protocol error (date)
Protocol error (time)
Protocol error (attribute)
Protocol error (forced overwrite)
Protocol error (EOF)
File not found
Path not found
Not formatted
Not right disk
Delete request to current directory
Not the same disk
File not existed
Write protect error
Undefined unit
Drive not ready
Data error
Seek error
Disk not formatted
Sector not found
Write error
Read error
Specified model of Handy Terminal not
correct
File share error
File lock error
Error Code
0x22
0x03
0x23
0x03
0x53
0x03
0x00
0x04
0x00
0x05
0x01
0x05
0x02
0x05
0x03
0x05
0x04
0x05
0x05
0x05
0x06
0x05
0x07
0x05
0x08
0x05
0x09
0x05
0x0A
0x05
0x0B
0x05
0x0C
0x05
0x0D
0x0E
0x0F
0x05
0x05
0x05
Error Message
InvalidDiskChanged
FCBFull
FatalError
ReadOnlyFileAccessError
CommunicationError
EndIndicationfromHT
PCSendsEndIndication
SpawnError
CommandTimoutError
ErrorOpeningErroLogFile
OptionError
StartupError
OpenError
ListenError
AcceptError
NotEnoughMemoryToExecute
Process
ArgumentListTooLargeForThe
Process
InvalidModeForTheProcess
ProcessTerminatedNormally
NoiseError
16
Description
Illegal disk change
FCB full
Fatal error
Access error to read-in only file
Communication error
End request from HT
End request from PC
Spawn error
Command timeout error
Fail to open log file
Option error
Start up error
Open error
Listening error
Accept error
Not enough memory to execute process
Too large process
Illegal end process
Normal end process
Communication noise error
8. Installation
The following files are supplied as part of the LMWIN.
Table 8.1
File Name
LMWIN32.EXE
Driver32.dll
Hfc32.dll
Lman32.dll
Scsidrv.dll
Tcpipdrv.dll
Remark
Upload/download utility execute type (GUI mode)
RS-232C driver
Command analysis driver
Connection observation driver
Driver for SCSI connection
Driver for TCP/IP connection
LMWIN.INI
DEVICE.INI
Other
Execution default setting file
Configuration file
File for Upload/Download utility/File for help
All the above files are provided in one package. Files and libraries necessary for all the installations
are generated by the Setup.exe program.
8.1 Version-up
If you install an updated version of the LMWIN, first uninstall a previous version of the software.
8.2 Uninstallation
To uninstall, select “Upload/Download” from “Append/Delete Application” in the control panel.
The uninstaller can be started up. The uninstaller cannot delete file and directory created by user in
the same directory where the LMWIN exists.
8.3 Syntax of Installer Command
The Upload/Download utility is installed by running the Setup.exe being installed in the setup
directory in FD. When the installer is started up, just follow instructions and select destination
directory. If the same file name exists in the selected destination directory, the file will be
overwritten by the new file.
>setup
17
8.4
Starting up LMWIN
Execute “LMWIN32.EXE” in the directory where you installed.
Command option
: None
Environment variable : Not necessarily to set up
Table 8.2 Causes not to start up “LMWIN32.EXE”
Cause
Countermeasure
Startup twice
If the LMWIN was started up already, the startup of the “LMWIN32.EXE”
will be ignored. If DUPLICATE=ON is set in the lmwin.ini, it is possible to
start up two or more the LMWINs at the same time.
Lack of memory
An error by the Windows will appear. Close other applications if opened.
capacity
DLL file not found An error from Windows will appear. Perform the installation once again.
INI file not found
An error from LMWIN will appear. After the setup of LMWIN is complete,
perform the installation once again.
8.5 Closing LMWIN
To close the “LMWIN”, select “Script – Close” from the main menu. After the selection, a
conformation dialogue box will appear. Click on the “Yes” to close the software.
18
9. Menu Layer
9.1 Screen Transition of Upload/Download Utility (GUI)
The following figure describes the screen transition for the Upload/Download utility (GUI).
Script
Configure
Execute
Help
New
Open
Exit
Script file editor
RS-232C
SCSI
TCP/IP
Set As Default
Settings
Configure Set
Screen
LinkManager
Command
Script File
Abort
Command Execution
Screen
Help Topics
About
Help Screen
Fig. 9.1
19
Script Execution
Screen
9.2 Main Menu Screen
The following screen will be displayed, which has four menus on the Menu Bar. They are:
Script
: This leads to the Script File Editor Wizard screens
Configure : This leads to the Configuration File Editor Wizard screen
Execute
: This leads to the Command Execution Wizard screen
Help
: This leads to the Help screens
20
9.3 Script Menu
This menu has the following pull down sub-menus:
New
Open
Print
Exit
: The New sub-menu is used for creating a new script file (having an extension .SCR )
: The Open sub-menu is used for opening and editing an existing script file.
: The Print sub-menu is used for printing a script file. This is not implemented as of now.
: The Exit sub-menu is used for exiting the Upload/Download utility.
21
9.3.1 Script File Editor
On selecting the New sub-menu option, the following screen is displayed:
From the menu above, the user can select the required command from the Command box.
On selecting the command, the options corresponding to the command are enabled. For example, if
the command chosen is “Send”, the following options are enabled:
File(s), Destination Dir, Options
After the options are selected, the user can do one of the followings:
Select “Exit” to exit the Script File Editor.
Select “Add” to add the command to the script file.
Select “Save” to save the script file.
Select “Save As” to save the script file with a different name.
Select “Combine” to add the currently selected command with the previous command on the
same line of the script file.
Select “Browse” to choose a file you wish to send to the DT-900.
22
9.3.2 Open
On selecting the Open sub-menu option, the following screen is displayed.
23
The following screen shows the display of the script file temp.scr :
24
9.4 Configure Set Menu
This menu enables the user to configure the communication interface with the Cradles.
This menu has the following pull down menus:
RS-232C
: Communication under the RS-232C interface.
SCSI
: Communication under the SCSI interface.
TCP/IP
: Communication under the TCP/IP interface.
Set As Default
: Selection for interface to be sued by the sub-menu.
Settings
: Display of communication setting screen.
25
9.4.1 Communication Setup Screen (RS-232C)
If the SETTINGS option is chosen, the following dialog box is displayed. The dialog box contents
depends upon the interface selected (RS-232C or SCSI or TCP/IP).
If the options are chosen and the OK button is clicked, the settings are saved to the Configuration
File (DEVICE.INI). If the “Save As Default” button is selected, the RS-232C interface with the
defined settings are saved as the default interface and settings for the utility.
Setting Screen for RS-232C
The following screen shows the settings of communication for RS-232C port to connect Cradle
(Set the same settings as the Cradle.).
The Working Directory and the name of the Error Log file also have to be specified using this
configuration dialog box. Clicking on the Cancel button cancels any selections/changes and reverts
to the earlier settings.
Working Directory
: Specify a directory to store the script file.
Error Log File
: Specify the error log file of the LMWIN.
For the SCSI interface refer to Chapter 15.4.2, or for the TCP/IP interface refer to Chapter 16.2.2.
26
9.5 Execute Menu
This menu has the following pull down sub-menus:
LinkManager
Command
Script
Abort
: The LinkManager has two sub menus -- LinkManagerStart and
LinkManagerStop. Selecting on the “LinkManagerStart” sets the Host
PC to receive commands from the DT-900.
: Displays the command execution screen.
: Displays the execution script selection screen.
: Aborts the communication.
The Configure menu is disabled during communication. Therefore, it is not possible to set
communication parameters, preventing the user from editing the Configuration File (DEVICE.INI)
while communication continues. Also, the New and Open sub-menus of the Script menu are
disabled (not shown in the screen). This prevents the user from editing the Script file or creating a
script file when a session is in progress. Thus, all editing functions are disabled when
communication is taking place.
27
9.5.1 Server Mode
Selecting “Start Link Manager” in the sub-menu initializes communication and changes LMWIN to
the status to wait for connect request from the DT-900.
If a connection request is received, communication with the Cradle is established, and the utility
enters the Server Mode. In this mode, it executes any command received from the Cradle (or the
DT-900). Once this option is selected, it is prevented by being selected again by disabling the menu.
28
9.5.2 Command Execute
The Command sub-menu leads to the following Command Execution Wizard screen. The following
screen shows the Command Execution Wizard displayed with the RS-232C interface selected from
the Configure menu.
For each command, the valid options are only enabled, while all invalid options are grayed out or
disabled.
Option of Single Shot Mode or Batch Mode :
The Command Execution Wizard Screen gives the user the options to execute each command once
(Single Shot Mode) or as a batch (many times - Batch Mode ) by proper selection of the Mode
option. If the Batch Mode is selected, the command is executed repeatedly until the user selects the
ABORT TRANSFER sub-menu on the EXECUTE menu. The default mode is the Batch Mode.
Refer to Chapter 10.1 for more detail.
If the interface selected is SCSI, then the following HT Selection Dialog is displayed. The user can
then select the IDs of the DT-900s to which the command is to be sent. On pressing OK, the
Command Execution Wizard as shown above is displayed, and the command entered from the
screen will be sent to the selected DT-900 IDs.
If “Select All option” is chosen, all IDs are selected, and if “Cancel All” is chosen, all selected IDs
are cancelled.
29
If the interface selected is the TCP/IP, then the following dialog is displayed. The user can then
Select the ID numbers of the Cradles which are to be used for communication.
30
9.5.3 Script Execute
The following screen shows the dialog box displayed when the user selects the Script pull down
menu from the Execute menu and the interface selected is RS-232C. On pressing OK, the selected
Script File is executed. The user has the option to use the batch or One shot mode. The default is the
batch mode. Refer to Chapter 10.1 for more detail.
If the interface selected is SCSI or TCP/IP, the HT Selection Dialog appears as shown in the
previous page, before the following screen is displayed.
31
9.5.4 Abort
The Abort sub-menu ends a session, when selected. If the interface selected is RS-232C, then only
one session exists. But if the interface selected is SCSI, then an HT selection dialog is displayed,
with all the active session IDs enabled. The user can then select the sessions that have to be aborted.
32
9.6 Help
The following screens show typical Help screens which appear when the Help menu is selected. The
user can search for help on any of the Upload/Download utility functions from these screens.
33
9.7 Status Display
Display of progress bar for File Transmission and Reception. This display contains the following
information:
•
Session No.
•
File Name with full path name
•
Tx or Rx (Send/Receive)
•
Progress bar
•
Percentage of file transmitted/received (range : 0 to 100%)
In case of multiple sessions, a maximum of 3 progress bars are displayed on the screen , and the
other bars can be seen by using the scroll bar. The following screen shows the progress bar display
during file transmission:
34
9.8 Error Message Display
Error Message display in the form of an Error Message Dialog Box. A maximum of 8 error message
boxes can be displayed on the screen at any time. If more than seven errors occur, the eighth message
box will display the following message:
“More Errors Exist... See Error Log File for details! “
The Error Message Display boxes will remain on the screen until the user acknowledges the message
by clicking on the OK button. The user has to press/click OK once for each Error Message Display
box. The following screen shows the display of an error message dialog box upon occurrence of an
error during file transmission.
35
10. Command Interface
The following commands can be issued from the User Interface of the Upload/Download utility
software. All the commands can be executed from a script file.
Send
Recv
Append send
Append recv
Delete
Move
Buzzer
Set time date
Display string
End session
Execute child process
Get disk info
Get file info
Set file info
Format
10.1 Single Shot Mode/Batch Mode
Every Command and Script File can be executed in two modes : Single Shot Mode and Batch
Mode. The Command Execution Wizard Screen gives the user the options to execute each command
once ( Single Shot Mode ) or as a batch ( many times - Batch Mode ) by proper selection of the mode
option. If the Batch Mode is selected, the command is executed repeatedly until the user selects the
ABORT TRANSFER sub-menu on the EXECUTE menu. The default mode is the Batch Mode.
Multiple Sessions
The Windows 95 version of the Upload/Download utility software supports multiple sessions. This
means that the utility can communicate simultaneously with a number of Cradles (if the SCSI or
TCP/IP interface is selected). The progress bars of all the active sessions can be displayed on the
screen, and any or all the sessions can be aborted.
36
10.2 Command Detail
The detail of the utility commands are described as follows.
10.2.1 Send
The files reside on the Host PC will be transferred to the DT-900. Here, destination directory means
the directory into which the send files shall be copied on the side of the station which receives the
files.
Way to describe in the script file :
/S[O|U|R] <file name> <destination directory>
<Communication Command Screen>
File
Specifies name of file in full path name which is to be sent.
Destination storage directory
Specifies destination storage directory of the DT-900 which receives the file.
Option
O (Forced overwrite) : Specifies the forced overwrite in read-only file.
When this option is specified, the process of write is executed in a read-only file.
U (Date verification) :
When this option is specified, a latest file in the storage directory will not be overwritten.
R (Recursive) :
When this option is specified, all files under the directory which is specified by send path
file name will be target for transmission file. If sub-directory is existed under the specified
directory, its sub-directory name is also appended, and the send process is done.
Even if this option is specified, send path file name must be specified by the full path name.
When this option is not specified, only files specified by send path file name will be target
for transmission file.
37
10.2.2 Receive
This function is to receive a file, by specifying request path name, which is resided in the DT-900.
If the specified directory by the receive directory is not resided in the DT900, the directory is
automatically generated in the Host PC.
Way to describe in the script file :
/R[O|U|R] <file name> <destination directory>
<Communication Command Screen>
File
Specifies the name of file on the DT-900 in full path name that is to be received by the Host PC.
Destination storage directory
Specifies the directory in the Host PC that is to receive files from the DT-900.
Option
O (Forced Overwrite) : Specify forced over-write even to read-only files.
When this option is specified, a write is executed even into read-only file.
R (With Directory) :
All files under the directory specified by requested path file name will be target for
transmission file.
If sub-directory exists under the specified directory, its sub-directory name and files under
the sub-directory are transmitted.
Even if this option is specified, requested path file shall be specified by the full path name.
U (Date Change) :
When this option is specified, later files in the receive directory will not be overwritten.
38
10.2.3 Append File Send
This function is to append the content of a file in the Host PC which is specified by the append path
file name to a file on the DT-900 which is specified by the target path file name. A wild card cannot
be specified. File is appended under the binary system (following the EFO code, it is appended.).
Way to describe in the script file :
/AS <source file name> <destination file name>
<Communication Command Screen>
Source File
Specifies a file in the Host PC by full path name.
Destination Storage File
Specifies a file of the DT-900 which connects with a file in the Host PC.
39
10.2.4 Append File Receive
This function is to append the content of a file in the DT-900 which is specified by the append path
file name to a file in the Host PC which is specified by the target path file name. A wild card cannot
be specified. The source file is appended as binary. (Even if there is an EOF code at the end of
destination file, source file is appended.)
Way to describe in the script file :
/AR <source file name> <destination file name>
<Communication Command Screen>
Source File
Specifies a file in the DT-900 by full path name.
Destination File
Specifies a file in the Host PC which receives the file sent from the DT-900.
40
10.2.5 File/Directory Delete
A file being resided in the DT-900 can be deleted by specifying it to < delete file name >.
Way to describe in the script file :
/D[O| R] <delete file name>
<Communication Command Screen>
File
Specifies a file to be deleted in the DT-900.
Option
Not available.
41
10.2.6 Move/Rename
This command is to move the specified file (with the full path name) to another directory in the same
drive of the same DT-900 with the same file name or different file name (specify in full path too).
The function can be used to move or to modify file on the same drive.
Way to describe in the script file :
/N <source file name> <destination file name>
<Communication Command Screen>
Source File
Specifies a file in the DT-900 by full path name.
Destination Storage File
Specifies a file in the DT-900 by full path name to which the file in the DT-900 is moved.
42
10.2.7 Buzzer
Turns ON the buzzer.
Way to describe in the script file :
/B
<Communication Command Screen>
43
10.2.8 Time Date Set
Sets the current time and date on the DT-900. If time and date are not specified by the script file, the
time and date in the Host PC are set on the DT-900.
Way to describe in the script file :
/T <YYYY-MM-DD HH:MM:SS>
<Communication Command Screen>
44
10.2.9 Character String Display
Displays character strings on the screen display of the DT-900. Character string(s) is enclosed by
(“ ).
Way to describe in the script file :
/P <character string to be displayed>
<Communication Command Screen>
Character String
A character string to be displayed on the DT-900 is written.
45
10.2.10 Session Termination
Terminates the connection with the DT-900. The following codes are available as the termination
code.
0 : Normal termination
220 : Format notification on Drive A.
to
245 : Format notification on Drive Z.
Way to describe in the script file :
// <termination code>
<Communication Command Screen>
46
10.2.11 Child Process Execution
Executes the executable file on the Host PC specified by <execution file path name>. It can write
parameters.
Way to describe in the script file :
/C <execution file path name> [<parameter> …]
<Communication Command Screen>
Child-process
Writes <execution file path name> <parameter>.
Limitations
The maximum number of bytes can be written on one line is 128 bytes including /C, execution
file path name and parameters.
If you write “/” twice at the end of parameter, the session cannot continue normally.
On the same line, two or more session commands of the LMWIN cannot be written.It is not
allow to join two or more session commands together.
An execution file to be started up must be a 32-bit application.
Selection Possible with Return Value from Child-process
Continuing session or aborting session can be selected with a return value from the child-process.
In the “lmwin.ini” file, if the following parameter (as an example) is set the selection can be valid.
Or, no parameter setting in the file will allow automatically the session to be continued.
[CODE]
-1=F501
If a return value from the child-process is between –1 and –10, Script Execute will be aborted
and the session stops.
The Host PC will return a termination code, 0xF501 to 0xF50A, to the DT-900.
Return Value
Termination Code
-1
0xF501
:
:
-10
0xF50A
If a return value is a value not in the range of the above the Script Execute will continue.
47
10.2.12 Drive Information Fetching
The drive information on the DT-900 will be appended to “ diskinfo.clp “.
Way to describe in the script file :
/I <drive name>
<Communication Command Screen>
Drive
Specify the drive name on the DT-900 you wish to fetch the information from.
48
10.2.13 File Information Fetching
The file information on the DT-900 will be appended to “ fileinfo.clp “.
Way to describe in the script file :
/I <file name>
<Communication Command Screen>
File
Specify the file on the DT-900 by full path name from which you wish to fetch the information.
49
10.2.14 File Information Setting
Sets for the information of file <updated file name> on the DT-900. <size> means the size of file
(0 specifies no update of file.).
Way to describe in the script file :
/X[R|H|S|A] <updated file name> <size> <YY-MM-DD> <hh:mm:ss>
<Communication Command Screen>
Size
Specify the size of a file (0 specifies no update).
Attribute
Change the attribute to one of the followings.
Write prohibited (R)
: Read only file
Hidden (H)
: Hidden file
System (S)
: System file
Archive (A)
: Archive file
Date / Time
Specify the date and time of a file.
50
10.2.15 Format
Formats the drive of the DT-900 specified by <drive name>. The execution of this command will
terminate the session between the Host PC and the connected DT-900.
Way to describe in the script file :
/I <drive name>
<Communication Command Screen>
Drive
Specify the drive on the DT-900 that is to be formatted.
51
11. Syntax of Script File Commands
This section describes the syntax of the script file commands. Script files shall have the
extension .SCR, and they shall be stored in the Working Directory as defined in the Configuration
file DEVICE.INI.
<SCRIPT FILE> ::= <COMMANDS>
<COMMANDS> ::= <COMMANDS>
<COMMAND> | null
<COMMAND> ::= '/' <CMDBODY> <LS>
<CMDBODY> ::=
<APPEND>
| <CHILD_PROC>
| <DELETE>
| <FORMAT>
| <BEEP>
| <RENAME>
| <RECEIVE>
| <SEND>
| <TIME_ADJUST>
| <END_SESSION>
<APPEND> ::= <APPEND_CMD> <APD_OPTION> <SP> <PATHNAME_PAIR>
<CHILD_PROC> ::= <CHILD_PROC_CMD> <SP> <CMD_PARAMETER>
<FORMAT> ::= <FORMAT_CMD> <SP> <DRIVE>
<BEEP> ::= <BEEP_CMD>
<RENAME> ::= <RENAME_CMD> <SP> <PATHNAME_PAIR>
<RECEIVE> ::= <RECEIVE_CMD> <OPTIONS> <SP> <PATHNAME_LIST>
<SEND> ::= <SEND_CMD> <OPTIONS> <SP> <PATHNAME_LIST>
<PRINT> ::= <PRINT_CMD> <SP> <STRING>
<TIME_ADJUST> ::= <TIME_CMD> <SP> <TIME_VALUE>
<END_SESSION> ::= <END_CMD> <PARAM>
<APPEND_CMD> ::= 'A'
<CHILD_PROC_CMD> ::= 'C'
<FORMAT_CMD> ::= 'F'
<BEEP_CMD> ::= 'B'
52
<RENAME_CMD> ::= 'N'
<RECEIVE_CMD> ::= 'R'
<SEND_CMD> ::= 'S'
<TIME_CMD> ::= 'T'
<PRINT_CMD> ::= 'P'
<END_CMD> ::= '/'
<PATHNAME_PAIR> ::= <PATHNAME> <DELM> <PATHNAME>
<CMD_PARAMETER> ::= <CMD_NAME> <STRING>
<CMD_NAME> ::= <PATHNAME>
<PATHNAME_LIST> ::=<PATHNAME><DELM> <PATHNAME_LIST> | <PATHNAME>
<DRIVE> ::= <DRIVE_LETTER> ':'
<TIME_VALUE> ::= <DATE> <TIME>
<OPTIONS> ::= <OPTIONS> <OPTION> | NULL
<OPTION> ::= <RECURSIVE_OPTION> | <UPDATE_OPTION>
<RECURSIVE_OPTION> ::= 'R'
<UPDATE_OPTION> ::= 'U'
<APND_OPTION> ::= 'S' | 'R'
<STRING> ::= '"' <CHARS> '"'
<DELM> :: = <SP>
<LS> ::= CR | <SP>
<SP> ::= <SP> SP | SP
<PARAM> ::= <SP> <NUMBER>
Notes:
<RECURSIVE_OPTION> is for sending or receiving files and directories and sub-directories.
<UPDATE_OPTION> is for sending or receiving updated files only.
<CHILD_PROC> is for executing child processes .
<PRINT> is for printing string to display.
<PATHNAME> follows the MS-DOS definition. <PATHNAME> means directory or file name.
53
12. Configuration Set File
A typical Configuration Set File “DEVICE.INI” will be as follows:
IF=RS232C
ErrorFile=c:\lmwin\lmwinerr.log
WorkFile=c:\lmwin
INFORMATION=0000000100
[RS232C]
Port=COM1
Baud=115200
Parity=NONE
Stop=1
Data=8
[SCSI]
Scantime=3
[ETHERNET]
PORTNO=50021
MAX_IO=100
[USE_IP]
1=192.168.1.1
Table 12.1
Item
Description
Common item to all devices
IF=
An interface to be used.
ErrorFile=
WorkFile=
INFORMATION=
Error log file name
Directory where the script file is
stored.
Data to be sent to the DT-900 at
beginning of session.
[RS232C] (setting items of RS-232C interface)
Port=
RS-232C port number to which
Satellite Cradle is connected.
Baud=
Baud rate
Parity=
Parity
Stop=
Stop bit
Data=
Data bit
Remark
RS-232C or SCSI or TCP/IP. An
interface selected as “Set As Default”
in the “Execute” is set up.
Specify by full path name. The same
file names as the ones at the session
setup screen are set up.
Used for the configure setting by
some of DT-900s. The default value,
0000000100, must be used as is.
The same port number set in the
communication setup screen is used.
Parameters for communication
between the Host PC and Satellite
Cradle. The same parameters set in
the communication setup screen are
used.
[SCSI] (setting items of SCSI interface)
Scan time=
Setting for timing of the SCSI
The default value, 3, must be used as
interface.
is.
[TCP/IP] (setting items of TCP/IP interface) For detail refer to Chapter 16 “TCP/IP Interface”.
PORTNO=
Port number
MAX_IO=
Maximum number of Cradles for simultaneous session
[USE_IP] (list of IP addresses for Master Cradle to be connected.) For detail refer to Chapter 16.
54
13. Format of LMWIN.INI
The following parameters are available to the LMWIN.INI. These parameters are read in when the
LMWIN is started up. Setting screen is not available for each parameter. In case the file is not
existed or is corrupted, the default values are valid to start.
Table 13.1
Definition (=default)
[CODE]
-1 (=F501)
[MODE]
MINIMIZE (=OFF)
SERVER (=OFF)
1SHOT (=OFF)
DUPLICATE (=OFF)
COMMAND_
TIMEOUT (=30)
Range
Description
Error return value of child processor (fixed currently)
ON
OFF
ON
OFF
ON
OFF
ON
OFF
0
1 to 3600
(unit=second)
Execute with the minimum.
Execute with Windows size.
Server mode is set at start up.
Communication mode is not set at start up.
Complete communication by executing once.
Start up under the batch mode.
Allow startup of multiple EXEs.
Not allow startup of multiple EXEs.
Infinite timeout is allowed during the session.
Timeout during the session is limited to a value
between 1 and 3600 (= 1 hour). Any value greater than
3600 is automatically set to 3600.
See note below.
Note:
If script is not specified by FLINK from the DT-900 and the session is established under the idle
mode, a timeout will occur if no access is made by the Host PC within the time specified at this
parameter setting (COMMAND_TIMEOUT in Table 13.1). As a result, the session will end because
of “Command Timeout Error”. This error will occur if the communication is executed under the
Single Mode and no command is issued consecutively.
55
14. RS-232C Interface
This chapter describes about the limitations and notes for the installation of RS-232C interface.
14.1 Notes about the Installation
This LMWIN will not establish the session under RS-232C interface if the Power Save Mode is
set to ON at the Host PC.
When you operate the LMWIN, set power save related parameter settings of Power
Management and Power Save functions to OFF for the BIOS and the OS of the Host PC.
Note;
Be sure to check if the default values of the related functions are not set to ON at your desk-top PC.
14.2 Limitation
It may take about 30 seconds to 2 minutes until you have a response if “Execute” →”Session”
→”Abort” is selected or the LMWIN is forced to end.
56
15. SCSI Interface
Since the higher-level commands operate in the same way as the RS-232C interface (version 1.0),
this chapter describes operations and specifications that are specific to the SCSI interface (version
2.0) only.
15.1 Installation
15.1.1 Setup Conditions
Host PC
Make sure that the installed SCSI board in the Host PC and the SCSI interface driver can operate
with the following parameter settings listed in Table 15.1.
Table 15.1
Setup Item
Host adaptor SCSI-ID
SCSI parity check
Host adaptor SCSI termination
Initiate sync negotiation
Enable disconnection
Enable wide SCSI
Enable ultra SCSI
Setup Value
7
Enable
Automatic
No
Yes
No
No
Only the following SCSI boards are recommended to use in your Host P/C, and other manufacturers’
SCSI boards are not recommended by CASIO because of the uncertainty of operability.
Table 15.2
Manufacturer
Adaptec
Bus
Model
AHA2910B
AHA2940AU
AHA2940W
AHA1510B
AHA1520B
AHA1540CP
AHA1542CF
PCI
ISA
Master Cradles
A maximum 7 Master Cradles, with ID numbers ID0 to ID6, can be connected. The ID number 7
must be used by the Host PC.
57
15.1.2 DIP Switch Setting on Master Cradle
Table 15.3 DIP Switch Setting on Master Cradle (DT-965IO-E)
Bit 10
Power supply terminator for the SCSI. These bits are used as terminator.
Bit 9
Both the switches should be set to ON for the last Cradle connected.
Bit 8
SCSI ID numbers, 0 to 6. ID7 is for the Host PC.
Bit 7
Bit 6 is the least significant bit.
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
IrDA communication.
ON : Set if only one Master Cradle is used for FIR communication.
OFF : Set if multiple Satellite Cradles are used for SIR communication, or
if FIR communication is not performed.
Bit3 Bit4
OFF OFF : Normal operation (default setting)
ON OFF : Download
OFF ON : Hardware diagnosis
ON ON : Not permitted
Baud rate for IrDA communication. Bit5 setting does not affect to these baud
rates.
Bit1 Bit2
OFF OFF : 38.4 Kbps
ON OFF : 115.2 Kbps
OFF ON : 230.4 Kbps
ON ON : Not permitted
Should be consistent with the settings on the partner station.
15.1.3 Note about the Installation
This LMWIN is designed to operate with optimum operability even if an optional device other than
the Master Cradles is connected to the same SCSI interface. However, depending on that device’s
nature, the performance of the LMWIN and the communication quality may vary. It is recommended
that before the final installation of the DT-900 system at client side, be sure to check the operability
with the optional device and Master Cradles connected.
15.2 SCSI Cable
The SCSI cables to be used for DT-965IO-E (Master Cradle) and the Host PC are as follows;
Table 15.4
Cable Model
SB-751HF
SB-752HH
SB-753HP
Use
SCSI cable for Adaptec AHA1540CP (ISA bus)
(between DT-965IO-E and Host PC. Centro 50-pin full male)
SCSI cable (between DT-965IO-Es. Centro 50-pin half male)
SCSI cable for AHA2940AU (between DT-965IO-E and Host PC.
Pin type half 50-pin male)
Note:
Cable Models in Table 15.4 are CASIO’s product number.
58
15.3 Bootup
The following steps must be followed when you start up the LMWIN. Otherwise the software may
not operate correctly.
STEP:
1) Turn ON the Master Cradle first connected at the most downstream end from the Host PC and the
Host PC as last to be turned ON.
2) Make sure “A” appears on the LED segment display of each Master Cradle connected and then
boot up the LMWIN by turning ON the power switch on the Host PC.
3) Do not turn ON and OFF the power of any Master Cradle while the Host PC is being switched
ON. If it is absolutely necessary to do that, select “LMSTOP” to terminate the LMWIN, then turn
ON or OFF the power of each Master Cradle. If this happens, restart the LMWIN on the Host PC
after making sure that “A” appears in the LED segment displays.
15.4 Function and Operation
15.4.1 Overview
If the SCSI interface is installed in the Host PC, the LMWIN version 3.0 can operate for multiple
sessions for connected Master Cradles. Each ID number of the connected Master Cradles can be
indicated in progress bar if they are in session with the Host PC.
15.4.2 Selection and Setup for SCSI Interface
The “SCSI interface” option is selected at ”Configure” menu. By setting as “Set As Default” in the
menu, the interface is registered in “device.ini” as the default interface and the interface will be
selected at a time of the LMWIN startup. If “Setting” is selected in the menu, the following display
will appear.
Setup Screen for SCSI Interface
Working Dir
Error Log
Specify a directory to store the script file.
Specify error log file of the LMWIN.
59
15.4.3 Specifying Command Execute/Script Execute
If “Command Execute” or “Script Execute” is selected in the pull-down menu of “Execute”, before
the “Command Execute” or “Script Execute” screen is displayed the “CRADLE Selection” screen
will appear. This screen is used to specify “Command Execute” or “Script Execute” to which Master
Cradle of the connected multiple Master Cradles. The screen will show SCSI-ID check-boxes of the
connected Master Cradles in order of SCSI ID0 to ID6. Select appropriate a check-box (or
check-boxes) that you wish to access. SCSI-ID number and its check-box of any Master Cradles
which are not operable under the LMWIN are indicated in gray color indicating the disability in the
session.
Different “Command Execute” or “Script Execute” for each connected Master Cradle can be issued.
After specifying “Command Execute (or Script Execute)” for a Master Cradle, you can specify
another “Command Execute (or Script Execute)” for other connected Master Cradle. The
operations, however, will be disabled for Master Cradles which are already selected by the Host PC.
The SCSI-ID numbers and their check-boxes will be indicated in gray color.
Operation Flow of Command Execute/Script Execute
Select “Command Execute”
Select appropriate Master
Specify “Command Execute”
or “Sxript execute” in the
Cradle in “CRADLE
or “Script Execute”.
pull-down menu of “Execute”.
Selection” screen.
Select other Master Cradles for “Command Execute” or “Script Execute”.
Fig. 15.1
Selection Screen for Cradle
Select All
Cancel All
OK
Cancel
All indicated Master Cradles are selected.
All checks in the check-boxes are cancelled.
Confirm on selected item and close “Cradle Selection” screen. “Command
Execute” or “Script Execute” screen will follow.
Cancel selected item and close “Cradle Selection” screen.
60
15.4.4 Abort
If “Abort” is selected in the pull-down menu of “Execute”, “CRADLE Selection” screen is
displayed before the session is aborted. This screen is to specify a Master Cradle of the connected
Master Cradles to be aborted. Just follow the same operating procedure described in Chapter 15.4.3
Specifying Command Execute/Script Execute. The operations can be possible for only accessible
Master Cradles. SCSI-ID number and its check-box are indicated in gray if disabled.
Select “Abort” in the menu.
Select appropriate Master Cradle
in the “CRADLE Selection” screen.
Fig. 15.2
15.4.5 Session Establishment
The session between the Master Cradle and the DT-900 being placed on the Cradle will be
established at the following timings. The session once established will not be aborted until the
selection “Execute → Session → Abort” is selected. Selecting “Abort” cannot abort the session.
•
•
When “Execute-Session-Start” is selected in the menu
Server mode
When “Command Execute” or “Script Execute” is selected in the menu.
61
16. TCP/IP Interface
In this chapter, the specific operations, screens and settings of the TCP/IP interface different from
other interfaces are described.
16.1 Installation
16.1.1 Required Environment
On Host PC
• Be sure that the TCP/IP driver produced by Microsoft Corporation is preset in the Host PC and in
operable condition.
• A fixed IP address is assigned.
On Network
• The TCP/IP packet can be transferred normally and its transfer delay is less than 600 msec.
• The ICMP[echo] packet can be transferred normally.
On Master Cradles
• Each Master Cradle has its own fixed IP address.
• Each Master Cradle has IP information being preset.
For further information on how to set IP information in each Master Cradle, refer to the reference
manual of “TCP/IP Master Cradle and IP Information Setting Tool”. As of April 1999, these
manuals are not released.
16.1.2 Number of Master Cradles
The theoretical maximum number of Master Cradles can be connected under the LMWIN is 254.
There is, however, some limitation in the simultaneous communication with multiple Master
Cradles. Refer to Chapter 16.1.3 “Limitation on Simultaneous Communication”.
16.1.3 Limitation on Simultaneous Communication
The hardware performance by the Host PC can affect the simultaneous communication by multiple
Master Cradles. For example, CPU clock speed, CPU its self, the size of installed memory capacity,
network line quality and how the communication is carried out will be factors to define the number.
Recommended maximum number of connected Master Cradles under the LMWIN are 100 which is
assumed to be a medium size for the DT-900 system. The followings are the hardware environment
used for assessing the operability of the system.
Table 16.1
Item
Host PC
HT
Network
Specification
Intel PentiumII 300 MHz, Memory 300 Mbytes, Windows NT 4.0 Server
DT-900
LAN for experiment (10BASE-T)
62
16.1.4 Setup of “ini” File
device.ini
Set up this file for the TCP/IP interface. Set up each of the followings in [ETHERNET] of
“device.ini” in sequential order. For other parameters not listed below, the default values must be
set.
Port number
Format
Default
: PORTNO= port number to specify (in decimal number)
: PORTNO= 50021
Specify a port number of the TCP/IP interface for the LMWIN to receive session request from
Master Cradle. Set the same port to be used for session. Setting the port number can be done in
“Communication Setup Screen” and “device.ini” will be changed accordingly. It is recommended
not to change the number, leave it as the default value (=50021 which is the value set for the Master
Cradle at the factory) as is.
Maximum Number of Master Cradles for Simultaneous Session
Format
Default
: MAX_IO= maximum number of Master Cradles for simultaneous session
: MAX_IO= 100
In such the system configuration that multiple Master Cradles are connected to the same interface,
you can specify a maximum number of Master Cradles for the simultaneous session. For example, if
the parameter is set as “MAX_IO=10” in a system configuration with 20 Master Cradles connected
and suppose 15 of them send session request at the same time, the priority of the simultaneous
session is limited to only the first 10 Master Cradles which made session request earlier. Session
request from the rest of 5 Master Cradles will be ignored and the connection between the last 5 units
and the Host PC will be cut off. When some of the Master Cradles of the first 10 Master Cradles have
completed their sessions, The same number of Master Cradles other than the first 10 Cradles can
establish their sessions with the Host PC.
Because of the limitation of operability by Host PC, a maximum number of Master Cradles for the
simultaneous session should be defined by the ability of each Host PC.
List of IP Addresses for Master Cradles
Format
Default
: [USE_IP]
Master Cradle management number= IP address (in decimal number with dot)
Specify all Master Cradles that are to be connected.
: [USE_IP]
1=192.168.1.1
Specify all IP addresses of the Master Cradles that are to be connected in the network. “Mater Cradle
management number” is a number, between 1 and 254, which must be allocated to each Master
Cradle. Each number must not be used twice. Use smaller number first to allocate. The management
number is used for specifying command for each Master Cradle in the LMWIN so that specifying IP
address of Master Cradle can be avoided.
63
Note:
For any Master Cradles of which IP addresses are not registered, specifying “Command Execute”
and “Script Execute” by the LMWIN and monitoring of statuses of the Master Cradles cannot be
possible. Only specifying “Command Execute” and “Script Execute” by the DT-900 can be
possible.
Setup Example of “device.ini” for TCP/IP interface
--------------------------------------- until here, other settings are written. -----------------------------------[ETHERNET]
PORTNO=50021
/* port number to receive session request from Master Cradles.
*/
MAX_IO=100
/* maximum number of Master Cradles for simultaneous session */
[USE_IP]
/* list of Master Cradle management numbers and IP addresses
1=192.168.1.1
2=192.168.1.2
3=192.168.1.5
8=192.168.1.11
10=192.168.1.30
254=192.168.1.31
64
*/
16.2 Function and Operation
16.2.1 Overview
With the TCP/IP interface, simultaneous session by connected Master Cradles is possible (limited
number of maximum Master Cradles that can achieve the simultaneous session).
The LMWIN can display each status of registered Master Cradle if it is ready to receive session
request from Master Cradles. The progress bar can display the Master Cradle management
number and its IP address of Master Cradle that is currently under session with the Host PC.
16.2.2 Selection and Setup for TCP/IP Interface
In the “Configure” menu, the TCP/IP interface can be selected by clicking on “TCP/IP”. In the same
menu, if you set the TCP/IP interface as “Set as Default”, the setting will be registered in
“device.ini” and the interface will be selected automatically as the LMWIN is started up. The
following display screen will appear when you select “TCP/IP” interface.
Setup Screen for TCP/IP
Port No.
Working Dir.
Error Log
Specify a port number to receive session requests from Master Cradles.
(Set the same port number as the one set for Master Cradle.)
Specify a directory to store the script file.
Specify error log file of the LMWIN.
65
16.2.3 Specifying Command Execute/Script Execute
If “Command Execute” or “Script Execute” is selected in the pull-down menu of “Execute”, before
the “Command Execute” or “Script Execute” screen is displayed the “CRADLE Selection” screen
will appear. This screen is used to specify to which Master Cradle of the connected multiple units the
Host PC will send “Command Execute” or “Script Execute”. The screen will show check-boxes of
the connected Master Cradles in sequential order by following Master Cradle management number
which are registered in “device.ini” file. Select appropriate check-box (or check-boxes) that you
wish to establish. When you move the cursor onto a Master Cradle management number, IP address
of the Master Cradle will be displayed as a tool chip. Different “Command Execute” or “Script
Execute” for each connected Master Cradle can be issued. After specifying “Command Execute (or
Script Execute)” for a Master Cradle, you can specify another “Command Execute (or Script
Execute)” for other connected Master Cradle. The operations, however, cannot be done for Master
Cradles which are already selected. The Management number and its check-box will be indicated in
gray color.
Operation Flow of Command Execute/Script Execute
Select “Command Execute”
Select appropriate Master
Specify “Command Execute”
or “Sxript Execute” in the
Cradle in “CRADLE
or “Script Execute”.
pull-down menu of “Execute”.
Selection” screen.
Select other Master Cradles for “Command Execute” or “Script Execute”.
Fig. 16.1
Cradle Selection Screen
Select All
Cancel All
OK
Cancel
All indicated Master Cradles are selected.
All checks in the check-boxes are cancelled.
Confirm on selected item and close “Cradle Selection” screen. “Command
Execute” or “Script Execute” screen will follow.
Cancel selected item and close “Cradle Selection” screen.
66
16.2.4 Abort
If “Abort” is selected in the menu, “CRADLE Selection” screen is displayed before the session is
aborted actually. This screen is to specify which a Master Cradle of the connected Master Cradles is
to be aborted. Just follow the same operating procedure described in Chapter 15.4.3
“Specifying Command Execute/Script Execute”. The operations can be possible for only accessible
Master Cradles. Management number and its check-box for non-accessible Master Cradles are
indicated in gray.
Select “Abort” in the
Select appropriate Master Cradle
pull-down menu of “Execute”.
in the “CRADLE Selection” screen.
Fig. 16.2
16.2.5 Session Establishment
The session between the Master Cradle and the DT-900 being placed on the Master Cradle will be
established at the following timings. At the same time, the Cradle monitoring panel will be displayed
on the Host PC. The session once established will not be aborted until the selection “Execute →
Session → Abort” is selected. Selecting “Abort” cannot abort the session.
When “Execute-Session-Start” is selected in the menu
Server mode
When “Command Execute” or “Script Execute” is selected in the menu.
67
16.2.6 Cradle Monitoring Panel
When the LMWIN is ready to receive session request from the Master Cradles, the status of each
Master Cradle of which its IP address is registered in “device.ini” file will be displayed. The status
will consist of management number and indicator in color to indicate the status. Status of all
registered Master Cradles will be displayed. Selection on particular Master Cradle can be done by
moving the cursor onto the check-box. Selected check-box will indicate the IP address as a tool chip.
When the Cradle monitoring panel appears on the display, all the indicators become black color and
then gradually connection check status will reflect each indicator on the display. This process begins
from the smallest number first and the largest number as last. “Ping executing” appears while the
process continues.
Example of Cradle Monitoring Panel
PING
: Check Cradle connection again.
Meaning of Indications on Monitoring Panel
Table 16.3
Color
Blue
Black
State
Ping success
Ping failure
Timing of display
After the beginning of panel
Session check – normal
Session check – abnormal display and the “Pin Execute”
button is depressed, each
status of the Master Cradles is
displayed. Except, status of
Master Cradle that is flashing
in green color.
After the session is complete.
While the session continues with DT-900.
After the session is complete anomaly.
Yellow
Session is complete.
Green in flash Session continues.
Red
Session is abnormal.
Note:
The session check will check a result of ICMP(echo) packet transmission to specified IP address and
its response. For example, if a confirmation was not returned within one second after the ICMP
(echo) was transferred to specified IP address, the check result will indicate as “anomaly”.
68
17. Other Errors
17.1 Errors under SCSI and TCP/IP Interfaces
17.1.1 Errors Caused by Simultaneous Communication
“File being Accessed”
The error occurs because a currently opened file is accessed again. When you have this kind of error,
follow instruction described in the table below so that such the error can be avoided.
Examples:
Writing a file with the same file name as one already being existed is attempted in the same
directory.
Writing a file with the same file name as one already being read is attempted in the same
directory.
Table 17.1
Multiple accesses to the same file on the Host PC
Transmission to the DT-900 while the Host PC is already transmitting.
Transmission to the DT-900 while the Host PC is receiving (or receiving append
file)
Reception (or reception of append file) by the Host PC while the Host PC is
transmitting.
Reception (or reception of append file by the Host PC while the Host PC is
receiving.
Reception of append file by the Host PC while the Host PC is receiving append
file.
Reception of append file by the Host PC while the Host PC is receiving.
Execution of child process.
Status
OK
Error
Error
Error
OK
Error
OK
17.1.2 Other Errors
“Command Timeout Error”
Besides the causes described in the Note of Chapter 13 ”Format of LMWIN.INI”, this error may
occur if the SCSI interface is abnomal. If such the error occurs, close the LMWIN and start up it
again. Or, close the LMWIN, turn OFF the Host PC and the Master Cradles, and start up all again.
“Cradle hang-up, Please reset scsi Idx”
This error indicates that the Master Cradle with the ID number “x” has fatal error. The
communication with the Master Cradle becomes disabled. Close the LMWIN and start up it again.
Or, close the LMWIN, turn OFF the Host PC and the Master Cradles, and start up all again. Make
sure that the Master Cradle with ID no. “x” indicates “A” on the LED segment display after turning
OFF and ON the power.
69
“Bind Error”,”Accept Error”,”Listen Error”
The errors are returned by the driver of either TCP/IP interface or SCSI interface.
Close the LMWIN and start up it again. If the remedy procedure does not recover from the error
state, close the LMWIN, turn OFF and ON the Host PC. If the same error continues to appear, check
the driver of SCSI interface or TCP/IP interface.
If the TCPIP interface is used, using with “netstat.exe” check if port number specified in the
configuration setting of the LMWIN is already used or not. If the port number is used by other
software, change the number to other port number for the software. Or, the port number used for the
LMWIN can be changed to other port number. Be sure to set the same port number to the setting for
the Cradles (changing the port number only for the LMWIN and not for the Cradles will cause error.)
17.2 Year 2000 Compliance
This LMWIN software is compliant with the year 2000. However, because of the limitation with the
C library (ANSI specifications) which is employed to develop the LMWIN, date and time on or after
January 18th 2038 cannot be handled. Thus, the LMWIN shall be recommended to use before
January 18th 2038.
70
18. File Check Utility
18.1 Development Concept
Because of careless mistakes by a program installer during the installation of the DT-900 system and
application programs, often the installation error is brought to light because system errors occurred
during operation by the user. Below are some of the actual problems that had occurred.
On an installation that extended over multiple cards, the postal number dictionary (POST.DIC)
was not installed. Subsequently, when a business application tried to convert a postal number, an
error occurred because the dictionary was not present.
On an installation for updating the driver a compatibility fault often occurred. It occurred
because the driver had not been updated and this fact was not checked at all.
When the application program was transferred for installation, one of the transfer packets was
omitted, resulting in an error at subsequent execution of the application program.
To prevent the above problems from happening again at your side this File Check Utility has
been created.
18.2 Purpose
The File Check utility is used, by both SE and user's system section, to ensure that installation is
properly completed. This will prevent the above described problems from occurring. Moreover,
problem such as (3) above, can now be avoided because the specification of the file transfer protocol
has been improved.
18.3 Scope
This File Check utility is capable of finding any installation error irrespective of the file transfer
method used for installation. The transfer method is the way the file is transferred between the Host
PC and the DT-900 (HT), and between DT-900s. The term "Host PC" includes a personal computer
(PC) and any DT-900 to emulate as PC.
71
18.4 Terminology
The following abbreviations are used in these chapters (Chapter 18 to 24) to describe specific model
name or software program.
Table 18.1
Abbreviation
PC (Host PC)
HT
FCHK.EXE
AP
HFC
LM
Cradle
Description
Personal computer (IBM PC/AT 100% compatible)
DT-900
File Check utility
Application program
High-performance File Copy program
Link Manager
Satellite Cradle (DT-964IO-E)
Host PC
RS232C cable
DT-900
DT-900
IrDA
Cradle
Cradle
DT-900
IrDA
Cradle
DT-900
IrDA
Cradle
Fig. 18.1
72
19. Operation Environment
The File Check utility must be used under the following operating environment.
File transfer between the Host PC and the DT-900
Note :
The system configuration (Fig. 18.1) described on the previous page is only one example of
PC-Cradle connections and does not limit all the possibilities that the DT-900 system has.
Table 19.1 Host PC
Operable model
IBM PC/AT compatible model
Operating System
MS-DOS (Ver.6.2 or later)
Program name
FCHK.EXE
Memory capacity
640 Kbytes or greater
Table 19.2 HT
Model
DT-900
Operating System
ITRON
Program name
Communication utility (FCHK function)
Memory capacity
Secured for OS
File transfer between DT-900s
IrDA
DT-900
Fig. 19.1
DT-900
Table 19.3 HT
Model
DT-900
Program name
Communication utility (FCHK function)
73
20. Functions
20.1 Operation Procedure
Use the File Check utility according to the following procedure. Here, the procedure is described
assuming that an application is installed from the Host PC to the DT-900.
(1) At the transmission side of PC (master side), set the file to be downloaded (copied).
(2) Specify the downloaded (copied) file using the script file, then direct the script file so that it
transmits a list file (FCHK.LOG).
(3) Create the list file using the File Check utility on the PC, as follows :
FCHK
/G /SC <Script file name> <Destination directory name>
The FCHK.LOG file is created (FCHK.LOG file = list file) .
(4) At file transfer via HFC, also transfer the FCHK.LOG file to the partner station.
(The FCHK.LOG file will be copied at the same time the target file is copied.)
(5) Start up the File Check utility at the reception-station side (duplication side), and check that the
transferred (copied) file and list file (FCHK.LOG) have been received (copied) properly. If the
check result is OK, this operation will terminate normally at error level 0, otherwise, it will
terminate abnormally at an error level other than 0.
FCHK /C A:\FCHK\FCHK.LOG
If error level 1 goto err
74
20.2 Detailed Functions
The File Check utility has the following functions :
List file creating function
List file comparing function
20.2.1 List File Creating Function
Command Option
FCHK /G [/Option] <file name list or Script file name> <Destination directory name>
[FCHK.LOG File output Directory name]
Function
Specifies the file name to be transferred (copied) from the Host PC or the DT-900, and creates a list
file that contains the list of all file names to be transferred (copied) and the check-sum data
calculated for all the files. In addition, it creates the check-sum data of the list file. The list and
check-sum data creation process will be displayed on the screen. The list file name created by this
function is set to FCHK.LOG, and it will be located under the current directory, if the output
destination is not specified. In file transfer (file copy) the user should transfer (copy) the list file
created by this function to the partner station (duplication side).
The following information should be included in the list file.
● File size
● Date and time of creation
● Transfer (copy) destination path (file) name
● Number of transferred (copied) files
● Check-sum data of all the transferred (copied) files
● Check-sum data of the list file
The check-sum for all the transferred (copied) files will be calculated in such a way that the data
sections of all the transferred (copied) files are exclusive ORed for each double-word length.
For the check-sum of the list file, its contents will be successively added (ANDed) for each doubleword length, and a value, which can offset this result to zero if it is added, will be employed as the
check-sum data.
The check-sum data will be outputted as follows ;
FILE_CHECKSUM=HHHHLLLL ( HHHH: HiGHT-WORD / LLLL: LOW-WORD )
LIST_CHECKSUM=HHHHLLLL ( HHHH: HiGHT-WORD / LLLL: LOW-WORD )
If an error occurs during the execution of this function, the existing list file (LOG file so far made at
this point in time) will not be deleted provided that the error occurs during the creation of list file.
However, the existing list file will not be deleted because of errors that occur during the command
parameter analysis process.
75
Options
/G :
/SC :
Creates a list file (FCHK.LOG). (This is MUST.)
Specifies the script file name.
A file name that is specified by the parameter is the script file. FCHK.EXE will analyze the file
name to be transferred against this script file, then a list file will be created.
/R
:
Specification of recursive call
All files under the directory of the file path name specified by the parameter will be assumed to be
the objectives of the list file creation. If the specified directory has sub-directories, the list file will
be created from the file names added with the sub-directory names. Even if this option is specified,
specify the file names using their full path names in the file name list. If this option is not specified,
only the files that are specified in the file name list can be the objectives of the file list creation.
/AO
:
Additional output
If the FCHK.LOG file exists in the directory specified by [FCHK.LOG file output directory name],
this file will be appended with additional logs. If it does not exist, a new FCHK.LOG file will be
created. However, if the specified directory does not exist, the operation will be abnormally
terminate (Error code : 0x13 Output path name for the specified list file is not found.).
Parameter
<File name list or Script file name >
To create the list file, describe the file name list of files to be transferred (copied). Specify the file
name at the transfer-side (copy-side) using its full path name. If multiple file names are specified at
the transfer-side (copy-side), separate the path names with a double-colon ("::"). File names can be
specified using a wild card. If the /SC option is specified, specify the path name under which the
script file exists. (For information about the specifications for the script file syntax, refer to Chapter
22 "Syntax Analysis of Script Files", and Chapter 11 "Syntax of Script File Commands".)
<Destination directory name>
Specify the directory name of the transmission destination (copy destination). The directory name
must include the drive name. The delimiter character of the directory name should be " \ ".
Example:
b:\
(Specification of root directory)
b:\PA\12KAI\ (Specification of sub-directory)
b:\PA
(Incorrect specification)
Note:
If the "/SC" option has been specified, this parameter will become invalid.
76
[FCHK.LOG file output directory name]
Specifies the output destination directory name of the FCHK.LOG file. The directory name must
include the drive name. The delimiter character of the directory name should be " \ ". If this
parameter is not specified, the FCHK.LOG file will be created under the current directory.
Example:
b:\
(Specification of root directory)
b:\PA\12KAI\ (Specification of sub-directory)
b:\PA
(Incorrect specification)
Restrictions
1. The number of objective files of collecting logs is limited to 65,000. If log collection exceeds
over 65,000 files, the operation terminates abnormally.
2. The file size of a script file should be a maximum of 32,000 bytes. If a script file is specified to
contain more than 32,000 bytes, the operation terminates abnormally.
20.2.2 List file Comparison Function
Command Option
FCHK /C <FCHK.LOG file path name>
Function
Performs the following verifications by comparing the file information of the files transferred
(copied) from the partner station (master side) with the contents of the list file (FCHK.LOG),
by calculating the check-sum data of the list file and comparing the result with that on the
transferred list file, and by calculating the check-sum data of all the files transferred (copied)
and comparing the result with the check-sum data in the list file.
The comparison process and results are displayed on the screen. If the comparison results are
correct, this operation will terminate normally at error level 0, which is used as the program
termination code, otherwise, it will terminate abnormally at an error level other than 0.
The following file information should be compared.
• File size
• Date and time of creation
• Transfer (copy) destination path (file) name
• Number of transferred (copied) files
• Check-sum data of all the transferred (copied) files
• Check-sum data of the list file
The check-sum for all the transferred (copied) files will be calculated in such a way that the data
sections of all the transferred (copied) files are exclusive ORed for each double-word length. For the
check-sum data of the list file, the contents will be successively added (ANDed) for each
double-word length, and a value, which can offset this result to zero if it is added, will be employed
as the check-sum data.
77
Option
Compares with the /C : list file (FCHK.LOG).
Parameter
<FCHK.LOG file path name>
Specifies the path name under which the list file (FCHK.LOG) exists.
Restriction
There can be a maximum of 65,000 files compared. If the value of " FILE_NO = " is greater than
65,000, operation terminates abnormally.
78
20.3 Format of List File
The list file created by the File Check utility should have the following format.
<FCHKLOG> :: = <FILENO> <FILEINFO> <FILECHECKSUM> <LISTCHECKSUM> null
<FILENO> :: = FILE_NO= <dec_num> <LS>
<FILEINFO> :: = <INFO> <LS>
<INFO> :: = <PATH> SP <SIZE> SP <DATE>
<LS> :: = CR
<FILECHECKSUM> :: = FILE_CHECKSUM= <hex_char> <LS>
<LISTCHECKSUM> :: = LIST_CHECKSUM= <hex_char> <LS>
<dec_num> :: = decimal number
<hex_char> :: = hexadecimal number represented in characters.
Example :
FILE_NO=3
A:\AP\MENU.EXE 12345 19960728-0630
A:\CONFIG.SYS 1000 19960308-2058
A:\AUTOEXEC.BAT 512 19960206-2340
FILE_CHECKSUM=XXXXXXXX
LIST_CHECKSUM=XXXXXXXX
20.4 Common Specifications to Each Function
If "Ctrl+C" keys are pressed during the creation of list file or during the comparison of list file, the
processing continues without interruption.
Note :
In some cases where the "Ctrl+C" (or STOP) keys are pressed, a " ^C " may appear in the display of
the progress percentage data, and the data display may be duplicated.
79
21. Screen Images of Operations
21.1 List File Creation
Host PC
DT-900
A:\>FCHK /G C:\AUTOEXEC.BAT::C:\CO
NFIG.SYS::C:\PROGMAN.EXE::C:\PROG
SUB1.EXE::C:\MASTER.DAT A:\
*** FCHK VER1.00 ***
FCHK.LOG Create
0
C:\PROGMAN.EXE
|* * * * * ·····|
50%
100
C:\AUTOEXEC.BAT
C:\CONFIG.SYS
C:\PROGMAN.EXE
A:\>FCHK /G C:\AUTOEXEC.BAT::C:\CO
NFIG.SYS::C:\PROGMAN.EXE::C:\PROG
SUB1.EXE::C:\MASTER.DAT A:\
*** FCHK VER1.00 ***
C:\MASTER.DAT
|* * * * * * * * * *|
0
100
C:\AUTOEXEC.BAT
C:\CONFIG.SYS
C:\PROGMAN.EXE
C:\PROGSUB1.EXE
C:\MASTER.DAT
File Count : 5
ErrorCode =00
The making of a list file completed.
A:\>
80
100%
21.2 List File Check
Host PC
DT-900
A:\>FCHK /C
*** FCHK VER1.00 ***
FCHK.LOG compare
0
A:\PROGRAM.DAT
|* * * * * ·····| 50%
100
A:\AUTOEXEC.BAT
A:\CONFIG.SYS
A:\PROGMAN.EXE
A:\MASTER.DAT
A:\>FCHK /C
*** FCHK VER1.00 ***
FCHK.LOG compare
0
100
* * * * * * * * *| 100%
A:\AUTOEXEC.BAT
A:\CONFIG.SYS
A:\PROGMAN.EXE
A:\PROGSUB1.EXE
A:\MASTER.DAT
File Count : 5
ErrorCode =00
The contents of the list file agreed.
A:\>
81
A:\>FCHK /C
*** FCHK VER1.00 ***
FCHK.LOG compare
0
100
A:\AUTOEXEC.BAT
A:\CONFIG.SYS
A:\XXXXXXXX.XXX
ErrorCode =07
The contents of the list file didn’t agree.
(All the file checksum data discord)
A:\>
82
22. Syntax Analysis of Script Files
If a script file name is specified when the list file creation function is executed, it will analyze the
syntax of the script file, then create the list file. The specifications of the script file syntax are given
below.
<SCRIPT FILE> :: = <COMMANDS>
<COMMANDS> :: = <COMMANDS> <COMMAND>
<COMMAND> :: =
/
<CMDBODY>
<CMDBODY> :: = <APPEND>
| <CHILD_PROC>
| <DELETE>
| <FORMAT>
| <BEEP>
| <RENAME>
| <RECEIVE>
| <SEND>
| <PRINT>
| <TIME_ADJUST>
| <END_SESSION>
| null
<LS>
<APPEND> :: = <APPEND_CMD> <APPEND_OPTION> <SP> <PATHNAME_PAIR>
<CHILD_PROC> :: = <CHILD_PROC_CMD> <SP> <CMD_PARAMETER>
<FORMAT> :: = <FORMAT_CMD> <SP> <DRIVE>
<BEEP> :: = <BEEP_CMD>
<RENAME> :: = <RENAME_CMD> <SP> <PATHNAME_PAIR>
<RECEIVE> :: = <RECEIVE_CMD> <OPTIONS> <SP> <PATHNAME_LIST>
<SEND> :: = <SEND_CMD> <OPTION> <SP> <PATHNAME_LIST>
<PRINT> :: = <PRINT_CMD> <SP> <STRING>
<TIME_ADJUST> :: = <TIME_CMD> <SP> <TIME_VALUE>
<END_SESSION> :: = <END_CMD> <PARAM>
<APPEND_CMD> :: = 'A'
<CHILD_PROC_CMD> :: = 'C'
<FORMAT_CMD> :: = 'F'
<BEEP_CMD> :: = 'B'
<RENAME_CMD> :: = 'N'
<RECEIVE_CMD> :: = 'R'
<SEND_CMD> :: = 'S'
<PRINT_CMD> :: = 'P'
<TIME_CMD> :: = 'T'
<END_CMD> :: = '/'
<PATHNAME_PAIR> :: = <PATHNAME> <DELM> <PATHNAME>
<CMD_PARAMETER> :: = <CMD_NAME> <STRING>
<CMD_NAME> :: = <PATHNAME>
<PATHNAME_LIST> :: = <PATHNAME> <DELM> <PATHNAME_LIST> | <PATHNAME>
<DRIVE> :: = <DRIVE_LETTER> ':'
83
<TIME_VALUE> :: = <DATE> <TIME>
<OPTIONS> :: = <OPTIONS> <OPTION> | null
<OPTION> :: = <RECURSIVE_OPTION> | <UPDATE_OPTION>
<RECURSIVE_OPTION> :: = 'R'
<UPDATE_OPTION> :: = 'U'
<APPEND_OPTION>::='S' | 'R'
<STRING> :: = ""<CHARS>""
<DELM> :: = <SP>
<LS> :: = CR | <SP>
<SP> :: = <SP> SP | SP
<PARAM> :: = <SP> <NUMBER>
This File Check utility searches <CMD_BODY> in the script file, and if it finds <CMD_BODY>
followed by <SEND> (='S': See Note below, it judges <PATHNAME_LIST> that follows <SEND>
as the destination path name and creates the list file (FCHK.LOG). Other <CMD_BODY> without
being followed by <SEND> will be ignored.
Note :
The following commands/options can be the objectives of creating the list file.
•
•
•
•
•
"/S"
"/SO"
"/SR"
"/SOR"
"/SRO"
84
23. Installation Method of File Check Utility
23.1 For Host PC
The File Check utility at the Host PC will be installed as if a DOS command is installed.
23.2 For DT-900
The File Check utility for the DT-900 will be installed as part of the DT-900 communication utility.
Since the installation to the DT-900 will be executed as a function, a file check (FCHK) function
must exist. This file check function must be supported by the user, however, it can be accessed either
from the user application or the System Menu. The following pages describe the interface
specifications of the file check function.
85
Title
Creating FCHK list file
Function
cu_fchklog_Create
Function
Creates the specified number of FCHK list files.
In the FCHK list files the following information will be created for the specified files.
(1) File path name (including the destination directory name of file transfer), (2) Date of creation, (3) Time of
creation, (4) File size, (5) Check-sum data of all the specified files, (6) Check-sum data of FCHK list file.
A graph to show the progress of FCHK list file creation can be displayed on the screen if specified by the parameter.
C-language Interface
[Calling sequence]
ER ercd = cu_fchklog_Create (H mode, B *fName, B *dir, B *listdir, H append,
CU_GRAPHSET *graphSet)
[Input Parameters]
H
mode
: File specification mode (Specify whether recursive call is used.)
CU_DIR_NORMAL:No recursive call used. CU_DIR_RECURSIVE: Recursive call used.
B
*fName
: Transfer file name list area (Multiple specifications and wild-card specification are permitted.)
B
*dir
: Transfer destination directory name area (Neither multiple specifications nor wild-card
B
*listdir
: Directory name under which FCHK list is created (Neither multiple specification nor wild-card
H
append
:
specification is permitted.)
specification is permitted.)
Append option (Specifies an append to the existing FCHK list file.)
CU_FCHK_CREATE: Creates anew.
CU_FCHK_APPEND: Appends to existing file.
(To be newly created if an existing file is present under the list file creation directory, if append
is specified.)
CU_GRAPHSET
*graphSet : Graph display information
typedef struct{
H
graphMode : Graph display mode
CU_GRAPH_ON_1: Indicates the percentage of progress with the whole list file
creation process being 100%.
CU_GRAPH_OFF : Does not indicate.
The following parameters will not be referenced except when CU_GRAPH_OFF is being set.
H
graphPos
: Top line of file name display (0 to 11)
H
graphCol
: Top column of file name display (0 to 25)
H
graphName : File name display flag (Specify whether full-path names or file names only are used.)
CU_GRAPH_NM_PATH : Full-path names
CU_GRAPH_NM_FILE
H
graphLine
: File names only
: Number of lines of file name area (1 to 12)
}CU_GRAPHSET;
[Return Parameters]
ER
ercd
: Processing status
FCHK_OK
: Normal
FCHK_NG0
: Specified path name not found
FCHK_NG02 : List file creation error
FCHK_NG03 : FCHK.LOG not found
FCHK_NG0D : Parameter error
Remark:
[Relevant functions]
cu_fchklog_Check
86
Title
Verifying FCHK list file
Function
cu_fchklog_Check
Function
Verify the contents of the FCHK specified by path with the file contents of the FCHK list file.
The followings are verified ;
(1) File path name (including the destination directory name), (2) Date of creation, (3) Time of creation,
(4) File size, (5) Check-sum data of all the specified files, (6) Check-sum data of FCHK list file.
A graph to show the progress of FCHK list file creation can be displayed on the screen if specified by the parameter.
C-language Interface
[Calling Sequence]
ER ercd = cu_fchklog_Check (B *listdir, CU_GRAPHSET *graphSet)
[Input Parameters]
B
*listdir
: Directory name under which FCHK list is created
(Neither multiple specifications nor wild-card specification is permitted.)
CU_GRAPHSET *graphSet : Graph display information
typedef struct{
H
graphMode : Graph display mode
CU_GRAPH_ON_1: Indicates the percentage of progress, with the whole list file
creation process being 100%.
CU_GRAPH_OFF : Does not indicate.
The following parameters will not be referenced except when CU_GRAPH_OFF is being set.
H
graphPos
: Top line of file name display (0 to 11)
H
graphCol
: Top column of file name display (0 to 25)
H
graphName : File name display flag (Specify whether full-path names or file names only are used.)
CU_GRAPH_NM_PATH : Full-path names
CU_GRAPH_NM_FIL
H
graphLine
: File names only
: Number of lines of file name area (1 to 12)
}CU_GRAPHSET;
[Return Parameters]
ER ercd
: Processing status
FCHK_OK
: Normal
FCHK_NG03 : FCHK.LOG not found
FCHK_NG04 : The content of List file not matched (path name not matched)
FCHK_NG05 :The content of List file not matched (file size not matched)
FCHK_NG06 :The content of List file not matched (Date/Time not matched)
FCHK_NG07 : The content of List file not matched (All file check-sum data not matched)
FCHK_NG08 : The content of List file not matched (File check-sum data not matched)
FCHK_NG0B : Error at List file reading in
FCHK_NG0D : Parameter error
Remark:
[Relevant functions]
cu_fchklog_Create
87
24. Error Messages/Codes from File Check Utility
The following messages can be given.
Table 24.1
Code
Message
00
The making of a list file completed.
The contents of the list file agreed.
01
Specified path name not found.
02
The list file making error.
03
FCHK.LOG not found.
04
05
06
07
08
09
0A
0B
0C
0D
10
11
12
13
FF
Meaning
Normal termination
The contents of the list file didn’t
agree. (The path name discords)
The contents of the list file didn’t
agree. (The size discords)
The contents of the list file didn’t
agree. (The date/the time discord)
The contents of the list file didn’t
agree. (All the file check-sum data
discord).
The contents of the list file didn’t
agree.
(The list file check-sum data discord)
A script file not found
The script file syntax error
The list file read error
It is an unjust option.
The parameter error.
Script file read error
It crossed limitation on the script file
size.
It crossed limitation on the number
of the log files.
The output path name of the specified
list file wasn’t found out.
The operation model is different.
The version of DOS is different.
88
File name specified by the list file does not exist.
Physical error occurs during list file creation.
List file (FCHK.LOG) could not be found by the list
file check.
Verification result of list file checks is not matched.
(No path name matched)
Verification result of list file checks is not matched
(No size matched)
Verification result of list file checks is not matched
(No date/time matched)
Verification result of list file checks is not matched.
(No all file check-sum matched)
Verification result of list file checks is not matched
(No check-sum data of the list files matched)
Script file with the specified file name was not found.
Specified script file includes a syntax error.
Physical error occurs during list file check when the
list file (FCHK.LOG) was being read.
Start-up option is illegal.
Specified parameter has an error.
Error occurs in the process of reading a script file.
The size of specified script file is 32,000 bytes or
greater.
There are 65,000 files or more that can be used as the
log files.
Output destination path name of the specified
FCHK.LOG file was not found.
Executed under an earlier version of the DOS than ver
6.2.