Errors returned by JVPC
As every program, JVPC can return errors. They have:
- a number, indicating in which area the error occured,
- a string, adding useful information.
For instance, opening a file that does not exist will result in error 11, where
the string should tell you which file in which directory the program was trying
to open.
Lists of errors
The errors below 10 are very rude:
Error Nr. | Description
|
---|
0 | Successful run (should not produce an error),
|
1 | Java API does not deal with this (extreme?) case.
|
The errors below 100 are triggered by use of Java standard libraries:
Error Nr. | Description
|
---|
11 | Could not open/read/write file (IOException).
|
The errors below 1000 are triggered by other libraries:
Error Nr. | Description
|
---|
101 | XML parser error
|
102 | JVCR error
|
256 | not available
|
512 | not available
|
768 | not available
|
The errors of 1000 and higher are JVPC specific:
Error Nr. | Description
|
---|
1000 | Internal error,
|
1001 | JVPC version mismatch,
|
1002 | JVPC data-file consistency check failed. This can mean JVPC
made an error (it is still beta), another VGAP client made an error, your
files were not transferred correctly, or you deliberately f*cked up.
|
1024 | not available
|
Kero,
12 IV 2000