|
Troubleshooting and Support
Error Messages
ByteBack D.R.I.S.TM can encounter 2 types of errors: disk access errors or runtime
errors. While disk access errors tell you something about the condition of your
hard disk, runtime errors can indicate errors in the ByteBack D.R.I.S.TM program, or
unexpected errors the program wasn't prepared for that were caused by for example the
operating system.
Disk access errors
ByteBack D.R.I.S.TM accesses hard disks using the Extended Int13h interface. This is a
set of commands offered by the BIOS or disk controller to access disks at the sector level (bypassing the operating system). Every time a command is executed, the BIOS or disk
controller will respond with a return code to inform the requesting program
(ByteBack D.R.I.S.TM in our case) if the command was successful. If not, the return code value will indicate
the nature of the problem.
When disk access errors occur the actual return code is reported in the
ByteBack D.R.I.S.TM logfile. The following is a list of possible return codes:
| Return Code |
Description |
| 01h |
Invalid function in AH
or invalid parameter |
| 02h |
Address mark not found |
| 03h |
Disk is write-protected |
| 04h |
Sector not found / Read
error |
| 05h |
Reset failed |
| 07h |
Drive parameter
activity failed |
| 08h |
DMA overrun |
| 09h |
Data boundary error |
| 0Ah |
Bad sector detected |
| 0Bh |
Bad track detected |
| 0Ch |
Unsupported track or
invalid media |
| 0Eh |
Control data address
mark detected |
| 0Fh |
DMA arbitration level
out of range |
| 10h |
Uncorrectable CRC or
ECC error on read |
| 11h |
Data ECC corrected |
| 20h |
Controller failure |
| 32h |
Incorrect drive type
stored in CMOS |
| 40h |
Seek failed |
| 80h |
Timeout |
| AAh |
Drive not ready |
| BBh |
Undefined error |
| CCh |
Write fault |
| HEh |
Status register error |
| FFh |
Sense operation failed |
| ?? |
Unexpected int13h error |
Extended Int13h errors often indicate a serious
problem on a hardware level that can not be resolved using software.
ByteBack D.R.I.S.TM can try to read a sector again after an error was returned,
however if serious hardware problems prevent the sector or even the entire
disk from being accessed, those attempts will be futile.
Runtime errors
Any other error that occurs during runtime and is not a disk access
error, is a runtime error. An example of
a condition that will cause a runtime error is trying to write to a bad
floppy diskette; ByteBack D.R.I.S.TM tries to open a file, and the operating system will
return the error to ByteBack D.R.I.S.TM. ByteBack D.R.I.S.TM does not have the ability to deal with
this error and aborts.
Runtime errors can also occur as a result of memory errors or bugs. When you
receive a runtime error, make sure to write down the following information:
- during which action the error occurred
- the error number (displayed by ByteBack D.R.I.S.TM on the error screen)
- the error address (displayed by ByteBack D.R.I.S.TM on the error screen)
Please submit this information to Tech Assist, Inc.
Technical Support.
Some common Runtime Errors:
| Code |
Description |
| Error 6 |
Overflow - Contact
technical support, include the error address. |
| Error 11 |
Division by zero -
Contact technical support, include the error address. |
| Error 53 |
File does not exist –
the program opened a file and tries to write to it while the file no
longer exists; can occur when you changed the media while not
letting the program finish writing files. |
| Error 57 |
Device I/O error - the
device is faulty (probably your diskette). |
| Error 58 |
File already exists |
| Error 61 |
Disk is full - the
diskette you're running ByteBack D.R.I.S.TM from is full. |
| Error 67 |
Too many files or invalid
filename - There are too many files in the diskette root folder. |
| Error 68 |
Device is unavailable -
resolve by making sure a diskette is inserted when writing to
diskette etc. Can also be caused by faulty hardware. |
| Error 70 |
Permission denied, write
protected - make sure the device can be written to; when writing to
network, check rights and permissions. When writing to removable
media, update drivers. Most common issue is that ByteBack D.R.I.S.TM is run
from a write protected diskette. |
| Error 71 |
Disk not ready - insert
floppy disk etc. Can also occur when after starting ByteBack D.R.I.S.TM the
diskette is removed from the drive. |
| Error 72 |
Disk media error - may be
caused by bad sectors, faulty hardware. To resolve, run a scandisk
on the destination media, run drive manufacturers diagnostic
utility. If the error occurs when you run ByteBack D.R.I.S.TM, the diskette is
probably faulty, use another diskette. |
Contacting Tech Assist, Inc.
Tech Assist, Inc.
31115 U.S. Hwy. 19 N.
Palm Harbor, FL. 34684
Sales: (800) 274-3785
General:(727) 547-0499
Support:(727) 374-0055
Fax: (727) 547-0768
info@toolsthatwork.com
sales@toolsthatwork.com
support@toolsthatwork.com
webmaster@toolsthatwork.com
The ByteBack D.R.I.S.TM logfile.
ByteBack D.R.I.S.TM creates a logfile every time the
program is started. If ByteBack D.R.I.S.TM encounters an existing logfile during startup,
this file will be renamed and a new file will be created. The logfiles are
renamed to "bb.lo?" where ? is 1 through 5, 5 being the oldest
logfile. All the ByteBack D.R.I.S.TM files are saved to the folder BB_FILES. This folder
is located in the directory that ByteBack D.R.I.S.TM is started from, usually the root of
the bootdiskette. The logfile can be found in the BB_FILES folder, and the most
current logfile is named BB.LOG. You should always include this logfile when
emailing a support request. Tech Assist, Inc.
Support needs this logfile to analyze your problem and make the appropriate
suggestions.
If you have not yet performed any
ByteBack D.R.I.S.TM actions but wish to ask a question that relates to datarecovery problems you might wish to address using
ByteBack D.R.I.S.TM, you must create a ByteBack D.R.I.S.TM Support Analysis Logfile and include this in
your support request. Also, Tech Assist, inc. support may ask you to create a
disk Support Analysis Logfile to facilitate repairs.
You can create an analysis log as follows:
- Start ByteBack D.R.I.S.TM
- select the appropriate disk
- go to the [Support] menu
- select [Create Support Analysis Log]
- let the scan finish
- exit ByteBack D.R.I.S.TM
- include the now created BB.LOG file in
your support request
The Support Analysis Log contains information about the disk layout (partition
tables), the boot sectors of individual partitions and all components that
ByteBack D.R.I.S.TM found during the disk scan.
|
