2. Installation

Installation is fairly simple.

  1. Insert the installation floppy into your disk drive.
  2. Type "A:" or "B:" depending on which floppy drive you use, followed by a return,
  3. Type "VEWDINST <sdrive> <ddrive> <pathname>" followed by a return, where <sdrive> is the drive letter of the installation floppy, <ddrive> is the drive letter of the hard disk, <pathname> is directory on the hard drive where you want the program to be stored. Include the colons after the two drive letters.
  4. Edit your CONFIG.SYS file and make sure the line "FILES = x", is at least 40.
    VEWD uses many open files, about 32. If you are running VEWD in a DOS window under Microsoft Windows the value may need to be even higher.

For example, "VEWDINST A: C: \VEWD" will install into the VEWD directory on hard drive C from floppy drive A.

2.1 Starting and Stopping

To start VEWD, change to the VEWD directory and type VEWD at the DOS prompt. VEWD supports the command line options specified in Table 2-1.

Table 2-1 Command Line Options
OptionDescription
/B=NOInhibits the beep on errors
/V=nSets the screen saver to n minutes.
Zero disables the screen save option.
/LDisables setting of keyboard locks.
/ESpecifies that an enhanced keyboard is being used.

2.2 Making Room for a Memory Hog

Although VEWD fits entirely in the lower 640 KB of DOS memory, it is somewhat of a memory hog. If you run with many Terminate and Stay Resident (TSR) programs, you may find yourself running short of memory. At bottom right corner of the screen, below the date and time, is the number of bytes of free memory remaining. If there is less than 32000 bytes free at the top level menu, you need to make more room. Each pop-up menu or form causes the portion of the screen that it covers to be saved for later restoration. By default this is in the low 640 KB memory. You can specify five alternate locations by including Virtual Memory environment variables in your AUTOEXEC.BAT file. Each variable is of the form:

SET CLAVMx=path,size[,ram­indicator]

Where,

For example, the line:

		SET CLAVM0=D:\,1024,M

defines the first virtual memory region as the root directory of a 1 megabyte RAM disk. Another example is the line:

		SET CLAVM1=C:\TEMP,768

specifies the second virtual memory region as a 768 KB area in the TEMP subdirectory of drive C.

If you have the memory, setting up a RAM disk is highly recommended. The RAM disk should be at least 64 KB in size (preferably 128 KB). To create a RAM disk you need to include a line in your CONFIG.SYS file similar to:

		DEVICE=C:\DOS\RAMDRIVE.SYS 1024 128 /E

This defines a 1024 KB RAM disk using extended memory.

Without specifying a virtual memory region on disk or in a RAM disk, the odds of being able to successfully access every VEWD screen is virtually NIL

2.3 Backup and Empty Databases

The install process created a complete set of startup database files. The VECLIST and ELEMSTAT files are pre-initialized with fixed data and don't change. The DEFAULTS file is initialized with a sample record that should be modified for the particular VE team(s). The remaining files are empty. The file EMPTYDB.ZIP is an archive containing these startup files. If it is ever desired to return to a fresh state, simply extract the files from this archive.

To prevent the loss of valuable session information, it is important that you make backup copies of all the data files. The minimum set of files to backup are those with the DAT and MEM extensions. VEWD will regenerate the key files at startup if they do not exist. However, if incorrect key files are used, the database files may become corrupted beyond recovery. Therefore you should backup the DAT, MEM and Knn files to insure a complete database. If you customize or create any printer control files (.DEV files) you should also make save copies of those.

A reasonable method of archiving the database files is to compress them into a single zip file. The archive can be named in form YYMMDDx. YYMMDD is the reference date of the archive. This is usually the date of a session. The x is one of the following:

Letter
Description
OOriginal. This is the archive made at the end of the session.
UUpdated. This is the archive made after post processing the session, making any corrections, adding candidate phone numbers but before merging the session candidate data into the global database. This is normally done by the VE preparing the paperwork for the VEC
blankThis is the archive made immediately after merging a session into the global database.

2.4 What Files are What

In case you're wondering what all those files are, Table 2-2 lists each of the database files. Table 2-3 lists optional files associated with the FCC data lookup function. Table 2-4 lists the sample Candidate and VE form letters, Table 2-5 lists the documentation files, and Table 2-6 describes the remaining files.

Each database consists of multiple files, each with the same name, and a different extension. Files with the extension .DAT contain the actual data, except for the free form memo fields. The .MEM files contain the memo fields. Files with the extension .Knn, where nn is a two digit number, are index files, used to speed access to the data.

Table 2-2 Database Files

FilenameExtensions Description
ATTVEDAT
K01
K02
The current session's attending VE database.
Callsign key file
Date/ID key file
DEFAULTSDAT
K01
Session, Printer, and Miscellaneous defaults
Configuration name key file
ELEMSTATDAT
K01
Element status choices
Status key file
LOCATIONDAT
K01
K02
The City, State, Zip Code database.
Zip Code key file
City key file
SESSIONDAT
K01
The Session list database.
Date/ID key file
VECLISTDAT
K01
The VEC choice lists.
VEC Name key file
VEINFODAT
MEM
K01
K02
VE personal information
VE Notes files
Callsign key file
Last Name key file
VICTIMGDAT
MEM
K01
K02
K03
The global (historical) candidate database.
Candidate Notes file
Last Name key file
Callsign key file
Date/ID key file
VICTIMSDAT
MEM
K01
K02
K03
The current session's candidate database.
Candidate Notes file
Last Name key file
Callsign key file
Date/ID key file


Table 2-3 Optional Database Files
FilenameExtensions Description
CALLSIGNDAT, K01Callsign index into FCCDATA.TXT.
FCCDATATXTFCC database information


Table 2-4 Sample Form Letters
FilenameFormatsDescription
VECARDBWord 7.0, and RTF Session notification postcard back
VECARDFWord 7.0, and RTF Session notification postcard front
VEENVWord 7.0, and RTF VE thank you form envelope
VEHEADERWord 7.0, and RTF Word Merge file header line
VELTRWord 7.0, and RTF VE thank you form letter
VESAMPWord 7.0, and RTF Sample VE merge file
VICENVWord 7.0, and RTF Candidate thank you form envelope
VICLTRWord 7.0, and RTF Candidate thank you form letter
VICSAMPWord 7.0, and RTF Sample Candidate merge file
VIHEADERWord 7.0, and RTF Word Merge file header line
FORMRTF.ZIPZip archive file Rich Format Text files
FORMWD70.ZIPZip archive file Word 7.0 files


Table 2-5 Documentation files
FilenameDescription
VEWD.DICWord 7.0 Custom Dictionary file for VEWD manual
VEWDMAN.DOTWord 7.0 document template for VEWD manual
VEWDMAN.PPTPowerPoint Document with audio schematic and convention layout
VEWDMAN1.DOC, HTMVEWD Chapter 1 -Introduction
VEWDMAN2.DOC, HTMVEWD Chapter 2 -Installation
VEWDMAN3.DOC, HTMVEWD Chapter 3 -Overview
VEWDMAN4.DOC, HTMVEWD Chapter 4 -Detailed Description
VEWDMAN5.DOC, HTMVEWD Chapter 5 -Pre-Session Activities
VEWDMAN6.DOC, HTMVEWD Chapter 6 -Session Activities
VEWDMAN7.DOC, HTMVEWD Chapter 7 -Post-Session Activities
VEWDMAN8.DOC, HTMVEWD Chapter 8 -Maintenance
VEWDMAN9.DOC, HTMVEWD Chapter 9 -Import/Export/Sort
VEWDMANA.DOC, HTMVEWD Chapter 10 -FCC Database Lookups
VEWDMANB.DOC, HTMVEWD Chapter 11 -An Audio System for CW Testing
VEWDMANC.DOC, HTMVEWD Chapter 12 -An Integrated Examination Session
VEWDMAND.DOC, HTMVEWD Chapter 13 -Troubleshooting
VEWDMANE.DOC, HTMVEWD Chapter 14 -Database Definitions
VEWDMSTR.DOC,
VEWDMAN.HTM
VEWD Master Document - Cover page, Copyright, trademark and license information, Table of Contents
VEWDMAN.ZIPZip archive of all the documentation files


Table 2-6 Non-Database files
FilenameDescription
CPRO.DMPNot provided on the install disk. Generated on occasion when the VEWD program abnormally terminates.
EMPTYDB.ZIPA zip file containing empty database files. If you ever want to start fresh, use these files.
EPSON.DEVPrinter control file for a standard Epson compatible
FCC2VEWD.EXEA Windows 3.1/95/NT program that will convert FCC data to VEWD format
GENERIC.DEVPrinter control file for a Generic printer
HPLASER .DEVPrinter control file for a HP LaserJet Series II
HPLASR4P.DEVPrinter control file for a HP LaserJet 4P
IBMPROXL.DEVPrinter control file for an IBM Proprinter XL
PS240.DEVPrinter control file for a Centronics PS240
README.VELast minute notes.
SAMPLE.DEVSample Printer control file
VEWD.EXEThe application program.
VEWD.HLPThe on-line help file
VEWD.ICOA Windows 3.1 Icon file for use with VEWD.
VEWD.PIFA Windows Program Information File for VEWD
VEWDBACK.BATSample session backup batch file.
VEWDFCC.EXEAn program to lookup VEWD format FCC data.
VEWDSORT.BATBatch file used to sort database files from within VEWD
VXT022.BATBatch file used to convert Version 2.0 database files to Version 2.2

2.5 Converting from Version 2.0/2.01 to Version 2.2

Between Version 2.0/2.01 and Version 2.2 changes were made to the DEFAULTS, VEINFO, VICTIMG, and VICTIMS databases. Attempting to start Version 2.2 using a prior version will result in the error display shown in Figure 2-1.

ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ» º Program Halt º º º º º º º º CLARION Version 2.1 Release 2105 1/01/98 1:17 AM º º D:\HAM\VEWD\V201\DEFAULTS.DAT º º ERROR CODE:47 INVALID RECORD DECLARATION º º DOS ERROR :0 º º º º Press any key to continue º ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ Figure 2-1 Database Version Mismatch Error

A conversion program called VXT022.EXE is available to convert the older database format to the newer format. To convert your older databases:

  1. Finish up any active session. There cannot be any active session in progress during the conversion.
  2. BACKUP ALL YOUR EXISTING DATA! This includes all the .DAT, .MEM, and .Knn files. If something goes horribly wrong during the conversion process you still have the original data.
  3. Delete all the key files. These are the files with the K0n extensions. The DOS command "del *.k0?" will do this.
  4. Start up VEWD and let it rebuild all the key files. Once this is done, exit.
  5. Create a sub-directory OLD underneath the VEWD directory.
  6. Move all the DEFAULT, VEINFO, and VICTIMG files (data, memo, and key indices) to the directory created in step 2.
  7. Delete all the VICTIMS files.
  8. Rename each file. The VEINFO.* files become OVEINFO.*; VICTIMG.* becomes OVICTIMG.* and the DEFAULTS.* files become ODEFAULT.*.
  9. Run the VXT022.EXE program from the VEWD directory.
  10. Select the "Convert All Files" Option.
  11. You're done. Delete the OLD sub-directory. You can also delete the VXT022 program.

The DOS batch command file VXT022.BAT will automatically perform steps 5 through 7.

Figure 2-2 shows the "Main Menu" for the VXT022 program. The following paragraphs describe each of the Choices on the menu.

"Convert All Files" performs the function of the "Convert DEFAULTS", "Convert VICTIMG", "Convert VEINFO", and "Update VECLIST" choices.

"Convert DEFAULTS" creates a new DEFAULTS database in the VEWD directory and copies the records in the ODEFAULT database to the new format.

"Convert VICTIMG" creates a new VICTIMG database in the VEWD directory and copies the records in the OVICTIMG database to the new format.

"Convert VEINFO" creates a new VEINFO database in the VEWD directory and copies the records in the OVEINFO database to the new format.

"Update VECLIST" reloads the VECLIST database to reflect the current active and defunct VEC’s.

"Exit" does just what you think it does. It terminates the program.

2.6 Convert your FORM 610 printer control files

With the changed FCC form 610, additional alignment fields were added to the printer control .DEV files to provide additional flexibility. The HPLASER .DEV and HPLASR4P.DEV have been updated with the additional control fields. Verify proper printing of form 610's with your session printer, updating the .DEV file as necessary, before your session.

ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ» º Volunteer Examinations Well Done º º Version 2.0x to 2.2 File Conversion º º 01/01/98 º ÌÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ͹ º º º Convert All Files º º º º Convert DEFAULTS º º º º Convert VICTIMG º º º º Convert VEINFO º º º º Update VECLIST º º º º Exit º º º ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ Figure 2-2 VXT022 Main Menu



Last Modified: 01 January 1998
Jim Heedles: heedles@ww1y.mv.com