Understanding viper pro files, Viper pro file structure, Accuboom™ folder – Seed Hawk Raven 2010 User Manual
Page 211: Appendix b, Appendix b, understanding viper pro files
APPENDIX
B
Manual No. 016-3001-003
201
Appendix B
Understanding Viper
Pro Files
Viper Pro File Structure
As explained in Chapter 1, Introduction, the Viper Pro uses information stored in internal memory to operate
while running. Proper file maintenance is the key to successful Viper Pro operation.
When you first start using your Viper Pro console, the internal Viper operating system automatically creates
certain files and folders on the internal memory. These files and folders will be where the Viper Pro system later
stores data files, such as navigation files, map files, and job files. Below is a list of the files and folders that
Viper automatically creates on the internal memory:
•
AccuBoom folder
•
AutoBoom Alarms folder
•
boundaryShp folder
•
clone folder
•
covMaps folder
•
guideArchive folder
•
jobs folder
•
rbin folder
•
rxMaps folder. This folder also contains the sub-folder colors.
•
scout folder
•
settings folder
•
streetmaps folder
•
vnav folder
•
zulu.ini file
AccuBoom™ Folder
The AccuBoom folder contains the SCT apply/no-apply boundary maps with a .sct extension. Viper creates
one file for each Sectional Control job.
You should store any previously created SCT apply/no-apply field boundary maps in this folder to make sure
that any .shp, .shx, and .dbf files associated with the field boundary files are also stored here.
These files are used by the Viper Pro OS and are not viewable.