Have a Question?
< All Topics

00147: List of possible reasons for Error 30


List of possible reasons for Error 30


1) Attempting to LOAD RUN CALL or ADDR a program that has an invalid header or checksum (HSH). 

2) Passing a bad string to the LST() function. 

3) This has been seen when modifying and saving a program in a live environment while others may be loading it. 

4) Transferring programs using FTP from one system to another not using binary mode. 

5) Newer versions of Vpro5/Pro5 have different encryption algorithms then earlier versions. Loading a program that was SAVEP with a new encryption algorithm on a earlier version using an older algorithm. 

6) Network Interface Card or Cable Error. 

7) The user map is corrupted on Novell. Verify by doing a START followed by a ‘.’ to force a user map verification. This error always occurs with rev 2.3 of the 1053 (386 Novell) port when run under Windows 95. Printing the dec(info(2,4)) reveals a user slot number of -1 (incorrect). This incorrect user slot number will corrupt the user map. The user map must be reestablished by running BBx as supervisor or admin. The solution is to upgrade to current product from BASIS and use the current client kit available from Novell. Note that this problem only applies if using revisions prior to P4 rev 2.4 and P5 1.05. 

8) This has been seen when adding a Macintosh to a Novell Network 

9) Earlier versions of P4 rev 2 and PRO/5 shipped with a bad “_search” utility. It would occasionally damage the file header and would create an Error 30 on programs larger than 64k. The solution is to download the latest standard utilities from HERE.

10) On old Compaq’s the 386 ports can get this error due to unreliable memory being given to BBx. The solution is to exclude most of the upper memory block – from C000-FFFF. This is done at the operating system level via the config.sys file. 

11) An older version of IBM DOS which has not been patched to current level. This was seen around the DOS 5.0 timeframe. 

12 ) This has also been attributed to system problems under Unix. When saving a program, BBx performs a hashing algorithm on the program and saves that value out with the program. When loading a program, it again performs the hashing algorithm and compares the result to the one saved in the program. If the two results don’t match, then it issues an Error 30. You can disable this (for test purposes only!) by turning on the setopts byte 3, bit $08$. If this makes the Error 30 go away, then that’s what’s going wrong. The next step is to find out why the hash values don’t match. This is usually due to system memory or disk problems, and a thorough examination of the system is in order. 

Last Modified: 04/04/2007 Product: PRO/5 Operating System: All platforms Error Number: 30

BASIS structures five components of their technology into the BBx Generations.

Table of Contents
Scroll to Top