Home
Forums
New posts
Search forums
What's new
New posts
New profile posts
Latest activity
Members
Current visitors
New profile posts
Search profile posts
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Home
Forums
CARDING & HACKING
Hacking Tools
TheJerm Best Software + Tutorial For...
Message
<blockquote data-quote="Prime" data-source="post: 938" data-attributes="member: 18"><p>* Copy</p><p></p><p>This button copies the text in the white textbox to the corresponding track's textbox on the "Actions" tab.</p><p></p><p></p><p>State License/ID Format Scripts</p><p>_______________________________</p><p></p><p>Each state must have its own custom script file in order to be able to encode license/ID tracks for that state. When the program is loaded it finds all the "*.idf" files that are in the same directory as the program and adds all the state names to the "State" dropdown menu on the "License/ID" tab for you to choose from. These instructions should allow you to be able to create or modify your own license/ID format scripts. It helps if you refer to the included California script as you're reading about the commands so you can see exactly how they're implemented. I used capitalization in my CA script to make it easier to read but none of the commands are case-sensitive so capitalization is not necessary. The scripts are regular text files but their file extension must be ".idf".</p><p></p><p>---</p><p>Command: state abbreviation</p><p>Example: %CA</p><p>Description: The first line of the script file must always contain the "%" sign followed by the two letter state abbreviation. The program reads this text and adds it to the "State" dropdown menu. If your script doesn't start with this line it won't be available in the program.</p><p></p><p>---</p><p>Command: track</p><p>Example: :track1</p><p>Description: Each track must be started off with ":track#", where "#" is the number of the track. All the data that follows up to the next "track" command applies to that track.</p><p></p><p>---</p><p>Command: # (field designator)</p><p>Example: #4</p><p>Description: Each track is broken down into several fields. Each field has a different name to identify it and can have different properties. Every field must be identified by the "#" sign followed by a number. The number determines the field's position in the track in relation to the other fields. The first field must be "#1".</p><p></p><p>---</p><p>Command: ## (subfield designator)</p><p>Example: ##2</p><p>Description: A field can be made up of multiple subfields. For example, the "NAME" field can contain three subfields for "LAST", "FIRST" and "MIDDLE". Each subfield must be identified by "##" followed by a number. The first subfield of any field must be "##1".</p><p></p><p></p><p>The properties of each field or subfield are set by using several commands which are placed on the lines following the "#" or "##" line. Each command must be preceded by a "*" and be on its own line. Most commands are followed by an "=" sign and then the parameters for that command. The order the commands are listed is not important. Following is a list of all the valid commands and their functions:</p><p></p><p>---</p><p>Command: name</p><p>Example: *name = CITY</p><p>Description: All fields and subfields must be given a name. All the standard ID fields such as NAME, ADDRESS, DOB, etc. have preset names that you must use so the program can recognize them and associate them with the proper fields on the "License/ID" tab. Any additional field not recognized by the program can be given any name you want as long as it's different from the preset names. Following are all the names of the preset fields and subfields:</p><p></p><p>STATE</p><p>CITY</p><p>NAME</p><p> LAST</p><p> FIRST</p><p> MIDDLE</p><p>ADDRESS</p><p> ADDRESS1</p><p> ADDRESS2</p><p>IIN</p><p>LICNUM</p><p>EXPDATE</p><p> EXPYEAR</p><p> EXPMONTH</p><p>DOB</p><p> DOBYEAR</p><p> DOBMONTH</p><p> DOBDAY</p><p>VERNUM</p><p>ZIP</p><p>CLASS</p><p>RSTR</p><p>ENDR</p><p>SEX</p><p>HT</p><p>WT</p><p>HAIR</p><p>EYES</p><p>DMVNUM</p><p>PHOTODATE</p><p> PHOTOYEAR</p><p> PHOTOMONTH</p><p> PHOTODAY</p></blockquote><p></p>
[QUOTE="Prime, post: 938, member: 18"] * Copy This button copies the text in the white textbox to the corresponding track's textbox on the "Actions" tab. State License/ID Format Scripts _______________________________ Each state must have its own custom script file in order to be able to encode license/ID tracks for that state. When the program is loaded it finds all the "*.idf" files that are in the same directory as the program and adds all the state names to the "State" dropdown menu on the "License/ID" tab for you to choose from. These instructions should allow you to be able to create or modify your own license/ID format scripts. It helps if you refer to the included California script as you're reading about the commands so you can see exactly how they're implemented. I used capitalization in my CA script to make it easier to read but none of the commands are case-sensitive so capitalization is not necessary. The scripts are regular text files but their file extension must be ".idf". --- Command: state abbreviation Example: %CA Description: The first line of the script file must always contain the "%" sign followed by the two letter state abbreviation. The program reads this text and adds it to the "State" dropdown menu. If your script doesn't start with this line it won't be available in the program. --- Command: track Example: :track1 Description: Each track must be started off with ":track#", where "#" is the number of the track. All the data that follows up to the next "track" command applies to that track. --- Command: # (field designator) Example: #4 Description: Each track is broken down into several fields. Each field has a different name to identify it and can have different properties. Every field must be identified by the "#" sign followed by a number. The number determines the field's position in the track in relation to the other fields. The first field must be "#1". --- Command: ## (subfield designator) Example: ##2 Description: A field can be made up of multiple subfields. For example, the "NAME" field can contain three subfields for "LAST", "FIRST" and "MIDDLE". Each subfield must be identified by "##" followed by a number. The first subfield of any field must be "##1". The properties of each field or subfield are set by using several commands which are placed on the lines following the "#" or "##" line. Each command must be preceded by a "*" and be on its own line. Most commands are followed by an "=" sign and then the parameters for that command. The order the commands are listed is not important. Following is a list of all the valid commands and their functions: --- Command: name Example: *name = CITY Description: All fields and subfields must be given a name. All the standard ID fields such as NAME, ADDRESS, DOB, etc. have preset names that you must use so the program can recognize them and associate them with the proper fields on the "License/ID" tab. Any additional field not recognized by the program can be given any name you want as long as it's different from the preset names. Following are all the names of the preset fields and subfields: STATE CITY NAME LAST FIRST MIDDLE ADDRESS ADDRESS1 ADDRESS2 IIN LICNUM EXPDATE EXPYEAR EXPMONTH DOB DOBYEAR DOBMONTH DOBDAY VERNUM ZIP CLASS RSTR ENDR SEX HT WT HAIR EYES DMVNUM PHOTODATE PHOTOYEAR PHOTOMONTH PHOTODAY [/QUOTE]
Name
Verification
Post reply
Home
Forums
CARDING & HACKING
Hacking Tools
TheJerm Best Software + Tutorial For...
Top