[A83] Re: Windows 2000 SP3
[Prev][Next][Index][Thread]
[A83] Re: Windows 2000 SP3
Can you be more specific?
I just did a quick verification of the source code with the format published
here:
http://gladstone.uoregon.edu/~tsinger/link/TI-83+/fformat.html
The only error I see is that the first 2 bytes of the variable entry should
be 0x0d instead of 0x0b. Is there anything else? Another possible issue is
that the variable type ID is 0x06 (edit locked program) when it possibly
should be 0x05 (program). Does it need to be changed?
The length values are weird and don't exactly match the specification, but I
remember doing a lot of tests and comparisons when I wrote the code, so it
is likely to be correct.
The rewrite of Bin2Var 2.0 will follow that specification exactly and the
layout of the source code will make it trivial to verify that it is correct
according to the specification.
The following patch should correct the first problem:
--- bin2var.c.orig 2002-08-06 16:20:53.000000000 -0500
+++ bin2var.c 2002-08-06 16:32:02.000000000 -0500
@@ -162,8 +162,10 @@
else
i = n + 18;
fwrite(&i, 2, 1, fp);
- if ((ext == E_82P) || (ext == E_83P) || (ext == E_8XP))
+ if ((ext == E_82P) || (ext == E_83P))
cfwrite("\x0b\0x00", 2, fp, &chk);
+ else if (ext == E_8XP)
+ cfwrite("\x0d\0x00", 2, fp, &chk);
else if (ext == E_85S)
{
i = 4 + strlen(str);
> Yes, but Bin2Var does not make _proper_ 8xps. Most software doesn't
> care, but the TI Flash Debugger will lock up if you try and send one to
> it.
Follow-Ups:
References: