Re: A86: 86g File Quirks

To: assembly-86@lists.ticalc.org
Subject: Re: A86: 86g File Quirks
From: Stan Seibert <indigo@aztec.asu.edu>
Date: Mon, 29 Sep 1997 04:28:35 -0700
References: <3.0.2.16.19970928232219.326fdeda@charlie.cns.iit.edu>
Reply-To: assembly-86@lists.ticalc.org

Alan Bailey wrote:
> 
> >At the name length offsets in all of the files that didn't work, I found
> >that the length stored there was correct (0x05 for a variable named
> >"Sqrxz") but the name that followed always contained 8 characters.  In
> >the Sqrxz.86g, the Sqrxz was followed by 3 spaces (0x20) then the
> >correct data length.  In Aurora, the first variable, APic1, was followed
> >by null characters.  Later in the same file, the variable named AuroraO2
> >(which has 8 letters) has a name length of 6 stored in the file.  It
> >seems like whatever program that everyone else is using ignores the name
> >length byte and assumes that the name has 8 characters no matter what.
> >Did I miss something in the standard?  Do 86g files differ from 85g
> >files?
> >
> 
> Yes, I noticed that when i was making a 86p maker for object code.
> (prgm86.exe)
> I don't know why they would do it, besides to make each file more equal in
> format.  They also might do this so that the 85 graphlink doens't read 86
> files but the 86 graphlink can read both.  possibly...
> 
> >Also, I was wondering if everyone uses the same program for converting
> >their object files to 85p/85g files?
> >
> 
> i just use the graphlink sofware for DOS, don't know about linux

Well, who decided to do this first?  It sounds as if you were just
making your program act like everyone elses.

Anyway, its not important.  I can rewrite that portion of the code to
work around this problem/feature/bug/whatever.

Stan

References:

Re: A86: 86g File Quirks

From: Alan Bailey <bailela@charlie.cns.iit.edu>