Real Estate Data Sites
SUCKS!!! for the DC area
Integrates CraigsList, mostly rentals
Ebay Listings with gmaps
Uses Microsoft Viewer, have to register for appraisals
gmaps with standard data like lost size and house size

Sending to Mailing Lists With Thunderbird

Here are the instructions for mailings to a large list of people using Mozilla Thunderbird:

1). If sending from an email address other then your own, setup a “new account”.
Select File > New > Account
Select Email Account then Next >
Enter the Name as you would like the Recipient to see (i.e. “Help Desk”)
Enter the email address you would like them to reply to (i.e. Note: this can be an alias or real email address
Select Next >
Enter “” as the incoming server Next >
Incoming username should be YOUR username (i.e. testuser) Next >
Account Name should be the email you are sending FROM Next >
Select Finish

2). Create a list with one email per line using a text editor and save the file in an obvious place with an obvious name (i.e. list.txt).

3). Open the Thunderbird Address Book and import the names into a new Address Book
Select Tools > Import
Select Address Book > Next
Select Text file > Next
Change the “File of Type” to “Tab delimited…” and select the file from step 2.
Using the “Move Up” and/or the “Move Down” buttons adjust the Book file to read “Primary Email” for the corresponding “Record data to import”. Uncheck “first record contains field names” Select OK, the import should take a few seconds.

4). Create a list and import the emails in the new Address Book (from step 3) into the list.
Right click the new Address Book and select “New List”
Enter a unique List Name (ex: list1) select OK
Now select ALL the names in the address book created in step 3 and drag them to this list.

5). Compose a message changing the “From” to the desired name. Address the message to the list using only the BCC. When the recipient reads the message they will see in the “To:” field and the address you designated in the “From:” field.

Hope this makes future mailings easier



TNS:could not resolve the connect identifier specified
Cause: A connection to a database or other service was requested using a connect identifier, and the connect identifier specified could not be resolved into a connect descriptor using one of the naming methods configured. For example, if the type of connect identifier used was a net service name then the net service name could not be found in a naming method repository, or the repository could not be located or reached.

– If you are using local naming (TNSNAMES.ORA file):

– Make sure that “TNSNAMES” is listed as one of the values of the NAMES.DIRECTORY_PATH parameter in the Oracle Net profile (SQLNET.ORA)

– Verify that a TNSNAMES.ORA file exists and is in the proper directory and is accessible.

– Check that the net service name used as the connect identifier exists in the TNSNAMES.ORA file.

– Make sure there are no syntax errors anywhere in the TNSNAMES.ORA file. Look for unmatched parentheses or stray characters. Errors in a TNSNAMES.ORA file may make it unusable.

– If you are using directory naming:

– Verify that “LDAP” is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA).

– Verify that the LDAP directory server is up and that it is accessible.

– Verify that the net service name or database name used as the connect identifier is configured in the directory.

– Verify that the default context being used is correct by specifying a fully qualified net service name or a full LDAP DN as the connect identifier

– If you are using easy connect naming:

– Verify that “EZCONNECT” is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA).

– Make sure the host, port and service name specified are correct.

– Try enclosing the connect identifier in quote marks. See the Oracle Net Services Administrators Guide or the Oracle operating system specific guide for more information on naming.

Force Carbonation

Force Carbonation

Good how to… available at:


To force carbonate beer and other beverages, refer to the chart at the end of this document. It shows the relationship of temperature and pressure on CO2 solubility. First, find the temperature of your beer in the leftmost column. Look across the row to find the volumes of CO2 desired. Finally, set your regulator to the pressure listed in the top row. Use the following as a guideline to determine the CO2 volumes desired:

* British Ale: 1.8 to 2.2 volumes
* German Lager: 2.5 volumes
* American Lagers and Ale: 2.6 to 2.8 volumes
* Wheat Beers: 3.0 volumes

Beer will absorb CO2 until it reaches equilibrium, normally after 3-4 days. The beer should be kept at this pressure throughout its life, so long as the temperature remains constant. You can hasten the force carbonation process by setting the pressure to 30 PSI on the first day, then reducing the pressure to the proper pressure the following day. This can speed the carbonation process by a full day.

Homebrewers often find it impossible to dispense beer at these pressures without causing excessive foaming. One solution is to lower the regulator pressure just prior to dispensing, and then depressurize the keg by pulling the pressure relief valve. This allows you to dispense at more rational pressures. However, this is wasteful of CO2. Additionally, some brewers believe that excessive CO2 purging can strip flavors from the beer. Instead, you may wish to inquire about Northern Brewer’s foam free tubing. This narrower beverage tubing (3/16″ I.D. instead of the standard 1/4″ I.D.) creates more flow resistance — about 2 PSI per foot. If you store beer at 10 PSI, you need to have 10 PSI of flow resistance between the keg and the faucet to get a decent pour. Five feet of foam free tubing should do the trick.

Table vailable at: