Re: digging in the 9100....

<x-flowed>
Not either CRC-16 or CRC-32 as far as I can tell. I did find a nice little
CRC calculator though, does -16 and -32 as you type in the string of
digits. Nice!

http://www.efg2.com/Lab/Mathematics/CRC.htm

Doesn't create the 9010A ROM signature either though...now to find a
signature generator like the CRC calculator...

John :-#)#

At 05:51 PM 22/09/2002 -0700, John Robertson wrote:
>Definitely the last two bytes are some sort of checksum.
>
>In further digging I find the following bytes are defined as follows:
>(note the bytes here refer to the original read as in serial #4900002 down
>below)
>
>Byte 04 = Hard drive type (according to the lookup list of fluke - 42 is
>the WD/Miniscribe8425
>Byte 0A = Report Drive Errors No = 00, Yes = 0A
>Byte 0F = RAM Size 18 = 1.5M, 20 = 2.0M, 40 = 4.0M
>Byte 11 = Network node #
>Byte 14 = No Network Boot (00) or Network Boot (01)
>Byte 18 = 9100 (FE) or 9105 (FF)
>
>and the last two bytes are changing each time...not an obvious checksum,
>might be the !@#$!$# Fluke Signature...it is for the entire data stream
>though, not just the serial number. Done enough for now, someone else can
>figure that out...need to get shopping done...kids lunches...etc...
>
>I've posted a series of different reads of the EEPROM on
>ftp://ftp.flippers.com/Fluke/9100_Fixture/ called EEPROM.ZIP and if anyone
>wants to figure that out go for it!
>
>Note that the data is scrambled on this EEPROM file as they are read by my
>Andromeda Research programmer and it seems to shuffle the data bytes
>around. If you compare the 2444pep1 to the stream from serial number
>4900002 you will see the pattern shift. instead of byte 0, 1, 2, 3, 4,
>5....1D, 1E, 1F the stream is 0,1, 10, 11, 8, 9, 18, 19, 4, 5, 14, 15, c,
>d, 1c, 1d, 2, 3, 12, 13, a, b, 1a, 1b, 6, 7, 16, 17, e, f, 1e, 1f. Like I
>say a bit scrambled...
>
>2444pep1 is the default
>2444pep2 is Network changed to 55, memory to 1.5m, system to 9105
>2444pep3 changed back to 9100 others left the same
>2444pep4 not sure thing this is where I changed the RAM to 2M
>2444pep7 Changed hard drive setting to 3rd option (on my machine)
>2444pep8 Changed to network boot
>2444pep9 Changed network node to -1 (FF)
>2444pepa Changed back to system boot and turned off disk error reporting.
>
>
>
>John :-#)#
>
>At 04:41 PM 20/09/2002 -0700, John Robertson wrote:
>>It appears the last two bytes (BF BE & 23 0F) are a checksum of some sort
>>for the serial number...anybody have an idea?
>>
>>004A C4A2 = #4900002 CS=BEBF?
>>0048 DC58 = #4775000 CS=0F23?
>>
>>John :-#)#
>>
>>At 07:38 AM 19/09/2002 +0000, steve@coule.freeserve.co.uk wrote:
>>
>>> > So what I have is two 32 byte data streams, the first one (old base) is
>>> > serial number 4900002 (unknown Site Code) is:
>>> > A2 C4 4A 00 42 03 FF FB 01 00 0A 00 03 50 08 40
>>> > 00 00 00 00 00 03 00 00 FE 02 00 00 00 00 BF BE
>>> >
>>> > And serial number (NOS) 4775000 "Site Code 1" is:
>>> > 58 DC 48 00 42 00 FC 00 FC 00 00 00 03 50 08 20
>>> > 00 00 00 00 00 00 00 00 FE 02 01 00 00 00 23 0F
>>> >
>>> > I suspect the first three
>>> > bytes are the serial number...maybe...
>>> >
>>>
>>>The first three bytes are the serial number! Just put the hex numbers
>>>004ac42a into calculator as a hex number, convert to decimal and it's
>>>4900002 ... he other works too!
>>>
>>>
>>>_______________________________________________________________________
>>>Freeserve AnyTime, only £13.99 per month with one month's FREE trial!
>>>For more information visit http://www.freeserve.com/time/ or call free
>>>on 0800 970 8890

</x-flowed>
Received on Sun Sep 22 22:40:19 2002