HDTenEightyP/NetNews huggingface dataset:
From: jochen@busybit.mrz.lm.sub.org (Jochen Fahrner)
Newsgroups: comp.unix.sysv386
Subject: Looking for XDM with XDMCP for SCO Unix
Date: 30 Jul 92 15:26:56 GMT
Organization: Busybit's Software Labor, D-8068 Pfaffenhofen
X-Md4-Signature: 06dde731ebe2917a380f87c8030c65c5

Im looking for a xdm display manager which run on SCO Unix and has the
XDMCP protocol. I have X11R4 for SCO Unix from the german N.A.T.
company, but in this compilation XDMCP does not work. If I look at the
source code from MIT, I see that XDMCP protocol is only implemented
for BSD-Unixes, not for SysV (except HPUX).

Another problem with xdm on SCO: it doesn't set the login-user-id (SCO
special). So you cannot run at, batch and crontab.

Where can I get a fully functional xdm (X11R4) for SCO Unix ?

Jochen
-- 
Jochen Fahrner, D-8068 Pfaffenhofen, jochen@busybit.mrz.lm.sub.org
From: jfh@rpp386.lonestar.org (John F. Haugh II)
Newsgroups: comp.unix.sysv386
Subject: Re: a better login program for ISC 2.2
Date: 26 Jul 92 19:14:43 GMT
Reply-To: jfh@rpp386.cactus.org (John F. Haugh II)
Organization: River Parishes Programming, Austin, Republic of Texas

In article <1992Jul17.155444.9778@csd.brispo> p_copela@csd.brispoly.ac.uk writes:
>|> >Does anyone have the FTP  address of a login program for ISC 2.2 which
>|> notes
>|> >the hostname that the caller is coming from? the one I have doesn't.
>
>|> >ie when I do a 'last', I only obtain 'localhost' as the calling destination
>
>|> So, where is the 'last' command?  I haven't got one that I could find.
>
>I used the coherent one that was freely available written by Randy Thomas
>rthomas@ucrmath.ucr.edu
>
>the tar file if only 20 k and the compressed file smaller still,.. I'll send
>you a copy through email (It's the in the distribution tape i'm compiling
>(also it may take a bit longer than I thought to build the tape)

The Shadow Password Suite also logs the remote host name.  It isn't just
20K, so I won't be mailing it to you ;-), but you can get a copy off of
any comp.sources.misc archive server.

It does more than just "login", but you are free to ignore those parts
if you don't want them.
-- 
John F. Haugh II                   | Vida en La Republica de Tejas:
Ma Bell: (512) 251-2151            |  A Tejana woman, after spending the rent
UUCP: ...!cs.utexas.edu!rpp386!jfh |  money on the Tejas Lottery - "I can't go
Domain: jfh@rpp386.cactus.org      |  home, my husband will beat me up."
From: davidsen@ariel.crd.GE.COM (william E Davidsen)
Newsgroups: comp.unix.sysv386
Subject: Re: Dell SVR4 and Postscript ANSWER (from the NET of course)
Date: 21 Jul 92 19:34:56 GMT
Reply-To: davidsen@crd.ge.com (bill davidsen)
Organization: GE Corporate R&D Center, Schenectady NY

In article <f8cmmkp@dixie.com>, stan@dixie.com (Stan Brown) writes:

|> When I installed the PostScript+ upgrade my printing stopped working
|> instantly.  The problem was that postio expects to be able to send
|> a ^T and get: %%[ status: whatever ]%% and Level II now returns:
|> %%[ Source: serial; status: whatever ]%% so postio keeps sending
|> ^T's hoping to get something it recognizes. :-(
|> 
|> BTW support@dell.com seemed to know/understand this problem but
|> 	
|> 	Funny, no one I talked to ther seemed to know anything about
|> 	this.
|> 
|> had no workaround.  They said the next release might include a
|> Level II compatable postio program.

  Did you try the option to not send ^T? I know that sounds so obvious
that anyone would have tried it, but if Dell says they don't have a
solution maybe it doesn't work. I think it's -a, but that's from memory,
and I suggest you read the manual description one last time before using
it.
-- 
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: alan@ernest.dseg.ti.com (Alan Edmonds)
Subject: Re: SCO ODT 2.0 ranlib question
Organization: Texas Instruments, Inc. - Plano, Tx
Date: Wed, 22 Jul 1992 00:42:11 GMT

In article <92203.161449JGROVER@MAINE.MAINE.EDU> John Grover <JGROVER@MAINE.MAINE.EDU> writes:
>I have mucho makefiles that ranlib libraries. However, ranlib uses the
>xenix ar so I always get the message that it cant complete because the
>library is not in x.out form. I don't intend to ever use xenix format
>libraries. How can I tell ranlib, or the rest of the system for that
>matter, to forget xenix format?

Easy, don't use ranlib.  Under Unix (not BSD), you don't use ranlib; it
is builtin to ar.  Just remove it or rename it to ranlib.xenix, and
create a link from /bin/true to ranlib so your makefiles will still
work.
-- 
Alan Edmonds                                     Texas Instruments, Inc.
I don't speak for TI; TI doesn't speak for me    M/S 8513
Work phone: (214)575-6427                        6620 Chase Oaks Blvd.
Email: alan@ernest.dseg.ti.com                   Plano, Texas  75023
Newsgroups: comp.unix.sysv386
From: rick@rei2.uucp (Richard J. Barton)
Subject: Re: Comm problems (Sys V R4)
Date: Thu, 30 Jul 1992 15:31:04 GMT
Organization: REI

mpark@milton.u.washington.edu (Michael Park) writes:

>(Posting for a friend, who says):

>I can't seem to get the serial port set up properly.  It looks like
>the OS is one character late.  Example: Type in "date" and you see
>"dat".  Hit CR and the "e" shows up.  Another character is needed
>before you get output.  Needless-to-say, this makes for an
>aggravating interface, especially when logging in.  I blame the OS
>because the serial port works fine under DOS and SCO Sys V.

>Anyone got any ideas or tips for further diagnostic research?

	I had problems with uucp with my port set at 38400 and it was
	having problems, then stepped down to 19200, and it works just
	fine.  Telebit pointed out that some serial cards may have
	buffering/flow control problems at too high speed.  This may
	or may not be your problem, but I thought it would be useful
	information just the same.

-- 
rick
:-)
rick@rei.com [Plexus Software, A Division of Recognition Equipment Inc.]
From: menze@cs.arizona.edu (Ed Menze)
Newsgroups: comp.unix.sysv386
Subject: direct ethernet access in Dell SVR4
Date: 29 Jul 92 04:08:52 GMT
Organization: U of Arizona, CS Dept, Tucson

Last week I wrote:

| I'm using Dell Unix (SVR4) on a 386 and am trying to write a
| user-level program which can access all ethernet packets received by
| my host.  I talked to Dell technical support and they pointed me at an
| ethernet device file which they said provided such access via a
| STREAMS interface.
| 
| I haven't made much use of STREAMS before, so please let me know if
| this question itself doesn't make sense.
| 
| After reading some of the SVR4 STREAMS documentation and poking around
| some header files, I'm guessing that this ethernet device file
| probably uses the STREAMS "Data Link Provider Interface," but I can't
| find a description of this interface beyond a header file which
| defines some DLPI structures.  
|
| ...

Several people directed me to Unix International who claim they will
send me a DLPI document within a week or so.  I thank you for your
help.  But I'd like to back up for a second.

In the third paragraph of my previous message, I mention that "I'm
guessing" about the link between the ethernet device file (/dev/eth0)
and DLPI.  I haven't actually confirmed this, so before I embark on
trying to figure out the DLPI spec, I'd like to re-ask my question
more generally:

	I'm using Dell Unix (SVR4) on a 386 and am trying to write a
	user-level program which can access all (or a selected subset)
	of the ethernet packets received by my host.  How can I do
	this?
	
I.e., can someone either confirm that accessing /dev/eth0 via DLPI is
the right way to go or else point me at another possible solution?

I got a couple of responses suggesting tcpdump.  I took a look at it,
but it seems to require either the Berkeley Packet Filter or Sun's
Network Interface Tap.  Nothing in the BPF documentation would seem to
imply that it is feasible to install it in a SVR4 system.

So if anyone would care to address the above more-general question in
a SVR4/Dell Unix context, I would greatly appreciate it.

Thanks,

Ed Menze
menze@cs.arizona.edu

Newsgroups: comp.unix.sysv386
From: larry@gator.rn.com (Larry Snyder)
Subject: Re: Dell SVR$ (and Dell hardware) total lack of success on Postscript
Organization: The Gator Public Access Unix Site - 219-289-3745
Date: Thu, 30 Jul 1992 11:46:45 GMT

gram@aim1.aztec.co.za (Graham Wheeler) writes:

>Agreed. That wasn't my point. My point was that Dell should make the
>most of the fact that they are shipping the best SVR4 around, and push it
>as a product *independent* of whether the client uses use Dell hardware or
>not. Sure, we would like Dell hardware. But we already had plenty of good

I agree.  Right now the official word is "it runs on Dell hardare, if it
runs on your hardware -- fine -- but we can't say for sure that it
will"

>Anyway, as you should know, the problem is rarely with the motherboard!
>It is the intelligent terminal controllers, etc, etc, (i.e., the drivers)
>where most of the problems are likely to occur.

We jumped on the SVR4 bandwagon in May of 91 -- and at the time we had
problems with drivers and hardware.  Starting with the 2.1 release of
Dell the hardware problems went away -- partly due to the fact Digiboard
released their streams 1.0 SVR4 drivers for the CX-16

-- 
Larry Snyder                                    internet: larry@gator.rn.com
4950 Estero Blvd, Ft. Myers Beach, FL            uucp: uunet!rde!nstar!larry
From: dougm@pnet51.orb.mn.org (Doug Mcintyre)
Newsgroups: comp.unix.sysv386
Subject: adding SLIP to sVr4..
Date: 27 Jul 92 15:45:07 GMT
Organization: People-Net [pnet51], Minneapolis, MN.

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
Newsgroups: comp.unix.sysv386
From: larry@trauma.rn.com (Larry Snyder)
Subject: Re: Problem with ISC3.0+AHA1740+CDROM
Organization: Gator Conferencing Systems - 219-289-0777 - 6 lines
Date: Sun, 26 Jul 1992 14:31:45 GMT

caf@omen.UUCP (Chuck Forsberg WA7KGX) writes:

>BTW, the original DAK $200 CDROM special works fine with a
>Adaptec 1542A for accessing CDROM files with either SCO ODT 2 or
>MS Windows New Tech beta.  I didn't check its operation with the
>NT CD-player.

Who's player and controller is DAK shipping?  Do you have any
specs that you could share with us?

-- 
Larry Snyder                                    internet: larry@gator.rn.com
4950 Estero Blvd, Ft. Myers Beach, FL            uucp: uunet!rde!nstar!larry
Newsgroups: comp.unix.sysv386
From: obrienb@agora.rain.com (Byron O'brien)
Subject: Problems with SCO FoxBase+ over NFS
Organization: Open Communications Forum
Date: Thu, 30 Jul 1992 19:11:34 GMT


Just wondering if anyone else has this problem, and whether or not any
solutions/suggestions are out there...

I have two 486 machines, each running DELL SVR4 v3.0.  The home directories
for the two machines are kept on the one named viola.  The relevant line
in viola's /etc/dfs/dfstab looks like this:
	share -F nfs -o rw /home

The other machine (called cello) has this line in /etc/vfstab:
	viola:/home     -       /net/viola/home nfs     -      yes    rw,hard

The problem is this:  When a user on cello wants to run (*cringe*) SCO 
FoxBase+ to access a file in her home directory (on viola), and sets an
exclusive lock, the file cannot again be accessed, even after the FoxBase lock
is cleared and the session is ended.  Using the fuser(1M) command on viola,
we find that the file in question is being held open by viola's lockd.

HELP!  Is there a way around this problem?  Will using RFS solve it?  If there
is no solution, we'll have to revert to eash user having their home directory
on their own server. =(

Thanks in advance.

Byron.

-- 
Byron Charles O'Brien

obrienb@agora.rain.com  -or-  ...!intelhf!agora!obrienb
Newsgroups: comp.unix.sysv386
From: hobbes@den.mmc.com ()
Subject: Experiences with ISC Bell HUB6 Multiport card...
Summary: does it work with 3.0?
Originator: hobbes@spacemanspiff.den.mmc.com
Keywords: ISC, HUB6, multiport card
Organization: Denver, Colorado
Date: Mon, 27 Jul 1992 20:58:16 GMT


Does anyone have experience with the Bell HUB6 Multiport card?
Does it run with ISC 3.0?  It used to be supported directly from 
ISC (i.e. they included drivers) up throught release 2.2, but
they dropped support from 3.0.  They said some hardware that had
been dropped might continue to work with old drivers, but that
they didn't recommend it.

If it works with ISC 3.0, what driver are you using?  An earlier
ISC driver, homegrown, or 3rd party?

Is this board only good for terminals, or can one attach mice, plotters, 
modems to it as well?

Finally, does anyone know if this board will function a a multi-serial port
under DOS?  (I know this is a unix group.  I run ISC 95%+ of the time,
but Autocad wouldn't port to ISC, and I was damned if i was going to 
run SCO, so I have to occasionally run DOS. sigh)

thanx in advance
steve camp
hobbes@spacemanspiff.den.mmc.com
From: ebert@esfra.sub.org (Christian Ebert)
Newsgroups: comp.unix.sysv386
Subject: Re: SCO UNIX 3.2.4 questions
Date: 20 Jul 92 13:43:59 GMT
Organization: Ebert & Stegemann GmbH; Frankfurt/Main

In <3109@blue.cis.pitt.edu.UUCP> fmgst+@pitt.edu (Filip Gieszczykiewicz) writes:


>	Greetings. I recently upgraded (?) from a 3B2/300 to SCO Unix
>	running on a 486/33 clone. I had to do this because I wanted
>	to add more terminals to my 3B2 (I had 8 ports already) but the
>	2MB total memory limit was in the way. 

>	The transition has been smooth except for 2 points: the SCO
>	platform does not have development tools, ie. C compiler and
>	I need dBase and no one knows if it exists for SCO UNIX 3.2.4

dBase doesn't exist for SCO Unix, but a dBase clone, called foxbase.

>	First, for the dBase point. My associate wrote a bunch of
>	dBase scripts (in dBase V2) which we would love to be able to
>	use again. I realize that this requires the purchase of a
>	dBase package but I have a few questions: 1) do I need the
>	development version of dBase or is there only one version
>	for SCO unix, 2) IS THERE dBase for SCO unix?, 3) All I need
>	is dBase 2 - not any new version since my scripts are in version
>	2 - anyone have an older version they would like to sell? 
>	4) what is the price and current version of dBase for SCO unix?

I don't know the prices you have to pay, because I'm living in Germany and
the software prices here are not the sane as in the U.S.

But Foxbase for SCO Unix should handle all your requirements.

>	Now for the C compiler. Is there anyone with a similar system
>	but has the development package and has compiled a "talk"
>	program? I need a way for users to talk to each other and this
>	is not supplied with the system (odd?) 

I'm running SCO ODT, and I found a running "talk" in /usr/bin

Running custom to list the software packages I found, that "talk" and "talkd"
is part of the SCO tcpip package.



>	P.S. In general, can I use a pre-compiled binary (made on a
>	486 with same version UNIX) on my machine? 

Yes, I think so.

Best regards


Christian

-- 
----------- beware of programmers who carry screwdrivers -------------
| Christian Ebert                |  ebert@esfra.sub.org              |
| Staedelstrasse 8               |  100016.633@compuserve.com        |
| D-6000 Frankfurt 70 / Germany  |  +49 (69) 61 90 47                | 
Newsgroups: comp.unix.sysv386
From: mark@cyantic.com (Mark T. Dornfeld)
Subject: Re: Wyse 60 & curses
Organization: CYANTIC Systems
Date: Sat, 25 Jul 1992 13:07:17 GMT

In article <1992Jul25.011344.10285@bilver.uucp> bill@bilver.uucp (Bill Vermillion) writes:
>In article <1992Jul20.113320.3167@lugb.latrobe.edu.au> lhscmc@luxor.latrobe.edu.au (Craig Macbride) writes:
>>In article <1992Jul17.232342.1300@mnemosyne.cs.du.edu> gmatrang@nyx.cs.du.edu (Geoff Matrangola) writes:
>
>>Wyse60's are a pain: (Where I work uses them all the time! Groan.)
>
>You noticed that too?
>
>>We do the following:
>>- Re-program <back> and <down> arrows and <end> so they can be recognised.
>>- Make dim the default, so that bold turns normal on.
>
>
>>Conclusion:
>>Most designers of terminals are idiots who got sacked from designing things
>>that matter, so now they get to screw up terminal design instead. :-)
>
>I spent some time with the guy who designed the Link-6.  Neat terminal.
>I need to try to scrounge one up and put it through it's paces.  It
>even has hardware cut and paste between the two serial port connectors.
>
>But the Wyse arrow keys do show some simple-midness about the design :-)
>
>>(Wyse have the colour 325 out now: it emulates 98% of a Wyse 60, just to
>>make sure that a few things will fail miserably if you try to run them in
>>straight Wyse 60 mode!)
>
>What I have found very well, is a Wyse 160.  Turn it loose at high
>speed and tell it that it is a VT220-7.   
>
>On the plain 60's I've done the same as you and reprogammed the arrow
>keys to look like Vt100s'

One of the terminfo entries on SCO UNIX is named wyse60ak (ak for ANSI
keys).  The init string automatically puts the arrow keys on the wyse into
ANSI (vt100) mode.  No need to reprogram anything if you use this entry.

On the other hand, Wyse terminals have enough quirks in their native modes
to make them a pain in the butt.  I only use them emulating one of the DEC
personalities--but our customers don't.
-- 

Mark T. Dornfeld                              Voice: (416) 234-9048
CYANTIC Systems                               Facsimile: (416) 234-0477
101 Subway Crescent Suite 2103                Email: mark@cyantic.com
Xref: sparky comp.unix.sysv386:12400 comp.unix.programmer:3903 comp.unix.misc:3015
From: v043332@gandalf.stortek.com (Keith Amann)
Newsgroups: comp.unix.sysv386,comp.unix.programmer,comp.unix.misc
Subject: 3480 TAPE SCSI Device Driver
Keywords: tape device driver scsi
Date: 24 Jul 92 21:43:16 GMT
Distribution: usa
Organization: Storage Technology Corporation


I'm searching for a SCSI device driver for a 3480 style tape drive, under
Unix (preferably SCO, but anything will do).  Does such a beast exist in
the public domain?  If so, where might I find it?  If not, who sells them,
and at what cost?

Any and all information appreciated.  Please E-Mail responses.

-- 
Keith Amann, StorageTek                | My views/opinions belong to me, the 
 <Insert some snappy comment here!>    | company isn't responsible for them.
-------------------------------------------------------------------------------
Internet: v043332@stortek.com  VoiceNet: (303)673-4038  FAX-Net: (303)673-5019
Newsgroups: comp.unix.sysv386
From: steve@nuchat.sccsi.com (Steve Nuchia)
Subject: Re: Fun with uugetty (ISC)
Organization: South Coast Computing Services, Inc.  Houston
Date: Sun, 26 Jul 1992 00:47:50 GMT

In article <9207221736.AA12691@iecc.cambridge.ma.us> johnl@iecc.cambridge.ma.us (John R. Levine) writes:
>I don't understand why they still ship uugetty.  As of ISC 2.2, you don't
>need it.  You put regular old getty on /dev/ttyd00 and dial out on

The tty/acu approach works great for a single modem.  If you have
more than one you would really like to have something lock the
ports that are in use so that uucico can find the ones that aren't.

Some uucico's will error out after trying only a few lines.
-- 
Steve Nuchia      South Coast Computing Services, Inc.      (713) 661-3301
Newsgroups: comp.unix.sysv386
From: stan@dixie.com (Stan Brown)
Subject: AN ABJECT APPOLOGY TO THE NET (re Dell)
Date: Sat, 25 Jul 92 21:27:16 GMT
Organization: Dixie Communications Public Access.  The Mouth of the South.


   Recently I was a participant in what can only ne described as a
   flame war with certain people at Dell computer.

   I appears as though because of this some new *policies* are being
   put in place at Dell.  Thes new policies (offical or unoffical I'm
   not shure which) will apear to deisourage Dell personels active
   involvment (that is posting) on the Net.

   If this happean we will all suffer a loss of good support,
   inofrmation, comardeship, and general helpfulness which has been
   provided to us (the Net audience) in the past.

   The Net is an open forum for discussion, and such discussion should
   be encouraged.  Flame wars are *not* encouraged however, and i am
   sorry for having participated (perhaps instigated) one.

   If because of my actions we lose the good access to Dell that we
   have enjoyed in the past, then i must appologize for having caused
   this.  I regret deeply that jmy individual actions may result in a
   loss of usefuleness to the Netnews comunity in general.

   If in the future anyone sees a psoting from me that they think mya
   be inflamatory, I would appreciate if they would send me private
   email stating the fact, so that I can take appropriate action to
   correct my error.

   Thanks For your time,
   And again I appologize to all readers of this group for an problems
   I have cause.

   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
Newsgroups: comp.unix.sysv386,comp.os.linux
From: roell@informatik.tu-muenchen.de (Thomas Roell)
Subject: Re: Warning about Diamond Speedstar 24
Organization: Inst. fuer Informatik, Technische Univ. Muenchen, Germany
Date: Thu, 23 Jul 1992 13:31:04 GMT

>   I recently ordered a Diamond Speedstar HIColor and the manual called it
>the Diamond Speedstar 24.  Are these the same card?  If so, then they've
>changed something since the beginning of '92 because you can't get the
>dot clocks so X386 can set your monitor into modes about 640x480.
>This is because X386 1.2E reports:
>
>     25 28 0 0 0 0 0 0 13 14 0 0 0 0 0 0  (the 13 may be a 12, forgot)
>
>The report in the mode X386 database gives dot clock values for the 
>Diamond Speedstar HIColor but I'm thinking this person had an older
>card that didn't have these programmable dot clocks (VCO chip???)

Diamond has a new programmable PLL syntesizer on the newer board. The
Stealth VRAM BIOS Rev 2.0 and newer are examples of these cards. You
have to programm this chip before it will give you a new frequency
output besides those two standard clocks.

- Thomas
--
-------------------------------------------------------------------------------
Das Reh springt hoch, 				e-mail: roell@sgcs.com
das Reh springt weit,				#include <sys/pizza.h>
was soll es tun, es hat ja Zeit ...
From: fr@compu.com (Fred Rump from home)
Newsgroups: comp.unix.sysv386
Subject: Re: AN ABJECT APPOLOGY TO THE NET (re Dell)
Date: 26 Jul 92 22:51:47 GMT
Organization: CompuData Inc.

stan@dixie.com (Stan Brown) writes:


>   If in the future anyone sees a psoting from me that they think mya
>   be inflamatory, I would appreciate if they would send me private
>   email stating the fact, so that I can take appropriate action to
>   correct my error.

>Home (404) 299-2225				Atalanta Ga. (USA)
>Home (615) 894-5781				Chattoonaga TN (USA)

First of all I would suggest you read your posts before you actually send 
them. Do it several times. Check for content, grammar and spelling too. Maybe, 
when you're done, you won't want to send it any more.

These posting are read by thousands of people and there is a lot of waste in
having all those readers go thru a deciphering program instead of just the
original poster.

You might also tell us if such places as Atalanta and Chattoonaga actually 
exist or if they are simply anagrams of other cities.

Fred

PS Sorry - I just had to get this off my chest.  That sig has been bothering
me long enough now.

-- 
W. Fred Rump 	office:	   fred@COMPU.COM     'mans feet have grown/so big 
26 Warren St.   home: fred@icdi10.compu.com  that he/forgets his littleness'
Beverly, NJ. 08010                          		Don Marquis 
609-386-6846    bang:uunet!cdin-1!icdi10!fr