Xref: utzoo comp.sys.ibm.pc:10329 comp.binaries.ibm.pc:199 Path: utzoo!utgpu!water!watmath!clyde!rutgers!sunybcs!boulder!cu-den!udenva!isis!aburt From: aburt@isis.UUCP (Andrew Burt) Newsgroups: comp.sys.ibm.pc,comp.binaries.ibm.pc Subject: Re: 123 Fed tax forms Message-ID: <2176@isis.UUCP> Date: 11 Jan 88 04:11:50 GMT References: <6361@drutx.ATT.COM> <19838@clyde.ATT.COM> Reply-To: aburt@isis.UUCP (Andrew Burt) Distribution: comp Organization: Math/CS, University of Denver Lines: 78 In article <19838@clyde.ATT.COM> rcj@moss.UUCP (Curtis Jackson) writes: >In article <6361@drutx.ATT.COM> dsc@drutx.ATT.COM (DavisCS) writes: >>Attached is a uuencoded start on a '123' version of the 1987 Federal >>tax forms. >Although I appreciate someone taking the time and thought to share >software like this, it illustrates something I hope the new moderator >will avoid (if this group ever gets marked as moderated). >I am a software guru but a PC neophyte, so when I read the above I think: >a) What the hell is "a '123' version" of something? >...[and]...should I take the time and effort to download this to my PC >only to find out that it needs, say, some spreadsheet called 123 >that I don't have. In *this* case I don't think this is a major issue -- if you don't know what '123' is then you certainly know you won't be able to do anything with this software. (You may want to find out, but at the moment your lack of knowledge is the answer to the question.) >Could we make a general rule that every posting have a small header >listing some basic requirements, such as: This definitely needs to be done. What to include is hard to call, though. This comment goes for all software posting groups (comp.sources.*). >Amount of memory required on your PC to run the software >Any chip requirements (i.e., "this only runs on an 8087", or > "this will only sound right on an 8Mhz or faster chip") >Any software requirements (only runs with MS-windows, or Turbo Pascal, > or even BASIC -- my Toshiba T1000 didn't come with BASIC) The problems with the first two are that the author may not know; finding out may be impossible -- and if possible, is certainly impractical for something people will get for free. Determining the maximum memory required may be difficult -- e.g., if it allocates variable amounts of memory depending on what it does. Suggested "standard specs" should include: 1. Brief description of what the software does. A paragraph -- even a sentence is better than no clue. 2. Name and net address of author/person_posting/moderator, with note to send all requests for resubmissions to this person (e.g., in case of truncated article, missing parts of multiple posting). [Seeing all those 'please send me part N of M' messages is very annoying when the other M-1 parts could say who to ask!] 4. Hardware run on successfully and/or required, including machine class ('386, '286, etc.) clock speed (20Mhz, etc.) graphics support (EGA, CGA, Herc., text only...) joystick, mouse, ... amount of ram - On machines where it ran; and - estimated maximum, e.g., size of largest binary amount of disk space taken up (within 25% say) 5. Software needed to use (and version number if applicable). In paticular, source code should definitely include the compiler(s) successfuly compiled with. 6. Format sent in -- "uuencode arc", for example. THEN brief note explaining where to obtain uudecode/arc/etc. to avoid all the "where can I get..." requests. Some kind soul(s) should volunteer to be listed as a contact for this (or the moderator if moderated group). Also, a couple line example of how to uudecode/unarchive/etc. would probably be worth the "how do I..." articles it would keep from being posted. To really do this right, a STANDARD "submission form" could be worked up to include this and whatever else is deemed (a) useful and (b) easy for posters to include. Such form could be posted "regularly" to the groups used in. [No flames about regular posting of the Arbitron program, please!] -- Andrew Burt isis!aburt Fight Denver's pollution: Don't Breathe and Drive.