Ho ho ho Bin library

[Programmer]

How  do we know what the overlap is so you don't get
a bunch of the same thing ? Doesn't make much sense
to keep sending the same binaries over and over...
Lyndon.
-----Original Message-----
From: Bruce Plecan <nacelp at bright.net>
To: gmecm at diy-efi.org <gmecm at diy-efi.org>
Date: October 2, 2000 6:40 PM
Subject: Re: Ho ho ho Bin library


>
>
>  Just gonna do stock (gm) ones.
>  The aftermarket flames aren't worth wasting the band width on.  Seems
like
>when I broached that all folks wound up doing were looking to bad mouth the
>chip folks, while generally true, just went over board, IMO, and we got
>enough good stuff that I would perfer to stick with the originals.
>   I'm not really into sharing custom bins, kinda like making bread and
>learning to fish,  once ya get into it, no biggy.   Too many folks seem to
>be looking at times just to get close, and miss getting it right.
>   If anyone has any hacs or related material I would be more then willing
>to include that in the library.
>   Just having a BCC is fine, what helps is knowing the ecm part no., if
you
>include the mask no, that would save alot of work,  the  labeling I'm using
>is like  AMUR1234 42.bin,  so just looking at the file name, we can ID it
as
>a 747 bin file.
>   if you included a .txt with application (ie engine, tranny, final drive,
>platform), that would be spectacular.
>   Just sent the stuff to me for organizing,  if longer then 2 Meg please
>let me know it's coming, anything less, just hit send, bright.net is at
>times moody, but usually OK.
>   EVERTHING IN .BIN format please.
>   The vast majority of folks are using that.
>Bruce
>
>
>> Do you want just OE CAL's, or do you also want some aftermarket
commercial
>> tuner CAL's too?  Where's the deposit bag located?   How about
>> custom/private hac'd CAL's?   Just GM, or other's as well?  Can we tag a
>CAL
>> file on the end of an E-Mail description of same, and not have the
message
>> turned back due to "attachments" present?
>>
>> Assuming you are filing these CAL's in some categorical fashion, you'll
>need
>> to know at a minimum???.......1) ECM/PCM/Controller base P/N and
>description
>> 2)base MEMCAL broadcast code, or P/N if known, and description if known
>> 3)complete file checksum, and byte size    4)description of what the
CAL's
>> for/from    5)description of major changes/compilations    6)binary
>format,
>> or do you care?   7)mask ID.
>>
>> Anything else that contributors should also include to make your life
>> easier?
>>
>> Thanks for all of your work Bruce!
>>
>>
>> Walt.
>>
>>
>>
>>
>> > Ludis has generously shared his files with us.
>> > He even had the organized by ecm saving me a huge amount of work.
>> > I'd like to publicly Thank him for this.
>> >
>> > BTW, we're almost at the 1,000 mark!.
>> >
>> > Whoda thought
>> > Bruce
>> >
>> >
>>
>> -------------------------------------------------------------------------
-
>> --
>> > To unsubscribe from gmecm, send "unsubscribe gmecm" (without the
quotes)
>> > in the body of a message (not the subject) to
>majordomo at lists.diy-efi.org
>> >
>>
>> -------------------------------------------------------------------------
-
>--
>> To unsubscribe from gmecm, send "unsubscribe gmecm" (without the quotes)
>> in the body of a message (not the subject) to majordomo at lists.diy-efi.org
>>
>>
>
>---------------------------------------------------------------------------
-
>To unsubscribe from gmecm, send "unsubscribe gmecm" (without the quotes)
>in the body of a message (not the subject) to majordomo at lists.diy-efi.org
>
>

----------------------------------------------------------------------------
To unsubscribe from gmecm, send "unsubscribe gmecm" (without the quotes)
in the body of a message (not the subject) to majordomo at lists.diy-efi.org