I think Mark was talking about making it available to people who didn't
have email in the first place.

If anybody in the Boston area wants a sci.space feed by honest-to-gosh UUCP
(no weird offline malreaders), let me know.  I'll also hand out logins to
anyone who wants one, especially the Boston Chapter of NSS (which I keep forgetting
to re-attend).


SOMEONE PLEASE BUY THESE BOOKS!!!!!  I AM NOT ASKING MUCH!!!!!!

JUST MAKE ME AN OFFER AND I WILL PROBABLY TAKE IT!!!!!

* Calculus w/ Analytic Geometry by Authur B. Simon (copyright date 1982), below avg condition but still readable!

* Writing good software in Fortran, Graham Smith.

* The Holt Handbook by Kirszner & Mandell (copyright 1986) 720+ page writing guide.

* Algebra & Trigonometry, A problem Solving Approach, 3rd edition by W. Flemming and D. Varberg.  Very good condition.

* General Chemistry Principles & Modern Applications, R. Petrucci, fourth
  edition.  Big Book! Very good condition!

* Solutions manual for Chemistry book.  Paperback.

* Study guide for Chemistry book.  Paperback.

Send me your offers via email at 02106@chopin.udel.edu


I read this in an electronic "magazine" about NT:

"And for all the hoopla about NT, one would
think the thing would be multi-user but it's not. It supports
only one user at a time. It can support multiple clients but
only one actual user."

Your mileage may vary!

--
   THIS POSTING DOES NOT REPRESENT THE OPINIONS OF MY EMPLOYERS.


For Sale:

    Roland TR-606 Drum Machine
    Near Mint Condition (no scratches, fully operational).
    Sorry no Manuals.
    Asking $200 US + shipping

    Mirage Rack Mount Sampler
    Minor Scratches around rack ear screws
    with Advanced Sampling Option, 32 Disks
      and both manuals
    It's a long story, but I *may* have the Turtle Beach Vision, sample
        editing software for the IBM PC.
    Asking $400 US + shipping

Send all e-mail requests to:  barsz@bnr.ca

Regards,


Golgotha the whole process of the fall of man

This was precisely my point.  From a theological bent, those who lived
immediately after the flood, such as Noah, Ham, his son Cush, and his son
Nimrod had a much stronger appreciation of Divine wrath.  They also had a
stronger understanding of the True God.  In fact, this immediacy was a cause of
hardship for some, so much so that Atlas, who is seen with heavens resting on
his shoulders.  But this is not merely the physical heavens that he is lifting.
 It is to put God and the strict spirituality of His law at a distance, and
thus he became the "Elevator of the heavens."  This "god" made men able to
"feel" as if heaven were afar off and "as if either the God of Heaven could not
see through the dark cloud, or did not regard with displeasure the breakers of
His laws."  It is interesting to see that it was that was titled "Emancipator"
or "Deliverer"  or Phoroneus. It was Nimrod who invaded the patriarchal system
and abridged the liberties of mankind, yet was worship for having given many
benefits.  He was a deliverer all right but not as we think of Christ as a
Deliverer.  One delivered from a conscious feeling of God's wrath, the other
actually performed a delivery from Gods wrath and it is up to us to accept it
as true.

I don't see the problem.  From the time of Adam, those who looked forward to
the coming "Anointed One" and put their faith in the fact that it was God who
was to do the provision, were accounted as righteous.  But up to the
Crucifixion, their sins were only covered, not taken away.  Therefore, the
dispensation of the Church views the accountability of sin the same, but see it
as a completed action.  Rom's makes it clear that it has always been salvation
via faith and nothing else.

I understand what you're trying to convey, but I don't think I'd lay hold of it
because the scriptures do equate the eternality of the second death with the
eternality of, say the Church ruling with Christ.  Jn 17 tells us what eternal
life is exactly, as you are correct that it is much more than non-cessation of
consciousness.

It depends upon your def of "lost."  The elect were lost only in time as
outside of time they had been chosen from the foundation of the world.
Existentially we were all born "lost", but the "righteous" were "in Christ" and
therefore never *assuredly* lost.

Maybe this summer I could find time to put together a paper on it.  I simply
have to buy more books for myself, and these older books are very expensive.
Either that or countless trips to the oriental museum.

Couldn't agree with you more.  Our understanding, of say eschatology, is
clearly clearer than that of, say Isaiah.  But that is not what I was referring
to.

No, I understand it as you have said. This was my point.

Ah!  This is it.  This is the big question.  However, I would say, again I
think, that the best lie is one that has an appreciable amount of truth to it.
Look at Satan's twist of God's Word when he coerced Eve.  That is a very
interesting study.

 >The similarity in the midst of great variety of

Yes, that is my point.  But it is a two edged sword. For some do not want the
underlying reality to be revealed.  They were not known as "mystery" religions
for no reason.  There was the public side of them and there was the private
side, that was so protected that the initiates to an oath of death if they
revealed that private side.  That is why it is so hard to bring their teachings
to light. The "Mystery of Iniquity" that we find in the Bible, correlates to
this I think.  The primary object of the mysteries was to introduce privately,
little by little, under the seal of secrecy and sanction of oath, what it would
not have been safe to openly profess was the true religion.  Case in point
today might be the Masons.  (Just a note, that they too worshipped Osiris in
Egypt, who can be traced to Nimrod, the "husband son.")

No, I disagree with you here Gerry.  I know what you're alluding to in that the
church, primarily the RCC, did endorse Aristotelian philosophy into their
worldview, but I would disagree with you that it originated in Greece.  If you
are a student of history, you will come to see that much of what Greece came to
expound to the world as their original, was just an adulteration of that which
they had taken from conquered countries.  The soul is clearly mentioned and
discussed at length in the Egyptian religions. As was the unity of God and also
the trinity of God.  See if you can find Wilkinson's "Egyptians."  He really
does a number on what the Greeks did to what they "pilfered" from the
Egyptians.

I'm not knocking Aristotle or Plato or any other Greek thinker.  Its just that
"there is nothing new under the sun."


The CU people have been, and continue to be big ozone scientists. So
this is consistent. It is also consistent with the new "Comercial
applications" that NASA and Clinton are pushing so hard.

Did anyone catch the rocket that was launched with a movie advert
all over it? I think the rocket people got alot of $$ for painting
up the sides with the movie stuff. What about the Coke/Pepsi thing
a few years back? NASA has been trying to find ways to get other
people into the space funding business for some time. Frankly, I've
thought about trying it too. When the funding gets tight, only the
innovative get funded. One of the things NASA is big on is co-funding.
If a PI can show co-funding for any proposal, that proposal has a SIGNIFICANTLY
higher probability of being funded than a proposal with more merit but no
co-funding. Once again, money talks!


The trackbal on my PB140 no longer moves in the horizontal direction.  When I
called the nearest Authorized Apple Service person I was told that it probably
needed replacing and that would cost me over $150!  Ouch!
  Can anyone recommend a less expensive way to fix this problem?  One strange
symptom of the problem is that when I take the ball out of the socket and shine
a light into the hole I can make the cursor move horizontally by moving the
wheel with my finger, it works fine that way but won't work if I turn off the
light.  Any suggestions or comments?
-------------------------------------------------------------------------------
Ben Roy .......just a poor college student.......internet<br4416a@american.edu>


Anyone have any info. on the video/sound card from SIGMA designs.
It is called WIN STORM PC.
They also have another card called the legend 24lx

any info would be appreciated, incuding performance, pricing and
availability.
thanks


So why do I read in the papers that the Qumram texts had "different
versions" of some OT texts.   Did I misunderstand?


Will there be any support for round or circular widgets in Motif's next
release?. I'd love to have a circular knob widget which could be used
instead of a slider.


Hey, what do we look like, a parts store?  Has it ever occurred to you to
visit your dealer and fork out the bucks for a new one?  What are the
chances of someone happening to have a '92 part laying around, much less
one in working condition?  Sheesh, some edu's.

Besides, I only have the right side inverted GSX-R fork.  It's already been
converted into a floor lamp.


On the subject of CS/CN/tear gas: when I received my initial introduction to
tear gas, the first thing that came to mind was the location of the exit.  If
there had been anything in the way, corners to negotiate, doors to open, or
any other obstacles to movement, I would have had a difficult time exiting the
chamber.  And any concentration of tear gas is hazardous to individuals with
respiratory problems, and the wearing of soft contact lenses in a tear gas
contaminated area is considered a REAL BAD IDEA.  So hoping the BD's would
peaceably come strolling out the door after being gassed is a bit unrealistic.
If they could have found the door, having them staggering out retching wouldn't
be too far fetched.  Throw in the factor of 50-51 days of being under siege and
subject to psychological warfare, and all bets on functional abilities are off.
Anybody tried to get Amnesty International to jump in on this one?


Timeshare week for rent / must use before July / Best offer!!

Week can be "traded" to anywhere in the world (Hawaii, Austria,
Far East, U.S. etc.) under Interval International.

Will answer questions about that, and help you trade (we have
the paperwork and phone numbers in order to that).


In making batteries you could use copper and zinc in an acid electrolyte.
Copper=copper wire (pennies are now mostly zinc if I recall correctly)
zinc= zinc strip (Hardware stores arround here (Seattle) sell this to prevent
      moss buildup on the roof. An alternative would be to use a galvanized
      (zinc coated) nail
electrolyte= lemon juice -> Citric acid is the active ingrediant(sp).

Volta (late 18th century scientist) used a stack for his batteries-
copper disk, paper disk soaked in acid, zinc disk, copper disk, paper ....
they were advanced technology for the time.


I've been intently following the MAG thread while waiting for
mine to arrive in the mail. There seems to be a lot of
complaints about minor alignment problems with the MX15F. One
article contained a comment that the owner called the factory
and was told that his screen rotation was within spec (1/4").

Well, my monitor arrived last night and, sure enough, it has
a very noticable barrel distortion. It's not dramatic, but it
is there and it is especially noticable when the image doesn't
fill the entire screen. The fact that it is worse on the right
side doesn't help matters.

What I'm trying to find out is if these minor imperfections
are the norm or are most of their monitors perfect? I don't want
to send it back and get one with the same or an even worse
problem. Does the factory consider this kind of thing normal
and ship their monitors with less than perfect alignment?
Are other netters just living with these kind of imperfections?

--


I'm writting letters to my Congresscritters and was wondering if
 there is any reason(s) why I should NOT support the following
 Bills, other than the previous comments about S.458.  Just checking
 before I mail the letter to make sure I don't support something
 that I really shouldn't.

 -----------------
 I strongly SUPPORT the following laws currently being considered in Congress
 as they would either have a positive effect towards reducing crime, or re-
 enforce our Constitutional right under the 2nd amendment.

 * S. 441 (Campbell)	To amend title 18, United States Code, to provide a
			mandatory minimum sentence for the unlawful possession
			of a firearm by a convicted felon, a fugitive from
			justice, a person who is addicted to, or an unlawful
			user of, a controlled substance, or a transferor or
			receiver of a stolen firearm, to increase the general
			penalty for violation of Federal firearms laws,
			and to increase the enhanced penalties provided for the
			possession of a firearm in connection with a crime of
			violence or drug trafficking crime, and for other
			purposes.

 * S.458  (Smith) 	To restore the second Amendment Rights of all Americans.

 * S.488  (Specter)	To provide Federal penalties for drive-by shootings.

 * S.504  (Kohl)	To amend section 924 of title 18, United States Code to
			make it a Federal crime to steal a firearm or explosives
			in interstate or foreign commerce.

                                Bill Vojak
                                vojak@icebucket.stortek.com
				NRA, ILA,
                                Colorado Firearms Coalition
-----------------------------------------------------------------
 Here's a story, bout a man named Brady, who took a .22 bullet
 in his head.  Even though he can act perfectly normal, he
 prefers to pretend he's brain dead.

 Here's a story, bout a woman named Brady, who had nothing to
 do but sit around all day.  Then her husband became a media
 martyr, now she wants to take all your guns away.

 The Brady Bunch, The Brady Bunch, This is how we got stuck
 with the Brady Bunch. . . . .


I would suggest Draw for Windows (by Micrografx).  I have this on my
home box.  Its quite impressive and only cost UKL100.  It has a rather
nice clip-art library facility which you can expand with your own
drawings.  There is no circuit component clip-art included, but you
could add your own quite easily.

It works with any Windows printer driver of course, and can also
export embedded postscript and PCX files.

Note: I am not connected with Micrografx in any way.

Paul.


The latest Israeli "proposal", first proposed in February of 1992, contains
the following assumptions concerning the nature of any "interim status"
refering to the WB and Gaza, the Palestinians, implemented by negotiations.
It states that:
   >Israel will remain the existing source of authority until "final status"
    is agreed upon;
   >Israel will negiotiate the delegation of power to the organs of the
    Interim Self-Government Arrangements (ISGA);
   >The ISGA will apply to the "Palestinian inhabitants of the territories"
    under Israeli military administration. The arrangements will not have a
    territorial application, nor will they apply to the Israeli population
    of the territories or to the Palestinian inhabitants of Jerusalem;
   >Residual powers not delegated under the ISGA will be reserved by Israel;
   >Israelis will continue to live and settle in the territoriesd;
   >Israel alone will have responsibility for security in all its aspects-
    external, internal- and for the maintenance of public order;
   >The organs of the ISGA will be of an administrative-functional nature;
   >The exercise of powers under the ISGA will be subject to cooperation and
    coordination with Israel.
   >Israel will negotiate delegation of powers and responsibilities in the
    areas of administration, justice, personnel, agriculture, education,
    business, tourism, labor and social welfare, local police,
    local transportation and communications, municipal affairs and religious
    affairs.

Several question do come to mind concerning the "success" we all hope for
in the ongoing negotiation process. These arrangements certainly seem to
be essentially a rejection of any Palestinian "interim" self-control.
Without exposing itself to unwarranted risks and creating irresversible
vulnerability, can Israel reasonably put forward (at later points in the
negotiating process) more "relaxed" proposals for this"interim" period?
How should proposals (from either side) be altered to temper their
"maximalist" approaches as stated above? How can Israeli worries ,and
desire for some "interim control", be addressed while providing for a
very *real* interim Palestinian self-governing entity?

Tim


Toronto                          1 1 1--3
Detroit                          1 4 1--6
First period
     1, Detroit, Yzerman 1 (Gallant, Ciccarelli) 4:48.
     2, Toronto, Cullen 1 (Clark, Gill) 10:44.
Second period
     3, Detroit, Sheppard 1 (Probert, Coffey) pp, 5:04.
     4, Detroit, Burr 1 (Racine) sh, 6:42.
     5, Detroit, Chiasson 1 (Coffey) pp,11:00.
     6, Detroit, Howe 1 (Yzerman, Drake) 14:46.
     7, Toronto, Gilmour 1 (Borschevsky, Ellett) pp, 19:59.
Third period
     8, Detroit, Racine 1 (Primeau, Drake) 5:10.
     9, Toronto, Lefebvre 1 (Cullen, Pearson) 7:45.

Detroit: 6    Power play: 6-2   Special goals:  pp: 2  sh: 1  Total: 3
Scorer            G    A   Pts
---------------  ---  ---  ---
Burr               1    0    1
Chiasson           1    0    1
Ciccarelli         0    1    1
Coffey             0    2    2
Drake              0    2    2
Gallant            0    1    1
Howe               1    0    1
Primeau            0    1    1
Probert            0    1    1
Racine             1    1    2
Sheppard           1    0    1
Yzerman            1    1    2

Toronto: 3    Power play: 5-1
Scorer            G    A   Pts
---------------  ---  ---  ---
Borschevsky        0    1    1
Clark              0    1    1
Cullen             1    1    2
Ellett             0    1    1
Gill               0    1    1
Gilmour            1    0    1
Lefebvre           1    0    1
Pearson            0    1    1

-----------------------------------------
Winnipeg                         1 0 1--2
Vancouver                        2 0 2--4
First period
     1, Vancouver, Adams 1 (Linden, Bure) pp, 1:23.
     2, Vancouver, Craven 1 (Bure, Murzyn) 9:56.
     3, Winnipeg, Steen 1 (Shannon, Housley) pp, 17:53.
Second period
     No scoring.
Third period
     4, Winnipeg, King 1 (Barnes) 3:43.
     5, Vancouver, Linden 1(Courtnall, McLean) 12:16.
     6, Vancouver, Ronning 1 (Courtnall) 18:31.

Vancouver: 4    Power play: 6-1
Scorer            G    A   Pts
---------------  ---  ---  ---
Adams              1    0    1
Bure               0    2    2
Courtnall          0    2    2
Craven             1    0    1
Linden             1    1    2
McLean             0    1    1
Murzyn             0    1    1
Ronning            1    0    1

Winnipeg: 2    Power play: 3-1
Scorer            G    A   Pts
---------------  ---  ---  ---
Barnes             0    1    1
Housley            0    1    1
King               1    0    1
Shannon            0    1    1
Steen              1    0    1


Ok guys, I need a list of the teams who have been hot or cold during the
last 25 games.  Doesn't need to be accurate, a rough guess will do.  I'm
about to enter a playoff pool and I want to know who is hot going into
the playoffs.  Don't need to mention Pittsburgh.  They can't get any hotter
than they are now.

P.S. I need this by Sunday


Unfortunatly, this seems to be how Christians are taught to think when
it comes to their religion. Some take it to the extreme and say that
their religion is the ONLY one and if you don't accept their teachings
then you won't be "saved". It takes quite a bit of arrogance to claim
to know what God thinks/wants. Especially when it's based upon your
interpretation of a book. The logic in the above statement is faulty
in that it assumes two people with differing beliefs can't both be
correct. It's all about perception. No two people are exactly alike.
No two people perceive everything in the same way. I believe that
there is one truth. Call it God's truth, a universal truth, or call it
what you will. I don't believe God presents this truth. I think it is
just there and it's up to you to look for and see it, through prayer,
meditation, inspir- ation, dreams or whatever. Just because people may
perceive this truth differently, it doesn't mean one is wrong and the
other is right. As an example, take the question, "Is the glass half
empty or half full"? You can have two different answers which are
contradictory and yet both are correct. So, for your belief to be
true, does not require everyone else's belief to be wrong.


I created a pixmap or drawable window, then used XDrawLine() function
drawed a line as below fingure:

		width = 300
	================================
	|				|
	|				|
	|			p1	|
	|			\	|
	|			 \	| height = 300
	|			  \	|
	|			   \	|
	|			    \	|
	|			     \	|
	|			      \	|
	|			       \|p3
	|				|
	|===============================| \
					    \
					     p2

	I created the pixmap or drawable window only with size 300x300.
But I draw line from p1(x1=270,y1=100) to p2(x2=500,y2=800).
My question is, dose the XDrawLine function can finger out that correct
p3(x3 and y3) for me? If you calculate x3 and y3.

x3 = 300;

@ = art tan (( 800 - 100)/(500 - 270)) = 71.81 degrees;

y3 = 100 + x3/tan(@) = 100 + 300/tan(71.81) = 198.58 ~= (integer) 199.

How do I prove XDrawLine() give me the right x3, y3 or not?
Please don't ask me why I don't created a 900x900 pixmap. No, I don't
wan to.

Thanks in advance!


Hi... I'm not a religious guy so dont take this as some kinda flame (thanx
in advance)

I want to know why there are so many different versions of the bible? There
"....contains inaccurate data and inconsistencies."

					Thanx in advance... Shaz....

[I'm not sure quite what you mean by many different versions.
The primary distinction in versions you see today is in the style
of the translation.  It's pretty unusual to see significant
differences in meaning.  There are a few differences in the underlying
text.  That's because before printing, manuscripts were copied by
hand.  Slight differences resulted.  There are enough manuscripts
around that scholars can do a pretty good job of recreating the
original, but there are some uncertainties.  Fortunately, they are
generally at the level of minor differences in wording.  There are
something like 3 or 4 places where whole sentences are involved,
but with recent discoveries of older manuscripts, I don't think there's
much uncertainly about those cases.  As far as I know, no Christians
believe that the process of copying manuscripts or the process of
translating is free of error.  But I also don't think there's
enough uncertainty in establishing the text or translating it that
it has much practical effect.

Whether the Bible contains inaccurate data and inconsistences is a hot
topic of debate here.  Many Christians deny it.  Some accept it
(though most would say that the inaccuracies involved are on details
that don't affect the faith).  But this has nothing to do with there
being multiple versions.  The supposed inconsistences can be found in
all the versions.  I'm surprised to find a reference to this on the
title page though.  What version are you talking about?  I've been
referring to major scholarly translations.  These are what get
referenced in postings here and elsewhere.  There have certainly been
editions that are (to be kind) less widely accepted.  This includes
everything from reconstructions that combine parallel accounts into
single narrations, to editions that omit material that the editor
objects to for some reason or the other.  The copyright on the Bible
has long since expired, so there nothing to stop people from making
editions that do whatever wierd thing they want.  However the editions
that are widely used are carefully prepared by groups of scholars from
a variety of backgrounds, with lots of crosschecks.  I could imagine
one of the lesser-known editions claiming to have fixed up all
inaccurate data and inconsistencies.  But if so, it's not any edition
that's widely used.  The widely used ones leave the text as is.
(Weeeeelllllll, almost as is.  It's been alleged that a few
translations have fudged a word or two here and there to minimize
inconsistencies.  Because translation is not an exact science, there
are always going to be differences in opinion over which word is best,
I'm afraid.)


sandvik@newton.apple.com (Kent Sandvik) writes...

Which Jews KS?

(ex. as a people, as a language, religiously, politically, or...)

Do you mean those Jews who are God's chosen?

{And Malcolm, please, if you will, set your word wrap at 75 or less
to avoid clutter?}


   Geez wharfie, do you have to be so difficult? Mine was built in December
'88,
   which qualifies as pretty dang early, and it most certainly grinds away.


Wow.  ESPN can repeat eleven-year-old Bill James research.  (Literally.
Check the 1982 Abstract.)

Perhaps in 2004 they'll be as reliable as an average SDCN.

Oops, maybe not.


Ergo, if your life is sufficiently boring, you have no need for privacy?

(This is not meant to be personal, just the logical conclusion of your
statement.)


	Why?  Either the numerator or the denominator could fluctuate.
	The dollar value of a gun would (of course)
	go up if supply were restricted.  The weight of a gun might
	go down significantly as technology improved.   I don't
	think you have a basis to assert this.


The supersonic booms hear a few months ago over I belive San Fran, heading east
of what I heard, some new super speed Mach 25 aircraft?? What military based
int he direction of flight are there that could handle a Mach 25aircraft on its
landing decent?? Odd question??


Like it or not, Edward, Anwar has a very good, valid point.  Obviously,
in presenting it, he (quite legitimately and deliberately) takes a point
of view to an extreme which might not have been what you intended, but
that is one of the best ways to demonstrate a "slippery slope" type of
argument, which I believe was his aim.

I very frankly believe that the ADL will be proved innocent in this
case.  I doubt there's enough evidence to weigh against them even in a
civil court, where preponderance of the evidence, not evidence beyond
any reasonable doubt, is the standard for "winning" such a case.  That,
however, does not prevent me from seeing the merit in Anwar's point.

Rest deleted.


I'm posting this for a friend that runs a BBS. I'm not sure if its under
DOS or Windows.

He is interested in a board that has 16 ports on it. In another post,
someone suggeted a DigiBoard, but didn't have too much info on it.

Could someone give me information on any boards that they know of with
the before mentioned configuration. Models. Specifications. Prices.
 Manufacturers.

Thanks,

Rob

--


Bobby-

A few posts ago you said that Lucifer had no free will.  From the above
it seems the JW believes the contrary.

Are you talking about the same Lucifer?

If so, can you suggest an experiment to determine which of you is wrong?

Or do you claim that you are both right?


Could someone please post any info on these systems.

Thanks.
BoB
--
----------------------------------------------------------------------
Robert Novitskey | "Pursuing women is similar to banging one's head
rrn@po.cwru.edu  |  against a wall...with less opportunity for reward"


If she is having problems with fresh vegetables, the guess is that there
is some obstruction of the intestine.  Without knowing more it is not
possible to say whether the obstruction is permanent due to scarring,
or temporary due to swelling of inflammed intestine.  In general, there are
no dietary limitations in patients with Crohn's except as they relate
to obstruction.  There is no evidence that any foods will bring on
recurrence of Crohn's.  It is important to distinguish recurrence from
recurrent symptoms.  A physician would think of new inflammation as
recurrence, while pains from raw veggies just imply a narrowing of the
intestine.

Your friend should look into membership in the Crohn's and Colitis
Foundation of America.   1-800-932-2423

Good luck to your friend.


In New Orleans, LA, there was a company making motorcycles for WHEELCHAIR
bound people!  The rig consists of a flat-bed sidecar rig that the
wheelchair can be clamped to.  The car has a set of hand controls mounted on
conventional handlebars!  Looks wierd as hell to see this legless guy
driving the rig from the car while his girlfriend sits on the bike as a
passenger!

 ----===== DoD #8177 = Technician(Dr. Speed) .NOT. Student =====----


FOR SALE:
	Orchid Fareheit 1280 24bit color card
	-1 meg
	-almost new

$200 or best offer

This is a post for a friend

Call him (Thuan Pho) at 314-368-3624


Archive-name: x-faq/speedups
Last-modified: 1993/4/15

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
	HOW TO MAXIMIZE THE PERFORMANCE OF X -- monthly posting
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
	    Compiled by Art Mulder (art@cs.ualberta.ca)

  More RAM, Faster CPU's, More disk space, Faster Ethernet...  These
  are the standard responses you hear when you ask how to improve the
  performance of your workstation.

  Well, more hardware isn't always an option, and I wonder if more
  hardware is always even a necessity.

  This "FAQ" list is a collection of suggestions and ideas from different
  people on the net on how you can the best possible performance from X
  Windows on your workstation, WITHOUT PURCHASING MORE HARDWARE.

  Performance is a highly subjective issue.  The individual user must
  balance `speed' versus `features' in order to come to a personal
  decision.  Therefore this document can be be expected to contain many
  subjective opinions in and amongst the objective facts.

  This document is specifically concerned with X.  There are of course
  many other factors that can affect the performance of a workstation.
  However, they are outside the scope of this document.

    [ People seriously interested in the whole area of system
    performance, might want to look at the O'Reilly Nutshell Handbook
    "System Performance Tuning" by Mike Loukides.  I'm about 25% of the
    way through reading it, and it looks like a well-written
    comprehensive treatment of system performance.  I'm unaware of any
    other similar books.  --ed.]

-----------------
Table of Contents
-----------------
  0. Introduction & Administrivia
  1. What about the "Other X FAQ"?
  2. Window Managers
  3. The X Server
       Which Server?
       Locking the Server into RAM?
       Starting your Server
       Fonts
       About the Resources File
!      Define Your Display Properly
  4. Clients
       A Better Clock for X
       A Better Terminal Emulator for X
       Tuning your client
  5. Miscellaneous Suggestions
       Pretty Pictures
       A Quicker Mouse
       Programming Thoughts
       Say What!?
  6. Other Sources of Information
  7. Author & Notes

! = changed since last issue.
* = new since last issue.

-----------------------------
Introduction & Administrivia
-----------------------------

  This document is posted each month, on or around the 15th, to the
  Usenet news groups comp.windows.x, news.answers, and comp.answers.
  If you are reading a copy of this FAQ which is more than a few
  months old (see the "Last-modified" date above) you should probably
  locate the latest edition, since the information may be outdated.

  If you do not know how to get those newsgroups and/or your site does
  not receive them and/or this article has already expired, you can
  retrieve this FAQ from an archive site.

  There exist several usenet FAQ archive sites.  To find out more about
  them and how to access them, please see the "Introduction to the
  news.answers newsgroup" posting in news.answers.

  The main FAQ archive is at rtfm.mit.edu [18.172.1.27].  This document
  can be found there in /pub/usenet/news.answers/x-faq/speedups.  If
  you do not have access to anonymous ftp, you can retrieve it by
  sending a mail message to mail-server@pit-manager.mit.edu with the
  command "send usenet/news.answers/x-faq/speedups" in the message body.

-----------------------------
What about the "Other X FAQ"?
-----------------------------

  David B. Lewis (faq%craft@uunet.uu.net) maintains the informative and
  well written "comp.windows.x Frequently Asked Questions" document.
  Its focus is on general X information, while this FAQ concentrates
  on performance.

  The comp.windows.x FAQ does address the issue of speed, but only with
  regards to the X server.  The gist of that topic seems to be:
	"Use X11R5, it is faster than R4".
  (Please see the X FAQ for complete details).

---------------
Window Managers
---------------

  There are a lot of window managers out there, with lots of different
  features and abilities.  The choice of which to use is by necessity a
  balancing act between performance and useful features.  At this
  point, most respondents have agreed upon "twm" as the best candidate
  for a speedy window manager.

  A couple of generic tricks you can try to soup up your window manger,
  is turning off unnecessary things like "zooming" and "opaque move".
  Also, if you lay out your windows in a tiled manner, you reduce the
  amount of cpu power spent in raising and lowering overlapping
  windows.                           Joe English (joe@trystero.art.com)

  I've found that a good font for tiling is 7x13 (aka:
  -misc-fixed-medium-r-normal--13-100-100-100-c-70-iso8859-1 ). It is
  the biggest font I know of that I can use on my Sun (1152x900 screen)
  and still get two 80 column terminal windows side-by-side on the
  display with no overlap.  Other font suggestions will be accepted.

------------
The X Server
------------

Which Server?
- - - - - - -
  Make sure that your server is a proper match for your hardware.
  If you have a monochrome monitor, use a monochrome X11 server.

  On my Monochrome Sun, I haven't noticed much difference between
  the Xsun (colour) server and XsunMono, however it was pointed out to
  me that XsunMono is about 800k smaller and therefore should contribute
  to less paging.
         [ thanks to: Jonny Farringdon (j.farringdon@psychol.ucl.ac.uk),
                        Michael Salmon (Michael.Salmon@eos.ericsson.se) ]

  How your server was compiled can also make a difference.  Jeff Law
  (law@schirf.cs.utah.edu) advises us that on a Sun system, X should be
  compiled with gcc (version 2.*) or with the unbundled Sun compiler.
  You can expect to get "*very* large speedups in the server" by not
  using the bundled SunOS compiler.  I assume that similar results
  would occur if you used one of the other high-quality commercial
  compilers on the market.

Locking the Server into RAM?
- - - - - - - - - - - - - - -
  Has anyone tried hacking the X server so that it is locked into RAM and
  does not get paged?  eg: via a call to plock().  Does this help
  performance at all?  I've had one inquiry on this topic, and a few
  pointers to the plock() function call, but no hard evidence from someone
  who's tried it.  I am not in a position to give it a try.
			  [thanks to: Eric C Claeys (ecc@eperm.att.com),
				      Danny Backx (db@sunbim.be),
				      Juan D. Martin (juando@cnm.us.es) ]
Starting your Server
- - - - - - - - - - -
  Joe English (joe@trystero.art.com) :
    If you start up a lot of clients in your .xsession or whatever, sleep
    for a second or two after launching each one.  After I changed my
    .xclients script to do this, logging in actually took *less* time...
    we have a heavily loaded system without much core, though.

  This sounds crazy, but I have confirmed that it works!

  Warner Losh (imp@Solbourne.COM) provided me with a good explanation of
  why this works, which I have summarized here:

    When you start up an X server it takes a huge amount of time to
    start accepting connections.  A lot of initialization is done by
    the server when it starts.  This process touches a large number of
    pages.  Any other process running at the same time would fight the
    server for use of the CPU, and more importantly, memory.  If you
    put a sleep in there, you give the Server a chance to get itself
    sorted out before the clients start up.

    Similarly, there is also a lot of initialization whenever an X
    client program starts: toolkits registering widgets, resources
    being fetched, programs initializing state and "databases" and so
    forth.  All this activity is typically memory intensive.  Once this
    initialization is done ("The process has reached a steady state"),
    the memory usage typically settles down to using only a few pages.
    By using sleeps to stagger the launching of your clients in your
    .Xinitrc , you avoid them fighting each other for your
    workstation's limited resources

  This is most definitely a "Your Mileage May Vary" situation, as there
  are so many variables to be considered: available RAM, local swap
  space, load average, number of users on your system, which clients
  you are starting, etc.

  Currently in my .xinitrc I have a situation like:
	(sleep 1; exec xclock ) &
	(sleep 1; exec xbiff ) &
	(sleep 1; exec xterm ) &
	(sleep 1; exec xterm ) &

  I've experimented with:
	(sleep 1; exec xclock ) &
	(sleep 2; exec xbiff ) &
	(sleep 3; exec xterm ) &
	(sleep 4; exec xterm ) &

  I've even tried:
	(sleep 2; exec start_X_clients_script ) &
  and then in start_X_clients_script I had:
	(sleep 1; exec xclock ) &
	(sleep 1; exec xbiff ) &
	(sleep 1; exec xterm ) &
	(sleep 1; exec xterm ) &

    [ The idea with this last one was to make sure that xinit had
    completely finished processing my .xinitrc, and had settled down
    into a "steady state" before the sleep expired and all my clients
    were launched. ]

  All of these yielded fairly comparable results, and so I just stuck with
  my current setup, for its simplicity.  You will probably have to
  experiment a bit to find a setup which suits you.

Fonts
- - -
  Loading fonts takes time and RAM.  If you minimize the number of fonts
  your applications use, you'll get speed increases in load-up time.

  One simple strategy is to choose a small number of fonts (one small, one
  large, one roman, whatever suits you) and configure all your clients -- or
  at least all your heavily used clients -- to use only those few fonts.
  Client programs should start up quicker if their font is already loaded
  into the server.  This will also conserve server resources, since fewer
  fonts will be loaded by the server.
			      [ Farrell McKay (fbm@ptcburp.ptcbu.oz.au),
			        Joe English (joe@trystero.art.com) ]

  eg: My main xterm font is 7x13, so I also have twm set up to use 7x13
  in all it's menus and icons etc.  Twm's default font is 8x13.  Since
  I don't normally use 8x13, I've eliminated one font from my server.

  Oliver Jones (oj@roadrunner.pictel.com):
    Keep fonts local to the workstation, rather than loading them over nfs.
    If you will make extensive use of R5 scalable fonts, use a font server.

About the Resources File
- - - - - - - - - - - - -

    Keep your .Xresources / .Xdefaults file small.  Saves RAM and saves
    on server startup time.          Joe English (joe@trystero.art.com)

  One suggestion:

    In your .Xdefaults (.Xresources) file, try putting only the minimum
    number of resources that you want to have available to all of your
    applications.  For example:  *reverseVideo: true

    Then, separate your resources into individual client-specific
    resource files.  For example: $HOME/lib/app-defaults.  In your
    .login file set the environment variable XUSERFILESEARCHPATH:

	setenv XUSERFILESEARCHPATH $HOME/lib/app-defaults/%N

    [ The "comp.windows.x Frequently Asked Questions" FAQ contains
    an excellent explanation of how these environment variables work.
    --ed.]

    So, when xterm launches, it loads its resources from
    .../app-defaults/XTerm.  Xdvi finds them in .../app-defaults/XDvi,
    and so on and so forth.  Note that not all clients follow the same
    XXxxx resource-file naming pattern.  You can check in your system
    app-defaults directory (often: /usr/X11R5/lib/X11/app-defaults/) to
    find the proper name, and then name your personal resource files
    with the same name.

    This is all documented in the Xt Specification (pg 125 & 666).
		    [Thanks to: Kevin Samborn (samborn@mtkgc.com),
		         Michael Urban (urban@cobra.jpl.nasa.gov),
		             and Mike Long (mikel@ee.cornell.edu).
	     Kevin is willing mail his setup files to inquirers.]

  This method of organizing your personal resources has the following
  benefits:

    - Easier to maintain / more usable.

    - Fewer resources are stored in the X server in the RESOURCE_MANAGER
      property.  As a side benefit your server may start fractionally
      quicker, since it doesn`t have to load all your resources.

    - Applications only process their own resources, never have to sort
      through all of your resources to find the ones that affect them.

  It also has drawbacks:

    - the application that you are interested in has to load an
      additional file every time it starts up.  This doesn't seem to
      make that much of a performance difference, and you might
      consider this a huge boon to usability.  If you are modifying an
      application's resource database, you just need to re-run the
      application without having to "xrdb" again.

    - xrdb will by default run your .Xdefaults file through cpp.  When
      your resources are split out into multiple resource files and
      then loaded by the individual client programs, they will not.
      WATCH OUT FOR THIS!!

      I had C style comments in my .Xdefaults file, which cpp stripped
      out.  When I switched to this method of distributed resource
      files I spent several frustrating days trying to figure out why
      my clients were not finding their resources.  Xt did *NOT*
      provide any error message when it encountered the C style
      comments in the resource files, it simply, silently, aborted
      processing the resource file.

      The loss of preprocessing (which can be very handy, e.g. ``#ifdef
      COLOR'' ...) is enough to cause some people to dismiss this
      method of resource management.

    - You may also run into some clients which break the rules.  For
      example, neither Emacs (18.58.3) nor Xvt (1.0) will find their
      resources if they are anywhere other than in .Xdefaults.

    - when starting up a client on a machine that does not share files
      with the machine where your resources are stored, your client
      will not find its resources.  Loading all your resources into the
      server will guarantee that all of your clients will always find
      their resources.            Casey Leedom (casey@gauss.llnl.gov)

  A possible compromise suggestion that I have (and am planning on trying)
  is to put resources for all my heavily used clients (eg: xterm) into my
  .Xdefaults file, and to use the "separate resources files" method for
  clients that I seldom use.

Define Your Display Properly
- - - - - - - - - - - - - - -

  Client programs are often executed on the same machine as the server.  In
  that situation, rather than setting your DISPLAY environment variable to
  "<hostname>:0.0", where <hostname> is the name of your workstation, you
  should set your DISPLAY variable to "unix:0.0" or ":0.0".  By doing this
  you access optimized routines that know that the server is on the same
  machine and use a shared memory method of transferring requests.
			[thanks to Patrick J Horgan (pjh70@ras.amdahl.com)]

  See the _DISPLAY NAMES_ section of the X(1) man page for further
  explanation of how to properly set your display name.

  "I don't think it's stock MIT, but (at least) Data General and HP have
  libraries that are smart enough to use local communication even when
  the DISPLAY isn't set specially."
			      Rob Sartin (88opensi!sartin@uunet.UU.NET)

  [Jody Goldberg (jody@algorithmics.com) sent me an Xlib patch to change
  stock R5 to use local communication even if DISPLAY is not properly set.
  I don't want to get in the business of distributing or trying to juggle
  non-MIT patches and so have elected not to include it here.  Hopefully MIT
  will apply this minor (~8 lines) patch themselves.  In the meantime, if
  you want to try it yourself, email Jody.  --ed.]

-------
Clients
-------

  If you only have a few megabytes of Ram then you should think
  carefully about the number of programs you are running.  Think also
  about the _kind_ of programs you are running.  For example:  Is there
  a smaller clock program than xclock?

  Unfortunately, I haven't really noticed that programs advertise how large
  they are, so the onus is on us to do the research and spread the word.

  [ Suggestions on better alternatives to the some of the standard clients
  (eg: Xclock, Xterm, Xbiff) are welcome.  --ed.]

  I've received some contradictory advice from people, on the subject
  of X client programs.  Some advocate the use of programs that are
  strictly Xlib based, since Xt, Xaw and other toolkits are rather
  large.  Others warn us that other applications which you are using
  may have already loaded up one or more of these shared libraries.  In
  this case, using a non-Xt (for example) client program may actually
  _increase_ the amount of RAM consumed.

  The upshot of all this seems to be: Don't mix toolkits.  That is, try
  and use just Athena clients, or just Xview clients (or just Motif
  clients, etc).  If you use more than one, then you're dragging in
  more than one toolkit library.

  Know your environment, and think carefully about which client
  programs would work best together in that environment.

		  [Thanks to: Rob Sartin (88opensi!sartin@uunet.UU.NET),
      Duncan Sinclair (sinclair@dcs.gla.ac.uk | sinclair@uk.ac.gla.dcs) ]

A Better Clock for X
- - - - - - - - - - -

1) xcuckoo
   suggested by: Duncan Sinclair (sinclair@dcs.gla.ac.uk)
   available: on export.lcs.mit.edu

   Xcuckoo displays a clock in the title bar of *another* program.
   Saves screen real estate.

2) mclock
   suggested by: der Mouse (mouse@Lightning.McRCIM.McGill.EDU)
   available: larry.mcrcim.mcgill.edu (132.206.1.1) in /X/mclock.shar

   Non Xt-based.  Extensively configurable.  it can be made to look
   very much like MIT oclock, or mostly like xclock purely by changing
   resources.

  Of course, the ultimate clock --- one that consumes no resources, and
  takes up no screen real estate --- is the one that hangs on your wall.
  :-)

A Better Terminal Emulator for X
- - - - - - - - - - - - - - - - -

  From the README file distributed with xterm:

  +-----
  |		 Abandon All Hope, Ye Who Enter Here
  |
  | This is undoubtedly the most ugly program in the distribution.
  | ...
  +-----

  Ugly maybe, but at my site it's still the most used.  I suspect that
  xterm is one of the most used clients at many, if not most sites.
  Laziness?  Isn't there a better terminal emulator available?  See below.

  If you must use xterm, you can try reducing the number of saveLines
  to reduce memory usage.  [ Oliver Jones (oj@roadrunner.pictel.com),
		   Jonny Farringdon (j.farringdon@psychol.ucl.ac.uk) ]

1) Xvt
   suggested by: Richard Hesketh (rlh2@ukc.ac.uk) :
   available: export.lcs.mit.edu in /contrib/xvt-1.0.tar.Z

   "...if you don't need all the esoteric features of xterm, then get
   hold of xvt ...  it was written here just to save swap space as
   xterm is rather a hog! "

   This was written as a partial 'clone' of xterm.  You don't have to
   rename your resources, as xvt pretends to be XTerm.  In it's current
   version, you cannot bind keys as you can in xterm.  I've heard that
   there are versions of xvt with this feature, but I've not found any
   yet.

   UPDATE (March 1993):  I recently had a few email conversations with
   Brian Warkentin (brian.warkentine@eng.sun.com) regarding xvt.  He
   questions whether xvt really is at all faster than xterm.  For
   instance, xvt may initialize slightly faster, but compare scrolling
   speed (try this quickie benchmark: /bin/time dd if=/etc/termcap
   bs=40) and see which program can scroll faster.  Also, while xterm
   may be slightly larger in RAM requirements (We don't have any hard
   numbers here, does anyone else?) shared libraries and shared text
   segments mean that xterm's paging requirements are not that major.

   As an experiment, he ripped out all the tek stuff from xterm, but it
   made little difference, since if you never use it, it never gets
   brought into memory.

   So here we stand with some conflicting reports on the validity of
   xvt over xterm.  In summary?  Caveat Emptor, your mileage may vary.
   If you can provide some hard data, I'd like to see it.
   Specifically: How much RAM each occupies, how much swap each needs,
   relative speed of each

2) mterm
   suggested by: der Mouse (mouse@Lightning.McRCIM.McGill.EDU)
   available: larry.mcrcim.mcgill.edu (132.206.1.1) in
     /X/mterm.src/mterm.ball-o-wax.

   "I also have my own terminal emulator.  Its major lack is
   scrollback, but some people like it anyway."

Tuning your client
- - - - - - - - - -

  Suggestions on how you can tune your client programs to work faster.

  From Scott Barman (scott@asd.com) comes a suggestion regarding Motif
  Text Field Widgets:

    I noticed that during data entry into Motif text field widgets, I
    was getting a slight lag in response to some keystrokes,
    particularly the initial one in the field.  Examining the what was
    going on with xscope I found it.  It seems that when the resource
    XmNblinkRate is non-zero and the focus is on a text field widget
    (or even just a text widget) the I-beam cursor will blink.
    Every time the cursor appears or disappears in those widgets, the
    widget code is making a request to the server (CopyArea).  The user
    can stop this by setting the resource XmNblinkRate to 0.  It is not
    noticeable on a 40MHz SPARC, but it does make a little difference
    on a [slower system].

  This specific suggestion can probably be applied in general to lots
  of areas.  Consider your heavily used clients, are there any minor
  embellishments that can be turned off and thereby save on Server
  requests?

-------------------------
Miscellaneous Suggestions
-------------------------

Pretty Pictures
- - - - - - - -
  Don't use large bitmaps (GIF's, etc) as root window backgrounds.

  - The more complicated your root window bitmap, the slower the server
    is at redrawing your screen when you reposition windows (or redraw, etc)

  - These take up RAM, and CPU power.  I work on a Sun SPARC and I'm
    conscious of performance issues, I can't comprehend it when I see
    people with a 4mb Sun 3/60 running xphoon as their root window.

    I'll let someone else figure out how much RAM would be occupied by
    having a full screen root image on a colour workstation.

  - If you're anything like me, you need all the screen real estate
    that you can get for clients, and so rarely see the root window anyway.

		      [ Thanks to Qiang Alex Zhao (azhao@cs.arizona.edu)
			for reminding me of this one. --ed.]

A Quicker Mouse
- - - - - - - -
  Using xset, you can adjust how fast your pointer moves on the screen
  when you move your mouse.  I use "xset m 3 10" in my .xinitrc file,
  which lets me send my pointer across the screen with just a flick of
  the wrist.  See the xset man page for further ideas and information.

  Hint: sometimes you may want to *slow down* your mouse tracking for
  fine work.  To cover my options, I have placed a number of different
  mouse setting commands into a menu in my window manager.

  e.g. (for twm) :
      menu "mouse settings" {
        "Mouse Settings:"			f.title
	"  Very Fast"				! "xset m 7 10 &"
	"  Normal (Fast)"			! "xset m 3 10 &"
	"  System Default (Un-Accelerated)"	! "xset m default &"
	"  Glacial"				! "xset m 0 10 &"
      }

Programming Thoughts
- - - - - - - - - - -
  Joe English (joe@trystero.art.com) :
    To speed up applications that you're developing, there are tons of
    things you can do.  Some that stick out:

    - For Motif programs, don't set XmFontList resources for individual
      buttons, labels, lists, et. al.; use the defaultFontList or
      labelFontList or whatever resource of the highest-level manager
      widget.  Again, stick to as few fonts as possible.

    - Better yet, don't use Motif at all.  It's an absolute pig.

    - Don't create and destroy widgets on the fly.  Try to reuse them.
      (This will avoid many problems with buggy toolkits, too.)

    - Use a line width of 0 in GCs.  On some servers this makes a HUGE
      difference.

    - Compress and collapse multiple Expose events.  This can make the
      difference between a fast application and a completely unusable
      one.

  Francois Staes (frans@kiwi.uia.ac.be) :
    Just a small remark: I once heard that using a better malloc
    function would greatly increase performance of Xt based
    applications since they use malloc heavily. They suggested trying
    out the GNUY malloc, but I didn't find the time yet. I did some
    tests on small programs just doing malloc and free, and the
    differences were indeed very noticeable ( somewhat 5 times faster)

  [ Any confirmation on this from anyone?  --ed.]

  Andre' Beck (Andre_Beck@IRS.Inf.TU-Dresden.de) :

  - Unnecessary NoExpose Events.

    Most people use XCopyArea/XCopyPlane as fastest blit routines, but
    they forget to reset graphics_exposures in the GC used for the
    blits. This will cause a NoExpose Event every blit, that, in most
    cases, only puts load onto the connection and forces the client to
    run through it's event-loop again and again.

  - Thousands of XChangeGC requests.

    This "Gfx Context Switching" is also seen in most handcoded X-Apps,
    where only one or few GCs are created and then heavily changed
    again and again.  Xt uses a definitely better mechanism, by caching
    and sharing a lot of GCs with all needed parameters. This will
    remove the load of subsequent XChangeGC requests from the
    connection (by moving it toward the client startup phase).

Say What!?
- - - - - -
  Some contributors proposed ideas that seem right off the wall at first:

  David B. Lewis (by day: dbl@osf.org, by night: david%craft@uunet.uu.net) :
    How about this: swap displays with someone else. Run all your programs
    on the other machine and display locally; the other user runs off your
    machine onto the other display. Goal: reduce context switches in the
    same operation between client and server.

  I'm not in a situation where I can easily try this, but I have received
  the following confirmation...

  Michael Salmon (Michael.Salmon@eos.ericsson.se):
    I regularly run programs on other machines and I notice a big
    difference. I try to run on a machine where I will reduce net usage
    and usually with nice to reduce the impact of my intrusion. This
    helps a lot on my poor little SS1+ with only 16 MB, it was
    essential when I only had 8 MB.

  Casey Leedom (casey@gauss.llnl.gov) :
    [The X11 Server and the client are] competing for the same CPU as
    your server when you run it on the same machine.  Not really a
    major problem, except that the X11 client and the server are in
    absolute synchronicity and are context thrashing.

  Timothy H Panton (thp@westhawk.uucp) :
    Firstly it relies on the fact that most CPU's are mostly idle, X's
    cpu usage is bursty.  so the chances of you and your teammate
    doing something cpu-intensive at the same time is small. If they
    are not then you get twice the cpu+memory available for your
    action.

    The second factor is that context switches are expensive, using 2
    cpu's halves them, you pay a price due to the overhead of going
    over the network, but this is offset in most cases by the improved
    buffering of a network (typically 20k vs 4k for a pipe), allowing
    even fewer context switches.

----------------------------
Other Sources of Information
----------------------------

  Volume 8 in O'Reilly's X Window System Series, ``X Window System
  Administrator's Guide'' is a book all X administrator's should read.

  Adrian Nye (adrian@ora.com):
    A lot more tips on performance are in the paper "Improving X
    Application Performance" by Chris D. Peterson and Sharon Chang, in
    Issue 3 of The X Resource.

    An earlier version of this paper appeared in the Xhibition 1992
    conference proceedings.

    This paper is absolutely essential reading for X programmers.

--------------
Author & Notes
--------------
  This list is currently maintained by Art Mulder (art@cs.ualberta.ca)

  Suggestions, corrections, or submission for inclusion in this list
  are gladly accepted.  Layout suggestions and comments (spelling
  mistak's too! :-) are also welcome.

  Currently I have listed all contributors of the various comments and
  suggestions.  If you do not want to be credited, please tell me.

  speedup-x-faq is copyright (c) 1993 by Arthur E. Mulder

  You may copy this document in whole or in part as long as you don't
  try to make money off it, or pretend that you wrote it.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -


	Then they'll probably also want to start tracking the customer
lists of people purchasing SoundBlaster and similar boards, which can
be configured with the use of some code and a modem, to act as a pretty
decent digital-encrypting telephone. It's expensive, though, and kind
of awkward. I don't know any drug lords, but I'm sure they'd favor
something tappable over something secure as long as the user interface
is nice.

	When you've got HRH Prince of Wales saying stupid things over
cordless phones, it's not hard to imagine that drug dealers, child
pornographers, commies, LISP programmers, and other threats to the
civilized world might transact incriminating business over "encrypting"
cellular phones.


For the first Move incident (no bomb, several members killed in
gunfire, circa 1978) the mayor was the very white Frank Rizzo.
For the second (bomb included) the mayor was Wilson Goode, who
is indeed black.


Thanks to all who responded to my original post.  I got the number for
Western Digital tech support and determined that I need to upgrade the
BIOS to the Super BIOS.  It will handle hard drives with up to 16 read/
write heads and up to 1024 cylinders.  The upgrade is $15, payable by
check or money order.  Send to:

	Western Digital Corporation
	Technical Support Group
	P.O. Box 19665
	Irvine, CA  92713-9665

The Super BIOS is for any WD XT hard drive controller card in the
WD1002 series.

The BIOS on my system would only handle up to 20mb drives.

The responses to my request for help follow my .sig.  Warning: It's long.

Keith

--
_____________________________
__-----____--___--__-----____	D. Keith Rice
__--__--___--__--___--__--___	University of North Texas
__--___--__--_--____--___--__	Department of Computer Science
__--___--__----_____--__--___	Denton, Texas, USA
__--___--__--_--____--_--____
__--__--___--__--___--__--___	drice@ponder.csci.unt.edu
__-----____--___--__--___--__	drice@cs.unt.edu
_____________________________

<========================== responses below ==========================>

From ravalent@mailbox.syr.edu Sat Apr  3 16:45:03 1993
Received: from mailbox.syr.EDU by ponder (5.61/1.36)
	id AA15218; Sat, 3 Apr 93 16:45:00 -0600
From: ravalent@mailbox.syr.edu (Bob Valentine)
Received: from mothra.syr.EDU by mailbox.syr.edu (4.1/CNS)
	id AA16647; Sat, 3 Apr 93 17:44:49 EST
Received: by mothra.syr.EDU (4.1/Spike-2.0)
	id AA03607; Sat, 3 Apr 93 17:43:27 EST
Date: Sat, 3 Apr 93 17:43:27 EST
Message-Id: <9304032243.AA03607@mothra.syr.EDU>
To: drice@ponder
Status: OR

To: drice@ponder.csci.unt.edu
Subject: Re: Drive/Controller Compatibility
Newsgroups: comp.sys.ibm.pc.hardware
In-Reply-To: <drice.733866833@ponder>
Organization: Syracuse University, Syracuse, NY
Cc:

     Ah, finally a question I can answer.   I mess with this older
stuff alot.   Kinda fun.  8)

     First problem I can forsee is that the ST-251 will not be
compadible with that WD card unless it has the right bios rom.

    Check the numbers on it.  It should be the only non-smt chip on
the board.  Slightly below center, and left.    The bios should read
either :     62-000042-015 or
             62-000094-0x2

     If the last 3 digits are 013, you got problems.

    Looks right.   W5 and W7 are factory jumped (with a trace) between
pins 1 and 2 to select the primary controller address.

    Looks right.

[art deleted]

      I notice you left out the S1 jumper table settings.   Those are
what control what drive the controller thinks it has.   If you have
the 62-000042-015 rom, set it like this:

              5 + +    open
              6 + +    open
              7 + +    open
              8 + +    open
              4 + +    closed
              3 + +    closed
              2 + +    open
              1 + +    open

    Note:   those are how WD runs the numbers on the jumper block.
Top to bottom.   +'s represent the jumper pins.    Pins 3,4, and 8
select the first drive setting (drive 0) and pins 1,2 and 7 select the
second drive (drive 1).

      If you have the 62-000094 rom, it's a auto-config, and I'll have
to look up how to do it... I don't have the big book right here.

      See above.  You might have problems if the S1 jumpers are not
right.   Also,  at the risk of being insulting, make sure the cables
are on right and good. 8).    On the jumper on the 251, try moving it
to the opposite side of the drive.    It's one or the other.
     The narrow data cable goes to J2.   I've thrown it on J3 a few
times and banged my head for a day.....

     Dunno.    IBM roms had to be later than 10/27/82.   A quick way
to check is to boot dos and run debug.   Enter:

        -d f000:fff5 fffc    (the - is the debug prompt)

    This will return the rom date, if it's of any use.

      If I oversimplified any of the above, I appologize.     It's
just hard to know what caliber of person I'm talking to. 8).

                     -->   Bob Valentine  <--
                  --> ravalent@mailbox.syr.edu <--

From chpp@unitrix.utr.ac.za Mon Apr  5 06:33:46 1993
Received: from unitrix.utr.ac.za by ponder (5.61/1.36)
	id AA16194; Mon, 5 Apr 93 06:32:59 -0500
Received: by unitrix.utr.ac.za (Smail3.1.28.1 #1)
	id m0nfpMA-0001X7C; Mon, 5 Apr 93 13:28 GMT
Message-Id: <m0nfpMA-0001X7C@unitrix.utr.ac.za>
From: chpp@unitrix.utr.ac.za (Prof P. Piacenza)
Subject: ST251
To: drice@ponder
Date: Mon, 5 Apr 1993 13:28:49 +0200 (GMT)
X-Mailer: ELM [version 2.4 PL11]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 24559
Status: OR

If you are using a TWISTED 34-way cable then move the jumper
on your drive to the neighbouring pins   :8::::::.  Make sure that
the twisted cable is for a hard disk (and not a floppy disk) - the
coloured stripe (pin 1) should be furthest from the twist.

This may also help.

                             PRODUCTS FOR XT SYSTEMS

     HARD DISK CONTROLLERS FOR MFM HARD DISK DRIVES
                                  Reference NOTE 1.

          WD1002A-WX1, feature F300R - Half-slot size hard disk controller
          card with an ST506/ST412 interface.  It supports 2 MFM drives
          with up to 16 heads and 1024 cylinders and is jumper
          configurable for secondary addressing and default drive tables.
          Built in ROM BIOS supports non-standard drive types, virtual
          drive formatting, dual drive operation, bad track formatting and
          dynamic formatting.  This board features a power connector for
          filecard applications and it will also operate in AT systems.
          Please note that this controller card will be unavailable from
          the manufacturer (Western Digital) after March, 1989.  Reference
          NOTE 2.

          WDXT-GEN, feature F300R - Half-slot size hard disk controller
          card with an ST506/ST412 interface.  It  supports 2 MFM hard
          disk drives with up to 8 heads and 1024 cylinders.  Built-in ROM
          BIOS supports non-standard drive types, virtual drive
          formatting, dual drive operation, bad track formatting and
          dynamic formatting.  Please note that this controller card will
          be unavailable from the manufacturer (Western Digital) after
          March, 1989.

          WD1004A-WX1, feature F300R - Half-slot size disk controller
          card  with an ST506/ST412 interface.  It supports 2 MFM drives
          with up to 16 heads and 1024 cylinders and is jumper
          configurable for secondary addressing and default drive tables.
          Built in ROM BIOS supports non-standard drive types, virtual
          drive formatting, dual drive operation, bad track formatting and
          dynamic formatting.  This board features a power connector for
          filecard applications and it will also operate in AT systems.
          Reference NOTE 2.

          WDXT-GEN2, feature F300R - Half-slot size hard disk controller
          card with an ST506/ST412 interface.  It supports 2 MFM hard disk
          drives with up to 8 heads and 1024 cylinders.  Built-in ROM BIOS
          supports non-standard drive types, virtual drive formatting,
          dual drive operation, bad track formatting and dynamic
          formatting.  Reference NOTE 2.

     HARD DISK CONTROLLERS FOR RLL HARD DISK DRIVES
                                  Reference NOTE 2.

          WD1002-27X, feature F301R - Half-slot size hard disk controller
          card with an ST506/ST412 interface.  It supports 2 RLL hard disk
          drives with up to 16 heads and 1024 cylinders and is jumper
          configurable for secondary addressing and default drive tables.
          Built in ROM BIOS supports non-standard drive types, virtual
          drive formatting, dual drive operation, bad track formatting and
          dynamic formatting.  This board features a power connector for
          filecard applications and it will also operate in AT systems.
          Please note that this controller card will be unavailable from
          the manufacturer (Western Digital) after March, 1989.  Reference
          NOTE 2.

          WD1002A-27X, feature 300R - Half-slot size hard disk controller
          with an ST506/ST412 interface.  It supports 2 RLL drives with up
          to 16 heads and 1024 cylinders. Built-in ROM BIOS supports non-
          standard drive types, virtual drive formatting, bad track
          formatting and dynamic formatting.  Please note that this
          controller card will be unavailable from the manufacturer
          (Western Digital) after March, 1989.

          WD1004-27X, feature F301R - Half-slot size hard disk controller
          card with an ST506/ST412 interface.  It supports 2 RLL hard
          disk drives with up to 16 heads and 1024 cylinders and is jumper
          configurable for secondary addressing and default drive tables.
          Built in ROM BIOS supports non-standard drive types, virtual
          drive formatting, dual drive operation, bad track formatting
          and dynamic formatting.  This board features a power connection
          for filecard applications and it will also operate in AT
          systems.  Reference NOTE 2.

          WD1004A-27X, feature F300R - Half-slot size hard disk
          controller  with an ST506/ST412 interface.  It supports 2 RLL
          drives with up to 16 heads and 1024 cylinders.  Built-in ROM
          BIOS supports non-standard drive types, virtual drive
          formatting, bad track formatting and dynamic formatting.

          NOTE 1:  AT&T 6300 - The AT&T 6300 and the AT&T 6300 PLUS
          contain system BIOS chips that support the hard disk drive.
          When using a Western Digital XT controller card the system will
          not "boot."  To solve this problem, one of the ROM BIOS chips
          must be disabled.  To disable the BIOS on your Western Digital
          XT controller card, you must remove the jumper at position W-3
          or add a jumper at position R-23 (depending on which model of XT
          controller you are using).

                                       -2-

          NOTE 2:  TANDY 1000 SYSTEMS - The WD1002A-WX1, WD1004A-WX1,
          WDXT-GEN2 and the WD1004-27X can be modified to operate in
          Tandy 1000 series computers, models SX, TX and the original or
          "A" version.  These computers utilize an interrupt of 2 (IRQ2)
          instead of IRQ5, the IBM standard.  To modify the WD1002A-WX1 or
          the WD1002-27X to operate in these systems, you must cut the
          etch between pin 1 and pin 2 at jumper position W-7.  Then
          solder pin 2 and pin 3 at the position (W-7).  To complete the
          modification, a jumper must be added to position 7 of switch S-1
          (2 rows of 8 pins).  PLEASE NOTE THAT ANY PHYSICAL MODIFICATION
          TO YOUR WESTERN DIGITAL HARD DISK CONTROLLER VOIDS THE WARRANTY
          ON YOUR BOARD.  To modify the WD1004A-WX1, WDXT-GEN2 or the
          WD1004-27X for your Tandy 1000 system, a zero ohm resister must
          be soldered to jumper position W-27.  This will change the
          interrupt from IRQ5 to IRQ2.

     XT CONTROLLERS FOR FLOPPY DISK DRIVES

          WD1002A-FOX - Half-slot floppy disk controller for XT or AT
          systems.  Four versions of the board are available:
                Feature F001 supports two floppy disk drives.
                Feature F002 supports four floppy disk drives and includes
                an optional 37-pin control, data and power connector and
                an optional 4-pin power connector.
                Feature F003 supports two floppy disk drives and includes
                a ROM BIOS that will enable your system to recognize
                floppy disk drive that may not be supported by your AT
                system ROM BIOS.  The optional ROM BIOS will also allow
                this controller card to operate high density floppy disk
                drives in an XT system.
                Feature F004 supports four floppy disk drives and includes
                an optional 37-pin control, data and power connector, an
                optional 4-pin power connector and a ROM BIOS that will
                enable your system to recognize floppy disk drives that
                may not be supported by your AT system ROM BIOS.  The
                optional ROM BIOS will also allow this controller card to
                operate high density floppy disk drives in an XT system.

                                       -3-

                             PRODUCTS FOR AT SYSTEMS

     HARD DISK CONTROLLERS FOR MFM HARD DISK DRIVES - NO FLOPPY SUPPORT

          WD1003-WAH, feature F003R - Hard disk controller card with an
          ST506/ST412 interface.  It supports 2 MFM drives with up to 16
          heads and 2048 cylinders, 3:1 interleave.

          WD1003V-MM1, feature F300R - Hard disk controller card with an
          ST506/ST412 interface. It supports 2 MFM drives with up to 16
          heads and 2048 cylinders, 2:1 interleave.  The "V" boards can
          run in high speed AT systems (10 to 16 megahertz system speed).

          WD1006-WAH , feature F001R - Hard disk controller card with
          an ST506/ST412 interface.  It supports 2 MFM drives with up to
          16 heads and 2048 cylinders, 1:1 interleave.

          WD1006V-MM1, feature F300R - Hard disk controller card with an
          ST506/ST412 interface.  It supports 2 MFM drives with up to 16
          heads and 2048 cylinders, 1:1 interleave and faster data
          transfer due to "look ahead caching."  The "V" boards can run in
          high speed AT systems (10 to 16 megahertz system speed).

     HARD DISK CONTROLLERS FOR MFM HARD DISK DRIVES AND FLOPPY DISK DRIVES

          WD1003-WA2, feature F003R - Hard disk controller card with an
          ST506/ST412 interface, full AT form factor.  It supports 2 MFM
          drives with up to 16  heads and 2048 cylinders, at 3:1
          interleave and 2 floppy disk drives (360K and 1.2 MB).

          WD1003A-WA2, feature F003R - Hard disk controller card with an
          ST506/ST412 interface, full XT form factor.  It supports 2 MFM
          drives with up to 16 heads and 2048 cylinders, at 3:1 interleave
          and 2 floppy disk drives (360K and 1.2 MB).

          WD1003V-MM2, feature F300R - Hard disk controller card with an
          ST506/ST412 interface.  It supports a maximum of 2 MFM drives
          with up to 16  heads and 2048 cylinders at 2:1 interleave, and 2
          floppy disk drives (5-1/4" 360K, 1.2Mb; 3-1/2" 720K, 1.44Mb).
          The "V" boards can run in high speed AT systems, (10 to 16
          megahertz system speed).

          WD1006V-MM2, feature F300R - Hard disk controller card with an
          ST506/ST412 interface.  It supports a maximum of 2 MFM drives
          with up to 16 heads and 2048 cylinders at 1:1 interleave and
          faster data transfer due to "look ahead caching" and 2 floppy
          disk drives (5-1/4" 360K, 1.2 Mb; 3-1/2" 720K, 1.44 Mb).  The
          "V" boards can run in high speed AT systems, (10 to 16 megahertz
          system speed).

                                       -4-

     HARD DISK CONTROLLERS FOR RLL HARD DISK DRIVES - NO FLOPPY SUPPORT

          WD1003-RAH - Hard disk controller card with an ST506/ST412
          interface.  It supports 2 RLL hard disk drives with up to 16
          heads and 2048 cylinders at 3:1 interleave.

          WD1003V-SR1 - Hard disk controller card with an ST506/ST412
          interface.  It supports a maximum of 2 RLL hard disk drives with
          up to 16 heads and 2048 cylinders at 2:1 interleave. The "V"
          boards can run in high speed AT systems (10 to 16 megahertz
          system speed).
                Feature F301R includes an optional ROM BIOS that allows
                the user to define the drive's parameters.
                Feature F300R does not include the ROM BIOS and you must
                use the drive tables on your system's ROM BIOS that must
                contain the appropriate drive parameters.

          WD1006-RAH - Hard disk controller card with an ST506/ST412
          interface.  It supports a maximum of 2 RLL hard disk drives with
          up to 16 heads and 2048 cylinders, 1:1 interleave.
                Feature F001R includes an optional ROM BIOS that provides
                additional drive parameter tables.
                Feature F300R does not include the ROM BIOS and you must
                use the drive tables on your system's ROM BIOS that must
                contain the appropriate drive parameters.

          WD1006V-SR1 - Hard disk controller card with an ST506/ST412
          interface.  It supports 2 RLL hard disk drives with up to 16
          heads and 2048 cylinders, 1:1 interleave and faster data
          transfer due to "look ahead caching."  The "V" boards can run in
          high speed AT  systems (10 to 16 megahertz system speed).
                Feature F301R includes an optional ROM BIOS that allows
                the user to define the drive's parameters.
                Feature F300R does not include the ROM BIOS and you must
                use the drive tables on your system's ROM BIOS that must
                contain the appropriate drive parameters.

     HARD DISK CONTROLLERS FOR RLL HARD DISK DRIVES AND FLOPPY DISK DRIVES

          WD1003-RA2, feature F001R -  Hard disk controller card with an
          ST506/ST412 interface.  It supports a maximum of 2 RLL hard disk
          drives with up to 16  heads and 2048 cylinders, at 3:1
          interleave, and 2 floppy disk drives (5-1/4" 360K, 1.2 Mb).

                                       -5-

          WD1003V-SR2 -  Hard disk controller card with an ST506/ST412
          interface.  It supports a maximum of 2 RLL hard disk drives with
          up to 16 heads and 2048 cylinders, at 2:1 interleave, and 2
          floppy disk drives, (5-1/4" 360K, 1.2 Mb; 3-1/2" 720K, 1.44
          Mb).  The "V" boards run in high speed AT systems (10 to 16
          megahertz system speed).
                Feature F301R includes an optional ROM BIOS that allows
                the user to define the drive's parameters.
                Feature 300R does not include the ROM BIOS and you must
                use the drive tables on your system's ROM BIOS that must
                contain the appropriate drive parameters.

          WD1006V-SR2 -  Hard disk controller card with an ST506/ST412
          interface.  It supports a maximum of 2 RLL hard disk drives with
          up to 16 heads, 2048 cylinders and 2 floppy disk drives (5-1/4"
          360K, 1.2 Mb; 3-1/2" 720K, 1.44 Mb).   It also features 1:1
          interleave and faster data transfer due to  "look ahead
          caching".  The "V" boards can run in high speed AT  systems (10
          to 16 megahertz system speed).
                Feature F301R includes an optional ROM BIOS that allows
                the user to define the drive's parameters.
                Feature 300R does not include the ROM BIOS and you must
                use the drive tables on your system's ROM BIOS that must
                contain the appropriate drive parameters.

     HARD DISK CONTROLLERS FOR ESDI HARD DISK DRIVES - NO FLOPPY SUPPORT -

          WD1007A-WAH - This controller card will support up to 2 ESDI
          hard disk drives, 10 megabit per second data transfer rate and
          1:1 interleave.
                Feature F301R  includes an optional ROM BIOS with "shadow
                RAM" that will enable the controller card to interface
                with all types of ESDI drives without modifying the system
                ROM BIOS.
                Feature F300R does not include the ROM BIOS and you must
                use the drive tables on your system's ROM BIOS that must
                contain the appropriate drive parameters.

          WD1007V-SE1/ME1 - This controller card will support up to 2 ESDI
          hard disk drives, 15 megabit per second data transfer rate and
          1:1 interleave.  The "V" boards can run in high speed AT
          systems, (10 to 16 megahertz system speed).
                Feature F301R includes an optional ROM BIOS with "shadow
                RAM" that will enable the controller card to interface
                with all types of ESDI drives without modifying the system
                ROM BIOS.
                Feature F300R does not include the ROM BIOS and you must
                use the drive tables on your system's ROM BIOS that must
                contain the appropriate drive parameters.

                                       -6-

     HARD DISK CONTROLLERS FOR ESDI HARD DISK DRIVES AND FLOPPY DISK
     DRIVES

          WD1007A-WA2 - This controller card will support up to 2 ESDI
          hard disk drives, 10 megabit per second data transfer rate, 1:1
          interleave and 2 floppy disk drives (5-1/4" 360K, 1.2 Mb; 3-1/2"
          720K, 1.44 Mb).
                Feature F301R includes an optional ROM BIOS with "shadow
                RAM" that will enable the controller card to interface
                with all types of ESDI drives without modifying the system
                ROM BIOS.
                Feature F300R does not include the ROM BIOS and you must
                use the drive tables on your system's ROM BIOS that must
                contain the appropriate drive parameters.

          WD1007V-SE2/ME2 - This controller card will support up to 2 ESDI
          hard disk drives, 15 megabit per second data transfer rate, 1:1
          interleave and 2 floppy drives (5-1/4" 360K, 1.2 Mb; 3-1/2"
          720K, 1.44 Mb).  The "V" boards can run in high speed AT systems
          (10 to 12 megahertz bus speed).
                Feature F301R includes an optional ROM BIOS with "shadow
                RAM" that will enable the controller card to interface
                with all types of ESDI drives without modifying the system
                ROM BIOS.
                Feature F300R does not include the ROM BIOS and you must
                use the drive tables on your system's ROM BIOS that must
                contain the appropriate drive parameters.

          WD1007A-WA4 - This controller card will support up to 2 ESDI
          hard disk drives, 10 megabit per second data transfer rate, 1:1
          interleave and 2 floppy disk drives (5-1/4" 360K, 1.2 Mb; 3-1/2"
          720K, 1.44 Mb).  This board also has a serial port and parallel
          port.
                Feature F301R includes an optional ROM BIOS with "shadow
                RAM" that will enable the controller card to interface
                with all types of ESDI drives without modifying the system
                ROM BIOS.
                Feature F300R does not include the ROM BIOS and you must
                use the drive tables on your system's ROM BIOS that must
                contain the appropriate drive parameter.

                                       -7-

     HARD DISK CONTROLLERS FOR SCSI HARD DISK DRIVES

          7000-ASC - A SCSI host adapter that serves as an interface
          between the AT bus and the SCSI bus.  All necessary drivers and
          receivers are included, permitting direct cable connections to
          the SCSI bus through a 50 pin connector and to the AT bus
          through two edge connectors.  The 7000-ASC utilizes jumper
          configurable options that enable the address space, DMA channels
          and interrupt requests to be selected to suit the end user's
          application.  The board also features word data transfer at 4
          megabytes per second (synchronous), an on-board floppy disk
          controller and a ROM BIOS.  Please note that the 7000-ASC
          operates using standard DOS 3.2 or DOS 3.3 only.

          7000-FASST2 - This SCSI host adapter card provides the same
          features as the 7000-ASC plus additional support capabilities
          using software developed by Columbia Data Products.  The 7000-
          FASST2 will support MS-DOS 3.2-3.3, Compaq DOS 3.31, PC-DOS 4.0,
          PC-MOS/386 version 2.1, XENIX, Microsoft Windows, Novell and
          Sytos tape backup.

          WDATXT-FASST KIT - An "unintelligent" SCSI host adapter that is
          compatible with the IBM XT, AT and compatible systems.  It uses
          a 50 pin external SCSI bus "D" connector with a standard 50 pin
          internal SCSI cable.  The WDATXT-FASST can be used as  both a
          target and an initiator and it serves as an excellent tool for
          SCSI designers.  It also provides a low cost alternative for end-
          users desiring to install a SCSI peripheral device such as a
          hard disk drive or a tape backup unit. The kit includes an 8-bit
          SCSI HBA board, manual, FASST software diskettes and an internal
          SCSI cable.

          SYTOS TAPE BACKUP - (Utility for 7000-FASST) - FASST-SYTOS -
          FASST version of Sytos tape backup utilities.  MS-DOS
          compatible, it runs with FASST software products Revision 3.3+.

     HARD DISK CONTROLLERS FOR PS/2 MODEL 50, 60, 80 SYSTEMS
     (MICROCHANNEL ARCHITECTURE)

          WD1006V-MC1, feature F300R - Hard disk controller with an
          ST506/ST412 interface for microchannel systems.  It supports 2
          MFM drives with up to 16 heads and 2048 cylinders, 1:1
          interleave and faster data transfer due to "look ahead
          caching."  The"V" boards can run in high speed AT systems (10 to
          16 megahertz system speed).

                                       -8-

          WD1007V-MC1, feature F300R - This controller card will support
          up to 2 ESDI hard disk drives, 15 megabit per second transfer
          rate and it contains a ROM BIOS with "shadow RAM" that will
          enable the controller card to interface with all types of ESDI
          hard disk drives without modifying the system BIOS.  It uses 1:1
          interleave.  The "V" boards can run in high speed AT systems,
          (10 to 12 megahertz bus speed).

     CONTROLLERS FOR FLOPPY DISK DRIVES ONLY

          WD1002A-FOX - Half-slot floppy disk controller for XT or AT
          systems.  Four versions of the board are available:
                Feature F001 supports two floppy disk drives.
                Feature F002 supports four floppy disk drives and includes
                an optional 37-pin control, data and power connector and
                an optional 4-pin power connector.
                Feature F003 supports two floppy disk drives and includes
                a ROM BIOS that will enable your system to recognize
                floppy disk drives that may not be supported by your AT
                system ROM BIOS.  The optional ROM BIOS will also allow
                this controller card to operate high density floppy disk
                drives in an XT system.
                Feature F004 supports four floppy disk drives and includes
                an optional 37-pin control, data and power connector, an
                optional 4-pin power connector and a ROM BIOS that will
                enable your system to recognize floppy disk drives that
                may not be supported by your AT system ROM BIOS.  The
                optional ROM BIOS will also allow this controller card to
                operate high density floppy disk drives in an XT system.

--
    Prof. L. Piacenza - Chemistry Department - University of Transkei
    Internet: chpp@unitrix.utr.ac.za  (preferred).  Tel. 27-471-3022384
    Internet: sppp@hippo.ru.ac.za

From necis!mydual.uucp!olson@transfer.stratus.com Mon Apr  5 12:14:06 1993
Received: from transfer.stratus.com by ponder (5.61/1.36)
	id AA29202; Mon, 5 Apr 93 12:14:03 -0500
Received: from necis.UUCP by transfer.stratus.com (4.1/3.12-jjm)
	id AA22183; Mon, 5 Apr 93 13:12:04 EDT
Received: from mydual by necis.necis.ma.nec.com id aa21760; 5 Apr 93 12:50 EDT
Received: by mydual.UUCP (5.58/smail2.5/09-28-87)
	id AA18009; Mon, 5 Apr 93 13:24:23 EST
Date: Mon, 5 Apr 93 13:24:23 EST
From: "Kirtland H. Olson" <mydual!olson@transfer.stratus.com>
Message-Id: <9304051824.AA18009@mydual.UUCP>
To: drice@ponder
Subject: Re: Drive/Controller Compatibility
Newsgroups: comp.sys.ibm.pc.hardware
In-Reply-To: <drice.733866833@ponder>
Organization: The Harvard Group, 01451-0667
Reply-To: necis!olson%mydual.uucp@transfer.stratus.com
Cc:
Status: OR

Suggest you move jumper on drive rightward one position.

Regards,

      --Kirt


(stuff deleted)

The value of these workshops aside, you ought to be able to buy full copies
of all this software through your campus bookstore or software distributor
at these rates.  I'm not aware that the educational version of Word or Excel
is doped down in any way.


Anyone who worries about his own gun should not have one.  If you carry
any pistol with a empty chamber and safety the chances of it going off
are about zero.  Unless you sit it on top of a lite stove for a couple
of minutes or put it in a fire. :-)


It sounds like you got the cam timing off..........


...

	Before or after his kids were shot?

	Then why make the comment?

	As did the Jews against the Nazis in WW II:  do what I say or die.

	ALl humans, I hope.

	Or perhaps they have:  kill first, blame the dead ones,
	destroy all the evidence.


1. You need these resources :
	XTerm*EightBitInput:    true
	XTerm*EightBitOutput:    true

2. In the shell you need to do :
        stty cs8 -istrip

Good luck .
Victor .


Ever heard of something called the placebo effect? I think Dyer is
reacting because it looks to be yet another case of the same old
quackery over and over again.

It true that current medical knowledge is limited, but do you realize
just HOW MANY quacks exist eager to suck your $$$$. It's playing the
lottery at best.

If the results you got were so clear and obvious, would you mind
trying a little experiment to see if it is true? It would be quite
simple. Have sugar pills and have real pills.  Take one set for one
week and the other set for another week without knowing which ones are
the real pills. Then at the end of the 2 weeks compare the results.
Let's say you're wife would know which are the real ones. If what you
are experiencing is true there should be a marked difference between
each week.

john


You're assuming that "go solar" = "photovoltaic".  Solar dynamic power
(turbo-alternators) doesn't have this problem.  It also has rather less
air drag due to its higher efficiency, which is a non-trivial win for big
solar plants at low altitude.

Now, you might have to replace the *rest* of the electronics fairly often,
unless you invest substantial amounts of mass in shielding.

References?  Such treaties have been *proposed*, but as far as I know,
none of them has ever been negotiated or signed.


:  How about Kirlian imaging ? I believe the FAQ for sci.skeptics (sp?)
:  has a nice write-up on this. They would certainly be most supportive
:  on helping you to build such a device and connect to a 120Kvolt
:  supply so that you can take a serious look at your "aura"... :-)

:  Filipe Santos
:  CERN - European Laboratory for Particle Physics
:  Switzerland

    This has to be THE only, generally accepted, method of using common
physics lab equipment to find certain answers to all the questions about
afterlifes, heavens, hells, purgatory, gods etc. Krillean photography
will probably be ignored as insignificant compared to these larger
eternal verities. Publishing your results could be a bit of a problem,
though.


Well Henry, we are often reminded how CANADA is not a part of the United States
(yet).  You could have quite a commercial A-SAT, er sky-cleaning service going
in a few years.

"Toronto SkySweepers:  Clear skies in 48 hours, or your money back."
	   Discount rates available for astro-researchers.