Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!sun-barr!sun!imagen!atari!kbad
From: kbad@atari.UUCP (Ken Badertscher)
Newsgroups: comp.sys.atari.st
Subject: Re: versions
Message-ID: <1555@atari.UUCP>
Date: 13 Jun 89 04:16:37 GMT
References: <865@stag.UUCP>
Reply-To: kbad@atari.UUCP (Ken Badertscher)
Organization: Atari Corp., Sunnyvale, CA
Lines: 32

In article <865@stag.UUCP> to_stdnet@stag.UUCP writes:
|  kbad@atari.UUCP (Ken Badertscher) writes ...
|
| > Hmm, Sversion is returning a float value?  Hmmm... ;-)
|
| No, I'm not *that* silly.  [source code omitted...]

Of *course* you aren't.  *I* was being silly (note the smiley above... ;-).

| ... basing the above on the Sversion() documentation in Pollack & Weber's
| "Atari ST Application Programming," which says in part:
|     "The high byte contains the minor version number and the low byte
|      the major version number."

Oh my, I stand corrected.  That documentation is corroborated by the
GEMDOS documentation, which says that Sversion returns the GEMDOS
version number "in byte-reversed format."  Don't ask me why it's like
that...  In fact, the Pexec Cookbook is incorrect in this regard, it
states that the high byte is the major version number.  According to
the GEMDOS bible, the high byte is the MINOR version number.  So
byteswap it before doing any version dependancy tests.

| Heh... what IS the new version of TOS going to be called, Ken? 
| Besides late, I mean. :-)

My lips are sealed until the general ROM release.  WhoKnowsWhen.


-- 
   |||   Ken Badertscher  (ames!atari!kbad)
   |||   Atari R&D System Software Engine
  / | \  #include <disclaimer>