DOS Errors from Basic for RDPDOS 

Error#

Error Definition

Possible Solution 

*3

Return without GOSUB 

Report as a bug to RDP support - 970-845-7108

*5

Illegal Function Call

Report as a bug to RDP support - 970-845-7108

*6

Overflow

A number is too large.  For example, if a variable is dimensioned as an integer it can be no larger than 32676.  Report as a bug to RDP support - 970-845-7108

*7

Out of Memory

The 640,000 byte DOS limit has been exceeded.  Try the command MEM/C.  

*14

Out of String Space

Memory; Data looping on report.   This may be solved by running RDP994 on all critical files. 

*24

Device Timeout

Usually means the local printer is turned off or broken

*25

Device Fault

Usually from printer - may be out of paper, cable loose, or a reboot of workstation and printer sometimes solves this.

*27

Printer out of paper

If this occurs when running a utility, such as RDP995, make sure the Utility finished correctly.  If not, load paper and re-run the utility.

*52

Bad File Number

Use RDP090 to check Table 00 to see if the file is in the file listing, and has the same correct name.  

53

File Not Found

Check to see if the file is in the RDP data directory.  Also check rights to the directory

*54

Bad File Mode

Report as a bug to RDP support - 970-845-7108

*55

File Already Open

Report as a bug to RDP support - 970-845-7108

*57

Device I/O Error

Input/Output Error.  This usually means the hard disk or other hardware device is broken. Also error 57 can occur with a bad network card on either the workstation or data server.  Shut down all workstations and servers and hubs and turn them back on.

*58

File Already Exists

Report as a bug to RDP support - 970-845-7108

*61

Disk Full

Out of disk space.  Check to see if there is enough disk space on the server.

*63

Bad Record Number

Part of Record is damaged.  Run RDP994 on all critical files, also RDP995.

*64

Bad File Number

Report as a bug to RDP support - 970-845-7108

*67

Too Many Files

On Windows XP check the C:\windows\system32\config.nt file and make sure the line "files=99" is included.  When a command prompt is started with Window XP, the system always processes the AUTOEXEC.NT and CONFIG.NT files found in the C:\windows\System32 folder.  

68

Device Unavailable

Usually a hardware error, such as a broken hard disk.  Shut down all workstations and servers and hubs and turn them back on.

*70

Disk Write Protect

If writing to a floppy or CD, it is write protected.  Might be a rights problem.  Shut down all workstations and servers and hubs and turn them back on.

*71

Disk Not Ready

Hard disk or network communication issue. Shut down all workstations and servers and hubs and turn them back on.

*72

Disk Media Error

Hard disk or network communication issue. Shut down all workstations and servers and hubs and turn them back on.

*75

Path/File Access Error

On Windows XP check the C:\windows\system32\config.nt file and make sure the line "files=99" is included.  When a command prompt is started with Window XP, the system always processes the AUTOEXEC.NT and CONFIG.NT files found in the C:\windows\System32 folder.  

*76

Path Not Found

File Paths may not be correct.  Check with menu 98, option 094.

*195

General Error

Report as a bug to RDP support - 970-845-7108.  Might be solved by rebooting server and workstation and running RDP994 - Rebuild all. 

*201

Access Error Key = ??

Key # is critical; missing records.  Might be solved by rebooting server and workstation and running RDP994 - Rebuild all.