Article View: general
Article #601Re: HELP VIN' requested
From: Hugh Johnson
Date: Fri, 22 Apr 1994 14:21
Date: Fri, 22 Apr 1994 14:21
35 lines
2903 bytes
2903 bytes
In article <1156kc7w165w@slic.cts.com> mikey@slic.cts.com (Mike Shirley) writes:
johnson@cambridge.mitchell.com (Hugh Johnson) writes:
> Hey guy: The man has 192 page document from NICB (National
> Insurance Crime Bureau) that describes the exact method of decoding
> the V.I.N. of various manufacuturers. Guess What??? No
> manufacuturer maintains the same VIN decoding as any other,
> further, a manufacturer may not even do it the same way in
-- -- -- -- < snip > -- -- --
This being the case, then to dispel the feelings of title fraud,
I'd suggest that folks who send you their VIN and vehicle
description, replace the last 6 digits of the VIN with
place-holding X's. This will still give you what you need without
passing the owner's actual "serial" number.
-- -- -- -- < snip some more > -- -- --
How do you propose to debug the alogorithm without being able to
test the decoding of the check digit that is built into EVERY VIN?
Besides, the last n digits of the VIN that is the actual serial
number of that very vehicle is appropiate *ONLY* to the vehicles
assembled at *ONE* assembly plant. If the vehicle mnake/model is
assemble at more than one location in the world, then the serial
number doen'e mean diddly, except to the exact plant of assembly.
Wanna try again??
--
johnson@mitchell.com or | Opinions? I doan' have no steenkin'
hugh@seada.com or | opinions. They doan' let me have
76317.2234@compuserve.com | none.
Technical Details
Message-ID:
<JOHNSON.94Apr22142116@cambridge.mitchell.com>Path:
arc1-ca.pugleaf.net!bga.com!cs.utexas.edu!usc!howland.reston.ans.net!europa.eng.gtefsd.com!library.ucla.edu!ihnp4.ucsd.edu!news.cerf.net!news.cerf.net!johnsonReferences:
<JOHNSON.94Apr20131544@cambridge.mitchell.com> <1156kc7w165w@slic.cts.com>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 106ed4,dcc02b24d9c88c1 X-Google-Attributes: gid106ed4,public X-Google-Thread: fa37c,dcc02b24d9c88c1 X-Google-Attributes: gidfa37c,public X-Google-Thread: f765b,dcc02b24d9c88c1 X-Google-Attributes: gidf765b,public X-Google-Thread: 101049,dcc02b24d9c88c1 X-Google-Attributes: gid101049,public X-Google-Thread: 10a12a,dcc02b24d9c88c1 X-Google-Attributes: gid10a12a,public X-Google-Thread: 103916,dcc02b24d9c88c1 X-Google-Attributes: gid103916,public X-Google-Thread: 12e62e,33d3956bb867ea2 X-Google-Attributes: gid12e62e,public X-Google-ArrivalTime: 1994-04-22 14:18:42 PST Path: arc1-ca.pugleaf.net!bga.com!cs.utexas.edu!usc!howland.reston.ans.net!europa.eng.gtefsd.com!library.ucla.edu!ihnp4.ucsd.edu!news.cerf.net!news.cerf.net!johnson From: johnson@cambridge.mitchell.com (Hugh Johnson) Newsgroups: general,tx.general,nj.general,ca.general,ny.general,dc.general,mn.general,ca.dri Subject: Re: HELP VIN' requested Date: 22 Apr 94 14:21:16 Organization: /cambridge/usr2/users/johnson/.organization Lines: 35 Message-ID: <JOHNSON.94Apr22142116@cambridge.mitchell.com> References: <JOHNSON.94Apr20131544@cambridge.mitchell.com> <1156kc7w165w@slic.cts.com> Reply-To: johnson@mitchell.com NNTP-Posting-Host: mitchell.com In-reply-to: mikey@slic.cts.com's message of Thu, 21 Apr 94 22:27:47 PDT