|
DiskPatch 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 DiskPatch program, or
unexpected errors that were caused by the
operating system.
Disk access errors
DiskPatch 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
(DiskPatch 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
DiskPatch log file. 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.
DiskPatch 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; DiskPatch tries to open a file, and the operating system will
return the error to DiskPatch. DiskPatch 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 DiskPatch on the error screen)
- the error address (displayed by DiskPatch on the error screen)
Please submit this information to DIY DataRecovery
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 DiskPatch 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 DiskPatch is run
from a write protected diskette. |
| Error 71 |
Disk not ready - insert
floppy disk etc. Can also occur if the diskette was removed after
starting DiskPatch. |
| Error 72 |
Disk media error -
if this error occurs when you run DiskPatch, the diskette is
probably faulty; use another diskette. |
|