Even if it is the same readme each time... it is specific to that "author" and thus the name ought to reflect the ownership. Just readme.txt means it probably won't get seen much less read. Saying "SAMSreadme.txt" or Travelers_readme.txt" is a hint that it is the same general readme with nothing specific. Inside near the top ought to be a sentence identifying the version number and date when the product was finished. Example: "American Flag, version 1, D Ross, January 1775" is probably different from "American Flag, version 3, D. Ross, April 1777" even if the file name was simply "Flag Texture" and they have the same usage restrictions. If it is SAMS_Dollhouse_readme.txt, that is a hint that I might find information on loading or assembling or using various pieces of that particular package. An example here might be "Main camera is set to the exterior of the house and Posing camera to the interior, both with appropriate focal lengths." That might minimize questions from people wondering why they can't see inside, and it is the sort of information which might apply to your residences, but not to the barbeque or swingset or picture frame. ;) My main pet peeve with readmes though... is when the person makes them a doc file. :grrrrr: I don't have Word on the Mac, and don't want to corrupt my sweet little graphics machine with some ill-executed excrable cross-eyed wonder masquerading as a text processor. I can read .txt files on all of my machines, in almost any program which opens an ASCII file. If the carefully-crafted prose is supposed to be read by everyone, why limit the audience? Carolly