Free us zip code 21150 software for linux

Files Zip for Plone project allows users to download all files from a folder (recursively) in a ZIP archive.

Adds a document action to folders (and folderish contents) that enables to download all files and images from archetypes based contents available from that folder in a ZIP file.

Optionally, the user may get the DC metadata of the contents that provide files in XML-RDF format in the ZIP file.

Kunzip is a free (but not opensource) library for decompressing ZIP archives. Kunzip started out as a test program I wrote for decompressing .zip files through a command line program.
I eventually added hooks to make it a DLL that can be used from Windows programs. It is also possible to compile it for Unix (and Unix-like OSs such as Linux) as a .so library.
My plan for the kunzip.dll was to make it as simple to use as possible so it can even be used from VisualBasic or such. It should be fully compatible with zipfiles created by InfoZip, PkZip, and WinZip. You can download it from the link below and view the prototypes for different languages that can call kunzip.dll.
I originally started this code to be able to decompress (and maybe even compress) PNG graphic files. Since this is the same algorithm used in gzip and zip (WinZip, InfoZip, etc), I decided to make it work with .zip files instead. Unfortunately, all the specs I had for this compression were for PNG and Zip is slightly different, so I had some problems getting it working :).
My first version kunzip (which built the huffman tables using arrays instead of trees and did a lot of fseeking) ran painfully slow, but my latest version runs quite well. One interesting thing I found, when I did static huffman decompression for TIFF, I did it using lookup tables instead of trees. This actually ran very fast, altho Im not sure of the speed difference if I used trees instead. On this project, I started out doing all 3 huffman sets using lookup tables.
After I saw how slow it ran, I switched the length huffman codes to a tree and the decompression ran almost double the speed. When I changed the distance huffman codes to trees, the decompression slowed down by a few seconds. So I left length/distance huffman codes as trees and kept the first huffman codes as lookup tables. I may try and improve on the speed even more later.
Not only can you download the source code which can be compiled on both Unix/Linux and Windows, but Ive also included a Windows DLL I built for doing unzipping. I think it is quite easy to use, so if you need an unzip library for Windows, feel free to use this (feel free to make a donation to my PayPal account too if you like.
Btw, this code was written to be compiled on Unix (Linux,FreeBSD,etc) systems. If you want to build the DLL, you can download the source code and type: make dll. The mingw C compiler needs to be used. Im 99% sure I did some things that dont work in Visual C++. I may make it compile to a Unix shared lib too for fun.
The original May 6, 2005 version of kunzip decompresses a 120meg file in about 3min40sec on my AMD Athlon XP box. Since then, I put some major optomizations in and it now decompresses the same file in 20 seconds.
Enhancements:
- The license has been changed to the LGPL.

podLoader allows you to load content from the Web or other desktop files onto your iPod. Later, for example while traveling, you can check out news from any RSS feed, the weather, or the contents of any file from your desktop.
This application uses the "Notes" feature on third-generation or later touch wheel iPods.
Usage:
In Brief:
- Run podLoadr by double-clicking on podloadr.jar after installing the JRE (or run java -jar podloadr.jar from a command prompt)
- Drag & drop files or links onto the "Files & Links" tab. Browsing or manually typing the file name also works.
- Check some news feeds, add weather zip codes and create a notes on their respective tabs.
- Click the run button (ensure that the iPod is connected and enabled in disk mode).
In Detail:
- In order to load a web page or news feed simply do the following:
- Ensure that your iPod is enabled for disk use. To do this in iTunes:
- Select your iPod under Devices in the Source list.
- Click the Summary tab.
- In the Options section of the Summary pane, click the "Enable disk use" checkbox.
- Note that if the "Manually manage songs and playlists" option is enabled, "Enable disk use" is always enabled or turned on.
- Connect your iPod to your computer as you usually do.
- Exit iTunes - just to be safe.
- Ensure that you have a recent version of the Java runtime (either JDK or JRE) from Sun.
- Run podLoadr by double clicking on podLoadr.jar. Alternatively you can open a command prompt and type java -jar podLoadr.jar
- Note that podLoadr.jar itself can be stored on the ipod and run directly from there. Keep podLoadr.jar and podLoadr.ini together.
- Populate the various tabs in podLoadr.
- Add your custom items to the "Files & Links" tab. This can be done in any of the following ways.
- Drag a file from your desktop or Explorer onto the list
- Drag a link from Internet Explorer or Firefox onto the list (by grabbing the icon in the address box)
- Type the full name of a file in the Name box and click on add
- Click on "Add/Browse" and navigate to the file you need and add it to the list.
- Check off the news feeds that you want from the categorized list.
- Enter the ZIP codes of the weather you want separated by commas.
- Double check the ipod tab to ensure that the drive letter is correct. Or if you have multiple iPods then you can change this setting. (If thats too confusing feel free to send the other iPod my way :-)
To view the note, disconnect your iPod, scroll the menu to Extras, and select Notes. Choose the name the file you created and press the Center button to display the content of the file. You can.t edit the file using iPod, but you can delete it or update it whenever your iPod is connected to your computer.
podLoader uses the "Notes" feature of the iPod to support downloading and offline viewing of online content. Such presentations can be used, for example, as directed lessons or self-paced electronic guided tours. Notes is available on iPod models beginning with third-generation iPod (dock connector) models with the touch wheel.

uCON64 project is a game backup tool and emulator Swiss Army knife program.
uCON64 is a tool to backup all kinds of video games (cartridges and CDs).
It supports most available backup units for cartridge-based consoles. It also performs many other tasks, like ROM hacking and conversion of proprietary CD images for use with cdrecord.
Support for many different backup units to backup/restore ROM(s) and SRAM(s) is also continuously added and updated (if their manufacturers cooperate).
Supports all common patch file formats like IPS (with RLE compression), APS, BSL (Baseline Patch format), PPF (Playstation Patch File), and Game Genie
Support for use and creation of RomCenter Data files (DAT) for secure detection of bad dumps.
Has many options for every kind of ROM or SRAM handling, modification, and management .
Supports gzip and zip.
Enhancements:
- updated (GBA) fixed F2A USB send code (by dbjh; many thanks to David Gauchard for feedback, testing and sending a patch to fix the problem)
- updated (N64) cleaned up Doctor V64 Junior transfer source code (by dbjh; thanks to TenOfTen and GameCopierUser0666 for testing)
- updated (SNES) added new SWC "I/O mode" 0x100, dump BIOS (by dbjh)
- updated (GB) improved ROM info (by dbjh)
- updated (GB) fixed problem with dumping "Rocket Games" cartridges with the Game Boy Xchanger (by dbjh; thanks to Anna Kubisty for reporting the problem and testing, and thanks to Cowering for his help and providing us with the necessary information)
- updated (GB) cleaned up Game Boy Xchanger transfer source code (by dbjh; many thanks to Anna Kubisty for testing)
- added (DC) --scr scramble 1ST_READ.BIN for selfboot CDs (by NoisyB)
- added (DC) --unscr unscramble 1ST_READ.BIN for non-selfboot CDs (by NoisyB)
- added (DC) --mkip generate IP.BIN file with default values (by NoisyB)
- added (DC) --parse=TEMPLATE parse TEMPLATE file into a IP.BIN (by NoisyB)

rubyzip is a Ruby module for reading and writing zip files.
Installation:
If you have rubygems you can install rubyzip directly from the gem repository
gem install rubyzip
Otherwise obtain the source (see below) and run
ruby install.rb
To run the unit tests you need to have test::unit installed
rake test
Enhancements:
- Symlink support was added along with support for Unix file permissions.
- Memory usage during decompression was reduced.
- Zip streams now model IO objects more closely.

Resistor Color Code Calculator project calculates the value of a resistor (an electronic component).

The colors on the resistor are input into the program, and the result displays the resistance value of the resistor.

This is much easier than memorizing rhymes to remember colors.

Geo:Coder:US 1.00 offers a full-feature facility for geocoding US addresses, that is, estimating the latitude and longitude of any street address or intersection in the United States, using the TIGER/Line data set from the US Census Bureau. Geo:Coder:US uses Geo:TigerLine to parse this data, and DB_File to store a highly compressed distillation of it, and Geo:StreetAddress:US to parse addresses into normalized components suitable for looking up in its database.

You can find a live demo of this code at http://geocoder.us/. The demo.cgi script is included in eg/ directory distributed with this module, along with a whole bunch of other goodies. See Geo:Coder:US:Import for how to build your own Geo:Coder:US database.

Consider using a web service to access this geocoder over the Internet, rather than going to all the trouble of building a database yourself. See eg/soap-client.pl, eg/xmlrpc-client.pl, and eg/rest-client.pl for different examples of working clients for the rpc.geocoder.us geocoder web service.

Major Features:

1. Geo:Coder:US->geocode( $string )
   • Given a string containing a street address or intersection, return a list of specifiers including latitude and longitude for all matching entities in the database. To keep from churning over the entire database, the given address string must contain either a city and state, or a ZIP code (or both), or geocode() will return undef.
   • geocode() will attempt to normalize directional prefixes and suffixes, street types, and state abbreviations, as well as substitute TIGER/Line's idea of the "primary street name", if an alternate street name was provided instead.
   • If geocode() can parse the address, but not find a match in the database, it will return a hashref containing the parsed and normalized address or intersection, but without the "lat" and "long" keys specifying the location. If geocode() cannot even parse the address, it will return undef. Be sure to check for the existence of "lat" and "long" keys in the hashes returned from geocode() before attempting to use the values! This serves to distinguish between addresses that cannot be found versus addresses that are completely unparseable.
   • geocode() attempts to be as forgiving as possible when geocoding an address. If you say "Mission Ave" and all it knows about is "Mission St", then "Mission St" is what you'll get back. If you leave off directional identifiers, geocode() will return address geocoded in all the variants it can find, i.e. both "N Main St" and "S Main St".
   • Don't be surprised if geocoding an intersection returns more than one lat/long pair for a single intersection. If one of the streets curves greatly or doglegs even slightly, this will be the likely outcome.
   • geocode() is probably the method you want to use. See more in the following section on the structure of the returned address and intersection specifiers.
2. Geo:Coder:US->geocode_address( $string )
   • Works exactly like geocode(), but only parses addresses.
3. Geo:Coder:US->geocode_intersection( $string )
   • Works exactly like geocode(), but only parses intersections.
4. Geo:Coder:US->filter_ranges( $spec, @candidates )
   • Filters a list of address specifiers (presumably from the database) against a query specifier, filtering by prefix, type, suffix, or primary name if possible. Returns a list of matching specifiers. filter_ranges() will ignore a filtering step if it would result in no specifiers being returned. You probably won't need to use this.
5. Geo:Coder:US->find_ranges( $address_spec )
   • Given a normalized address specifier, return all the address ranges in the database that appear to cover that address. find_ranges() ignores prefix, suffix, and type fields in the specifier for search purposes, and then filters against them ex post facto. The intention for find_ranges() to find the closest match possible in preference to returning nothing. You probably want to use lookup_ranges() instead, which will call find_ranges() for you.
6. Geo:Coder:US->lookup_ranges( $address_spec, @ranges )
   • Given an address specifier and (optionally) some address ranges from the database, interpolate the street address into the street segment referred to by the address range, and return a latitude and longitude for the given address within each of the given ranges. If @ranges is not given, lookup_ranges() calls find_ranges() with the given address specifier, and uses those returned. You probably want to just use geocode() instead, which also parses an address string and determines whether it's a proper address or an intersection automatically.
7. Geo:Coder:US->find_segments( $intersection_spec )
   • Given a normalized intersection specifier, find all of the street segments in the database matching the two given streets in the given locale or ZIP code. find_segments() ignores prefix, suffix, and type fields in the specifier for search purposes, and then filters against them ex post facto. The intention for find_segments() to find the closest match possible in preference to returning nothing. You probably want to use lookup_intersection() instead, which will call find_segments() for you.
8. Geo:Coder:US->lookup_intersection( $intersection_spec )
   • Given an intersection specifier, return all of the intersections in the database between the two streets specified, plus a latitude and longitude for each intersection. You probably want to just use geocode() instead, which also parses an address string and determines whether it's a proper address or an intersection automatically.

Requirements: Perl

ctopy automates the parts of translating C source code to Python source code that are difficult for a human but easy for a machine.

This allows a human programmer to concentrate on the nontrivial parts of the translation.