HDTenEightyP/NetNews huggingface dataset:
From: d10590@tanus.oz.au (Robert Chalmers)
Subject: system dump
Organization: Pro-Net Australia
Date: Wed, 22 Jul 92 07:50:12 GMT

Could someone tell me how to stop the message 'dump image in swaop area, do
you wish to save it?' from appearing each time I start up. I say yes and save
it, still there next time. I say no, and continue, still there next time. Any
idesas anyne.
Bob
_________________________________________________________________________
|Robert Chalmers. d10590@tanus.cec.edu.au. Mackay, Queensland. Australia|
|APCUG nanguo!root   (AUS)               UUCP mwcbbs!nanguo!earth  (USA)|
|---------------------* ao zhong youyi wan sui *------------------------|
|  UUCP nanguo!root  +61  79-521070 AEST:24 Hours. in:nuucp rd:uupublic |
|  MYNAME=bbsuser   ~/INFO   Australian-Pacific Coherent User Group     |
|-----------------------------------------------------------------------|
Newsgroups: comp.unix.sysv386
From: slangley@constant.demon.co.uk (Simon Langley)
Subject: adding SLIP to sVr4.. 
Distribution: world
Organization: home
Date: Tue, 28 Jul 1992 21:34:04 +0000


In article <8160@orbit.cts.com> dougm@pnet51.orb.mn.org writes:

>
>What is needed to add SLIP to sVr4? I take it I need a bootp client/server of
>some kind, and someway to add the SLIP commands into the existing TCP/IP
>implementation?
>
>UUCP: {tcnet, crash}!orbit!pnet51!dougm
>ARPA: crash!orbit!pnet51!dougm@nosc.mil
>INET: dougm@pnet51.orb.mn.org                                GENIE:> D.MCINTYRE1
>
>
It rather depends which SVR4 you have.  The AT&T code did not contain a slip
implementation so the various sellers had to write their own.  I have ESIX
and their slip is a disaster.  The Dell one seems to work fine according to
a friend.

You do need to add the slip modules to the kernel but you do not need bootp.

There are many PD slips so you could ftp several (Intel have written one) 
of these and see what the makefile does.

I must say that I tried setting up a slip link and eventually gave up.  I am
now successfully using ppp which was really quite straightforward.

     ----------------------------------------------------------------------
       Simon Langley                 email: slangley@constant.demon.co.uk
     ----------------------------------------------------------------------
From: khoadley@ib.rl.ac.uk (Kevin Hoadley)
Newsgroups: comp.unix.sysv386
Subject: TCP maximum window size under SVR4 (Esix 4.0.3)
Keywords: Networking Performance Tuning Esix TCP
Date: 28 Jul 92 16:34:47 GMT
Organization: Rutherford Appleford Laboratory

Is there any way to increase the max window size for TCP under 
SVR4 ?

Many thanks

Kevin Hoadley -- khoadley@ib.rl.ac.uk
From: donn@dellunix.dell.com
Newsgroups: comp.unix.sysv386
Date: 18 Jul 92 04:28 MDT
Subject: Re: Dell SVR$ (and Dell hardware) total
Nf-ID: #R:z5-mfvq@dixie.com:-1675831847:1992Jul18.002830.9207@dellunix.d:222509369:001:2163
Nf-From: dellunix.dell.com!donn    Jul 18 04:28:00 1992


In article <z5-mfvq@dixie.com>, stan@dixie.com (Stan Brown) writes:
|> 
|>     I have been trying to get my HP LJ11 (with Postscript+ cartridge)
|> 	to work corectly with Dell's SVR4 and Dell hardware for about 4
|> 	weeks now.  I can't get it to work relaibly by hoook or by crook
|> 	and now I can't even get the suport people to call me back on it.
|> 
|> 	Needles to say I am not a happy camper.  I have wasted entirely to
|> 	much of my time on this!  If it doesn't work why can't they just
|> 	come out and say so!  I have always in the paast had a good
|> 	relationship with these folks and even sugested to my new
|> 	employers that we standardize on Dell hardware because of the good
|> 	suport I have had in the pat, but this is *way* past being funny!
|> 
|> 	If *anyone* has this working corectly (serial port prefered) I
|> 	would *really like to know about it since the people at Dell
|> 	suport seem to be unable (or is that unwiling) to provide suport
|> 	on this one.
|> 
|> 	Geuss it's time to find out what Compaq is selling these days.
|> 
|> 	Stan
|> -- 
|> Stan Brown					    Electric Systems Inc.
|> Home (404) 299-2225				Atalanta Ga. (USA)
|> Home (615) 894-5781				Chattoonaga TN (USA)
|> Work (615) 899-1714				stan@dixie.com
|> dixie.com = Public Access UNIX in Georgia

Bull.  Dell neither makes nor sells the HP LJII (with Postscript+ cartridge),
nor did we make the cable your using... so your complaint is unjustified.
We're familiar with your problem - even in development we've heard your
whining, and frankly you're not making your case any stronger.

We use a postscript printer in our lab and it works fine... when it's all
hooked-up and set-up correctly.  So you most assuredly are not hooked-up
or set-up correctly.  AND IT'S NOT DELL'S PROBLEM that someone else's printer
and cable doesn't work with our machine/software.  We have no obligation or
commitment to make your particular (and peculiar) setup work just because
the system unit and software you bought came from Dell.  AND IN SPITE OF THAT,
WE HAVE TRIED.  Thanks a lot...  I *personally* wish you would find out what
Compaq is selling these days.
								- Donn

Newsgroups: comp.unix.sysv386
From: lls@kings.demon.co.uk (Lady Lodge Systems)
Subject: DX2 in an Altos 5000?
Organization: Lady Lodge Systems, Peterborough, England
Date: Tue, 21 Jul 1992 15:42:13 GMT


Has anyone tried putting a 25Mhz 80486DX2 in an Altos 5000? What about
putting one in a generic 25Mhz board? is it just a case of prising out
the old processor and stuffing in a new one?

Ta.

Sorry for posting a question about Altos in comp.unix.sysv386 but
there is no comp.sys.altos group - surprising really because there
must be quite a few people on the net that use Altos.

PS. No comments about changing motherboards please - we don't really
have that option with the Altos.
-- 
Regards,
        Russell
 ---------------------------------------------------------------------------
| Russell Brown          | MAIL : russell@kings.demon.co.uk                 |
| Lady Lodge Systems     | PHONE: 0832 272224 (Home/Work it's all the same) |
 ---------------------------------------------------------------------------
Newsgroups: comp.unix.sysv386
From: ignatz@chinet.chi.il.us (Dave Ihnat)
Subject: Re: >>An example of Dell's product support (Esix here I come...)
Summary: Mea Culpa
Date: Sun, 26 Jul 1992 19:01:38 GMT
Organization: Chinet - Public Access UNIX
Keywords: DELL Unix SVR4

In article <1992Jul22.210113.24810@sco.COM> staceyc@sco.COM (Stacey Campbell) writes:
>
>In article <1992Jul21.170345.19565@chinet.chi.il.us> ignatz@chinet.chi.il.us (Dave Ihnat) writes:
>>Come on, folks--drop the flames, keep it to
>                 ^^^^^^^^^^^^^^^
>>issues, and above all, don't let the polemic get to the point that Dell
>>management forbids the kind of close contact that we've been using.  They're
>>learning; if somebody does something that you consider unprofessional or
>>counter-productive, say so in unbiased and frank terms, without trying out
>>you new flamethrower.  Or they *will* become another USL or SCO...
>                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>Yipes, it is hard to play nice isn't it?  Just for the record* SCO employees
>are encouraged to make "close contact" with customers via the net, we are
>also encouraged to keep it professional, productive, unbiased and frank.

I've already been taken to task for this, and will admit that my experiences
with SCO are a couple of years old; it is time to refresh my relationship
with them vis a vis support.  (Old experiences *do* die hard.)  In fact,
I'm starting this now with a new client, so I'll withhold any statements about
SCO until I deal with the current support folks.  Again, apologies for
not updating my personal experience file before posting...

		Dave Ihnat
		ignatz@homebru.chi.il.us (preferred return address)
		ignatz@chinet.chi.il.us
From: bill@Celestial.COM
Newsgroups: comp.unix.sysv386
Date: 19 Jul 92 01:27 MDT
Subject: Re: SCO UNIX and parallel printing
Nf-ID: #R:1992Jul16.142009.11728@apricot.c:1843396357:1992Jul19.002757.13887@celestial:-1483991485:001:1274
Nf-From: celestial.com!bill    Jul 19 01:27:00 1992


In <qBR3NB3w164w@zswamp.UUCP> geoff@zswamp.UUCP (Geoffrey Welsh) writes:

:peterw@apricot.co.uk (Peter White) writes:

:> My department routinely concur with SCO in advising our sales
:> channels to avoid parallel printers

:   This workaround is unfortunate; there's a whole scad of UNIX people out 
:there who have no idea how fast their laser printers are because they insist 
:on operating them at 9600 bps serial.  Parallel has advantages in throughput, 
:especially on verbose work, like PostScript.  Sure, an Ethernet adapter would 
:be faster still, but a parallel cable is much cheaper, especially if the 
:computer doesn't already have an Ethernet card.

Given the brain-damage of the PC ``architecture'' in general, and
the fact that the SCO parallel drivers tend to drag the processor
down and occassionally corrupt VGA memory, I prefer the serial
port route freeing IRQ 7 and 5 for other devices.  I generally
run at 38.4 with an Intellicom 16K serial->parallel buffer which
gives quite acceptable performance.

Bill
-- 
INTERNET:  bill@Celestial.COM   Bill Campbell; Celestial Software
UUCP:   ...!thebes!camco!bill   6641 East Mercer Way
             uunet!camco!bill   Mercer Island, WA 98040; (206) 947-5591
SPEED COSTS MONEY -- HOW FAST DO YOU WANT TO GO?

Newsgroups: comp.unix.sysv386,comp.os.linux,comp.sys.ibm.pc.hardware
From: wlsmith@valve.heart.rri.uwo.ca (Wayne Smith)
Subject: Mis-convergence vs mis-registration (Was:What the 17" monitor reviews)
Organization: The John P. Robarts Research Institute, London, Ontario
Date: Sat, 25 Jul 1992 04:39:38 GMT

In article <1992Jul24.040047.3903@highlite.uucp> yarvin@highlite.uucp (Curtis Yarvin) writes:
>In article <1992Jul22.041743.9806@sinkhole.unf.edu> shite@sinkhole.unf.edu (Stephen Hite) writes:
>>(the Nanao 550i) and the one  I got has a tremendous problem with this
>>"rainbow effect" at 1024x768.  There's a term for it that starts with the
>>letter 'm' that I can't remember but the "look" is akin to a magnetic field
>>pattern.
>
>Misconvergence.  This is an annoying and common problem in cheap monitors;
>the convergence may be correctly-adjusted in the factory, but the slightest
>bump will throw it off.  I have the odd feeling that the quality of a
>monitor's convergence depends very closely on the quality of its packing...

I think he means mis-registration.  I notice this effect with my Viewsonic 6
with certain colors (like some background colors at 1024X768 in Windows).
Pure colors look fine, but some dithered colors show a kind of herring bone
effect.  So mis-registration will result in a fine herring-bone type pattern
when viewing areas of certain colors, and mis-convergergence results in
a ghosting of blue or red around white dots or lines.
From: davidsen@ariel.crd.GE.COM (william E Davidsen)
Newsgroups: comp.unix.sysv386
Subject: Re: CTRL-Keys under SCO Unix
Date: 24 Jul 92 20:08:01 GMT
Reply-To: davidsen@crd.ge.com (bill davidsen)
Organization: GE Corporate R&D Center, Schenectady NY

In article <1992Jul24.010608.1659@cs.mcgill.ca>, storm@cs.mcgill.ca (Horatio Gadsplatt III) writes:

| Having long used csh on SunOs, I have become very used to, and familiar with 
| keystrokes such as CTRL-Z Stopping a process and CTRL-C killing One.
| 
| However, recently, I started to use SCO Unix.  I noticed that neither 
| of these worked.

  The defaults for erase, kill, intr, and susp are not the same on SysV
as BSD. This is not related to SCO. Use stty to change them.

| Now, the system has been hacked seriously for security reasons, so something
| might have affected this.

  The system has NOT "been hacked seriously for security reasons," it
was egregiously mutilated with malice aforethought, IMHO. With the
worst ratio of added security to administrative inconvenience I could
imagine. Don't get me started on this one... 

  However, SCO did listen to their customers, and I'm happy to say
that ODT 2.0 seems to have fixed this completely. You can dial in as
little security as you need, while getting as much security as you need.

-- 
bill davidsen, GE Corp. R&D Center; Box 8; Schenectady NY 12345
	It never ceases to amaze me that otherwise rational people, able to
	understand calculus, compound interest, and the income tax form, can
	continue to believe that poker is a game of chance.
Newsgroups: comp.unix.sysv386
From: cpcahil@virtech.uucp (Conor P. Cahill)
Subject: Re: Inode help please
Keywords: inode
Organization: Virtual Technologies Inc.
Date: Thu, 30 Jul 92 12:32:44 GMT

mike@hernix.org (Mike Herman) writes:

>On ISC 386 V 3.2.2 how can I convert a given inode number to
>a filename?  fsck fails, and only gives the inode.  THANKS!

ncheck(1M) -i inode_number fsdevice

You might want to look at clri(1M) also, since that is one way to clear
a bad inode.  fsdb(1m) also comes to mind.

-- 
I guess these are the views of VTI - since it is my consulting company.

Conor P. Cahill              (703)430-9247              cpcahil@virtech.vti.com
Virtual Technologies, Inc.  46030 Manekin Plaza            Dulles, VA 20166 
Newsgroups: comp.unix.sysv386
From: staceyc@sco.COM (Stacey Campbell)
Subject: Re: >>An example of Dell's product support (Esix here I come...)
Organization: The Santa Cruz Operation, Inc.
Date: Wed, 22 Jul 1992 21:01:13 GMT
Keywords: DELL Unix SVR4


In article <1992Jul21.170345.19565@chinet.chi.il.us> ignatz@chinet.chi.il.us (Dave Ihnat) writes:
>Come on, folks--drop the flames, keep it to
                 ^^^^^^^^^^^^^^^
>issues, and above all, don't let the polemic get to the point that Dell
>management forbids the kind of close contact that we've been using.  They're
>learning; if somebody does something that you consider unprofessional or
>counter-productive, say so in unbiased and frank terms, without trying out
>you new flamethrower.  Or they *will* become another USL or SCO...
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Yipes, it is hard to play nice isn't it?  Just for the record* SCO employees
are encouraged to make "close contact" with customers via the net, we are
also encouraged to keep it professional, productive, unbiased and frank.

Even though all SCO posters are offering their personal opinion (unless
otherwise stated), speaking from a personal experience a number of years
ago it's fair to say that disclaimers are of limited use when an employee
is posting from a company machine.

Stacey

* - TM Metrolink and SGCS ;-)
-- 
     Stacey Campbell - staceyc@sco.com - {uunet,ucscc,att}!sco!staceyc
Newsgroups: comp.unix.sysv386
From: corey@cbnewsm.cb.att.com (william.c.brown)
Subject: Re: Inode help please
Organization: AT&T
Distribution: usa
Date: Wed, 29 Jul 1992 11:40:57 GMT
Summary: inode to filename
Keywords:  inode

In article <1992Jul29.003518.4778@hernix.org>, mike@hernix.org (Mike Herman) writes:
> On ISC 386 V 3.2.2 how can I convert a given inode number to
> a filename?  fsck fails, and only gives the inode.  THANKS!
> 

Try using the "ncheck" command to search for that inode and
report the filename... Works for me...



	--Corey Brown
	  AT&T NSD 
	  ALpharetta, Ga 30202

	  att!alphlk!wcb or att!attmail!wcbrown


Newsgroups: comp.unix.sysv386,comp.sys.ncr
From: root@casper.cs.uct.ac.za (The Superuser)
Subject: Anonymous ftp under NCR V.4
Organization: Computer Science Department, University of Cape Town
Date: Thu, 30 Jul 1992 19:53:33 GMT

Following the recent thread on setting up anonymous ftp under V.4 
(which unfortunately has already expired at my site), this is how
I got anonymous ftp to work under NCR V.4, which uses WIN-TCP.

BTW, thanks to those of you who posted about this - I would probably
never have got it working without your hints - I had got as far as
guessing that /dev/zero and /usr/lib/libc.so.1 should exist but was 
still missing /dev/tcp.

  ~ftp:	       dr-xr-xr-x   7 ftp      guest        512 Jul 30 21:03 .
	       dr-xr-xr-x   2 root     other        512 Jul 30 21:03 bin
	       dr-xr-xr-x   2 root     other        512 Jul 30 21:34 dev
	       dr-xr-xr-x   2 root     other        512 Jul 30 21:32 etc
	       dr-xr-xr-x   2 ftp      guest        512 Jul 30 21:30 pub
	       dr-xr-xr-x   3 root     other        512 Jul 30 21:35 usr

  ftp/bin:     ---x--x--x   1 root     other      13628 Jul 30 21:03 ls

* ftp/dev:     crw-rw-rw-   1 root     other      0, 41 Jul 30 21:02 tcp
  	       crw-rw-rw-   1 root     other      2,  4 Jul 30 21:02 zero

  ftp/etc:     -r--r--r--   1 root     other         42 Jul 30 21:05 group
	       -r--r--r--   1 root     other         91 Jul 30 21:06 passwd

* ftp/usr:     dr-xr-xr-x   2 root     other        512 Jul 30 21:30 lib

* ftp/usr/lib: -r-xr-xr-x   1 root     other     179220 Jul 30 21:14 libc.so.1

*: These files/directories are not mentioned in the manuals.
--
Sandi Donno
Computer Science, University of Cape Town
South Africa
From: davidsen@ariel.crd.GE.COM (william E Davidsen)
Newsgroups: comp.unix.sysv386
Subject: Re: DELL UNIX SysVr4 and ttydefs
Keywords: stty ttydefs svr4
Date: 24 Jul 92 19:24:12 GMT
Reply-To: davidsen@crd.ge.com (bill davidsen)
Organization: GE Corporate R&D Center, Schenectady NY

In article <stritzi.711924024@Physik.TU-Muenchen.DE>, stritzi@Physik.TU-Muenchen.DE (Peer Stritzinger) writes:
| Has anyone successfully changed the stty-settings for the console in DELL
| UNIX R4, so that the backspace key operates as DEL key?

  To change what keys generate you use a map??? program.

| stty erase ^? in the user profile works fine, but changing /etc/ttydefs
| and /etc/gettydefs has NO effect. 

  How does that effect the backspace key? It makes the DEL key the erase
(note that the docs say things about what happens when you define one
key for two different things, like erase and intr). I thing to make the
backspace key operate as the DEL key (ie do what the DEL key normall
does) you want stty intr ^H.

  And when doing whatever it is that you're trying to do (I admint it's
not clear to me) did you put the changes on the 2nd set of parameters?
The first set are used when presenting the login: message, the 2nd after
the username has been entered and login is actually called.

  It sounds like you're saying one thing and doing another...

-- 
bill davidsen, GE Corp. R&D Center; Box 8; Schenectady NY 12345
	It never ceases to amaze me that otherwise rational people, able to
	understand calculus, compound interest, and the income tax form, can
	continue to believe that poker is a game of chance.
Newsgroups: comp.unix.sysv386
From: allbery@NCoast.ORG (Brandon S. Allbery KF8NH)
Subject: Re: Destiny X Dell, Esix, Microport etc.
Reply-To: allbery@ncoast.org (Brandon S. Allbery KF8NH)
Organization: North Coast Public Access *NIX, Cleveland, OH
Date: Wed, 29 Jul 1992 00:59:48 GMT
Followup-To: comp.unix.sysv386

As quoted from <2A740945.6FC7@telly.on.ca> by evan@telly.on.ca (Evan Leibovitch):
+---------------
| I know ESIX committed early on to Solaris, but is re-evaluating the
| situation. The company does not want to plunge into both Solaris and
| R4.2, but wants to make sure it chooses what will be the best long-term
| path.  As a source licencee of Solaris, ESIX would not be restricted by
| some of the claims presently made about it (ie, distribution only on CD-ROM).
| But there appear to be many desirable features in 4.2 which Solaris
| won't have (ie, swictable Motif and OL look-and-feel).
| 
| Are there any comments on the net, based on the available knowledge,
| about the plusses and minuses of Solaris 2.0 vs. System V R4.2, from the
| viewpoint of a poptential source licensee?
+---------------

From the viewpoint of a source license?  Hard for me to say at this point.
But consider---

Solaris is intended as a high-end workstation environment.  Sun has never
claimed that Solaris was intended to compete for the low- and mid-end markets;
SVR4.2 is claimed to target both (I have my doubts --- but much hope --- about
the low end).  The two products really don't seem to overlap that much.

Which is not to say that a source licensee wouldn't be able to strip it down,
but the result would most likely be indistinguishable from SVR4.2, so why
bother with the extra effort when it's already been done for you in R4.2?

From what (admittedly little) I know about Everex/Esix's Unix clientele, I
suspect SVR4.2 would be the *much* better choice.  In fact, I'd be hard put to
locate a market for Solaris/Intel at all; the high-end folks generally don't
bother with Intel-based iron.

++Brandon
P.S.  Yes, the above means I've written off Solaris/Intel as a viable product.
-- 
Brandon S. Allbery, KF8NH [44.70.4.88]: allbery@NCoast.ORG, bsa@telotech.com
Senior Programmer, Telotech, Inc. (if I may call myself that...)
Newsgroups: comp.unix.sysv386
From: richard@xanth.b11.ingr.com (Richard Griffiths)
Subject: Re: Archive Viper 525 and Dell
Reply-To: richard@xanth.b11.ingr.com
Organization: Intergraph Corporation, Huntsville, AL
Date: Wed, 29 Jul 1992 21:36:46 GMT

In article <Bs55tB.6EI@zeus.dialix.oz.au>, peter@zeus.dialix.oz.au (Peter Wemm) writes:
|> bruno@thunder.mcrcim.mcgill.edu (Bruno Hall) writes:
|> 
|> >I am trying to get Dell SVR4 2.1 to talk to an Archive Viper 525.  
|> 
|> >Has anyone managed to do this?  
|> 
|> >At the moment, it'll write a tape file at the beginnig of a tape, and
|> >then refuse to write another after the first.  Also, the light on the
|> >drive stays on after the initial access -- until the tape is removed.
|> 
|> Whew!  For a while there, I thought I was the only person having
|> problems with the 525 on Dell.  My problems are MUCH worse than yours though,
|> I cannot even write (there's a blocksize problem somewhere..).
|> If I write with a blocksize of 20K (the blocksize is irrelevant- i have tried
|> every different one I could think of), a program I set up to debug
|> the thing says "write failed: could only write 10240 of 20480 bytes".
|> Reads are similar:  If I read 20K blocks, the read says it read 20K, but in
|> actual fact only put 10K in the buffer.  No matter the blocksize, it
|> is always out by 50%.
|> My Viper 2150S Drive works fine.
|> I have no idea why it does this, but I am getting annoyed enough to start
|> "hacking".  I have though of putting a wrapper around the st01read and
|> st01write to double and halve the block counts as appropriate - any reason
|> this wont work?
|> Also, the drive *floods* the SCSI bus *much* more than the 150 drive..
|> (Yes, I have tried all sorts of combinations of the jumpers...)
|> 
|> Anybody else seen this?
|> 
The Archive 525 I have installed on my Esix 4.04a system works great! 
(apologies to Larry and the Dellevangelists, I just couldn't resist).  
The reason it works great is I modified the driver for the folks at Esix so 
the damn thing would work.  Archive screwed up the auto density select.  
The USL scsi tape drivers check the min/max block length returned by the drive 
to decide if they are working with fixed or variable block lengths.  If you 
use anything other than a 565mb tape you can only write to it in fixed block 
mode (512 bytes, we're talking hardware level here not cpio/tar).  The Archive 
drive always returns the maximum block length the drive is capable of 
regardless of the tape media installed.  Stupid.  That means the tape driver
will assume variable block lengths when the media is incapable of it.
By the way, make sure your rom level on the Archive is at least 7.  Prior to 
that auto density did not work at all.


-- 
Richard A. Griffiths              ...uunet!ingr!b11!xanth!richard   (UUCP)
Intergraph Corp.                  richard@b11.ingr.com          (Internet)
"Something's happening here but you don't know what it is. Do you, Mr. Jones."