Error codeError message
1
NEXT without FOR
Cause
When the FOR instruction corresponding to the NEXT instruction is not found, it is generated.
2
Syntax error
Cause
When the grammar of the delimitation of the position of the number of the format of the instruction and () and commas and the instructions etc. is wrong, it is generated.
3
RETURN without GOSUB
Cause
When RETURN is used from the GOSUB instruction while not called, it is generated.
4
Out of DATA
Cause
It is generated when there is no data that should be read by the instruction that reads DATA initialization statements such as READ, SETCHR, and SETPOLYGON.
5
Illegal function call
Cause
When the method of the call of the instruction and the function is wrong, it is generated.
6
Overflow
Cause
When the range where the fixed zero point type can be shown is exceeded by converting the numerical value into the fixed zero point type when the calculation of the numerical value and the polygon are registered, it is generated.
7
Out of memory
Cause
When the memory cannot be secured when it tries to exceed the user's area with PEEK and POKE when a necessary area cannot be secured by the CLEAR instruction or a necessary number of elements cannot be secured by the DIM instruction or it tries to read a program that is larger than the program area by the program by the edit display registration and the LOAD instruction and to read and write it, it is generated.
Action method
Please change the distribution of the memory by the CLEAR instruction.
8
Undefined line number
Cause
When neither the line - number nor the label specified with GOTO and GOSUB, etc. exist, it is generated.
9
Subscript out of range
Cause
When the price specified for the subscript of the array has risen the range when the array is declared, it is generated.
10
Variable already defined
Cause
When the variable that has already been defined is registered by the DIM instruction, it is generated.
11
Division by 0
Cause
When the instruction that cannot be executed directly is executed, it is generated.
13
Type mismatch
Cause
It is generated when the numerical value is substituted for the character string variable or the type is not suitable.
14
Sound: MML String too short
Cause
When time length of the MML character string is too short, it is generated.
15
String too long
Cause
It is generated in the following cases.
. When you treat the character string that exceeds 65535 characters
. When the character string input by the edit display is too long
16
Formula too complex
Cause
It is generated in the following cases.
. When the expression is too complex
. When the nest of the function is too deep
17
Can't continue
Cause
When execution cannot be restarted, it is generated.
18
Undefined array
Cause
When the array variable to which DIM is not declared is treated, it is generated.
19
Dimension size error
Cause
When the array variable of a number of dimension when DIM is declared and a different number of dimension is treated, it is generated.
20
Communication error
Cause
It is meant that the communication error occurred.
Action method
The connection of the communications cable is confirmed. First of all, it is confirmed that there is a transmission rate of the set screen displayed with the setting of the speed of the communication software and the L+R+Z button of the control pad, and reconnects connected button of the communication software pushing.
21
No RESUME
Cause
It is generated when not returning for the RESUME instruction when the program reaches during error processing by the ON ERROR instruction to the last minute. When the program ends by the END sentence, it is not generated.
22
RESUME without error
Cause
When RESUME is done though the error doesn't occur, it is generated.
23
Illegal line number
Cause
It is generated in the following cases.
. For injustice the line - number
. When the line - number that exceeds 0 or 99999 is specified
24
Stack overflow
Cause
It is generated in the following cases.
. When FOR-NEXT or the GOSUB stack overflows
When the figure painted out with .PAINT instruction is too complex
25
IF stack overflow
Cause
When the nest of the IF instruction is too deep, it is generated.
26
ELSE/ENDIF without IF
Cause
It is generated when there is no IF corresponding to ELSE or ENDIF.
27
FOR without NEXT
Cause
When the NEXT instruction corresponding to the FOR instruction is not found, it is generated.
28
Direct statement only
Cause
When an instruction an indirect execution impossible side is executed, it is generated.
29
Data statement
Cause
It is generated when there is no double quotation (") that shuts to the last minute when the content of the DATA initialization statement is read by the READ instruction etc. In the instructions other than the DATA initialization statement and the comment sentence, it is added automatically when there is no second double quotation.
30
String format error
Cause
When the structure of the specified character string is wrong in the GCOPY instruction and the CCOPY instruction, it is generated.
31
Parameter mismatch
Cause
It is generated when the parameter is not suitable in PRINT USING etc.
32
IF/ELSE without ENDIF
Cause
It is generated when there is no ENDIF corresponding to IF or ELSE.
33
34
Undefined vertex
Cause
It is generated in the following cases.
When you register the top in undefined top ID by .SETVERTEX instruction
When you use undefined top ID because of .SETPOLYGON instruction
When you examine the content of undefined top ID by .VERTEXID function
35
Undefined polygon
Cause
It is generated in the following cases.
When you register data in undefined polygon ID by .SETPOLYGON instruction
. When you register undefined polygon ID in the object
When you examine the content of undefined polygon ID by .POLYGONID function
36
Undefined attribute
Cause
It is generated in the following cases.
When you register data in undefined attribute ID by .SETATR instruction
. When you register undefined attribute ID in the object
37
Undefined texture
Cause
It is generated in the following cases.
When you register data to undefined texture ID by .SETTEX instruction
When you register undefined texture ID in the attribute by .SETATR instruction
When you use undefined texture ID because of .PUTSPRITE instruction(It is necessary to define sprite pattern = texture beforehand by the SPRITE$ instruction. )
When you examine the content of undefined texture ID by .TEXID function
38
39
Version mismatch
Cause
When the version of BASIC program is different, it is generated.
40
41
Unusable charactor
Cause
When an invalid character is registered when BASIC is registered, it is generated.
42
Buffer full
Cause
 BRAM:, CRAM:, FD0:, FD1:, COM: When the size of the buffer secured by the CLEAR instruction is exceeded when the FWRITE instruction to the device is executed and data is written, it is generated.
43
Device not connected
Cause
 CRAM:, FD0:, FD1: When Sega Saturn is started without the device of the object not being connected or nor putting the floppy disk when the device is used, it is generated.
Action method
Please read the manual of each equipment.
44
Device not formatted
Cause
 FD0:, FD1: When the floppy disk not formatted to the device (all deletions) is used, it is generated.
Action method
Please make "Protecting notch" "It is possible to record" if you may delete the content after often confirming the content of the floppy disk and execute the FORMAT instruction. Please read the manual of the Sega Saturn floppy disk drive about details.
45
Device write protected
Cause
When the file is broken, it is generated.
47
Not enough space
Cause
 BRAM:, CRAM:, FD0:, FD1: It is generated when there is no space enough for writing when the device is used.
48
Backup RAM error
Cause
 BRAM:, CRAM:, FD0:, FD1: They are other errors when the device is used.
49
50
File access error
Cause
When the host's file cannot be read and written when the communication software is used, it is generated.
51
Internal error
Cause
It is an internal error.
52
Sound: Out of layer memory
Cause
When the layer area is insufficient, it is generated.
53
File not found
Cause
When the file is not found, it is generated.
54
File already open
Cause
When OPEN and KILL, etc. are done to the file that has already been opened, it is generated.
55
Access past EOF
Cause
When the end of the file is exceeded and it accesses it, it is generated.
56
Bad file name
Cause
When an invalid file name is used, it is generated.
57
Invalid BASIC file
Cause
When the label is defined in the multiple, it is generated.
58
Duplicated label
Cause
It is generated when used without the file number opening.
59
File not OPEN
Cause
It is generated when already formatted.
60
Already formatted
61
Bad file mode
Cause
When the file mode is illegal, it is generated.
62
Bad device name
Cause
When the device name is illegal, it is generated.
63
Sound: Not layer mode
Cause
When it is not a layer edit mode, it is generated.
64
File still open
Cause
When the file that has been opened is used, it is generated.
65
Sound: Command buffer full
Cause
Sound. Command on driver side. When the buffer becomes full, it is generated.
66
Sound: Out of sound memory
Cause
When the sound memory cannot be secured, it is generated.
67
Sound: MML command error
Cause
It is a command of MML error. The error displayed at the same time is detailed as follows.
MML Syntax error
Cause
It is generated when there is a grammatical error.
Bad note length
Cause
When the specification of the length of the sound is not correct, it is generated.
Velocity value( 0 <=> 127 )
Cause
When the velocity value is not correct, it is generated.
Not gate time ratio
Cause
The key to the length of the sound . When the format of on specification is not correct, it is generated.
Bad gate time ratio
Cause
The key to the length of the sound . When the range of on specification is not correct, it is generated.
Bad pitch bend value
Cause
When the numerical value of the pitch pipe bend option is not correct, it is generated.
Not chord '(...)'
Cause
When the specification of harmony is not correct, it is generated.
Can't nest - plets
Cause
When it is a nest, Ren is generated.
Bad note number( 0 <=> 127 )
Cause
When the note number is not correct, it is generated.
Bad tone number
Cause
When the tone specification is not correct, it is generated.
Bad signature( -7 <=> 7 )
Cause
When the mixture specification is not correct, it is generated.
Bad transpose value( -127 <=> 127 )
Cause
The key . When a transformer posed value is not correct, it is generated.
Bad tempo value( 40 <=> 300 )
Cause
When the tempo value is not correct, it is generated.
Tempo change over
Cause
Tempo. The change frequency is generated in an excess case.
Bad volume value( 0 <=> 15 @:127 )
Cause
When the specification of the volume value is not correct, it is generated.
Bad direct pan value( 0 <=> 127 )
Cause
When the bread value is not correct, it is generated.
Bad octave valpue( 0 <=> 8 )
Cause
When the specification of the octave is not correct, it is generated.
Not MML command
Cause
When it is not MML command, it is generated.
Bad damper value( 0 or 1 )
Cause
When the specification of the damper is not correct, it is generated.
Macro error
Cause
It is a macro registration error.
Software layer error
Cause
When the Software layer parameter is not correct, it is generated.
Pitch bend cmd.buffer overflow
Cause
Pitch. The pipe bend specification number is generated in an excess case.
Not base track
Cause
Base. When the command that can be put only on the track is described, it is generated.
Bad label( 0 <=> 7 )
Cause
When the range of the label is not correct, it is generated.
D.S. without '$'
Cause
When the Sanyo sign corresponding to Dalsanyo is not found, it is generated.
Bad '$'*'or'ds' position
Cause
When the position of Sanyo, the coda, and the Dalsanyo sign is not correct, it is generated.
Repeat command error
Cause
When the repetition processing command is not correct, it is generated.
Bad effect pan value( 0 <=> 127 )
Cause
When the effect bread value is not correct, it is generated.
Bad effect level( 0 <=> 7 )
Cause
When the effect level value is not correct, it is generated.
Bad effect number( 0 <=> 15 )
Cause
When the effect number is not correct, it is generated.
Not DSP mode
Cause
When it is not DSP mode, it is generated.
Bad DSP mixer number( 0 <=> 15 )
Cause
When the DSP output mixer number is not correct, it is generated.
Bad status value( 0 <=> 127 )
Cause
When the status value is not correct, it is generated.
Not code name
Cause
Code. When the name is not correct, it is generated.
Chord note over( 2 <=> 32 )
Cause
The number of notes that compose harmony is generated in an excess case.
68
Sound: Out of MML data
Cause
When the MML character string is insufficient, it is generated.
69
File read error
Cause
When it is not possible to read from the file, it is generated.
70
File write error
Cause
When it is not possible to write it in the file, it is generated.
71
Sound: Song bank full
Cause
When the secured block is exceeded, it is generated.
72
Sound: Layer overflow
Cause
When the layer cannot be registered any further, it is generated.
73
Sound: Tone overflow
Cause
When the tone cannot be registered any further, it is generated.
74
Sound: VL overflow
Cause
When VL (velocity level) conversion data cannot be registered any further, it is generated. When the layer area is insufficient, it is generated.
75
Sound: PEG overflow
Cause
When PEG (Pittiemberorb) data cannot be registered any further, it is generated. When the layer area is insufficient, it is generated.
76
Sound: PLFO overflow
Cause
When PLFO (pitch LFO) data cannot be registered any further, it is generated. When the layer area is insufficient, it is generated.
77
Sound: No layer
Cause
When any layer is not registered, it is generated.
78
Invalid USERDATA
Cause
It is invalid USERDATA.
79
Vertex size mismatch
Cause
When a size registered before and a different size are specified for re-registration of same ID by the SETVERTEX instruction, it is generated.
80
Vertex number
Cause
When the top list of SETPOLYGON is larger than that of the length point defined in the top group that corresponds, it is generated. (In a word, when an undefined top number is used. )
Explanation
The SETPOLYGON instruction connects 3~4 top numbers defined by the SETVERTEX instruction and registers respect. Therefore, when it is not a value that enters 0~ top -1 in top ID to try to correspond, the number of the top list of SETPOLYGON doesn't become it.
81
Vertex ID over
Cause
When the top identification number cannot be registered any further by the SETVERTEX instruction, it is generated.
82
Vertex data ove
Cause
When data cannot be registered by the instruction any further (When you secure a lot of tops with one ID) of SETVERTEX, it is generated.
83
Vertex out of area
Cause
When <_̐>data is defined exceeding the length point in which SETVERTEX instruction is reserved, it is generated.
84
Texture size mismatch
Cause
When a size registered before and a different size are specified for re-registration of the texture by the SETTEX instruction, it is generated.
85
Texture ID over
Cause
When the identification number cannot be registered any further by the SETTEX instruction, it is generated.
86
Texture data over
Cause
When data that is larger than the area size specified by the SETTEX instruction is registered, it is generated.
87
Sound: Invalid WAVE file
Cause
Wave. When it is not data, it is generated.
88
Sound: Bad WAVE file format
Cause
Wave. When the format of data is different, it is generated.
89
Polygon size mismatch
Cause
When a size registered before and a different size are specified for re-registration by the SETPOLYGON instruction, it is generated.
90
Polygon ID over
Cause
When ID cannot be registered any further by the SETPOLYGON instruction, it is generated.
91
Polygon data over
Cause
When data cannot be registered by the instruction any further (When you secure a lot of tops with one ID) of SETPOLYGON, it is generated.
92
Attribute size mismatch
Cause
When a size registered before and a different size are specified for existing attribute ID re-registration by SETATR instruction SETPFONT instruction, it is generated.
93
Attribute ID over
Cause
When the attribute identification number cannot be registered any further by the SETATR instruction, it is generated.
94
Attribute data over
Cause
When data cannot be registered by the instruction any further (When you secure a lot of tops with one ID) of SETATR, it is generated.
95
Attribute out of area
Cause
When data more than the size specified by the SETATR instruction is registered, it is generated.