*FDownload,A
DOWNLOAD  FILE dialog box is used to download an object  file  to
MICE memory. The object file may be of an Intel hex, Intel binary
(OMF), Motorola S or Tektronix hex. After downloading, the symbol
table file specified in the "Filename" field is then automatical-
ly loaded.

The "Mode" field can be  accessed only if USD-III is  linked with
MICE-16 68000,  MICE-16 80286 or MICE-32 80386.  Otherwise,  this
field is skipped.
*DownFilename,A
Download  object filename must be entered in this field  in order
to invoke the "Download" command.
*DownloadFormat,A
If USD-III is linked with MICE-16 68000, select applicable memory
space  format provided in the choice list. The options are:  User
Program (UP); User Data (UD); Supervisor Program (SP); and Super-
visor Data (SD).

If USD-III is linked with MICE-16 80286 or MICE-32 80386,  select
applicable mode format. "Protected Mode" will load the Descriptor
Table and cause  MICE  to enter into Protected Mode.  "Real Mode"
will download data in Real Mode.
*FInclude,A
INCLUDE COMMAND FILE dialog box is used to execute a user-defined
command  file. When "Include" command is executed, the  variables
(%0...%9)  specified  in the user-defined command  file  will  be
substituted with the arguments entered in this dialog box.
*IncludeFilename,A
To execute "Include" command, the user-defined command file file-
name  containing the specified variables (%0...%9), must  be  en-
tered in this field.
*IncludeArgument,A
During execution of "Include" command, if Arguments (e.g.,  MICE/
USD-III commands, command  parameters,  nested commands,  macros,
values,  etc.)  are specified in the "Argument" field,  the Argu-
ments  will  substitute the variables  (%0...%9)  defined in  the
command file. Arguments must be entered separated by commas  (NOT
spaces) and enclosed in parentheses.

                Example: (100,10,200,8F,0,3FFFF)
*FJournal,A
Journal's  LOG OUTPUT FILE dialog box logs all  COMMAND  viewport
activities (input and responses) to a designated filename as they
took place during a debugging session.
*JournalFilename,A
Enter a  filename in  this field to store the logged COMMAND view
-port activities. If it is a new filename, it will be created. If
it is an existing filename, the stored data may be overwritten or
appended depending on the option specified in the "Append" field.
If no filename is entered, the existing journal filename (if any)
and the journal toggle status will display.
*JournalAppend,A
If  an existing filename has been designated to log  the  COMMAND
viewport activities, instruction must be given whether to  append
the  newly  logged activities into the existing  filename  or  to
overwrite  the existing data with the newly logged  data.  Select
appropriate (Yes/No) instruction with <space-bar>.
*FLog,A
LOG  COMMAND FILE dialog box is used to  log all  commands  to an
assigned  filename  as  they  are  entered  and executed during a
debugging session.
*LogFilename,A
Enter a  filename in  this field  to store the logged commands as
they are  entered and executed in a debugging session. If it is a
new filename, it will be  created. If it is an existing filename,
the stored data may be  overwritten or  appended depending on the
option specified in the "Append" field. If no filename is entered
the existing log filename (if any) and the log toggle status will
display.
*LogAppend,A
If  an existing filename has been designated to log  the  entered
and executed  commands, instruction  must  be  given  whether  to
append the newly logged commands into the existing filename or to
overwrite the existing  data with  the newly  logged data. Select
appropriate (Yes/No) instruction with the <space-bar>.
*FUpload,A
UPLOAD FILE dialog box uploads object code from MICE to a  speci-
fied filename.

The "Memory Type" field can be accessed only if USD-III is linked
with MICE-16 68000 or MICE-II 8051/8052. Otherwise, this field is
skipped.
*UpFilename,A
When  uploading object code from MICE, a disk file filename  must
be assigned to store the object code. Enter the filename in  this
field.
*UploadFormat,A
When uploading object code from MICE with USD-III linked to MICE-
32 68030, MICE-16 68000 or MICE-II 8051/8052, the "Memory Type" 
choice list will display  a selection of memory types. Select 
memory  type  appropriate for the MICE model involved.
*MChecksum,A
MEMORY CHECKSUM dialog box will accomplish checksum when the  me-
mory  location where the checksum operation is to begin  and  the
last memory location where the checksum is to be carried out  are
specified.
*ChecksumBegin,A
Memory  checksum will begin at the memory location  specified  in
this field.
*ChecksumEnd,A
The block of memory checksum will end at the memory location spe-
cified in this field.
*MCompare,A
MEMORY COMPARE dialog box  compares two defined  blocks of memory
when the start and end address of the first block are  specified.
Only  the start address is needed to be specified for the  second
block.
*CompBegin,A
Memory  compare will begin at the starting address of Block 1  as
specified in this field.
*CompEnd,A
Memory compare will end at the last address of Block 1 as  speci-
fied in this field.
*CompDest,A
The starting address of the second block in memory comparison  is
specified in this field.
*MCopy,A
MEMORY  COPY dialog box is used to copy the content of  a  memory
block  to another within emulation or target memory. It  is  also
used  for copying a memory block from target memory to  emulation
memory.
*CopyBegin,A
The first location in the memory block to be copied is  specified
in this field.
*CopyEnd,A
The  last location in the memory block to be copied is  specified
in this field.
*CopyDest,A
Copies  the contents of the memory block specified in  the  above
fields to the block beginning at the memory location specified in
this field.
*MDisassembly,A
MEMORY DISASSEMBLY dialog box disassembles and displays the  con-
tents of the memory, one page (16 statement line) at a time.  The
starting  and end address of the memory contents must  be  speci-
fied,  otherwise  disassembly will start at the  current  program
counter (pc).
*DisASMBegin,A
The  first memory location where disassembly is to begin, is  en-
tered in this field.
*DisASMEnd,A
The  last memory location where disassembly ends, is  entered  in
this field.
*MDump,A
MEMORY  DUMP dialog box will display the contents of a  specified
block of memory.

If no address is specified, memory display will start at the cur-
rent  program counter (pc). If the starting address is  specified
and no end address is given, the contents of memory  will display
one page (256 bytes) at a time. The message "[MORE]" will  appear
at the bottom of each page. Press <CR> to view the next page.
*DumpBegin,A
Memory Dump execution will begin at the address specified in this
field.
*DumpEnd,A
Memory  Dump execution will end at the address specified in  this
field.
*MFill,A
MEMORY FILL dialog box fills a specified memory block with a par-
ticular value or string.
*FillBegin,A
Memory  Fill  execution begins at the address specified  in  this
field.
*FillEnd,A
Memory Fill execution ends  at  the  address  specified  in  this
field. 
*FillData,A
The  desired memory fill value or string in 1 to 32 bytes  format
is specified in this field.
*MSearch,A
MEMORY  SEARCH dialog box searches a particular value  or  string
within  the boundary of a specified memory block.
*SearchBegin,A
Memory  Search execution begins at the address specified in  this
field.
*SearchEnd,A
Memory  Search  execution ends at the address specified  in  this
field.
*SearchData,A
The desired memory search value or string in 1 to 32 bytes format
is specified in this field.
*MTest,A
MEMORY  TEST dialog box performs test operation on each  location
of a specified memory block.
*TestBegin,A
Memory  Test  execution begins at the address specified  in  this
field.
*TestEnd,A
Memory Test execution ends at the last address specified in  this
field.
*ODefine,A
DEFINE SOFTKEY dialog box is used to define function-keys <Shift-
F1>  to <Shift-F10>) as the key macros to substitute one or  more
chained standard commands.

To execute  a  key  macro, press  <Shift>  and  the  function-key
defined with the desired chained commands.
*DefineCommand,A
Enter the  command or the chained commands delimited by ";"  into 
this field.
*OUpdate,A
UPDATE  VIEWPORT dialog box shows the current status of data  up-
dates on BREAKPOINT, CODE, REGISTER, STACK and TRACE viewports. A
check mark (V) prefix means the update feature is ON for the  in-
dicated viewport.

Disabling  viewport update feature will speed-up USD-III commands
execution.
*UpdateField,A
To  enable/disable  the  update  feature in  this viewport, press
<space-bar>  toggle.  Note  that  the check mark (V) prefix is ON
when update is enabled and OFF when update is disabled.
*SMap,A
MEMORY MAP dialog box maps a defined block of memories.  Possible
attributes of the block to be mapped must also  specified.  If no
memory block is defined, the current map setting will display.
*MapBegin,A
Define  the starting  address of the  block to  be mapped in this
field.
*MapEnd,A
Define the end address of the block to be mapped in this field.
*MapAttribute,A
If  attributes are required for the defined block of  memory  for
mapping, enter the attributes in this field. If MICE-III 68000 or
MICE-III 68302 is connected, memory bank number should be set in 
the Attribute field.
*TBackward,A
BACKWARD TRACE dialog box starts real time emulation of the  tar-
get and immediately begins recording target status until the spe-
cified  trigger  address is reached. Emulation stops  when  trace
stops.  Target CPU may however  continue to run if the "Run after
trace ends" is toggled to "YES".

Options to specify a number of times the target condition has  to
be matched before trace stops is provided. A single qualifier may
also  be specified to choose the type of CPU activity  associated
with the trigger address.

Note that this command is NOT applicable to MICE-8/16/32.
*BackRunends,A
This  field uses <space-bar> to "YES/NO" toggle to  continue/dis-
continue running emulation after it stops when trace stops. 

*BackAddx,A
Backward trace starts real time emulation of the target and imme-
diately begins recording target status until the trigger  address
specified in this field is reached.
*BackCount,A
Specify a number of times the target condition has to be  matched
before trace stops in this field.
*BackQualifier,A
A single qualifier may also be specified in this field to  select
the  type  of CPU activity associated with the  trigger  address.
Note  that "Backward Count" must be pre-specified  before  speci-
fying a qualifier.
*TEvent,A
EVENT SETTING   dialog  box  displays,  adds  and  deletes  event
settings.
*EventNo,A
To  add  or delete event settings, enter the event number  to  be
added/deleted in this field. Valid event numbers are 1 to 6.
*EventArg,A
Whenever  a  valid  event number is entered in  the  "Event  no."
field,  the corresponding MICE event setting will always  display
in  this field. If event setting is cleared, this  field  becomes
empty.
*EventAction,A
Use <space-bar> toggle to switch this field to "Add" or  "Delete"
mode.
*TForward,A
FORWARD TRACE dialog box starts real time emulation of the target
and  begins recording target status immediately after the  speci-
fied trigger address is reached. Forward trace stops at the break
address when the trace buffer is full or breakpoint 2 is reached.
Target CPU may however continue to run if the <space-bar>  toggle
is switched to "YES".

Options to specify a number of times the target condition has  to
be matched before trace stops is provided. A single qualifier may
be  also specified to choose the type of CPU activity  associated
with the trigger address.

Note that this command is NOT applicable to MICE-8/16/32.
*ForwardRunends,A
This  field uses <space-bar> to toggle "YES" to continue  running
emulation after it stops when trace stops.
*ForwardAddx,A
Forward trace starts real time emulation of the target and  imme-
diately begins recording target status until the trigger  address
specified in this field is reached.
*ForwardCount,A
Specify a number of times the target condition has to be  matched
before trace stops in this field.
*ForwardQualifier,A
A single qualifier may also be specified in this field to  choose
the  type  of CPU activity associated with the  trigger  address.
Note that "Forward Count" must be pre-specified before specifying
a qualifier.
*TList,A
LIST  TRACE BUFFER dialog box lists information recorded  in  the
trace  buffer. Select the desired format. The number of the  last
frame recorded in the trace buffer is also displayed on the first
line of this dialog box.

Options  for specifying memory block to be listed (Begin/End  Ad-
dress),  processor status code (Status), trace bit level  (Trace-
bits)  and buffer frame to begin listing (Begin frame), are  also
provided in this dialog box.
*ListTotalFrame,A
This field displays the number of the last frame recorded in  the
trace  buffer. Note that the frame count begins at zero,  so  the
total number of frames is one more than the value on display.  If
"7FF" is displayed, the trace buffer is full. 
*ListFormat,A
Press <F2> to display format choice list.  Select by highlighting
the desired list format from this choice list.
*ListBegAddr,A
Enter the starting address of the block for trace buffer  listing
in this field.
*ListEndAddr,A
Enter  the last address of the block for trace buffer listing  in
this field.
*ListStatus,A
Processor  status codes representing specific type  of  processor
activity  may be defined in this field. If none is  entered,  the
default  is for all cycles to be listed regardless  of  processor
status.
*ListTraceBits,A
Trace bit level may be assigned to specify that only cycles  mat-
ching  the indicated level are to be listed. The trace bit  level
may  be indicated in this field. If none is entered, the  default
is for all cycles to be listed regardless of trace bit levels.
*ListBegFrame,A
The  frame  at which the listing is to begin is entered  in  this
field. If none is entered, listing will begin at the last page of
the buffer.
*TSoftwareBreak,A
SET SOFTWARE BREAKPOINT dialog box is used to set or clear a sof-
tware execution breakpoint.
*BpAction,A
Use  <space-bar>  to  toggle between "Add" and "Delete" operation
when adding and clearing breakpoint.
*BpAddr,A
Enter the  address in  this field  when adding/deleting  a break-
point.  Press <F2> to  display a choice list  showing the current
breakpoint address.

Note that  if DELETE operation is selected, a  breakpoint  number 
should be entered in the address field.
*TTrace,A
TRACE CONTROL dialog box provides MICE 8/16/32 trace control set-
ting for Trigger, Cycle Qualify, Timebase and Synchronization, in
one display. One or all of the commands may be set and  activated
in one execution.

Note  that all default settings displayed in this dialog box  are
current MICE settings.

Note that this command is NOT applicable to MICE-II.
*TraceCycle,A
Toggle the  <space-bar> between "SET" and "CLEAR" to set or clear
the cycle setting. If "Set" cycle qualify is selected, enter cor-
responding data in the "addx" and "status" fields.  Otherwise the
"addx" and "status" fields are skipped.
*TraceAddx,A
Specify  a  cycle  qualify  hexadecimal address  setting in  this
field.
*TraceStatus,A
Specify a cycle  qualify processor status code in this field. The
available types are; AK, I, O, H, S, R and W. For details, please
refer to the MICE manual.
*TraceSyncI,A
Toggle the <space-bar> to set the ON/OFF status of the synchroni-
zation input command. 
*TraceSyncO,A
Toggle the <space-bar> to set the ON/OFF status of the synchroni-
zation output command.
*TraceTimebase,A
Press  <F2> to display the timebase choice list.  Select  desired
timebase. If this  field is  empty, no  time-base command will be
executed.
*TraceTimer,A
<Space-bar>  toggle  between "EVENT" and "GO".  Selecting "EVENT"
activates timer when the  first  event is  encountered. Selecting
"GO" will activate the timer when emulation starts.
*TraceTrigger,A
Toggle the <space-bar> to SET/CLEAR a trigger command.  Selecting
"SET" will cause more fields to be filled. 
*TraceRunends,A
Press  <space-bar>  to toggle "YES/NO" status for this field. Se-
lecting  "YES"  will allow  the  emulation  processor to free run
after the trace ends. "NO" will stop the  emulation processor one
cycle  beyond  the  location  where  the  trigger  condition  was
matched.
*TraceEvent,A
This  field displays  current MICE  trigger setting.  The trigger
condition  may be a single  event or a logical construct of up to
three  breakpoints with "And", "Or" and "Then"  connectives. Only
Events 1 to 3 can be used in the trigger definition. Note that no
event may be specified more than once in the trigger setting. 

Press <F2> to display listing of all combinations available.
*TraceDelay
This field will display a cycle-count delay selections (Backward,
Center, Forward and Count). Select desired delay count.

When emulation begins, the MICE immediately starts recording tar-
get system and emulation processor status in real-time. Data  are
recorded  until cycle-count delay (Backward, Center,  Forward  or
Count) and other trigger condition is matched.
*TraceCount,A
Specify  the number of cycle count (hex value from 0H to  0FFFFH)
in this field.

After  all other trigger conditions have been matched, the  trace
will continue until the specified number of cycles has elapsed
*YCreate,A
CREATE  SYMBOL dialog box is used to create a global symbol.  Any
symbol  created by this command is temporary and  effective  only
during the current debugging session. It will not be written back
to the symbol file.
*address,A
Specify the required symbol address in hex value in this field.
*YAddress,A
ADDRESS QUERY dialog box will search through the symbol table and
list all occurrences of the specified address.
*symname,A
Specify  the symbol name in this field. Symbol may use any of the
alphanumeric  characters. Note that the percent (%)  sign is used
as prefix to symbol names. 
*YDelete,A
DELETE  SYMBOL  dialog box is used to delete symbols  created  by
"CREATE" command.
*YLoad,A
LOAD SYMBOL TABLE dialog box loads  symbol file from disk to USD-
3. Symbol  files with extensions ".TBL" and ".SYB" are the output
of CONV3.
*LoadFilename,A
Specify symbol file to be loaded in this field.
*YSymbol,A
SYMBOL QUERY dialog box will search through  the symbol table and
list  all  occurrences  of  the  specified symbol. Module name in
"[%%module]%symbol" symbol format may also be indicated, but only
the specified module will be searched.
*FCloseJournal,A
Toggle the <Space-bar> to enable/disable "save and close" journal
file feature. If opened, the journal filename will display. Check
mark ({) indicates feature is enabled. 
*FCloseLog,A
Toggle  the  <space-bar> to  enable/disable  "save and close" log
file  feature.  If opened,   the log filename will display. Check
mark ({) indicates feature is enabled. 
*FDos,A
Allows temporary exit to DOS without quitting USD-III. 
*FQuit,A
Quit USD-III and exit to DOS.
*FVersion,A
USD-III  version  number is always displayed at the bottom of the
"FILE"  pull-down  menu. Except for informing user of the USD-III
version he is using, this option has no other function.
*EIstep,A
This is an  instruction step  command to  execute  instruction by
single-stepping and returns to  command prompt  mode after execu-
ting the command.  After each step, the viewports information are
also  updated  accordingly if their respective updating toggle is
enabled.
*EIstepOver,A
This is an  instruction step command to treat subroutines as nor-
mal instructions. User needs  NOT step into  subroutines which he
is  not  concerned  about.  USD-III will run through such subrou-
tines.

Note that this command is NOT applicable to MICE-II.
*EIstepForever,A
This is an  instruction  step command to step instruction contin-
uously until forced to stop by pressing <ESC> key.
*EIstepOverForever,A
This is an  instruction step  command  to  treat  subroutines  as
normal  instructions and to  step instruction  continuously until
forced  to  stop by  pressing <ESC> key. User needs NOT step into
subroutines  which  he  is  not concerned about. USD-III will run
through such subroutines.

Note that this command is NOT applicable to MICE-II.
*ECycle,A
Cycle step will initially stop the emulation processor, steps the
program one cycle, and then halts the processor in HOLD state.
*OSymbolToggle,A
Toggle  the  <space-bar> to enable/disable the symbolic debugging
feature. Check mark ({) indicates feature is enabled. 
*OLogToggle,A
Toggle the <space-bar> to enable/disable the command line logging
feature. Check mark ({) indicates feature is enabled. 
*OJournalToggle,A
Toggle the  <space-bar> to enable/disable the output logging fea-
ture. The output contains all the  COMMAND  viewport  activities,
including the user input and USD-III output. Check mark ({) indi-
cates feature is enabled. 
*OSwToggle,A
Toggle the  <space-bar> to enable/disable the software breakpoint
feature. Note that a check mark ({) is turning on the feature.
*SRecall,A
Recall command is used to recall the emulation memory map,  time-
base, clock, Channel B baud rate and select code currently  saved
in  non-volatile  RAM  and to  check  compatibility of the NOVRAM
stored  data with  MICE Identification  Code (ID). Note that this
command is  automatically  executed on power-up and after a hard-
ware reset.
*SSave,A
Save  is  the command to save the current  memory  map  settings,
timebase  and  other data to the non-volatile RAM; and to  subse-
quently  check these parameters for compatibility with  the  MICE
Identification Code (ID).
*TGo,A
Go command is used to start program emulation at the current pro-
gram counter.
*THalt,A
This command may be used during free-run emulation to stop  prog-
ram execution any time. 
*YList,A
List  command will display all symbols, including global  symbols
(from symbol file or created by "CReate" command) and symbols  in
each module.
*YModule,A
Module  command will display all modules existing in  the  symbol
file.
*OUsave,A
This command saves current window status (including screen layout
and  viewport  update  flag)  and  softkey  definitions  into the
USD3.SAV file.
*OUrecall,A
This command recalls window status and softkey definitions  saved
in the USD3.SAV file.
*PEntry,A
"Entry"  will unveil the Module Entry Chart. The chart will  dis-
play the total number of calls made to a group of specified prog-
ram addresses. It also displays the count for calls made to  each
individual program address along with a bar graph indicating  the
percentage of processor activity involved for each address.  This
command permits quick display of the relative amount of  activity
for specified addresses under different operating conditions.
*PDuration,A
Invoking  "Duration" will unveil the Module Duration  Chart.  The
chart  will display the overall duration of activity for a  group
(maximum of 4) of selected program modules. At the same time exe-
cution  duration for each individual program module is also  dis-
played along with a bar graph indicating percentage of  processor
activity  involved for the module. Calculation begins  each  time
execution  enters  the start address of a module  and  terminates
only when the module end address is reached.
*PTime,A
Invoking  "Time"  will unveil an Execution Time  Histogram.  This
histogram will display the activity distribution for a  specified
program module range. The frequency of execution within different
time  frames is displayed for a program module along with  a  bar
graph  indicating the percentage of processor  activity  involved
for each specified time frame.
*LsaMenu,A
Lsa Menu will invoke the Logic State Analysis feature of USD-III.
It  initially displays the LSA Signal Specification Screen  where
configuration for the LSA Signal Waveform is specified. 

The resulting LSA provides a signal waveform display for up to 16
channels and displays waveform diagram for a maximum of 56  trace
points  including up to 8 hardware trace points. All  trace  data
recorded in the buffer can be conveniently displayed.

The  screen  display  may be zoomed  4/8/16/32/64  machine cycles
frames per screen. Display may be scrolled one page at a time.
*FileMenu,A
File Menu  provides file  management  commands. It also  provides
commands  for temporary exit to DOS, quitting USD-III and USD-III
version display.
*SetupMenu,A
Setup Menu provides commands for memory mapping. It also provides
commands to recall and save  MICE  setup  parameters  from and to
NOVRAM.
*MemoryMenu,A
Memory  Menu   provides  commands   to   perform  memory  related
operations.
*EmulationMenu,A
Emulation Menu provides commands for instruction and cycle  step-
ping.
*TraceMenu,A
Trace Menu provides commands to trace program execution.
*OptionsMenu,A
Options Menu  provides  "ON"  and  "OFF"  toggle for  Symbol/Log/
Journal/Sw-Breakpoint  features. It  also  provides  utility  for
saving and recalling window status and softkey definitions.
*SymbolMenu,A
Symbol Menu provides commands for symbolic debugging information.
*SpaMenu,A
Spa  Menu provides software performance analysis utilizing  wave-
form and bar graphs to display results of the analysis.
*OUrecallScreen,A
Use  <space-bar> toggle to enable/disable the "recall window sta-
tus" feature.  The status from the  USD3.SAV  file last  saved by
USAVE command,  will be recalled. Check mark ({) prefix indicates
feature is enabled. 
*OUrecallSoftkey,A
Use <space-bar> toggle to enable/disable the "softkey definitions
recall"  feature.  The  definitions  from the  USD3.SAV file last
saved by USAVE  command  will be recalled.  Check mark ({) prefix
indicates feature is enabled. 
*OUsaveScreen,A
Use <space-bar> toggle to enable/disable feature to save the cur-
rent  window  status to the  USD3.SAV file. Check mark ({) prefix
indicates feature is enabled.
*OUsaveSoftkey,A
Use <space-bar> toggle to enable/disable feature to save the cur-
rent  softkey  definitions to the  USD3.SAV file.  Check mark ({)
prefix indicates feature is enabled. 
*OToggle,A
TOGGLE STATUS  dialog box  is used  to turn  ON/OFF the following
features:
             - symbolic debugging 
             - command line logging
             - output logging 
             - software breakpoint setting
*FCloseLogJournal,A
CLOSE LOG/JOURNAL  dialog  box is used to save and close the cur-
rent log or  journal file  session, or both.  If a log or journal
file has been opened, the  filename will show up on their corres-
ponding field. Otherwise the field is empty.
*ODlgColor,A
This dialog allows users to change the colors for all the  dialog 
boxes.  The three areas where users can change the colors are the 
foreground  and  background colors for text including  title  and 
border, the active field and the inactive field. 

Once  the colors have been changed and saved by exiting the  this 
dialog, all the dialog boxes will show the new color settings  in 
the remaining USD3 session until next changes.  The new  settings 
can  be saved into USD3.SAV as part of screen layout  information 
if  the  USAVE command is issued; or responding 'Y' to  save  the 
screen layout when exiting USD3.  The new colors will show  again 
in the subsequent USD3 session.

The following lists the keyboard operations:
''     indicates the current field

<F9>    changes the foreground color
        for  a monochrome display, an <F9> toggles the  addtional       
        attributes  among the zero (shows base  attribute  only),       
        high intensity, blinking and high intensity with blinking
        
        for a color display, an <F9> toggles the 16 colors  among       
        BLACK, BLUE, GREEN, CYAN, RED, MAGENTA, BROWN, WHITE, and       
        the high intensity of each color

<F10>   changes the background color    
        for  a  monochrome  display, an <F10>  toggles  the  base 
        attributes among NORMAL, UNDERLINE, and REVERSE
        for a color display, it toggles the same colors as <F9>

<CR>    keeps  pressing this key to exit the dialog and save  the 
        settings

<ESC>   quits the dialog and loses all the changes

The following lists the mouse operations:           
cursor stays     Left Button              Right Button
--------------   ---------------------    ----------------------
inactive field   make this field active   no operation
active field     changes the foreground   changes the background
                 color                    color
dialog area      save the settings        loses all changes
*SPACoverageClist,A
The following lists the keyboard operations:

<Up/Down>  To  alternate the highlighted item  for  selecting  a           
           memory range.
<Enter>    An <Enter> will display the first page of the  current           
           memory  range  if  the previous keystroke  is  not  an           
           <Enter>;  Otherwise,  it will go to  the  next  memory          
           range, then display the first page of it.
           
<PgUp>     To turn to the previous page of current memory range.
<PgDn>     To turn to the next page of current memory range.
<Space>    To toggle between "memory dump" and  "assembly  code"           
           for display of the current memory range.
<F7>       To exchange the window size between full  screen  and           
           partial screen display.
<Escape>   To quit from the SPA Code Coverage.
*MMonitor,A
DATA  MONITOR  dialog  box is used  to  set/clear  the  monitored 
variables which are displayed in the DATA viewport.
*MonitorOperation,A
Press <F2> to display the operation choice list. Select "SET"  to 
set a monitored variable. Select "CLEAR" or "CLEAR ALL" to  clear 
some or all monitored variables.
*MonitorVariable,A
If  you select "SET" in the operation field, please fill  in  the 
symbol or address which will be monitored.

If you select "CLEAR" in the operation field, a choice list  will 
be displayed to show the current monitored variables. Use <CR> to 
select the variables which will be deleted and <F10> to save  the 
selection.
*MonitorElement,A
Fill  in the number of elements in this field. The size for  each 
element  is  defined in the Type field.  These elements  will  be 
indicated by +1, +2, ... in the DATA viewport. 
*MonitorType,A
Press  <F2> to display the type choice list.  Select  appropriate 
type  (Byte, Word, Long) for the monitored variable. The  default 
is Byte.
*SPACoverage,A
"Coverage"  supports the environment that allows users to set  or 
clear coverage settings, to execute program segments, and then to 
look  at  the contents of memory ranges in the  form  of  "memory 
dump" or "assembly code". Therefore, it is very convenient for  a 
user  to  clearly know which subroutine or data  block  has  been 
accessed in his program.
*MemoryType,A
Using <Space> to check or clear the memory type (if 68-family) or 
bus  status  (if 80C186) to be executed with  the  code  coverage 
test.
<Space>       To toggle between check and clear.
<Enter>       To go to the following field.
<Up/Down>     To go to the previous/following field.
*CCStartAddr,A
Providing a hexadecimal address or a symbol as the start point of 
your  execution. If not provided, the default address is  program 
counter of MICE.
<Enter>       To go to the following field.
<Up/Down>     To go to the previous/following field.
<Right/Left>  To move the cursor.
<F6>          To erase the address.
*CCEndAddr,A
Providing  a hexadecimal address or a symbol as the end  of  your 
execution.  If  not provided, the execution will  continue  until 
<Escape> is pressed.
<Enter>       To go to the following field.
<Up/Down>     To go to the previous/following field.
<Right/Left>  To move the cursor.
<F6>          To erase the address.
*CodeBlockOp,A
Using <Space> to set or mask this memory range setting.
<Space>       To toggle between setting and masking.
<Enter>       To go to the following field.
<Up/Down>     To go to the previous/following field.
*CodeBlockStart,A
Specify a hexadecimal address or a symbol as the start point of a 
memory block.
<Enter>       To go to the following field.
<Up/Down>     To go to the previous/following field.
<Right/Left>  To move the cursor.
<F6>          To erase the address.
*CodeBlockEnd,A
Specify  a hexadecimal address or a symbol as the end point of  a 
memory block.
<Enter>       To go to the following field.
<Up/Down>     To go to the previous/following field.
<Right/Left>  To move the cursor.
<F6>          To erase the address.
*TBreak,A
The  BREAK  ON  READ  dialog box  provides  the  LAM2  INITIALIZE 
command, allowing user to define up to sixteen memory block range 
settings  for the Break-On-Read-Before-Write  function;  although 
the command itself can accept up to twenty block range settings.

The  current MICE settings will show up in the appropriate  field 
when this dialog is called up.
*BreakOperation,A
Press  <F2>  to  get  a  list  of  operation  provided  from  the 
INITIALIZE command.  Choosing "SET" from the list enables you  to 
go  to  the subsequent fields to set the memory types  and  block 
ranges.   "RESET"  clears  the results from  last  run.   "CLEAR" 
clears  all the existing memory block range  settings.   "ENABLE" 
enables  all the memory block settings.  "DISABLE"  disables  all 
the memory block settings.
*BreakBlockOp,A
The <SPACE> key toggles the operation between "SET" and  "CLEAR". 
"SET" makes the next two fields available for user's input, while  
"CLEAR" clears this address settings.
*BreakBlockStart,A
Enter a starting address of this memory block.
*BreakBlockEnd,A
Enter an ending address of this memory block.
*TLAM2Trace,A
TRACE  CONTROL  dialog  box provides user  with  the  MICE  trace 
control   commands   including  Cycle   Qualify,   Timebase   and 
Synchronization in one display. One or all of the commands may be 
set and  activated in one execution.

Note  that all default settings displayed in this dialog box  are 
current MICE settings.
*LAM2TraceCycle,A
Type  <F2>  for a list of the operations for  the  cycle  qualify 
command,  including "SET", "CLEAR", "ENABLE" and "DISABLE".   The 
arguments of address, status and trace bits specify which machine 
cycles are to be recorded in the trace buffer.

The LAM-II provides two cycle qualify settings.
*TraceAddx,A
Specify  a  hexdecimal address or a range of  addresses  prefixed 
with  "Range" keyword followed by the start and end addresses.
*TraceStatus,A
Specify  1 to 8 processor status codes (SP, SR, SW, UP,  UR,  UW, 
AK,   and  AW) indicating the type of processor  activity  to  be 
recorded.
*TraceBit,A
Specify a 1-byte hexadecimal setting for the trace bits.
*TTriggerLevel,A
TRIGGER  SETTINGS dialog allows you to set 1 to 8 trigger  levels 
and the TRIGGER command.
*LevelOperation,A
Type  <F2> for a list of the operations, "SET" to set  a  trigger 
level,  "CLEAR" to clear a specified trigger level  setting,  and 
"CLEAR ALL" to clear all the 8 trigger level settings.
*TriggerLogic,A
May sepecify a single event or a logical construct of up to  five 
breakpoints with OR, AND and NOT.  Only events 1 to 5 can be used 
in  the   trigger level definitions;  execution  breakpoints  are 
automatically  joined to the specified construct by a logical OR.
*TriggerTrace,A
Use <SPACE> to toggle between "ON" and "OFF" to enable or disable  
recording  the trace information into trace buffer while  program 
execution.
*TriggerTimer,A
Use <SPACE> to toggle between "ON" and "OFF" to enable or disable 
the  time measurement while program execution.
*GlobalTrace,A
Use <SPACE> to toggle between "ON" and "OFF" to enable or disable 
recording  the trace information into trace buffer while  program 
execution.
*GlobalTimer,A
Use <SPACE> to toggle between "ON" and "OFF" to enable or disable 
the time measurement while program execution.
*TriggerSequence,A
LAM-II  supports  very  powerful trigger  setting.   The  Trigger 
sequence  can use up to 8 trigger levels and mixing with THEN ... 
and IF ... ELSE ... connectives creates great flexibility.
*YSsave,A
SYMBOL  SAVE  dialog  box saves the symbols,  created  by  CREATE 
command,  to  a disk file specified in the filename  field.  This 
file  will  be  created  if it does not exist;  and  it  will  be 
overwritten if it exists.
*YSrecall,A
SYMBOL  RECALL  dialog box creates symbols defined  in  the  file  
specified  in  the filename field, and insert them into  the  new 
symbol table.  

If  the  new symbol table has symbols created by  user,  all  the 
symbols  from the input file will be appended to the  new  symbol 
table.  If the table becomes full, the rest from the file will be 
truncated.

Before  any insertion to the new table, the new symbol name  will 
be  checked against the new table.  If the symbol name exists  in 
the new table, this symbol will be ignored and no insertion  will 
be done.
*YSsaveFilename,A
Specify  a file name to this field for saving all the symbols  in 
the new table.

If an existing filename is given in this field, the file will  be 
overwritten without further notice.
*YSrecallFilename,A
Specify  a  filename to this field to include  the  user  defined 
symbols from the file previously created through SSAVE command.





















