Agilent Technologies A.18.00 Weather Radio User Manual


 
339
Chapter 6, Memory Cards/Mass Storage
DOS and LIF File System Considerations
TESTS Subsystem DOS File Restrictions
The Test Set uses IBASIC revision 1.0. The IBASIC 1.0 file system cannot
distinguish between DOS files that have been “SAVEd” and those that were
“STOREd.” As shown in
Table 37 on page 6 338, SAVE and STORE both produce
a file type DOS. This can result in undesired operation when trying to run a Test
procedure from the TESTS (Main Menu) screen.
The process for running a Test Procedure is described below. The potential
problem is described in step 3.
1. The procedure file location is selected using the Select Procedure Location:
field.
2. The desired procedure file is selected using the Select Procedure Filename:
field. When the procedure file is selected, the Test Set loads the specified procedure file
into memory. One of the pieces of information in the procedure file is the name of the
code file used with that procedure.
3. The Run Test softkey is selected. When the Run Test softkey is selected the Test
Set attempts to load the code file into memory. If the code file is located on a DOS
formatted media the Test Set will attempt to GET the file (the Test Set assumes the file
was stored using the SAVE command). If the code file was stored to the DOS formatted
media using the STORE command an ERROR 58 Improper file type is
generated.
If an ERROR 58 Improper file type is generated the code file must be
loaded into memory and then stored back to mass storage using the SAVE
command as follows:
1. Access the TESTS (IBASIC Controller) screen and LOAD the code file into the Test
Set.
2. Delete the stored code file from the mass storage location using the IBASIC PURGE
command.
3. SAVE the program as a Code file, using a lower-case c as a prefix, to the same mass
storage location as the original code file.
The IBASIC 1.0 file system can distinguish between LIF files that have been
“SAVEd” and those that were “STOREd.” Consequently the Test Set can
determine whether to use a GET or a LOAD on a code file which is located on a
LIF formatted media.