abelerr.mnu

自己编写的GAL可编程逻辑电路的编译软件abel4的windows界面

*3439,A
Warning 3439: write error during chip report

The system could no longer write to the chip report file. Could be
an access problem or the disk is full.

*3424,A
Warning 3424: Could not create version locking file xxx

File protection or disk space problems while creating the
database.

*3000,A
Warning 3000: Directory 'xxx' does not seem to have a database! ...

The environment variable ABEL4DB seems to be pointing to a
directory that does not have a database. Or there could be a file
protection problem.

*3460,A
Warning 3460: cannot create lock file xxx

A protection problem prevented making the interlock system work.
Note the system may fail in a strange way if another user can get
past the protection problem and try to use the database.

*3463,A
Warning 3463: could not delete lock file xxx

A strange protection problem prevented removing the database
interlock. The system will not allow another access to the
database until the lock file is removed.

*3172,A
Warning 3172:  problems reading the ASCII dump file xxx

Error signaled while reading chip information file.

*3173,A
Warning 3173:  file not found error (maybe bad pathname)

Could not open the chip information file, either protection
problem or wrong pathname.

*3330,A
Warning 3330:  Could not access the ABEL-PLA file xxx

Could not open input design. May be a bad pathname or a protection
problem.

*Memory problems*
*------------------------------------------------------------*
*3085,A
Warning 3085:  out of memory failure! ...

Could not get enough memory to create internal cache for the
database.  Either release more memory for the program by removing
resident functions or reduce the database cache by changing the
environment variable DB_PAGES (minimum recommended is 8)

*3480,A
Warning 3480: could not allocate memory in build_mfg_list!!

Not enough memory to handle the list of manufactures specified.
Free up more memory for the program.

*3482,A
Warning 3482: could not allocate memory in build_spc_list!!

Not enough memory to handle the list of operating ranges
specified.  Free up more memory for the program.

*3483,A
Warning 3483: could not allocate memory in build_tech_list!!

Not enough memory to handle the list of device technologies
specified.  Free up more memory for the program.

*3485,A
Warning 3485: Could not allocate memory in sigs!!!

Not enough memory to handle decoding the input design. Free up
more memory for the program.

*3370,A
Warning 3370: Out of memory in open_databases !!

Not enough memory to handle startup. Free up more memory for the
program.

*3427,A
Warning 3427:  Could not get any memory to open databases!

Not enough memory for startup. Either release more memory for the
program by removing resident functions or reduce the database
cache by changing the environment variable DB_PAGES (minimum
recommended is 8)

*3481,A
Warning 3481: could not allocate memory in build_pkg_list!!

Not enough memory to handle the list of package types specified.
Free up more memory for the program.

*Command line parser problem*
*------------------------------*
*3394,A
Warning 3394: Command line error occurred ...

There was a serious problem in the command line. Correct the
call to this program or contact Data I/O Customer Resource
Center if this happened while using the design environment
menus.

*3403,A
Warning 3403:  error in device description

DEVSEL only. One of the specified device architectures is illegal.
You may have mistyped the command line or that architecture is not
in the database.

*3414,A
Warning 3414: You must specify some manufacturer

-MAN command line option must have manufacturer names after it.

*3028,A
Warning 3028: Note package type sss is not known

Illegal package type after the -PACK command line option.

*3415,A
Warning 3415:  You must specify some package

-PACK command line option must have package types after it.

*3029,A
Warning 3029: Note operating range spec type sss is not known

Illegal operating range after the -OPR command line option.

*3416,A
Warning 3416:  You must specify some operating range

-OPR command line option must have operating ranges after it.

*3030,A
Warning 3030: Note technology type xxx is not known

Illegal technology type after the -TECH command line option.

*3417,A
Warning 3417:  You must specify some technology

-TECH command line option must have device technologies after it.

*3031,A
Warning 3031: exact range for xxx does not make sense

In a range criteria, the "exact #" did not get an integer. If
this is from the design environment menus, contact Data I/O
Customer Resource Center.

*3032,A
Warning 3032:  less range for xxx does not make sense

In a range criteria, the "less #" did not get an integer. If
this is from the design environment menus, contact Data I/O
Customer Resource Center.

*3033,A
Warning 3033: greater range for xxx does not make sense.

In a range criteria, the "greater #" did not get an integer. If
this is from the design environment menus, contact Data I/O
Customer Resource Center.

*3034,A
Warning 3034: range for xxx does not make sense

In a range criteria, the "range # #" did not get two integers,
or the integer form a poor range (i.e. 3 to 1). If this is from
the design environment menus, contact Data I/O Customer
Resource Center.

*3035,A
Warning 3035: syntax error yyy is not exact, less, greater, or
range for xxx

In a range criteria, could not make sense out the the command.
If this is from the design environment menus, contact Data I/O
Customer Resource Center.

*3036,A
Warning 3036: Note that arg xxx for yyy did not make sense

A command line error occurred. If this is from the design
environment menus, contact Data I/O Customer Resource
Center.

*3075,A
Warning 3075:  No more than 4 fields can be selected for sorting.

Present system has a hard limit on 4 sorting fields. Contact
Data I/O Customer Resource Center if that is a problem.

*3076,A
Warning 3076: direction xxx cannot be first word in sorting,
must have field first

For -SORT, the directions UP, DOWN, ... must follow a field name.

*3077,A
Warning 3077: word xxx not a field or a sorting direction

For -SORT, the word could not be parsed.

*3344,A
Warning 3344: Note given device xxx in -devices is not valid

There was an illegal device name after the -DEVICE command line
option. This could be a typing error or that device architecture
is not in the database.

*3012,A
Warning 3012: Command line error occurred ...

There was a serious problem in the command line. Correct the
call to this program or contact Data I/O Customer Resource
Center if this happened while using the design environment
menus.

*3401,A
Warning 3401: Error parsing command arguments

One or more of the options in the command line was illegal.
Other messages should have explained what was the problem.
Correct the call to this program.

*3027,A
Message 3027: Note manufacturer ddd is not in the database

manufacturer specified in -MAN was illegal. May be a typing
mistake or that manufacturer is not in the database.

*System Problems*
*----------------------------------------------------------------*
*3372,A
Warning 3372: Wrong version of database, ...

SmartPart's executables internal version number does not match the
internal version number of the database. Data in the database may
not align correctly and the the selector function may fail in
strange ways. You may have to dump the database using the old
executables and rebuild it using the new executables.

*3374,A
Warning 3374: Database name xxx is too long, aborting

The directory name specified in the environment variable ABEL4DB
or the database field in the "Modify Criteria" menu is unusable.
Correct the name or move the database directory to a more
reasonable place.

*3376,A
Warning 3376: Filename xxx is too big

Obvious

*3082,A
Message 3082:  Note using existing database at 'xxx'

A note that a new database was not created as one already exists.
The device information will be added to the information already in
the existing database.

*3083,A
Message 3083:  Note new database initialized at 'xxx'

A note that a new database was created.

*3467,A
Warning 3467: Cleaning up for abort ...

A ^c or break was detected and the program has terminated
gracefully.

*3455,A
Warning 3455: could not enable INT error handler!

System problem, could not enable ^c or break trapping functions.
The database may get locked or corrupted if you try to abort the
program.

*3456,A
Warning 3456: could not enable ABRT error handler!

System problem, could not enable ^c or break trapping functions.
The database may get locked or corrupted if you try to abort the
program.

*3457,A
Warning 3457: could not enable TERM error handler!

System problem, could not enable ^c or break trapping functions.
The database may get locked or corrupted if you try to abort the
program.

*3425,A
Warning 3425: Lockmgr program not running, its required

Optional inter-network database manager is needed for this
system and it is not there. Contact Data I/O Customer Resource
Center.

*3426,A
Warning 3426: The Lockmgr said that the database is already in
use...

Optional inter-network database manager has determined that the
database is already in use and you must try again later.

*3428,A
Warning 3428: your user_id (environment variable USER) is
already in use

Optional inter-network database manager has determined that you
are already using a database on the network. Contact Data I/O
Customer Resource Center.

*3429,A
Warning 3429: your user_id (environment variable USER) is not set!

Optional inter-network database manager needs a user name to
resolve database conflicts. Contact Data I/O Customer Resource
Center.

*3430,A
Warning 3430: your user_id (environment variable USER) is garbage!

Optional inter-network database manager needs a user name to
resolve database conflicts. Contact Data I/O Customer Resource
Center.

*3459,A
Warning 3459: Database is already locked by user xxx Database
lock file is yyy

The device database can only be used by on person at a time. If
the user's name is 'anonymous', he did not set his environment
variable USER. If you determine that there is no other users for
the database, the lock system may be jammed, erase the lock file
only to unjam the interlock.

*Memory corruption (bad pointer type stuff)*
*-------------------------------------------------------------------*
*3335,A
Warning 3335:  Utilization factor is unreliable ...

Mathematics for calculating utilization factor failed in some
way. Contact Data I/O Customer Resource Center.

*3270,A
Warning 3270: internal error for sorter direction on sort key ddd

Contact Data I/O Customer Resource Center.

*3271,A
Warning 3271: internal error for decoding field for key ddd

Contact Data I/O Customer Resource Center.

*3407,A
Warning 3407: internal options list is unsynced!!!

Contact Data I/O Customer Resource Center.

*Other errors not in a catagory*
*------------------------------------------------------------------*
*3022,A
Message 3022:  No chip report done, use -log or -sort options

DEVSEL only. A note that only the device architecture candidate
list was created (or sent to STDOUT) and no chip report was
done. Use the -LOG option on the command line or use the
"Report File name" and "Report Sort order" in the design
environment menus.

*3013,A
Message 3013: Selecting from given set of device architectures

DEVSEL only. The normal mode of operation is to check all device
architectures for suitability, you have specified only some device
architectures and have limited the search area.

*3014,A
Message 3014: Selecting from all device architectures

DEVSEL only. The normal mode of operation is check all device