Appendix 6 - Hardware DevicesTable of ContentsIndex


APPENDIX VII

REBUILDING CORRUPT FILES

File Error 98 or 98,xx, indicates that the file in question is corrupt. This type of error is the result of a hardware problem. We have never seen this error caused by any type of software issue. Typical hardware issues that can cause file corruption are:

-Power surges -Powering off the system improperly

-Bad Hard Disk Controller -Trying to operate a single-user

version of V/BOSS in a multi-user environment.

-Bad memory chip(s) -Other failing hardware components

Corrupt files must be repaired/rebuilt before you continue using V/BOSS. Please see appropriate instructions for the operating system you are using. If you need assistance, call the V/BOSS Support Hotline at 800-226-8387.

REBUILDING CORRUPT FILES

XENIX/UNIX

To rebuild a corrupt file, everyone must be off the system. You should go to the Main workstation. From the Root Menu select [X] to exit. You will be at a # prompt.

You will type in the following command, inserting the proper switches and filename. Type in the case (upper/lower) shown.

/acu386/vutil -rebuild {switches} /usr/vbfiles/FILENAME

NOTE: If the corrupt file is CLINIC, you should be sure to use the [-x] switch. If the corrupt file is RJRNL, you should use (-k 1].

Using syntax for switches:

/acu386/vutil - rebuild [-b #] -23] [-ac] [+ce) [-k keynum] [-d dir] [-f factor [-s spoolfile [-r] [-m size]

[-g ext-factor(blocks)] /usr/vbfiles/FILENAME

Switches:

-b blocking 1 or 2 default is 1

-23 -2 vision 2 -3 vision blank use existing

-a automatic replacement

-k keynumber to rebuild default is 0

-d alternative directory for rebuilt file, orig not replaced, implies -a

-f compression factor 0 = 0; 1 = 70; 2 - 100 =

-g new extension factor

-s spooling form of rebuild. i.e., /dev/rmt0 (will prompt for media change when full).

-m spoolfile size in 1024 blocks, i.e., -m 1200 = 1.2mb floppy

-r interrupted.... used spooled info

When finished, look for:

# records recovered

# records broken & skipped.

# records lost

For Lost Records, usually under 5 is acceptable. If you are not sure of the results, please call for assistance. If OK, type [Y] to replace with new file. Then hold down <Ctrl> and type [d]. Type [root] <Enter>. Choose [1] Run Permissions. The "Can't Access" messages are normal.

DOS

To rebuild a corrupt file, go to the DOS prompt for the drive where V/BOSS is installed (usually C:\).

You will type in the following command, inserting the proper switches, path and filename.

\vboss\etc\vutil -rebuild {switches} /{PATH}/FILENAME

NOTE: If the corrupt file is CLINIC, you should be sure to use the [-x] switch. If the corrupt file is RJRNL, you should use [-k 1].

Using syntax for switches:

\vboss\etc\vutil - rebuild [-b #J -23] [-ac] [+ce] [-k keynum] [-d dir] [-f factor [-s spoolfile [-r] [-m size]

[-g ext_factor(blocks)] /{PATH}/FILENAME

Switches:

-b blocking 1 or 2 default is 1

-23 -2 vision 2 -3 vision blank use existing

-a automatic replacement

-k keynumber to rebuild default is 0

-d alternative directory for rebuilt file, orig not replaced, implies -a

-f compression factor 0 = 0; 1 = 70; 2 - 100 =

-g new extension factor

-s spooling form of rebuild. i.e., /dev/rmt0 (will prompt for media change when full).

-m spoolfile size in 1024 blocks, i.e., -m 1200 = 1.2mb floppy

-r interrupted.... used spooled info

When finished, look for:

# records recovered

# records broken & skipped.

# records lost

For Lost Records, usually under 5 is acceptable. If you are not sure of the results, please call for assistance. If OK, type [Y] to replace with new file.


Appendix 6 - Hardware DevicesTable of ContentsIndex


home page