Hi Willi,

>    Here you go:

first of all thanks :-)

>Version      Contents
>-------      --------
>1.0.1        7
>1.0.2        7
>1.1.1        7
>1.2          2

Is there some misunderstanding or transmission error? It looks like
you wrote, that the first three verions had a KVERSION of _SEVEN_ !

I've got a 1.0.1 here that has zero and I've got a very early Global
Page Disassembly Listing showing zero as well...

Oliver



a2@wilserv.com (Willi Kusche) writes:
>> Unfortunately I didn't find sonmething like that on the web nor in
>> this group nor in the ProDOS TechNotes. So can somebody supply such a
>> table?

>    Here you go:

>Version      Contents
>-------      --------
>1.0.1        7
>1.0.2        7
>1.1.1        7

Where did you get the above? I tested 1.1.1 and it was definitely $01.
Also, ProDOS Technote #23 definitely states that KVERSION was incremented
when the version went from 1.0.2 to 1.1.

>1.2          2
>1.3          3
>1.4          4
>1.5          5
>1.6          6
>1.7          7
>1.8          8
>1.9          8
>2.0.1        $21
>2.0.2        $22
>2.0.3        $23

I agree with these.
-- 
David Wilson  School of IT & CS, Uni of Wollongong, Australia



Hi Willi,

>> [...] you wrote, that the first three verions had a KVERSION of _SEVEN_ !
>
>    Oops, I was wrong.  1.1.1 is 1.  1.0.1 is 0.  1.0.2 is 0.  That
>makes much more sense.

Indeed ;-))

So for the records the reason I asked for that: I need to implement an
'operating system ID', but I can't use the KVERSIONs straight because
I need the $00 as "No ProDOS present at all -> DOS 3.3 active".

But from what I learned now I can safely add a $10 to all values < $10
because there were never KVERSIONs in the range $10-$1F. This approach
gives me both a destinctable $00 and the benefit of the high nibble of
my ID being always identical to the ProDOS major number :-))

Again thanks for your help, Oliver