Enclosed are the rules, guidelines and related information for the 10th
International Obfuscated C Code Contest.  (This is part 1 of a 2 part
shar file).

Enjoy!

chongo <Landon Curt Noll> /\oo/\
Larry Bassel

=-=

#!/bin/sh
# This is a shell archive (shar 3.32)
# made 03/01/1993 12:01 UTC by chongo@toad.com
# Source directory /tmp
#
# existing files WILL be overwritten
#
# This shar contains:
# length  mode       name
# ------ ---------- ------------------------------------------
#   8585 -r--r--r-- rules
#  25375 -r--r--r-- guidelines
#  33961 -r--r--r-- mkentry.c
#   6257 -r--r--r-- obfuscate.info
#
# ============= rules ==============
echo "x - extracting rules (Text)"
sed 's/^X//' << 'SHAR_EOF' > rules &&
X10th International Obfuscated C Code Contest Rules
X
XCopyright (c) Landon Curt Noll & Larry Bassel, 1993.
XAll Rights Reserved.  Permission for personal, education or non-profit use is
Xgranted provided this this copyright and notice are included in its entirety
Xand remains unaltered.  All other uses must receive prior permission in writing
Xfrom both Landon Curt Noll and Larry Bassel.
X
X    Obfuscate:  tr.v.  -cated, -cating, -cates.  1. a.  To render obscure.
X		b.  To darken.  2. To confuse:  his emotions obfuscated his
X		judgment.  [LLat. obfuscare, to darken : ob(intensive) +
X		Lat. fuscare, to darken < fuscus, dark.] -obfuscation n.
X		obfuscatory adj.
X
X
XGOALS OF THE CONTEST:
X
X    * To write the most Obscure/Obfuscated C program under the rules below.
X    * To show the importance of programming style, in an ironic way.
X    * To stress C compilers with unusual code.
X    * To illustrate some of the subtleties of the C language.
X    * To provide a safe forum for poor C code.  :-)
X
X
XRULES:
X
X    To help us with the volume of entries, we ask that you follow these rules:
X
X    1) Your entry must be a complete program.
X
X    2) Your entry must be <= 3217 bytes in length.  The number of characters
X       excluding whitespace (tab, space, newline), and excluding any ; { or }
X       followed by either whitespace or end of file, must be <= 1536.
X
X    3) Your entry must be submitted in the following format:
X
X---entry---
Xrule:	1993
Xfix:	y or n   (n => this is a new entry, y => this replaces an older entry)
Xtitle:	title of entry  		    (see comments below)
Xentry:	Entry number from 0 to 7 inclusive  (your 1st entry should by 0)
Xdate:	Date/time of submission in UTC	    (see comments below)
Xhost:	Machine(s) and OS(s) under which your entry was tested
X	Use tab indented lines if needed
X---remark---
X    Place remarks about this entry in this section.  It would be helpful if
X    you were to indent your remarks with 4 spaces, though it is not a
X    requirement.  Also, if possible, try to avoid going beyond the 79th
X    column.  Blank lines are permitted.
X---author---
Xname:	your name
Xorg:	School/Company/Organization
Xaddr:	postal address
X	use tab indented lines to continue
X	don't forget to include the country
Xemail:  Email address from a well known site or registered domain.
X        If you give several forms, list them on separate tab indented lines.
Xanon:	y or n   (y => remain anonymous, n => ok to publish this info)
X---info---
XIf your program needs an info file, place a uuencoded copy of it in
Xthis section.  In the case of multiple info files, use multiple info
Xsections.  If your entry does not need a info file, skip this section.
X---build---
XPlace a uuencoded copy of the command(s) used to compile/build your program
Xin this section.  It must uudecode into a file named 'build'.  The resulting
Xfile must be 255 bytes or less.
X---program---
XPlace a uuencoded copy of your program in this section.  It must uudecode
Xinto a file named is 'prog.c'.  The resulting file must follow rule #2.
X---end---
X
X      Regarding the above format:
X
X	* The title must match the expression: [a-zA-Z0-9_=][a-zA-Z0-9_=+-]*
X	  and must be 1 to 12 characters in length.
X
X	  It is suggested, but not required, that the title should
X	  incorporate your username; in the case of multiple authors,
X	  consider using parts of the usernames of the authors.
X
X	* The date in the ---entry--- section should be given with respect
X	  to UTC.  The format of the date should be as returned by asctime()
X	  using the C locale.  (see guidelines for more info)
X
X	* You may correct/revise a previously submitted entry by sending
X	  it to the contest email address.  Be sure to set 'fix' in the
X	  ---entry--- section to 'n'.  The corrected entry must use the same
X	  title and entry number as submittion that is being corrected.  Be
X	  sure that you note the resubmittion in the ---remark--- as well.
X
X	* With the exception of the header, all text outside of the above
X	  format may be ignored by the judges.  If you need tell the judges
X	  something, put it in the ---remark--- section, or send a separate
X	  Email message to the judges.
X
X	* Information from the ---author--- section will be published unless
X	  'y' was given to the respective author's 'anon' line.
X
X	* To credit multiple authors, include an ---author--- section for
X	  each author.  Each should start with ---author--- line, and
X	  should be found between the ---entry--- and ---build--- sections.
X
X	* The entry's remarks should include:
X	    - what this program does
X	    - how to run the program (sample args or input)
X	    - special compile or execution instructions, if any
X	    - special filename requirements (see rule 4 and 5)
X	    - information about any ---data--- files
X	    - why you think the program is obfuscated
X	    - note if this entry is a re-submission of a previous entry.
X	    - any other remarks (humorous or otherwise)
X
X	* Do not rot13 your entry's remarks.  You may suggest that certain
X	  portions of your remarks be rot13ed if your entry wins an award.
X
X        * Info files should be used only to supplement your entry.  They
X	  should not be required to exist.
X
X	  If your entry does not need an info file, skip the ---info---
X	  section.  If your entry needs multiple info files, use multiple
X	  ---info--- sections, one per info file.  You should describe
X	  each info file in the ---remark--- section.
X
X    4) If your entry is selected as a winner, it will be modified as follows:
X
X	   'build' is incorporated into a makefile, and 'build' is removed
X	   'prog.c' is renamed to your entry's title, followed by an optional
X	       digit, followed by '.c'
X	   your entry is compiled into a file with the name of your entry's
X	       title, possibly followed by a digit
X
X       If your entry requires that a build file exist, state so in your
X       entry's remark section.  The makefile will be arranged to execute a
X       build shell script containing the 'build' information.  The name of
X       this build shell script will be your entry's title, possibly followed
X       by a digit, followed by '.sh'.
X
X       If needed, your entry's remarks should indicate how your entry must
X       be changed in order to deal with the new filenames.
X
X    5) The build file, the source and the resulting executable should be
X       treated as read-only files.  If your entry needs to modify these files,
X       it should make and modify a copy of the appropriate file.  If this
X       occurs, state so in your entry's remarks.
X
X    6) Entries that cannot be compiled by an ANSI C compiler will be rejected.
X       Use of common C (K&R + extensions) is permitted, as long as it does not
X       cause compile errors for ANSI C compilers.
X
X    7) The program must be of original work.  All programs must be in the
X       public domain.  All copyrighted programs will be rejected.
X
X    8) Entries must be received prior to 07-May-93 0:00 UTC.  (UTC is
X       essentially equivalent to Greenwich Mean Time)  Email your entries to:
X
X		...!{apple,pyramid,sun,uunet}!hoptoad!obfuscate
X		obfuscate@toad.com
X
X       We request that your message use the subject 'ioccc entry'.
X
X       If possible, we request that you hold off on Emailing your entries
X       until 1-Mar-93 0:00 UTC.  Early entries will be accepted, however.
X       We will attempt to email a confirmation to the the first author for
X       all entries received after 1-Mar-93 0:00 UTC.
X
X    9) Each person may submit up to 8 entries per contest year.  Each entry
X       must be sent in a separate Email letter.
X
X   10) Entries requiring human interaction to be built are not allowed.
X       Compiling an entry produce a file (or files) which may be executed.
X
X   11) Programs that require special privileges (setuid, setgid, super-user,
X       special owner or group) are not allowed.
X
X
XFOR MORE INFORMATION:
X
X    The Judging will be done by Landon Noll and Larry Bassel.  Please send
X    questions or comments (but not entries) about the contest, to:
X
X	...!{apple,pyramid,sun,uunet}!hoptoad!judges
X	judges@toad.com
X
X    The rules and the guidelines may (and often do) change from year to
X    year.  You should be sure you have the current rules and guidelines
X    prior to submitting entries.  To obtain all 3 of them, send Email
X    to the address above and use the subject 'send rules'.
X
X    One may also obtain them via anonymous ftp from:
X
X	host: ftp.uu.net	(137.39.1.9)
X	user: anonymous
X	pass: yourname@yourhost
X	dir:  /pub/ioccc
X
X
Xchongo <Landon Curt Noll> /\cc/\  	hoptoad!chongo
XLarry Bassel			  	{uunet,ucbvax,cbosgd}|sun!lab
SHAR_EOF
chmod 0444 rules ||
echo "restore of rules failed"
set `wc -c rules`;Wc_c=$1
if test "$Wc_c" != "8585"; then
	echo original size 8585, current size $Wc_c
fi
# ============= guidelines ==============
echo "x - extracting guidelines (Text)"
sed 's/^X//' << 'SHAR_EOF' > guidelines &&
X10th International Obfuscated C Code Contest Guidelines, Hints and Comments
X
XCopyright (c) Landon Curt Noll & Larry Bassel, 1993.
XAll Rights Reserved.  Permission for personal, education or non-profit use is
Xgranted provided this this copyright and notice are included in its entirety
Xand remains unaltered.  All other uses must receive prior permission in writing
Xfrom both Landon Curt Noll and Larry Bassel.
X
XABOUT THIS FILE:
X
X    This file is intended to help people who wish to submit entries to
X    the International Obfuscated C Code Contest (IOCCC for short).
X
X    This is not the IOCCC rules, though it does contain comments about
X    them.  The guidelines should be viewed as hints and suggestions.
X    Entries that violate the guidelines but remain within the rules are
X    allowed.  Even so, you are safer if you remain within the guidelines.
X
X    You should read the current IOCCC rules, prior to submitting entries.
X    The rules are typically sent out with these guidelines.
X
X
XWHAT IS NEW IN 1993:
X
X    The entry format is better (for us anyway).  The program mkentry.c
X    has been updated.  See ENTRY FORMAT.
X
X    We will reject entries that cannot be compiled using an ANSI C
X    compiler.  Certain old Obfuscation hacks that cause ANSI C compilers
X    fits are no longer permitted.  Some of the new issues deal with
X    non-integral array types, variable number of arguments, C preprocessor
X    directives and the exit() function.  See OUR LIKES AND DISLIKES.
X
X
XHINTS AND SUGGESTIONS:
X
X    You are encouraged to examine the winners of previous contests.  See
X    FOR MORE INFORMATION for details on how to get previous winners.
X
X    Keep in mind that rules change from year to year, so some winning entries
X    may not be valid entries this year.  What was unique and novel one year
X    might be 'old' the next year.
X
X    An entry is usually examined in a number of ways.  We typically apply
X    a number of tests to an entry:
X
X	* look at the original source
X	* convert ANSI tri-graphs to ASCII
X	* C pre-process the source ignoring '#include' lines
X	* C pre-process the source ignoring '#define' and '#include' lines
X	* run it through a C beautifier
X	* examine the algorithm
X	* lint it
X	* compile it
X	* execute it
X
X    You should consider how your entry looks in each of the above tests.
X    You should ask yourself if your entry remains obscure after it has been
X    'cleaned up' by the C pre-processor and a C beautifier.
X
X    Your entry need not do well under all, or in most tests.  In certain
X    cases, a test is not important.  Entries that compete for the
X    'strangest/most creative source layout' need not do as well as
X    others in terms of their algorithm.  On the other hand, given
X    two such entries, we are more inclined to pick the entry that
X    does something interesting when you run it.
X
X    We try to avoid limiting creativity in our rules.  As such, we leave
X    the contest open for creative rule interpretation.  As in real life
X    programming, interpreting a requirements document or a customer request
X    is important.  For this reason, we often award 'worst abuse of the
X    rules' to an entry that illustrates this point in an ironic way.
X
X    If you do plan to abuse the rules, we suggest that you let us know
X    in the remarks section.  Please note that an invitation to abuse
X    is not an invitation to break.  We are strict when it comes to the
X    3217 byte size limit.  Also, abusing the entry format tends to
X    annoy more than amuse.
X
X    We do realize that there are holes in the rules, and invite entries
X    to attempt to exploit them.  We will award 'worst abuse of the rules'
X    and then plug the hole next year.  Even so, we will attempt to use
X    the smallest plug needed, if not smaller.  :-)
X
X    Check out your program and be sure that it works.  We sometimes make
X    the effort to debug an entry that has a slight problem, particularly
X    in or near the final round.  On the other hand, we have seen some
X    of the best entries fall down because they didn't work.
X
X    We tend to look down on a prime number printer, that claims that
X    16 is a prime number.  If you do have a bug, you are better off
X    documenting it.  Noting "this entry sometimes prints the 4th power
X    of a prime by mistake" would save the above entry.  And sometimes,
X    a strange bug/feature can even help the entry!  Of course, a correctly
X    working entry is best.
X
X
XOUR LIKES AND DISLIKES:
X
X    Doing masses of #defines to obscure the source has become 'old'.  We
X    tend to 'see thru' masses of #defines due to our pre-processor tests
X    that we apply.  Simply abusing #defines or -Dfoo=bar won't go as far
X    as a program that is more well rounded in confusion.
X
X    Many ANSI C compilers dislike the following code, and so do we:
X
X	#define d define
X	#d foo		   <-- don't expect this to turn into #define foo
X
X	int i;
X	j;		   <-- don't use such implicit type declaration
X	int k;
X
X    We suggest that you compile your entry with an ANSI C compiler.  If you
X    must use non-ANSI C, such as K&R C, you must avoid areas that result in
X    compile/link errors for ANSI C compilers.
X
X    Unfortunately, ANSI C requires array indexes to be of integral type.
X    Thus, the following classical obfuscation hacks are no longer allowed:
X
X	int i;
X	char *c;
X	i[c];		   <--- use c[i] instead
X	(i+3)["string"];   <--- use "string"[i+3] instead
X
X    If your entry uses functions that have a variable number of
X    arguments, be careful. Systems implement va_list as a wide variety
X    of ways.  Because of this, a number of operations using va_list are
X    not portable and must not be used:
X
X	* assigning a non-va_list variable to/from a va_list variable
X	* casting a non-va_list variable into/from a va_list variable
X	* passing a va_list variable to a function expecting a non-va_list arg
X	* passing a non-va_list variable to a function expecting a va_list arg
X	* performing arithmetic on va_list variables
X	* using va_list as a structure or union
X
X    In particular, do not treat va_list variables as if they were a char **'s.
X
X    Avoid using <varargs.h>, use <stdarg.h> instead.
X
X    If you use C preprocessor directives (#define, #if, #ifdef, ...),
X    the leading '#' must be the first character on a line.  While some
X    C preprocessors allow whitespace the leading '#', many do not.
X
X    Because the exit() function returns void on some systems, entries
X    must not assume that it returns an int.
X
X    Small programs are best when they are short, obscure and concise.
X    While such programs are not as complex as other winners, they do
X    serve a useful purpose.  They are often the only program that people
X    attempt to completely understand.  For this reason, we look for
X    programs that are compact, and are instructional.
X
X    One line programs should be short one line programs, say around 80
X    bytes long.  Getting close to 160 bytes is a bit too long in our opinion.
X
X    We tend to dislike programs that:
X
X	* are very hardware specific
X	* are very OS or Un*x version specific
X	     (index/strchr differences are ok, but socket/streams specific
X	      code is likely not to be)
X	* dump core or have compiler warnings
X	     (it is ok only if you warn us in the 'remark' header item)
X	* won't compile under both BSD or SYS V Un*x
X	* abusing the build file to get around the size limit
X	* obfuscate by excessive use of ANSI tri-graphs
X	* are longer than they need to be
X	* are similar to previous winners
X	* are identical to previous losers  :-)
X
X    Unless you are cramped for space, or unless you are entering the
X    'best one liner' category, we suggest that you format your program
X    in a more creative way than simply forming excessively long lines.
X
X    The build file should not be used to try and get around the size
X    limit.  It is one thing to make use of a several -D's to help out,
X    but it is quite another to use 200+ bytes of -D's in order to
X    try and squeeze the source under the size limit.  You should feel
X    free to make use of the build file space, but you are better off
X    if you show some amount of restraint.
X
X    We allowed whitespace, and in certain cases ; { or } do not impact
X    your program size (up to a certain point), because we want to get
X    away from source that is simply a compact blob of characters.
X
X    Given two versions of the same program, one that is a compact blob
X    of code, and the other that is formatted more like a typical C
X    program, we tend to favor the second version.  Of course, a third
X    version of the same program that is formatted in an interesting
X    and/or obfuscated way, would definitely win over the first two!
X
X    We suggest that you avoid trying for the 'smallest self-replicating'
X    program.  We are amazed at the many different sizes that claim
X    to be the smallest.  There is nothing wrong with self-replicating
X    programs.  In fact, a number of winners have been self-replicating.
X    You might want to avoid the claim of 'smallest', lest we (or others)
X    know of a smaller one!
X
X    X client entries should be as portable as possible.  Entries that
X    adapt to a wide collection of environments will be favored.  Don't
X    depend on a particular type of display.  For example, don't depend
X    on color or a given size.  Don't require backing store.
X
X    X client entries should avoid using X related libraries and
X    software that is not in wide spread use.  We ask that such X client
X    entries restrict themselves to only the low level Xlib and the
X    Athena widget set (libX11.a, libXaw.a, libXmu.a and libXt.a).
X    Don't use M*tif, Xv*ew, or OpenL*ok toolkits, since not everyone
X    has them.  Avoid depending on a particular window manager.  Not
X    everyone has X11r5, and some people are stuck back in X11r4 (or
X    earlier), so try to target X11r5 without requiring X11r5.  Better
X    yet, try to make your entry run on all version 11 X Window Systems.
X
X    X client entries should not to depend on particular items on
X    .Xdefaults.  If you must do so, be sure to note the required lines
X    in the ---remark--- section.
X
X    We like programs that:
X
X	* are as concise and small as they need to be
X	* do something at least quasi-interesting
X	* pass lint without complaint (not a requirement, but it is nice)
X	* are portable
X	* are unique or novel in their obfuscation style
X	* MAKE USE OF A NUMBER OF DIFFERENT TYPES OF OBFUSCATION
X	* make us laugh and/or throw up  :-)
X
X    Some types of programs can't excel in some areas.  Of course, your
X    program doesn't have to excel in all areas, but doing well in several
X    areas really does help.
X
X    We freely admit that interesting, creative or humorous comments in
X    the ---remark--- section helps your chance of winning.  If you had to
X    read of many twisted entries, you too would enjoy a good laugh or two.
X    We think the readers of the contest winners do as well.
X
X    Be creative!
X
X
XENTRY FORMAT:
X
X    In order to help us process the many entries, we must request your
X    assistance by formatting your entries in a certain way.  This format,
X    in addition, allows us to quickly separate information about the
X    author from the program itself.  (see JUDGING PROCESS)
X
X    We have provided the program, mkentry, as an example of how to
X    format entries.  You should be aware of the following warning that
X    is found in mkentry.c:
X
X	This program attempts to implement the IOCCC rules.  Every
X	attempt has been made to make sure that this program produces
X	an entry that conforms to the contest rules.  In all cases,
X	where this program differs from the contest rules, the
X	contest rules will be used.  Be sure to check with the
X	contest rules before submitting an entry.
X
X    You are not required to use mkentry.  It is convenient, however,
X    as it attempts to uuencode the needed files, and attempt to check
X    the entry against the size rules.
X
X    If you have any suggestions, comments, fixes or complaints about
X    the mkentry.c program, please send Email to the judges.  (see below)
X
X    The following is a sample entry:
X
X---entry---
Xrule:	1993
Xfix:	n
Xtitle:	chonglab
Xentry:	0
Xdate:	Mon Mar  1 08:45:20 1993
Xhost:	Un*x v6, pdp11/45
X	2.9BSD, pdp11/70
X---remark---
X    This is a non-obfuscated obfuscated C program.
X
X    It is likely not to win a prize.  But what do you expect from
X    a short example!
X---author---
Xname:	Landon Curt Noll
Xorg:	IOCCC Judging Group
Xaddr:	Toad Hall
X	PO Box 170608
X	San Francisco, California
X	94117-0608
X	USA
Xemail:	chongo@toad.com
Xanon:	n
X---author---
Xname:	Larry Bassel
Xorg:	IOCCC Judging Group
Xaddr:	Toad Hall
X	PO Box 170608
X	San Francisco, California
X	94117-0608
X	USA
Xemail:	hoptoad!sun!lab
X	lab@sun.com
Xanon:	n
X---info---
Xbegin 444 info.file
XM0V]P>7)I9VAT("AC*2!,86YD;VX@0W5R="!.;VQL+"`Q.3DS+@I!;&P@4FEG
XM:'1S(%)E<V5R=F5D+B`@4&5R;6ES<VEO;B!F;W(@<&5R<V]N86PL(&5D=6-A
XM=&EO;B!O<B!N;VXM<')O9FET('5S92!I<PIG<F%N=&5D('!R;W9I9&5D('1H
XM:7,@=&AI<R!C;W!Y<FEG:'0@86YD(&YO=&EC92!A<F4@:6YC;'5D960@:6X@
XM:71S(&5N=&ER971Y"F%N9"!R96UA:6YS('5N86QT97)E9"X@($%L;"!O=&AE
XM<B!U<V5S(&UU<W0@<F5C96EV92!P<FEO<B!P97)M:7-S:6]N(&EN('=R:71I
XM;F<*9G)O;2!,86YD;VX@0W5R="!.;VQL+@H*5&AA="!T:&%T(&ES+"!I<RX*
XM5&AA="!T:&%T(&ES(&YO="P*("`@(&ES(&YO="!T:&%T('1H870@;F]T(&ES
XM+@I4:&%T(&ES+"!T:&%T('1H870@:7,@;F]T+"!I<R$*"@D)+2T@8VAO;F=O
XM(#$Y-S0*"DQA<W0@>65A<BP@;VYE('!E<G-O;B!T;VQD('5S('1H870@=&AE
XM>2!A8W1U86QL>2!D96-O9&5D('1H:7,@9FEL92X*22!W;VYD97(@:&]W(&UA
X9;GD@=VEL;"!D;R!I="!T:&ES('EE87(_"@``
X`
Xend
X---build---
Xbegin 444 build
X28V,@<')O9RYC("UO('!R;V<*
X`
Xend
X---program---
Xbegin 444 prog.c
XM;6%I;B@I"GL*(VEF(&1E9FEN960H05]214=)4U1%4D5$7U9/5$527TE.7U-5
XM3DY95D%,15]#04Q)1D]23DE!7U5302D*("`@('!R:6YT9B@B5F]T92!,86YD
XM;VX@3F]L;"!F;W(@4W5N;GEV86QE($-I='D@0V]U;F-I;"!S96%T(",Q+EQN
X:(BD["B-E;F1I9@H@("`@97AI="@P*3L*?0H`
X`
Xend
X---end---
X
X    Typically the build file should assume that the source is prog.c
X    and will compile into prog.  If an entry wins, we will rename
X    its source and binary to avoid filename collision.  By tradition,
X    we use the name of the entry's title, followed by an optional
X    digit in case of name conflicts.
X
X    If the above entry somehow won the 'least likely to win' award,
X    we would use chonglab.c and chonglab.
X
X    If your entry depends on, or requires that your build, source
X    and/or binary files be a particular name, please say so in the
X    ---remark--- section.  If this case applies, it would be be helpful
X    if you did one of the following:
X
X	* Tell us how to change the filename(s) in your entry.
X
X	* Have the build file make copies of the files.  For example:
X
X		cc prog.c -o special_name		need special binary
X
X	    or  rm -f special_src.c			need special source
X		cp prog.c special_src.c
X		cc special_src.c -o special_name
X
X	    or  rm -f special_build			need special build
X		tail +4 build > special_build
X		sh < special_build
X
X	* Assume that we will use the entry title.  Send us a version of
X	  your build/program files that uses the name convention.  You
X	  should uuencode these files in ---data--- sections.
X
X    If your entry needs to modify its source, info or binary files,
X    please say so in the ---remark--- section.  You should try to avoid
X    touching your original build, source and binary files.  You should
X    arrange to make copies of the files you intend to modify.  This
X    will allow people to re-generate your entry from scratch.
X
X    Remember that your entry may be built without a build file.  We
X    typically incorporate the build lines into a Makefile.  If the
X    build file must exist, say so in the ---remark--- section.
X
X    If your entry needs special info files, you should uuencode them
X    into ---info--- sections.  In the case of multiple info files,
X    use multiple ---info--- sections.  If no info files are needed,
X    then skip the ---info--- section.
X
X    Info files are intended to be input, or detailed information that
X    does not fit well into the ---remark--- section.  For example, an
X    entry that implements a compiler might want to provide some sample
X    programs for the user to compile.  An entry might want to include a
X    lengthy design document, that might not be appropriate for a
X    'hints' file.
X
X    Info files should be used only to supplement your entry.  For
X    example, info files may provide sample input or detailed
X    information about your entry.  Because they are supplemental,
X    the entry should not require them exist.
X
X    In some cases, your info files might be renamed to avoid name
X    conflicts.  If info files should not be renamed for some reason,
X    say so in the ---remark--- section.
X
X    Info files must uudecode into the current directory.  If they
X    absolutely must be renamed, or moved into a sub-directory, say
X    so in the ---remark--- section.
X
X    When submitting multiple entries, be sure that each entry has
X    a unique entry number from 0 to 7.  Your first entry should
X    have entry number 0.
X
X    With the exception of the header, all text outside of the entry
X    format may be ignored.  That is, don't place text outside of the
X    entry and expect the judges to see it.  (Our decoding tools aren't
X    AI progs!) If you need tell the the something, put it in the
X    ---remark--- section, or send a Email to the judges at:
X
X	...!{apple,pyramid,sun,uunet}!hoptoad!judges	(not the address for
X	judges@toad.com					 submitting entries)
X
X    The date should be given with respect to UTC.  (Some systems refer
X    to this as GMT or GMT0)  The format of the date should be that as
X    returned by asctime() in the C locale.  An example of such a string is:
X
X	Thr Apr 01 00:47:00 1993
X
X    This format is similar to the output of the date(1) command.  The
X    string does not include the timezone name before the year.  On many
X    systems, one of the following command will produce a similar string:
X
X	date -u "+%a %h %d %T 19%y"
X	date -u | sed -e 's/... \(19[0-9][0-9]\)$/\1/'
X	sh -c 'TZ=UTC date | sed -e "s/... \(19[0-9][0-9]\)$/\1/"'
X	sh -c 'TZ=GMT date | sed -e "s/... \(19[0-9][0-9]\)$/\1/"'
X	sh -c 'TZ=GMT0 date | sed -e "s/... \(19[0-9][0-9]\)$/\1/"'
X
X    You are allowed to update/fix/revise your entry.  To do so, set
X    the 'fix' line in the ---entry--- section to 'y' instead of 'n'.
X    Be sure that the resubmittion uses the same title and entry number
X    as well, as these are used to determine which entry is to be
X    replaced.
X
X
XJUDGING PROCESS:
X
X    Entries are judged by Larry Bassel and Landon Curt Noll.
X
X    Entries are unpacked into individual directories.  The Email message
X    is unpacked into individual files, each containing:
X
X	---entry--- section
X	all ---author--- sections
X	all ---info--- sections
X	---build--- section
X	---program--- section
X	any other text, including the Email message headers
X
X    Prior to judging, the 'any other text' file is scanned to be sure
X    it does not contain useful information (or in case the entry was
X    malformed and did not unpack correctly).  Information from the
X    ---author--- sections are not read until the judging process is
X    complete, and then only from entries that have won an award.
X
X    The above process helps keep us biased for/against any one particular
X    individual.  We are usually kept in the dark as much as you are
X    until the final awards are given.  We like the surprise of finding
X    out in the end, who won and where they were from.
X
X    We attempt to keep all entries anonymous, unless they win an award.
X    Because the main 'prize' of winning is being announced, we make all
X    attempts to send non-winners into oblivion.  We remove all non-winning
X    files, and shred all related paper.  By tradition, we do not even
X    reveal the number of entries that we received.  (for the curious,
X    we do indicate the volume of paper consumed when presenting the IOCCC
X    winners at talks)
X
X    After the Usenix announcement, we attempt to send Email to the
X    authors of the winning entries.  One reason we do this is to give
X    the authors a chance to comment on the way we have presented their
X    entry.  They are given the chance to correct mistakes, typos.  We
X    often accept their suggestions/comments about our remarks as well.
X    This is done prior to posting the winners to the wide world.
X
X    Judging consists of a number of elimination rounds.  During a round,
X    the collection of entries are divided into two roughly equal piles;
X    the pile that advances on to the next round, and the pile that does
X    not.  We also re-examine the entries that were eliminated in the
X    previous round.  Thus, an entry gets at least two readings.
X
X    A reading consists of a number of actions:
X
X	* reading the ---entry--- section
X	* reading the uudecoded ---build--- section
X	* reading the uudecoded ---program--- section
X	* reading the uudecoded ---info--- section(s), if any
X	* passing the source thru the C pre-processor
X	    shipping over any #include files
X	* performing a number of C beautify/cleanup edits on the source
X	* passing the beautified source thru the C pre-processor
X	    shipping over any #include files
X
X    In later rounds, other actions are performed:
X
X	* linting the source
X	* compiling/building the source
X	* running the program
X	* performing misc tests on the source and binary
X
X    Until we reduce the stack of entries down to about 25 entries, entries
X    are judged on an individual basis.  An entry is set aside because it
X    does not, in our opinion, meet the standard established by the round.
X    When the number of entries thins to about 25 entries, we begin to form
X    award categories.  Entries begin to compete with each other for awards.
X    An entry often will compete in several categories.
X
X    The actual award category list will vary depending on the types of entries
X    we receive.  A typical category list might be:
X
X	* best small one line program
X	* best small program
X	* strangest/most creative source layout
X	* most useful obfuscated program
X	* best game that is obfuscated
X	* most creatively obfuscated program
X	* most deceptive C code
X	* best X client (see OUR LIKES AND DISLIKES)
X	* best abuse of ANSI C
X	* worst abuse of the rules
X	* <anything else so strange that it deserves an award>
X
X    We do not limit ourselves to this list.  For example, a few entries are so
X    good/bad that they are declared winners at the start of the final round.
X    We will invent awards categories for them, if necessary.
X
X    In the final round process, we perform the difficult tasks of
X    reducing the remaining entries (typically about 25) down to 8 or 10
X    winners.  Often we are confident that the entries that make it into
X    the final round are definitely better than the ones that do not
X    make it.  The selection of the winners out of the final round, is
X    less clear cut.
X
X    Sometimes a final round entry good enough to win, but is beat out
X    by a similar, but slightly better entry.  For this reason, it is
X    sometimes worthwhile to re-enter an improved version of an entry
X    that failed to win in a previous year.  This assumes, of course,
X    that the entry is worth improving in the first place!
X
X    More often that not, we select a small entry (usually one line), a
X    strange/creative layout entry, and an entry that abuses the contest
X    rules in some way.
X
X    In the end, we traditionally pick one entry as 'best'.  Sometimes such
X    an entry simply far exceeds any of the other entry.  More often, the
X    'best' is picked because it does well in a number of categories.
X
X
XANNOUNCEMENT OF WINNERS:
X
X    The first announcement, occurs at a Summer Usenix conference.  By tradition,
X    this is done during the latter part of the UUNET/IOCCC BOF, just prior to
X    the Berkeley BSD, and BSDI BOF.
X
X    Winning entries will be posted in late June to the following groups:
X
X	    comp.lang.c		  comp.unix.wizards	alt.sources
X
X    In addition, pointers to these postings are posted to the following
X
X	    comp.sources.d	  alt.sources.d		misc.misc
X	    comp.sources.misc	  comp.windows.x
X
X    Winning entries will be deposited into the uunet archives.  See
X    below for details.
X
X    Often, winning entries are published in selected magazines.  Winners
X    have appeared in books ("The New Hackers Dictionary") and on T-Shirts.
X
X    Last, but not least, winners receive international fame and flames!  :-)
X
X
XFOR MORE INFORMATION:
X
X    You may contact the judges by sending Email to the following address:
X
X	...!{apple,pyramid,sun,uunet}!hoptoad!judges	(not the address for
X	judges@toad.com					 submitting entries)
X
X    Questions and comments about the contest are welcome.
X
X    One may obtain a copy of the current rules, guidelines or mkentry
X    program.  To obtain all 3 of them, send Email to the address above
X    and use the subject 'send rules'.
X
X    One may also obtain the above items, we well as winners of previous
X    contests, via anonymous ftp from:
X
X	host: ftp.uu.net	(137.39.1.9)
X	user: anonymous
X	pass: yourname@yourhost
X	dir:  pub/ioccc
X
X    Often, contest rules, guidelines and winners are available from
X    archive sites.  Check comp.sources.unix archives, for example.
X    You may also request previous winners by Email, using the judges
X    Email address, though we ask that you do this as a last resort.
X
X
Xchongo <Landon Curt Noll> /\cc/\  	hoptoad!chongo
XLarry Bassel			  	{uunet,ucbvax,cbosgd}|sun!lab
SHAR_EOF
chmod 0444 guidelines ||
echo "restore of guidelines failed"
set `wc -c guidelines`;Wc_c=$1
if test "$Wc_c" != "25375"; then
	echo original size 25375, current size $Wc_c
fi
echo "End of part 1, continue with part 2"
exit 0


The following is an introduction as to who is Muhammad SAW
as will be covered with this treatise.

MUHAMMAD peace and blessings of Allah be upon him (SAW)
is the last prophet of Islam.  He is the Prophet who is revealed
the last Holy Scripture, Qur'an, by Allah SWA (all praise be to Him)
through the Arch Angel Gabriel.  He is the seal of all prophets
till the day of judgement as stated in the Qur'an by Allah
SWA (all praise be to Him).  Muhammad SAW lived between
571-632 AC.  All other prophethoods claimed after Muhammad SAW,
is a treason against Islam, against Qur'an, against the message
of Allah SWA.  Muhammad SAW is from the seed of Ishmael, another
messenger of Allah and son of Abraham also a messenger of Allah.
He is the Messenger that previous holy scriptures foretold his
coming.  The above mentioned verse from the Qur'an is from
Chapter 33, Verse 40 whose rough translation is as follows:

	Muhammad is not the father of any of your men,
	but (he is) the messenger of Allah, and the seal
	of the prophets, and Allah has full knowledge of
	all things.

---------------------
Commentary on the above verse:  When a document is sealed,
it is complete, and there can be no further addition.  The
Holy Prophet Muhammad SAW closed the long line of Messengers.
Allah's teaching is and will always be continuous, but there
has been and will be NO Prophet after Muhammad SAW.  The later
ages will want thinkers, and revivers, not Prophets.  This is not
an arbitrary matter.  It is a decree full of knowledge and wisdom,
"for Allah has full knowledge of all things."

----------------------
DROPLET VOL 1, No 11, Part 2

A   D R O P L E T
From The Vast Ocean Of The Miraculous Qur'an

Translations from the Arabic and Turkish Writings of
Bediuzzaman Said Nursi, The Risale-i Noor

VOL 1, No 11, Part 2
------------------------------------------------------------------
   		 NINETEENTH LETTER

		 MU'JIZAT-I AHMEDIYE RISALESI
(A TREATISE ON THE MIRACLES OF MUHAMMED SAW)

(continued from Droplet Vol 1, No 11, Part 1)

   SECOND  SIGN:   The  Noble  Messenger  (SAW)
declared His prophethood, and presented to humanity a
decree as the Glorious Qur'an and manifest miracles
which number, according to the scholars, one thousand.
The occurrence of those miracles in their entirety is as
certain as the fact that He declared himself prophet.  In
fact, as a shown by the words of the  most obstinate
unbelievers quoted in various places of the Wise
Our'an, even they could not deny the occurrence of His
miracles, but only called them -hasha wa kella!-(Allah forbids)
sorcery, in order to satisfy themselves, or to deceive their
followers.  The miracles of Muhammad (SAW) have the
certainty of confirmation by consensus of Ulema (scholars
of Islam) to the hundreth degree.
   The Miracle is the conformation by the CREATOR of
the universe of His declaration of Prophethood; it has the
effect of the words,'You have indeed spoken the truth !'
   Suppose that you said in the assembly of a ruler,
while being observed by Him, 'The true ruler has
appointed me to such and such position.  'At a time when
you were asked to prove your claim, the word 'Yes'
uttered by the ruler would sufficiently support you.  Or, if
the ruler changed his usual practice and attitude at your
request, this would confirm your claim even more soundly
and more definitely than would the word 'Yes.'
   In the same way, ALLAH's Most Noble Messenger
claimed: 'I am the envoy of the CREATOR of this
universe.  My proof is that He will change His unbroken
order at my request and my prayer.  Now look at my
fingers:  He makes them run like a fountain with five
spigots.  Look at the moon: by a gesture of my finger, He
splits it in two.  Look at that tree: to affirm me, and to bear
witness to me, it moves and comes near to me.  Look at
this food: although it is barely enough for two or three
men, it satisfies two or three hundred.  'Further he shows
hundreds of similar miracles.  However, the evidences  of
the veracity of this high being and the proofs of his
prophethood are not restricted to his miracles.  All his
deeds and acts, his words and behavior, his moral
conduct and manners, his character and appearance
prove to the attentive his truthfulness and seriousness.
Indeed, many people  such  as  Abdullah  b. Salam,  the
famous scholar of the Children of Israel, came to belief
merely by seeing him, and said, 'No lie can hide in this
face, nor can any fraud be found in it!'
   Although many of the  researchers have concluded
that the proofs of the prophethood of Muhammad and his
miracles number about one thousand, there are
thousands, perhaps hundreds of thousands of proofs  of
his prophethood.  And hundreds of thousands of
truth-seeking men (muhakkikiin) with varying opinions
have affirmed his prophethood in an equal number of
ways.
   The Wise Our'an alone demonstrates thousands of
the proofs of his prophethood, in addition to its own forty
aspects of miraculousness.  Since prophethood is as a
phenomenon of humanity, and hundreds of thousands of
individuals who claimed prophethood and performed
miracles have lived and passed away; then, the
prophethood of Muhammad (SAW) is of a certanity
superior to that of the prophethood of all the others.  For
whatever evidences, qualities  and attributes  became the
means of the prophethood and messengership of all the
messengers such as Jesus (AS) and Moses (AS), they
are all owned in a more perfect and comprehensive
fashion by Muhammad (SAW).  And since the causes and
means of prophetic authority exist more perfectly in the
person of Muhammad (SAW), this authority is to be found
in him with more certanity than all the other prophets.


:My wife's ob-gyn has an ultrasound machine in her office.  When
:the doctor couldn't hear a fetal heartbeat (13 weeks) she used
:the ultrasound to see if everything was ok.  (it was)
:
:On her next visit, my wife asked another doctor in the office if
:they read the ultrasounds themselves or if they had a radiologist
:read the pictures.  The doctor very vehemently insisted that they
:were qualified to read the ultrasound and radiologists were NOT!
:
:[stuff deleted]

This is one of those sticky areas of medicine where battles frequently
rage.  With respect to your OB, I suspect that she has been certified in
ultrasound diagnostics, and is thus allowed to use it and bill for its
use.  Many cardiologists also use ultrasound (echocardiography), and are
in fact considered by many to be the 'experts'.  I am not sure where OBs
stand in this regard, but I suspect that they are at least as good as the
radioligists (flame-retardant suit ready).


I am looking for a Windows Utility that would give me a listing of files
in a directory, but also display a description of the file.  This utility
would allow me to enter and edit file descriptions of, hopefully, any
length (maybe a small window with a scroll bar?).  I would then be able
to browse my directories and be able to see what is in a file without
having to open or execute it.  Any such beast out there?  If not, anyone
want to write one?


:    Where can I get xman source?  I would like to get the binaries for
: xman for an HP 9000/700, but I would settle for source.
:
: --
Try xport.lcs.mit.edu, in direcotry /contrib.
--


For Sale:

Turbo Pascal 5.5 - all original manuals and disks:  $30 obo + shipping

Borland Paradox 3.5 with tall boxed manual set & Kallista desktop - all
original disks.  $50 obo + shipping

Borland Paradox 4.0 - opened but never used.  All manuals & disks.
$125 obo + shipping

Borland Quattro Pro 4.0 (DOS) all manuals & disks.  $40 obo + shipping

E-mail or phone if interested.

John Hansen
(513) 257-6084


PDR and CPS are good places to starts.

do a medline search... lots of interesting debates going on (remember
when Prozac was impicated in suicidal behaviour?)


[deletions]
[deletions]

 As you have presented it, it is indeed an argument from incredulity.
However, from what I have seen, it is not often presented in this manner.
It is usually presented more in the form, "And *besides*, I cannot see...
...nor have I ever been offered a convincing explanation."
 Moreover, it is not unreasonable to ask for an explanation for such
phenomena. That theism does not provide a convincing explanation is not
an argument in theism's favor. Especially when different theisms offer
different explanations, and even different adherents of what is purportedly
the same theism give different explanations...

 Not im my experience. In my experience, the most common reason is the
lack of evidence in theism's favor. You mileage may vary. :->

 Oh, heck, I'll be snide this once. :-> It's also fairly easy to attack
arguments that are not made. (I.e. 'strawmen'.)

 Sage advice indeed.

 Sincerely,

 Raymond Ingles                       ingles@engin.umich.edu


The European Space Agency has involvement with remote earth
observation, and I presume this includes surveillance (optical etc.).
So it's not just the US/USSR(ex) who are in the game.

But what *is* the game? What can be done with space observation?
The military functions of missile spotting, troop spotting etc. are well
documented, but what about anything else?

The biggest eg I can think of is to get a  metal sensing sat over a
paying country and scan their territory for  precious metals.

More importantly, if radar can spot water vapour (clouds), presumably
a radar based sat will be capable of spotting rivers,open water and
*underground water* from space. This would be a positive life saver
for African or other drought affected countries. Implementing a
clean water and irrigation program would be of imense benifit to such
countries and should cut down mortalities considerably.

So how about it? Is there a charity or government agency that would
pay for a third world country to have their minerals and water deposits
mapped?

Or is this still sci-fi?

Mail replies would be great.

Thought for the day: Thermal energy needs water to make steam so sstick
it in the ocean!


San Mateo Duplex houses for sale:

	West side location, Alameda and HWY 92. large lot 55X140. Nice
	quiet location, No front neighbor, space for pool or jacuzzi.
	spacious rooms, cozy living room with fireplace. Only minutes
	from highways 280 and 92 and 101. Excellent schools, shopping
	and transportation nearby.

	Unit one:  " Remodeled "  2100 SQ foot
		3 bedrooms	2 baths		Large master suite
		Den/study	Eat in Kitchen	Very large Backyard
		Fenced backyard	Hardwood floor	Wall to wall carpet
		Marbel/tile/vinyl		2 car garage
		car port	Washer and dryer hook up
		Living room dinning combo	totally remodeled

	Unit two:   " BRAND NEW CONSTRUCTION " 645 SQ Foot
		1 bedroom	1 bath		Fire place
		Dinning room	Private yard 	Private entry
		detached unit	Washer & dryer	Living room
		Barbeque patio	All separet Utilities from the city

	Price $468,500   ( By Owner )

	Call Medi Amadi at   510-601-1525   eves
			     510-823-3366   days


If you can get it, you might want to try a Canadian over-the-counter product
called Secaris, which is a water-soluble gel.  Compared to Vaseline or other
greasy ointments, Secaris seems more compatible with the moisture that's
already there.


RIX's files with the extension  .sci and .scf are just a RAW file with
a 256 color palette.
The first 10 bytes is a kind of header, with the name RIX among 7bytes unknown stuff. The you have 768 bytes of palette info (3*256 for the colors RGB)
and then you have the picture in raw format.
If you dont know how to make a viewer of of this description you can get VPIC
it is able to read the files!


For an upcoming project I want to use 4 Megs of DRAM configured as two 2
Meg banks of 16 bit data.  I was wondering if anyone out there knows of a
DRAM controller which will handle refreshing the data.  It's ok if the
controller doesn't handle bank switching - that part is easy.

The only controllers I know of are the ones out of the National
Semiconductor DRAM Management Handbook (1988 edition) eg. DP8429.  I would
like to know if another manufacturer produces one which may be easier to
implement in my circuit.

BTW, if anyone is wanting to hook up DRAM to a microcontroller, Dallas
Semiconductor makes a neat chip: the DS1262 Serial DRAM Nonvolatizer
Chip.  It uses the SPI (I2C) bus and refreshes/controls up to 16Mx1 of DRAM
memory.  It can use an external battery to refresh the DRAM when the
power is off.  Price is $11.75 from Dallas (quan 1).  I wish I could use
this chip but its maximum SPI clock rate is 1 MHz (too slow for me...).

Thanks in advance,

Wayne Schellekens
<schellew@wu2.wl.aecl.ca>


Here's a list of 800 numbers I have compiled from other sources...
anybody got anything to add?

It's formatted for Alpha, and looks fine for me, so don't complain if it
doesn't look good to you.

  * Adobe					1-415-961-0911
	FAX info				1-800-235-0078
  * Aldus					1-206-622-5500
  * Alladin					1-408-685-9175
  * Altsys					1-214-680-2060
  * APDA 					1-800-282-2732
    (Apple Prog Dev Assoc)
  * Apple Computer			1-408-996-1010
  * Apple Customer 			1-800-776-2333
    Non-Tech assistance
  * APS						1-800-233-7550
    (Alliance Peripheral Sys)
  * ASD Softwae				1-714-624-2594
	FAX						1-714-624-9574
  * Berkeley Systems		1-415-540-5535
  * Cayman Systems			1-800-473-4776
  * CE Software				1-515-224-1953
  * Claris					1-408-727-8227
							1-408-727-9054
  	Claris Software			1-800-3CL-ARIS
  * Compatible Systems		1-800-356-0283
  * Computer Associates C.A	1-408-648-4000
  * Connectix				1-800-950-5880
  * DataViz					1-203-268-0300
  * Dayna					1-801-972-2000
  * DeltaPoint				1-800-367-4334
  * Deneba					1-305-594-6965
  * Dr.Mac:       	 		1-800-825-6227
  * Fifth Generation		1-800-873-4384
  * GreatWave				1-408-438-1990
  * ICOM Simulations		1-708-520-4440
  * MacAvenue:    			1-800-926-6221
  * MacConnection: 			1-800-334-4444
  * MacLand:    	   		1-800-888-8779
  * MacroMind				1-415-442-0200
  * Mac's Place:   			1-800-367-4222
  * MacWarehouse:	  		1-800-255-6227
  * Microcom				1-919-490-1277
  * Microsoft				1-800-426-9400
      Educational:			1-800-227-4679
      General:				1-206-882-8088
      Sales and Services:  	1-800-426-9400
		Then punch:
		    1 Technical Assistance
		    2 University
  * Shiva					1-617-864-8100
  * Silicon Beach			1-619-695-6956
  * Symantec				1-800-441-7234
  * The Mac Zone:	  		1-800-248-0800
  * Chip Merchant			1-800-426-6375
  * ClearPoint Computers	1-800-253-2778
  * ClubMac					1-800-CLU-BMAC
  * Delta Research Labs		1-800-999-1593
  * Diamond					1-800-541-7126
  * Dynamic Electronics		1-800-845-8228
  * ETC						1-800-882-2863
  * Global Village Telecom.	1-800-736-4821
    Mac ADB modems
  * Lifetime Memory			1-800-233-6233
  * LLB						1-800-848-8967
  * Macproducts USA			1-800 MAC DISK
  * MacProducts:   			1-800-MAC-USA1
  * Megabyte Memory			1-800-748-5766
    Products
  * Memory International	1-800-266-0488
  * Memory Plus				1-800-388-PLUS
  * Micro Electronic Tech	1-800-766-7466
  * Newer Technology		1-800-678-3726
  * Peripheral Outlet		1-800-332-6581
  * PSI						1-800-622-1722
  * Quadmation				1-800-733-7887
  * Shecom Computers		1-800-366-4433
  * SII Micros				1-800-424-1126
  * South Coast Electronics	1-800-289-8801
  * Stratum Technologies	1-800-533-1744
  * Technology Works		1-800-688-7466
  * Texas Macstuf			1-800-MAC-STUF
  * Third Wave Computing	1-800-284-0486
  * Third Wave				1-800-284-0846
  * Turbo Technologies		1-800-542-7466


And some BDC in a Volvo comes careening off the freeway and lands on top of
you in said pool. You can't win.

jim


Wrong information. They just announced that Suhonen has made a deal with
Jokerit.


When the Quran uses the word *din* it means way of individual thinking, behaving,
communal order and protocols based on a set of beliefs. This is often
interpreted as the much weaker term religion.

The atheists are not mentioned in the Quran along with Jews,
Mushriqin, Christians, etc. because the  latter are all din. To have a
din you need a set of beliefs, assumptions, etc, to forma a social
code. For example the Marxist have those, such as History, Conflict,
etc. That they do not put idols (sometimes they did) to represent
those assuptions  does not mean they are any different from the other
Mushriq, or roughly polytheists.

There cannot be social Atheism, because when there is a community,
that community needs common ideas or standard beliefs to coordinate
the society. When they inscribe assumptions, say Nation, or "Progress is
the natural consequence of Human activity" or "parlamentarian
democracy is doubtlessly the best way of government", however
they individually insist they do not have gods, from the Quranic point
of view they do. Therefore by definition, atheism does not exist.
"We are a atheist society" in fact means "we reject the din other than
ours".

Atheism can only exist when people reject all the idols/gods/dogmas/
suppositions/.. of the society that they part, and in that case that
is a personal deviation of belief, and Quran tells about such
deviations and disbelief. But as I mentioned, from a Quranic point of
looking at things, there is no Atheism in the macro level.

I think it took more than one minute.


The newest JDR Microdevices catalog has at least one variant of the HC11.


You forget that Apollo was a Government program and had to start
relatively from scratch. Some people at NASA think that this could work.
One of them replied to me personally after I posted this original message
several days ago. I have heard Jerry Pournelle suggest this idea before.


Has anyone connected a high-res, fixed frequency monitor to their PC?
I have a mitubishi monitor that does 1024x768 at 60hz, but won't do
any other resolutions.  All the video cards designed for this sort of
thing are very expensive (>$400).  Has anyone done it with an SVGA
card (I know it can be done, it's just a question of getting the card
at the right resolution and frequency)?  I'd like to use a mono
(hercules) monitor as my dos/command line monitor, and switch to the
mitsu for Windows or X-windows (under Linux or 3BSD).

Any suggestions would be greatly appreciated.  E-mail, please.

Thanks,


A list of options that would be useful. They can be existing
options on a car, or things you'd like to have...

1) Tripmeter, great little gadget. Lets you keep rough track of
   mileage, makes a good second guesser for your gas gauge...

2) Full size spare

3) Built in mountings and power systems for radar detectors.

4) a fitting that allows you to generate household current with
the engine running, and plug ins in the trunk, engine compartment
and cabin.

Feel free to add on...

Regards, Charles
x


You know what my answer will be: Hrivnak! The choice is obvious.


...deleted lines...

   As I live in Sweden I remember the day perfectly well. We changed
side 1967-09-03 (or 03-SEP-1967). I don't remeber the exactly time but
it was in the night. (in the 'big' cities like Stockholm & Gothenburg
all trafic was forbidden, exept busses and taxis, during the whole
weekend.) The day was a Sunday and everything was prepared in before.

Before the day we was told to follow the yellow lines on the road and
after it was the white one that matters. The signs with arrows on was
prepared with a 'left mode' label that was torn off that night to
reveal the new right mode arrow.

The year after Iceland also changed.

About cars: Before the H-day (H as in "Hoegertrafik". "hoeger" is
Swedish and stands for 'right') practically all cars already had their
steering wheels on the left side. Even the imported cars from UK had
the wheel on 'the right side'. At last we have cars with the wheels on
the right side. :-)

More contries that uses the left side is:

Japan
Tanzania (I think)
New Zeeland
How about South Africa?

BTW. Some sais that the left side is the right side because Ivanhoe
and other knights meet at the left when they fight in tournaments. :-)

...deleted lines...


Any suggestions as to what a better solution might be?  I realize the
off-hand nature of the numbers I used.  And I can't answer as to what
an acceptable loss rate is.  However,  as I said in another post,  I
despise the idea of supporting criminals for life.  It's the economics
of the situation that concern me most.  The money spent feeding, clothing,
housing and taking care of people who have demonstrated that they are
unfit to live in society could go to a number of places,  all of which
I, and probably others,  would consider far more worthwhile and which
would enrish the lives of all Americans.  Give people jobs,  give the
homeless shelter.  Any number of things.

Clyde


It is funny how this one little quote from Genesis is treated
by certain anti-Christians as if Christians have been given a
firm command to destroy the earth. You could prove almost
anything by taking little quotes out of context from the Bible
- it's a big book, you know. I doubt you could find a single
case of a anti-ecological action taking place specifically
because teh perpetrator was motivated by a Christian belief.

As for the Nazis, they were motivated by German Nationalism,
not by Christianity. In fact they despised Christianity as a
weak pacifist religion, and were much more keen on pagan
glorification of strength and warfare. They killed the Jews
because they were not Germans, not because they were
"Christ-killers" - they were just as keen on killing the other
non-German ethnic minority, the Romanies or Gypsies.


he ones I have seen are all fluorescent tubes. Maybe you could find a
small tube to go in one of those hand-held fluoro lanterns?

Blue lights. Ultra-violet (by definition?) goes from the blue end of the
spectrum that people see to the radio spectrum (X-rays, cosmic rays etc).

possibly you could get light at the fringe of visibility (which people
with false eye-lenses can see easily, since it's your lenses that soak up
most of the UV), however since most people use UV to get other things
to `glow', and the near-blue is less energetic, it would probably not
work as well, if it worked at all. (lecture on basic atomic physics
fits in here, about electron transitions (quantum leaps) and stuff.


[stuff deleted]
                                       ^^

  Just a note, even though the 805 can address 2 megs of dram, the
Stealth 24 VLB can only handle 1 meg, unless Diamond has a newer
design (or some special deal with Zeos).


I expect what is going on here is that your colormap is full and, when the new application starts up, it cannot add the colors that it needs to the colormap.
It therefore has to pick and choose from the existing colors.  This makes it look
ugly until it's window gets priority.  Then Macx changes the colormap so that
the selected app is getting the exact colors it wanted, but now other applications
are having to make do with it's colormap.

This is a problem with all color X servers (or at least all color Xservers I have
seen) when the demands of the applications exceed the size of the colormap.
My solution is usually to (1) avoid colormap-greedy apps and (2) display
applications where color is just icing on the cake in monochrome mode rather
than in color (if this is an option for the application).

 - Doug Shaker
	voice:	415/572-0200
	fax:	415/572-1300
	email:	dshaker@qualix.com
	mail:	Qualix Group
		1900 S. Norfolk St., #224
		San Mateo, CA 94403


1. IBM PS/2 286; 30 meg hd; 1.44 disk drive 3.5"; extended keyboard; mouse,
   mouse-pad; DOS, DOSSHELL, EXCEL, WINDO S, WORD, AMIPRO, GRE StudyWare.
   $500 / b.o.

2.  Zenith Date Systems supersport laptop computer
    w/ 120V AC recharger; model 150-308 60 hz.
    DOS 4.0
    2 disc drives for 3.5" floppy
    carrying case, manuals.
    $350 / b.o.

3.  2 leather desk chairs  (1) black $200. (2) brown $150. or both for
$300.

4.  Olivetti manual typewriter, Tropical model.
    Incl. characters for typing in Italian language.
    $100.

Please reply via email or call me at my home number:  (617) 277-9234.

Thanks,
Jason


  I won't argue too much about anything.  I am probably one of those that
think that we can't have enough safety on the roads.  I would gladly
sacrifice distractions (as you call it), than someone having trouble seeing
danger earlier.  One saved life justifies more than my lifetime of "distractions"
for me.

   Problem is that, I may just kill the guy. I agree that I would be at fault,
and I will have my license revoked, why, I might even go to the gas chamber.
But the fact still remains that the guy is dead.  Someone died because I
was too stingy to put on my lights.

   The ratio of the probability of fallen trees/rocks on the roads to
oncoming traffic is too low to even be considered.  The difference is also
working on what we *know* could happen, to what *might* happen.

  Compared to the number of gallons of gas consumed by those 200 million cars,
it is miniscule!

  Whatever.....  'tis a pity I have to share the same roads with a person
not concerned with safety.

-S
ssave@ole.cdac.com


:      Hello,
:
:    Let me introduce a problem:
:
:    When I measure a sinusoidal wave (voltage) with a digital voltmeter, using
: AC mode, my output is an rms value (a peak value over 2 squared). / Right? /
:    When I measure a square wave in the same mode (AC), my output is equal
: to a peak value, actually, to the upper flat boundary of the wave.
:    I assumed, that a digital voltmeter makes some kind of integration of the
: input value, and divides it over the wave period. / Right?/
:    Now, I used it to measure the same  square wave as above, but distorted
: by high-frequency harmonics. Ideally, output should be the same, but...
: The output value was only about 10% of the previous one!
:    Why? What is the nature of this output value? What does the voltmeter
: actually measure? And what does it show?

Re: RMS readings

Unless the DVM *says* it's measuring RMS, it's probably Average voltage.
The input is diode rectified and measured as DC.  If it says it's RMS
and but measures square/triangle/etc.  incorrectly, it's measuring
average and multipling by a correction that's *only* true for sine waves
(i.e.  Vave*(0.707/0.63) = Vrms).  If you want correct RMS for (most)
any waveform, you need a "True-RMS" DVM/DMM which literally does the
Root-Mean-Square calculation in either analog or digital circuitry.

:
:    Related question (less important to me):
:    What are advantages and disadvantages of digital voltmeters to compare with
: analog ones?

The last significant advantage of analog (IMO) ** was ** being able to
"see" the signal if it was changing over time (e.g.  checking
electrolytic capacitors).

Anymore, most DMM have bargraphs, etc. that duplicate this.

:
:    Thank you for your attention, you could mail me your opinion at
: avm1993@zeus.tamu.edu or open a discussion here. I would appreciate either
: way.
:
:
: Alexander V. Mamishev
:
: ____________________________________________________________________________
: Power System Automation Laboratory    <>   phone office (409) 845-4623
: Department of Electrical Engineering  <>   phone home   (409) 846-5850
: Texas A&M University                  <>   fax   (409) 862-2282
: College Station, TX 77843, USA        <>   Internet: avm1993@zeus.tamu.edu
: ----------------------------------------------------------------------------
:


I use xwd and xwd2ps. To do it from within a program I use
xwd -id xxxxx where xxxxx is the window id obtained from XtWindow(widget).
--
-----------------------------------------------------------------------


Dennis, I'm astounded. I didn't know you were interested to even
study such filth as alt.sex.stories provide...

Cheers,
Kent


GAME(S) OF 4/15
---------------
ADIRONDACK 6	CDI 2	(Adirondack leads series, 1-0)

=================================================
FIRST ROUND
Springfield Indians vs Providence Bruins
Gm 1:	Springfield 3	PROVIDENCE 2
Gm 2:	Springfield 5	PROVIDENCE 4
Gm 3:	4/16	Providence at Springfield
Gm 4:	4/17	Providence at Springfield
Gm 5:	4/22	Springfield at Providence	*
Gm 6:	4/24	Providence at Springfield	*
Gm 7:	4/27	Springfield at Providence	*

CD Islanders vs Adirondack Red Wings
Gm 1:	ADIRONDACK 6	CDI 2
Gm 2:	4/17	CDI at Adirondack
Gm 3:	4/18	Adirondack at CDI
Gm 4:	4/21	Adirondack at CDI
Gm 5:	4/23	CDI at Adirondack	*
Gm 6:	4/24	Adirondack at CDI	*
Gm 7:	4/26	CDI at Adirondack	*

Baltimore Skipjacks at Binghamton Rangers
Gm 1:	4/16	Baltimore at Binghamton
Gm 2:	4/17	Baltimore at Binghamton
Gm 3:	4/23	Binghamton at Baltimore
Gm 4:	4/24	Binghamton at Baltimore
Gm 5:	4/26	Baltimore at Binghamton	*
Gm 6:	4/28	Binghmaton at Baltimore	*
Gm 7:	4/30	Baltimore at Binghamton	*

Utica Devils vs Rochester Americans
Gm 1:	4/16	Utica at Rochester
Gm 2:	4/17	Utica at Rochester
Gm 3:	4/20	Rochester at Utica
Gm 4:	4/22	Rochester at Utica
Gm 5:	4/24	Utica at Rochester	*
Gm 6:	4/26	Rochester at Utica	*
Gm 7:	4/28	Utica at Rochester	*

Moncton Hawks vs St John's Maple Leafs
Gm 1:	St John's 4	Moncton 2
Gm 2:	4/17	Moncton vs St John's at Halifax
Gm 3:	4/21	St John's at Moncton
Gm 4:	4/23	St John's at Moncton
Gm 5:	4/26	Moncton vs St John's at Halifax	*
Gm 6:	4/28	St John's at Moncton		*
Gm 7:	4/30	Moncton vs St John's at Halifax	*

Cape Breton Oilers vs Fredericton Canadiens
Gm 1:	Fredericton 4	Cape Breton 3	(2OT)
Gm 2:	4/16	Cape Breton at Fredericton
Gm 3:	4/20	Fredericton at Cape Breton
Gm 4:	4/22	Fredericton at Cape Breton
Gm 5:	4/24	Cape Breton at Fredericton	*
Gm 6:	4/26	Fredericton at Cape Breton	*
Gm 7:	4/28	Cape Breton at Fredericton	*


W4WG requires DOS drives.  I use LASTDRIVE=J which makes my first Novell drive
K and leaves me drives G, H, I and J for W4WG.  My local DOS drives use A-F.


the
boot
reboots

This problem is usually a low +5 Vdc from the power supply, there is an
adjustment for this on the supply. If the voltage is still unstable or low
then the culprit is probably a bad rectifier at CR20.


Purists often distinguish between "true" clubbing and "pseudo"
clubbing, the difference being that with "true" clubbing the
angle of the nail when viewed from the side is constantly
negative when proceeding distally (towards the fingertip).
With "pseudo" clubbing, the angle is initially positive, then
negative, which is the normal situation. "Real" internists
can talk for hours about clubbing. I'm limited to a couple
of minutes.

Whether this distinction has anything to do with reality is
entirely unclear, but it is one of those things that internists
love to paw over during rounds. Supposedly, only "true" clubbing
is associated with disease. The problem is that the list of
diseases associated with clubbing is quite long, and includes
both congenital conditions and acquired disease. Since many of
these diseases are associated with cardiopulmonary problems
leading to right to left shunts and chronic hypoxemia, it is
very reasonable to get a chest xray. However, many of the
congenital abnormalities would only be diagnosed with a cardiac
catheterization.

The cause of clubbing is unclear, but presumably relates to
some factor causing blood vessels in the distal fingertip to
dilate abnormally.

Clubbing is one of those things from an examination which is
a tipoff to do more extensive examination. Often, however,
the cause of the clubbing is quite apparent.


Hi,
I have got a Quantum ProDrive 80AT IDE harddisk and would
like to format it. When trying to format it (*no* low-level
format, just FDISK and DOS FORMAT), I somehow messed up the
parameters... I had entered FDISK /MBR not exactly knowing
what this does.
The suggested drive type 38 formats the drive only to 21MB.
I tried type 25, but this gives only around 70MB and not
the nominal 80MB.
Could I use user type 47? However, I don't know the actual
parameters (cylinders, heads,...) Could someone give me them?
And how does FDISK work together with user type 47?
Please reply by email to GERTHD@MVS.SAS.COM
Thank you,
Thomas
+-------------------------------------------------------------------+
+-------------------------------------------------------------------+


What files do I need to download for GhostScript 2.5.2?  I have never used
GhostScript before, so I don't have any files for it.  What I *do* have is
gs252win.zip, which I downloaded from Cica.  Unfortunately, it doesn't seem to
work on it's own, but needs some more files that I don't have.  I want to run
GhostScript both in Windows 3.1 and in MS-DOS on a 386 PC (I understand there's
versions for both environments).  What are all the files I need to download and
where can I get them?  Any info would be appeciated.

--------------------------------------------------------------------------------
  Steve W Brewer                                                rewerB W evetS
  cl238405@ulkyvx.louisville.edu                ude.ellivsiuol.xvyklu@504832lc


I'm posting this for my Mom and Dad's neighbor.  Please contact her
directly.

				For Sale


Hey GUI folks,

Does anyone out there have experience with the HP Interface Architect
(GUI dev tool)?  If so, can I call you and ask a couple of quick
questions?  I promise I'll be brief, the questions are simple, and of
course I'll call on my nickel.

Jeff Copeland
jeffcop@i88.isc.com

708-505-9100 x330
INTERACTIVE Systems Corp. (now a Systemhouse co.)


Presumably, the key split is so that no one group controls the privacy
of the key, and that it would be infeasible to illicitly gain access from
both agents.

However, if one agent wishes to break the crypto without the cooperation
of the other agent, a 40-bit key is not going to stand in the way of a
brute force attack.  If an agency (for example, the NSA) were to hold one
of the two key-halves, then I don't imagine they really need the other half of
the key to start listening in.

Or was that the point?   <grin>

(This is not to imply, at all, that I like the idea of the rest of the
system.)


The number of civilian Iraqi deaths were way over-exaggerated and
exploited for anti-war emotionalism by the liberal news media.  The
facts are that less Iraqis died in the Gulf War than did civilians
in any other war of comparable size this century!  This was due mostly
to the short duration coupled with precise surgical bombing techniques
which were technically possible only recently.

The idea that "hundreds of thousands" of Iraqi citizens died is
ludicrous.  Not even "hundreds of thousands" of Iraqi soldiers died,
and they were the ones being targeted!  Or do you think that the US
and its allies were specifically out to kill and maim Iraqi civilians?
Either the smart bombs didn't hit their targets (and we know they did),
or they were targeting civilian targets (!) which is hardly condusive to
destroying Iraq's military potential.  The military mission planners are
not fools, they know they have to hit *military* targets to win a war.
Hitting civilian targets does nothing but unite the people against you,
not a laudable goal if one wants the people to rise up against their
tyrant-dictator.

How about all the innocent people who died in blanket-bombing in WW2?
I don't hear you bemoaning them!  War is never an exact science, but
with smart bombs, it's becoming more exact with a smaller percentage
of civilian casualties.  Sometimes mistakes are made; targets are
misidentified; innocents die.  That's war the way it really is.
But the alternative, to allow tyrannical dictators to treat the earth
like it's one big rummage sale, grabbing everything they can get is
worse.  Like Patrick Henry said some 217 years ago, "I know not what
course others may take -- but as for me, give me liberty, or give me
death!"  War is always the price one must be willing to pay if one
wishes to stay free.

Mathew, your sarcasm is noted but you are completely off-base here.
You come off sounding like a complete peace-nik idiot, although I
feel sure that was not your intent.

So the Iraqi war was wrong, eh?  I'm sure that appeasement would have
worked better than war, just like it did in WW2, eh?  I guess we
shouldn't have fought WW2 either -- just think of all those innocent
German civilians killed in Dresden and Hamburg.  How about all the poor
French who died in the crossfire because we invaded the continent?  We
should have just let Hitler take over Europe, and you'd be speaking
German instead of English right now.

Tyrants like Hussein *have* to be stopped.  His kind don't understand
diplomacy; they only understand the point of a gun.  My only regret is
that Bush wimped out and didn't have the military roll into Baghdad, so
now Hussein is still in power and the Iraqi people's sacrifice (not to
mention the 357 Americans who died) was for naught.  Liberating Kuwait
was a good thing, but wiping Hussein off the map would've been better!

And as for poor, poor Rodney King!  Did you ever stop and think *why*
the jury in the first trial brought back a verdict of "not guilty"?
Those who have been foaming at the mouth for the blood of those
policemen certainly have looked no further than the video tape.
But the jury looked at *all* the evidence, evidence which you and I
have not seen.  When one makes a judgment without the benefit of a
trial where evidence can be presented on both sides, one has simply
lowered himself to the level of vigilante justice, a state-of-mind
which your sarcasm above seemingly spoke against, but instead tends
to support in the case against the policemen.

Law in this country is intended to protect the rights of the accused,
whether they be criminals or cops.  One is not found guilty if there is
a reasonable doubt of one's guilt, and only the jury is in a position
to assess the evidence and render a verdict.  Anyone else is simply
succumbing to verbal vigilantism.

Regards,