PTBurn
SDK
Page
31
of
68
©
2011
Primera
Technology,
Inc.
Primera
is
a
registered
trademark
and
Bravo
is
a
trademark
of
Primera
Technology,
Inc.
All
other
trademarks
are
the
property
of
their
respective
companies.
3.2.4.15
DiscErrorIndexX
Integer
value
that
details
which
disc
in
the
job
had
the
error.
In
other
words,
the
disc
number
within
the
job
that
the
software
is
attempting
to
record
(e.g.
the
first
disc
of
the
job
=
1,
second
disc
of
the
job
=
2,
etc.).
X
is
a
value
from
0
to
9
that
provides
a
sequential
unique
key.
So,
the
first
disc
error
that
is
encountered
in
the
job
will
be
given
the
key
value
of
DiscErrorIndex0,
the
second
disc
error
(within
the
same
job)
will
be
given
the
key
value
of
DiscErrorIndex1,
and
so
on.
The
number
of
disc
errors
reported
is
limited
to
10
so
the
values
for
this
key
can
range
from
DiscErrorIndex0
up
to
DiscErrorIndex9.
A
disc
may
have
more
than
1
error
reported
if
the
disc
was
retried.
Example:
A
job
is
set
to
record
3
copies
of
a
disc:
Disc
1
is
recorded
successfully.
Disc
2
is
recorded
successfully.
Disc
3
fails
to
record
two
times
before
successfully
burning
on
its
third
attempt.
In
this
example,
the
entries
for
this
job
will
be:
DiscErrorIndex0
=
3
DiscErrorIndex1
=
3
3.2.4.16
DiscErrorNumberX
Integer
value
that
details
what
disc
error
has
occurred.
Please
see
Appendix
C
for
details
on
disc
errors
and
the
potential
values.
X
is
a
value
from
0
to
9
that
provides
a
sequential
unique
key.
So,
the
first
disc
error
that
is
encountered
in
the
job
will
be
given
the
key
value
of
DiscErrorNumber0,
the
second
disc
error
(within
the
same
job)
will
be
given
the
key
value
of
DiscErrorNumber1,
and
so
on.
The
number
of
disc
errors
reported
is
limited
to
10
so
the
values
for
this
key
can
range
from
DiscErrorNumber0
up
to
DiscErrorNumber9.
3.2.4.17
DiscErrorStringX
String
corresponding
to
the
DiscErrorNumber.
Please
see
Appendix
C
for
details
on
disc
errors
and
the
possible
strings.
X
is
a
value
from
0
to
9
that
provides
a
sequential
unique
key.
So,
the
first
disc
error
that
is
encountered
in
the
job
will
be
given
the
key
value
of
DiscErrorString0,
the
second
disc
error
(within
the
same
job)
will
be
given
the
key
value
of
DiscErrorString1,
and
so
on.
The
number
of
disc
errors
reported
is
limited
to
10
so
the
values
for
this
key
can
range
from
DiscErrorString0
up
to
DiscErrorString9.
