HDTenEightyP/NetNews huggingface dataset:
From: dlparker@dlpinc00.rn.com (David L. Parker)
Subject: Re: PC-Clone UNIX Hardware Buyer's Guide
Organization: Automated Data Management Services
Date: Fri, 14 Aug 1992 12:49:23 GMT

In article <1hQSvZ#5NQTrw8sLg8W9wJLZM5ny9ts=esr@snark.thyrsus.com> esr@snark.thyrsus.com (Eric S. Raymond) writes:
>Archive-name: pc-unix/hardware
>
>over it.  Best of all is a buddy with a state-registered dealer number; these
>aren't very hard to get and confer not just exemption from sales tax but
>(often) whopping discounts from the vendors.  Hand him a dollar afterwards to
>make it legal.
>
>(Note: I have been advised that you shouldn't try the latter tactic in
>Florida -- they are notoriously tough on "resale license" holders).
>
>	Send your feedback to: Eric Raymond = esr@snark.thyrsus.com

At least in the state of Missouri (and I'm sure many other states have similar laws
and regulations), you must pay sales tax on all items which you purchase which are
not resold to a reseller with a valid sales tax id (also referred to as a reseller
certificate, among other things).  In Missouri, you usually send in the sales tax you
have collected each quarter.  Along with that, you must send in sales tax on items
purchased for resale which you later converted to your own use, whether for business
use or personal use.  If audited, you have to be able to produce at least a valid
reseller number, or have a copy of the reseller certificate, for each entity to which
you have sold goods, but not collected sales tax.  Otherwise, you are liable for the
sales tax.  

In other words, be careful of you (those of you with sales tax ids), about allowing 
anyone to buy goods under your tax id in order to get good prices and avoid paying 
sales tax.  You could wind up paying the sales tax for your "buddys".  Tends to cut 
into the margin somewhat.

Also, even though the id wasn't tough to get, you do have to put up a bond, based on a 
percentage of projected sales.

A minor nit to pick (unless you get stuck with somebody else's sales tax bill :-) ) with an
otherwise fine article.  Thanks, Eric...

-- 
Dave Parker
Automated Data Management Services, Pleasant Hill, MO 64080-1331
(816) 987-5167/5218 voice/fax
From: galaad@broue.rot.qc.ca (Colin Surprenant)
Newsgroups: comp.unix.sysv386
Subject: lpr on ISC 3.2 & PCTCP 2.05
Date: 21 Aug 92 16:24:34 GMT
Distribution: world
Organization: Groupe de Recherche Operationnelle en Telecommunication (ROT)
X-Newsreader: Tin 1.1 PL4

I am currently trying to configure lpr on ISC SVR3.2 and DOS workstations
using PCTCP R2.05. I can't get the damn thing working...

On the UNIX side I have lp configured properly with a printer called 'laser'.
Now, I'm trying to configure lpr with the /etc/printcap file. One way I have
lpr working localy only is like that:

lp|TI laser:\
  :lp=/dev/lp:sd=/usr/spool/lpd/lp:

Then I try to lpr.exe from PCTCP and it complains telling me :
error from server : 47 usr/lib/lpd: host name for your address (x.x.x.x) 
unknown

(x.x.x.x) being my PC IP address. 

So, browsing through documentation I find out I have to insert my workstation
name in the file 'hosts.lpd' which I did. I tried with the name 'PC2' or with
the complete domain 'PC2.syner.net' or even with the IP... no go.

I tried to configure /etc/printcap in this other way:

lp|TI laser:\
  :lp=:rm=isc1:rp=lp:sd=/usr/spool/lpd/lp:

isc1.syner.net being my UNIX server.

Like that when I try to lpr localy, it get in the queue but nothing come out
and when I issue a lpq to look at the queue, it give me this message:
ISC1: waiting for queue to be enabled on isc1

But the queue is enabled when I look at the status using lpc.

HELP!
-------------------------------------------------------------------------------
galaad@rot.qc.ca     | Colin Surprenant
                     |
IP: 192.77.49.131    | ROT inc.
                     | Recherche Operationelle en Telecommunication
                     |
Voice: 514-685-7575  | Synerlogic (a Anderson Consulting Division)
Fax:   514-685-7692  | Montreal, Quebec
-------------------------------------------------------------------------------
Newsgroups: comp.unix.sysv386,comp.unix.xenix.sco,alt.sources
From: jdc@tropix.uucp (Jim Cronin)
Newsgroups: comp.unix.sysv386
Subject: RPC error on Esix 4.0.3
Date: 14 Aug 92 19:24:12 GMT
Organization: GCA/Tropel Division, Fairport, NY


Under Esix 4.0.3, logins hang during .kshrc (using korn shell).
Breaking out generates the console message:

lock-manager: RPC error; RPC  Interrupted

Is there some 'idtune' parameter that needs to be set?

Thanks...Jim
-- 
	James D. Cronin			jdc@tropel.gca.com
	GCA/Tropel Division 		{rit,uunet!gca}!tropix!jdc
	60 O'Connor Rd.   Fairport, NY 14450	
	716-388-3508	    FAX 716-377-6332
Newsgroups: comp.unix.sysv386
From: jruss@ebers.in-berlin.de (Juergen Russ)
Subject: Re: SCO: loosing characters on serial port
Organization: Private Site
Date: Wed, 19 Aug 1992 17:00:25 GMT

jochen@busybit.mrz.sub.org (Jochen Fahrner) writes:

>I have big trouble with my serial port on SCO Unix.
>It looses characters during disk-i/o. It seems, that the adaptec 1542B
>hostadapter occupies the bus too long during disk-i/o.

[...]

>N.B.
>On another system (at work) I have errors in floppy read/writes in
>conjunction with heavy disk i/o. This is probably the same problem,
>the adaptec prevents the cpu from accessing the bus.
>Probably you should not use bus master dma cards in ISA-bus systems !!!????

Some months ago I tried to transfer my tape backup system (Archive SC499
board (long board), Wangtek tape drive (60 MB)) from my 286 XENIX System
to my SCO SVR3.2v2.0 system. When I made my first tar archive apparently
all went well, but when I listed the contents of the tape, I got
"directory checksum error" after a while, that's a sign for a corrupt
header.
When I had a better look at the backup I realised that also a lot of
files had been corrupted. It turned out that in these cases a string
of about 50 to 100 bytes had been replaced by null bytes, so the
file length remained the same.
When I did heavy disk I/O in the background while taring, the frequency
of the errors was increasing tremendously, and even the file length
was changing.
At work we have also SCO Un*x with a Wangtek QIC 02-Streamer, but with
one of these new short boards. Runs without any problems.
So I thought it's a problem with this old Archive board. Just a few
days ago I've ordered a SCSI tape drive.
Oh, yes, I forgot: My host adapter is a AHA 1542B.

BTW, Jochen, you wrote, that you've patched/tuned the sio driver
and adjusted the bus on/off time of the Adaptec. How have you done
this?

Bye,
    Juergen

-- 
Berlin                    Juergen Russ                           Germany
jruss@ebers.in-berlin.de        ...!unido!fub!unlisys!desert!ebers!jruss
Newsgroups: comp.unix.sysv386
From: larry@gator.rn.com (Larry Snyder)
Subject: Re: nntp for esix
Organization: The Gator Public Access Unix Site - 219-289-3745
Date: Sat, 15 Aug 1992 14:38:09 GMT

joubert@teldata.UUCP (Joubert Berger) writes:

>Has anyone ported nntp to Esix?  If so, where can I get patches?

Esix 3.2, Esix 4.0?  

nntp comes with Dell SVR4 and I assume would run under ESIX SVR4
as well

-- 
Larry Snyder                                    internet: larry@gator.rn.com
Gator Communications                              uucp: ..!uunet!gator!larry
From: preston@nic.cerf.net (Preston L. Bannister)
Newsgroups: comp.unix.sysv386
Subject: Re: PC-clone UNIX Software Buyer's Guide
Date: 15 Aug 92 19:46:14 GMT
Organization: CERFnet

In article <1hQSr7#4j0mn690sxx39LFgDX47gPx5=esr@snark.thyrsus.comPeter> esr@snark.thyrsus.com (Eric S. Raymond) writes:

> You say you want cutting-edge hacking tools without having to mortgage the
> wife'n'kids?

In article <id.LQCS.QG4@ferranti.comPeter> peter@ferranti.com (Peter da Silva) writes:

>Nope.

>Other people have flamed enough about the presentation of this information.
>I'd like to gripe about the information itself. Eric's the sort of guy who,
>were he a car nut, would be buying a new car every other year and customize
>it to death.

>I'd like to put in a word for the people who, if they were car nuts, would be
>working on keeping their old car running well. Or who aren't car nuts at all,
>but just want reliable transportation. That, after all, is where the money is.

>And here's my request for Eric: more older systems listed in the Guide. You
>say you can be a powerful advocate for the net... well let's see you be a
>powerful advocate for the little guys on it as well. If support for folks
>with '87 chevys as well as people with '92 vettes gets rewarded with good
>publicity, maybe your vette will still be drivable in '97.

Peter has a good point about backwards compatibility and support, but
as Eric's rhetorical questions suggests, that is not the focus of the FAQ.

In fact, I think Peter has just volunteered to write the FAQ covering 
the compatibility and support issue.  :-)

In my case, Eric's question is right on the mark.  So I'm not
volunteering.   :-)

-- 
Preston L. Bannister 
Upstanding Systems
preston@cerf.net
Newsgroups: comp.unix.sysv386
From: k2ph@dxis.att.com (Bob Schreibmaier)
Subject: HELP!  I goofed big time!
Organization: QRM Central, Kresgeville, PA
Date: Fri, 15 Aug 1992 02:26:54 GMT

Okay, I know I must have done something REALLY stupid... :-(

When a friend recently upgraded to USL System V/386 Release
4.whatever-they're-up-to-now, I was able to get his old
AT&T UNIX(r) System V/386, Release 3.2.3, 2-User System for
a song (okay, two songs).  I successfully booted it on my
brother's 386SX from Disk 1 of 7, so I know it worked at one
time.  Somewhere along the way I must have damaged the floppy,
because it no longer boots.

Is there any way to repair the damage?  Is there anything at
all I can do short of buying another operating system?  HELP!

Thanks in advance for any advice.

-- 
=======================================================
| Bob Schreibmaier K2PH | UUCP:     att!dxis!k2ph     |
| (a.k.a. "The QRPer")  | INTERNET: k2ph@dxis.att.com |
| Kresgeville, PA       | ICBM:     40o55'N, 75o30'W  |
=======================================================
From: dsiegel@Seagull.Tucson.AZ.US (Dave Siegel)
Newsgroups: comp.unix.sysv386
Subject: Looking for 1280x1024 solution
Keywords: IDEK ORCHID DIAMOND
Date: 15 Aug 92 10:31:29 GMT
Organization: RTD Systems and Networking, Inc.


I'm looking for a 1280x1024 solution for my 486EISA running Dell Unix v2.1 (soon
to be 2.2)  I like the looks of the Idek MF5421-a (the one that runs up to
1600x1200, and is 21").  At first I wanted to buy the ATI Ultra to go with it,
but I guess that doesn't run at 1280, so what are my options.  The only ones
that i've seen are the Orchid Fahrenheit 1280, and the Diamond Stealth (which is
just interlaced, /blech).

Has anyone had experience with either of these boards on the Idek?  Are they
decent peices of equipment?  other recommendations?

-dave
------
Dave Siegel
Computer Engineering, U of Az
dsiegel@seagull.tucson.az.us
dsiegel@biosci.arizona.edu
Newsgroups: comp.unix.sysv386
From: kreed@telesys.tnet.com (Kevin W. Reed)
Subject: Re: FAS 2.10 async driver, part 5/5
Organization: TeleSys Development Systems, Mesa AZ
Date: Tue, 18 Aug 1992 18:01:59 GMT

davidsen@ariel.crd.GE.COM (william E Davidsen) writes:

>In article <102.26574@incc.com>, jerry@incc.com (Jerry Rocteur) writes:
>| Who is the irresponsible bastard who posts large files in a non source
>| newsgroup.
>| 
>| I have to pay for my news, plus I have to pay for the US-Europe phone
>| call and I am not impressed having to pay to get this crap.
>| 
>| What is the ruling regarding posting large files like this?

>  The ruling is that when a new version of something comes along, used
>by thousands of people and contributed freely by the author, you hit
>the N key and politely say "thanks for the new version." You don't post
>flames because, like the loaves and fishes, they are going to come back
>manyfold.

What ruling makes it ok to post source code in a discussion newsgroup?

Actually, he made a valid point.  There is no reason for that source
code to be distributed in a discussion newsgroup.  It was posted 
incorrectly.  What should have been done was a message posted in the
discussion groups saying that the sources have been posted in a valid
source code newsgroup.  The crossposting was inappropriate.

I do believe that posting a message calling someone a bastard is a bit
excessive, but I can imagine my displeasure if I had to pay for a feed
across the pond and someone incorrectly posted large postings in 
the newsgroups I was subscribed to.

Whether or not the contributed software is of value doesn't make it alright
to post it in the wrong places.

>-- 
>bill davidsen, GE Corp. R&D Center; Box 8; Schenectady NY 12345
>    I admit that when I was in school I wrote COBOL. But I didn't compile.

-- 
+-------------+
|   TeleSys   | Kevin W. Reed  ------  Public *NIX Site and Newsfeed Source
| Development | kreed@tnet.com   UUCP: ...!ncar!asuvax!enuucp!telesys!kreed
|   Systems   | SCO Xenix/Unix Support       Data/UUCP/BBS: +1 602 649 9099
+-------------+
From: shih@madrone.eecs.ucdavis.edu (Alan S. Shih)
Newsgroups: comp.unix.sysv386
Subject: bin. distribution for Tex/LaTex?
Date: 16 Aug 92 07:21:34 GMT
Distribution: comp.unix.sysv386
Organization: U.C. Davis - Department of Electrical Engineering and Computer Science


Hello netlanders:

can ANYONE tell me where to find binary distributions of TeX and LaTeX
for SysvR4? I have seen it before but forget where it is.  However, I
checked with suphys.physics.su.oz.au and they only have something
called: minimal-tex-sysv4.tar.Z where it is incomplete (not even
previwer *shrug*).

Any information is greatly appreciated!!


-- 
|   ALAN SHIH  
|   UC.Davis EE dept
|   "When I realized my life is full of sh*t, it was good;
|      because I can start cleaning it UP."
From: melchers@Chico.Chemie.FU-Berlin.DE (Bernd Melchers)
Newsgroups: comp.unix.sysv386
Subject: inline _asm support for DELLs cc?
Date: 21 Aug 92 12:55:20 GMT
Organization: Free University of Berlin, Germany

Does the c compiler for DELL Unix support inline
assembler within a c program like this:

...
C-Code
...
			*left++ = *rigth;
			*rigth-- = tmp;
			}
		left += loops;
		rigth += size15;
		}
	return array;
}

#ifdef MSDOS
long int _fastcall Mips2IntelDoubleword(long int dw /* in DX:AX */)
{
	_asm
		{
		;exchange most with least significant word
		mov cx, dx
		mov dx, ax
		mov ax, cx
		;exchange most with least significant byte
		rol ax, 8
		rol dx, 8
		}
}/*Mips2IntelDoubleWord*/
...
c code
...
#endif /* MSDOS */


-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Bernd Melchers                   | melchers@chico.chemie.fu-berlin.de
Freie Universitaet Berlin        | Lieblingsessen: Pizza, aber nur
Institut fuer Kristallographie   |              selbstgemachte...
Takustr. 6                       |              und ohne Tierkadaver
D 1000 Berlin 33                 |
Earth                            |
Tel.: 0049-30-8383612            |
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Newsgroups: comp.unix.sysv386
From: drew@ophelia.cs.colorado.edu (Drew Eckhardt)
Subject: Re: PC-Clone UNIX Hardware Buyer's Guide
Organization: University of Colorado at Boulder
Date: Thu, 13 Aug 1992 23:17:42 GMT

You should probably add a few comments : 

1.  All monitors are not created equal.

If you can, buy your monitor from someplace that will let you see the 
same monitor (exact same, not the same monitor) that will be on your 
system.    

Quality varies greatly from monitor to monitor.  Personally, I've
seen Sony Trintrons that have lower quality  (in terms of convergance,
brightness, useable image size, etc) than my $300 -  purchased locally 
from a hole in the wall - 14" Samsung.

IMHO, convergance on a color monitor is largely a function of how 
much it bounced arround when it got shipped. 

2.  Supported hardware : 

Everyone supports Adaptec 154x boards.

Everyone supports Tseng ET4000 boards.

Everyone supports Western Digital 8003 ethernet boards.

Don't deviate from these unless you are SURE your Unix vendor will
support your hardware.

3.   Software

This is the hardware FAQ, but you're quoting prices for X, etc : 

BSDI has a real nice implementation of BSD, bundled with 
TCP/IP, NFS, an Xserver, all of the clients, GNU tools, full kernel
sources, etc, for $1000 including full source and binaries for everything. 

Linux - we have X11R5 and most of the GNU utilities available in
binary form, for free.  TCP/IP is in alpha test, so are SCSI and QIC-02 
tape drivers, and we have beta support for ISSO-9660 / Rock Ridge on CD ROMS.

There's also the Jolitz port of BSD.
 

	  
-- 
Microsoft is responsible for propogating the evils it calls DOS and Windows, 
IBM for AIX (appropriately called Aches by those having to administer it), but neither is as bad as AT&T.  Boycott AT&T, and let them know how you feel.
From: xmpcwsh@dp7up.com (Bill Harris)
Newsgroups: comp.unix.sysv386
Subject: Re: email address for Mark Williams Co (Coherent unix)
Date: 12 Aug 92 22:09:46 GMT
Organization: Dr Pepper Company/The Seven-Up Company, Dallas

In article <1992Aug7.221847.14550@hamblin.math.byu.edu> ocon@bert.cs.byu.edu (John S. O'Conner) writes:
>In article <gilmaas.3.0@vm.uoguelph.ca> gilmaas@vm.uoguelph.ca (Jim Maas ) writes:
>>Can anyone tell me what the email addres is for Mark Williams Co.
>>who produce the PC unix product called Coherent?
>>Thanks
>>Jim
>
>Unfortunately, I don't have the email address available right now, but I do
>now their telephone number.  Maybe they can give you some more info about
>email.  The number is 1-800-MARK WMS.  No joke.  If that number won't work
>for you, repost and I may be able to produce something for you by Monday,
>August 10.
>
>John -- ocon@bert.cs.byu.edu

The email address is:		sales@mwc.com
-- 
------------------------------------------------------------------------------
Bill Harris - MIS				xmpcwsh@dp7up.com
Dr Pepper/The Seven-Up Company			The opinions expressed are my
Dallas, Texas  					own. (emphasis on the period)
Newsgroups: comp.unix.sysv386
From: roe@Unibase.SK.CA (Roe Peterson)
Subject: Re: Anyone heard of the BocaBoard?
Organization: Unibase Telecom Ltd.
Date: Sun, 23 Aug 1992 06:18:38 GMT

roe@Unibase.SK.CA (Roe Peterson) writes:

Watch, now, as I follow up my own follow-up:

>evan@telly.on.ca (Evan Leibovitch) writes:
>>I/O addresses are assigned in blocks of 0x40 10-bit addresses based

>At first glance, I would say not.  64 I/O addresses for 8 ports would
>appear to be double the number required for a simple "lets' put
>8 16550's in a row".

Open mouth.  Insert foot.  Proceed to multiply 8 and 8 and get 32.

Sorry, folks, I'm normally more competent than this.  64 I/O addresses
is _precisely_ whats' required.

Evan:  can you send me vendor info?  We'll order one instantly and
I'll check it out.  Thanks.
From: jim@ferkel.ucsb.edu (Jim Lick)
Subject: Re: Anyone get BIND 4.8.3 to work under System V
Organization: University of California, Santa Barbara
Date: Thu, 20 Aug 1992 04:57:58 GMT

In <1992Aug19.225616.1492@tygra.Michigan.COM> jp@tygra.Michigan.COM (John
Palmer
) writes:
>Has anyone gotten BIND to work under System V UNIX (ISC)??

I just ported bind 4.8.3 to my SVR4 system a couple of days ago, as my
system does not have direct access to the internet, and the shipped named
doesn't support the forwarders and slave options.  However, due to your past
threats against me and other members of the network community, I won't give
you a copy no matter how much you beg.

                            Jim Lick		       
Work: University of California	| Play: 1236 Camino Meleno
      Santa Barbara		|       Santa Barbara, CA 93111-1007
      Dept. of Mechanical Engr. |	(805) 964-2088 voice/msg
      2311 Engr II Building     |	(805) MUD-SPY1 data
      (805) 893-4113            |       jim@tcp.com
      jim@ferkel.ucsb.edu	| This space intentionally left blank
Newsgroups: comp.unix.sysv386
From: roe@Unibase.SK.CA (Roe Peterson)
Subject: Re: SLIP Esix Sys V Rel 4.0.4
Organization: Unibase Telecom Ltd.
Date: Sat, 15 Aug 1992 18:27:53 GMT

gantzm@gantz.bowlgreen.oh.us (Michael L. Gantz) writes:

>Where can I get a working copy of SLIP for Esix SysV Rel 4.0.4?  The
>SLIP that comes with the system tends to choke with NFS and a few
>other things. 

>Anything that I can just plug and play would be well appreciated.
>Downloaded some slip code for SYSVR4 but keeps coughing on ioctl's
>with TCGETA.

I've got an implementation of SLIP for SVR4 (specifically runs on ESIX).
It includes VJ header compression.  Anon. FTP to rapfast.unibase.sk.ca,
directory pub/drivers.
Newsgroups: comp.unix.sysv386
From: kdenning@portal.hq.videocart.com (Karl Denninger)
Subject: Re: Dell SVR4: no SCSI support for Exabyte and/or CDROM?
Summary: We don't have any problems
Organization: VideOcart Inc.
Date: Fri, 21 Aug 1992 04:22:35 GMT

In article <rvdp.714299697@yam> rvdp@sow.econ.vu.nl (Ronald van der Pol) writes:
>kdenning@portal.hq.videocart.com (Karl Denninger) writes:
>
>>In article <rvdp.714220940@yam.sow.econ.vu.nl> rvdp@sow.econ.vu.nl (Ronald van der Pol) writes:
>>>
>>>It looks like Dell SVR4 (Issue 2.1) does *not* support the SCSI
>>>Exabyte 8200 and does *not* support CDROM.
>>>When using the non-rewinding device with the Exabyte we get
>>>I/O-errors. Also only 32k block writes seem to be supported.
>>>
>>That's funny, we use an Exabyte here on an Intel machine with DELL SVR4
>>issue 2.1 and it seems to work just fine..... (and we do multiple save-set
>>backups).
>
>Oops, my fault. It is when we use a *rewinding* device that we get
>I/O-errors. How about that? Do you know what PROM revision your
>Exabyte has. Ours has "firmware 2618". Do you use ufsdump/ufsrestore 
>or something else for your backups. What blocksize do you use?

We use an 8500 which works perfectly both with the rewind and non-rewind
device.

As for blocksize, I don't know -- we use cpio & mtio to do our backups,
which is what "imageb" does and uses.

--
Karl Denninger 		Inet:  kdenning@hq.videocart.com
VideOcart Inc.		Voice: (312) 987-5022

Newsgroups: comp.unix.sysv386
From: pss1@kepler.unh.edu (Paul S Secinaro)
Subject: Re: larger/higher resolution displays
Organization: University of New Hampshire  -  Durham, NH
Date: Wed, 19 Aug 1992 12:23:33 GMT

In article <Bt5rD7.1rw@mudos.ann-arbor.mi.us> mju@mudos.ann-arbor.mi.us (Marc Unangst) writes:
>In article <1992Aug17.222036.29571@crd.ge.com> davidsen@crd.ge.com (bill davidsen) writes:
>>  Now, even if you spend the money for a very fine dot pitch, you will
>>find that the human eye limits you, and you have to get very close to
>>the display to read reasonable text. 1024 on a good 15 inch display is
>>useful, but if the price were right I would go to 20.
>
>The major problem here, I think, is a basic misunderstanding.  When
>you go to 1024x768 on a 14" monitor, you're not usually trying to make
>the text smaller so you can cram more on the screen.  (Like I said,
>usually.)  Instead, you want to keep the text about the same size as
>you might use at 800x600, but have finer characters with a bigger
>character box.
>

It's also good for displaying large images in applications where you
are more interested in being able to put the whole thing on the screen
at once than you are in being able to resolve every single pixel.

On the whole, though, I'd take my 21" Idek monitor over a 14-incher
anyday :-)

Paul

-- 
Niven's Law #14:   There exist minds that think as well as you do, but
                   differently.
Niven's Corollary: The gene-tampered turkey you're talking to isn't
                   necessarily one of them.
Newsgroups: comp.unix.sysv386