HDTenEightyP/NetNews huggingface dataset:
From: mknewman@blkbox (Marc Kraker Newman)
Newsgroups: biz.sco.general
Subject: Re: talk command and talkd
Keywords: talk unix sco opendesktop
Date: 13 Oct 92 12:15:08 GMT
Distribution: biz
Organization: The Black Box BBS (713) 480-2686 V32/V42bis/HST

jeffl@comix.UUCP (Jeff Liebermann) writes:

>In article <1992Oct07.014459.1626@i88.isc.com> stevea@i88.isc.com (Steve Alexander) writes:
>>In any event, this probably means that your /etc/utmp file is either corrupted
>>or unreadable.  In the version of talk supplied with TCP/IP 1.2.0, an attempt 
>>is made to look you up in the password file as well, which allows talk to work 
>>regardless of the status of /etc/utmp.

>I can't make it work either on 2 different system using
>SCO Unix 3.2v4.1.  It worked fine in tcp/ip 1.1.3 but not 1.2.0.
>The /etc/talkd is not even mentioned in /etc/tcp script
>used to start tcp.  I copied the the section which loads talkd
>from the 1.1.3 version, shutdown, and rebooted.  The listing of
>"PROCS" from the /etc/tcp script stops for an exessive amount of
>time (approx 15 sec) at talkd before continuing.  ps -ef shows
>that talkd is NOT running.  There is nothing on the SCO Support
>BBS and email to support@sco.com went unanswered.

Actually, I have gotten it to work from a non-X session.  This does not help
me much as I spend all my time in X :-(

Maybe SCO is listening and will post something here or on SOS for us.  It seems
to be a glaring anomaly.

Marc

-- 
Marc K. Newman (N5SLG)			Is UNIX pronounced 
mknewman@blkbox.com or			"UNIQUES" or
blkbox!mknewman				"EUNICHS"?
Newsgroups: biz.sco.general
From: jwassell@iat.holonet.net (John Wassell)
Subject: Disable Shell Escape in SCO Manager?
Organization: HoloNet (BBS: 510-704-1058)
Date: Thu, 15 Oct 1992 00:15:49 GMT

     Does anyone know if it's possible to disable the shell escape capability 
in the SCO Manager (by typing an exclamation point).  The answer was easy
to find in the SCO Professional and Lyrix manuals, but I couldn't find it
for the Manager.  Every once in a while, one of our users inadvertently gets
to the shell, which is extremely bad!  Thanks in advance.

Newsgroups: biz.sco.general,comp.unix.sysv386
From: tomh@wes.on.ca (Tom Haapanen)
Subject: Re: SCO Unix 3.2.2, C News and lack of inodes
Organization: Waterloo Engineering Software
Date: Thu, 15 Oct 1992 10:06:20 GMT

> Dean.Roth <Dean.Roth@mixcom.mixcom.com> writes:
>> Are you saying that 3.2r4 does NOT allow the creation of filesystem
>> with more than 64K inodes yet?!  

sef@kithrup.COM (Sean Eric Fagan) writes:
> Correct.  The SCO filesystems are still V7-type (which, despite what Larry
> Snyder wants to believe, can be a good thing in a lot of cases, but it also
> does have its limitations), which 16-bit inodes.  (The kernel doesn't have
> this limitation, just the filesystem.)

BZZZZT!  The EAFS filesystem in 3.2.4 has 32-bit inodes (and soft links),
removing the 65,536-inode limitation.

Unfortunately we're still with 3.2.2 (our Unix box is leased -- long story,
don't ask -- and SCO Unix OS+DS are part of the lease package, so I really
don't want to spend $1K Canadian to upgrade to 3.2.4 and then throw it 
away in two years).

I've now installed another 200 MB disk, though, and I happily have a new
/usr/spool2/news/comp filesystem with lots of free inodes.  :)  And I'm 
running a modified relaynews to handle two separate news filesystems...

[ \tom haapanen    "i don't even know what street canada is on" -- al capone ]
[ tomh@wes.on.ca                   "trust the programmer" -- ansi c standard ]
[ waterloo engineering software      "to thine own self be true" -- polonius ]
Newsgroups: biz.sco.general,comp.unix.sysv386
From: Dean.Roth <Dean.Roth@mixcom.mixcom.com>
Subject: Re: SCO Unix 3.2.2, C News and lack of inodes
Organization: Milwaukee Internet Xchange BBS, Milwaukee, WI U.S.A.
Distribution: usa
Date: Tue, 13 Oct 1992 23:48:36 GMT

In <1992Oct12.054702.2252@xenitec.on.ca> eah@xenitec.on.ca (Ed Hew) writes:


>Symbolic links exist on SCO UNIX 3.2v4, in EAFS filesystems.

>>I bought a new drive yesterday, I'll be getting news installed on three 200mb
>>partitions overnight and into tomorrow. We'll see if it works!!!

I have not bought the 3.2r4 upgrade yet.  I have not yet decided
to buy it or get a different version of UNIX.

Are you saying that 3.2r4 does NOT allow the creation of filesystem
with more than 64K inodes yet?!  If so, then I'll be seriously
looking at an SCO alternative because I need a filesystem with 
lots of inodes. And I don't want to play games with symbolic
links and multiple filesystems because I cannot predict how big
each "64K inode" filesystem has to be.

Dean
Newsgroups: biz.sco.general
From: Gordon Nussey <gordon@mogwah.dsto.gov.au>
Subject: HELP required with PANIC
Resent-From: mmdf@xenitec.on.ca
Submit-To: scogen@xenitec.on.ca
Organization: [resent by] The SCOGEN gateway and Propagation Society
Date: Wed, 14 Oct 1992 21:46:48 GMT
Precedence: bulk

Could some kind generous person (SysAdmin) Please HELP me...

  I am using SCO ODT 1.1 on a 486/33 and communicating to the  outside 
world via TCP/IP using an Interlan ni5210 network card.

  I have encountered Three system errors in the past 2 weeks, I don't know
if they are related, or what they actually mean, or how to fix them!!!!!


 They are:-
             1. PANIC: RFD_BBIT  (with page dump, sys halt etc)
                  (there is no register info, therefore debugging with
                   crash or _fst is almost impossible)
             2. During system bootup :- netbios reports :-
                  nb: namesvc: uderror 115, dest=00000000:00000000
                  nb: expected unitdata_ind, got type 18
                  nb: dgsvc: uderror 115, dest=00000000:00000000
                  nb: unexpected TPI primitive (18)
             3. After bootup has completed :- 
                  cpd reports :- SIOCGIFADDR Connection refused

  There is *NO* information in any of the manuals I have to cover any of the
 above problems.


Regards,

--------------------------------------------------------------------------
Gordon NUSSEY                               E-mail: gxn@dstos3.dsto.gov.au
                                                  : gxn@mogwah.dsto.gov.au
Electro Optic Seekers                       Phone : +61 8 259 7088
Aeronautical Research Laboratory            FAX   : +61 8 259 7080
DEFENCE SCIENCE AND TECHNOLOGY ORGANISATION Postal: Bld 42 Labs Area
SALISBURY                                           PO Box 1500 Salisbury
SOUTH AUSTRALIA                                     South Australia  5108
                                                    AUSTRALIA
--------------------------------------------------------------------------
From: ti@bazooka.amb.org (Ti Kan)
Newsgroups: biz.sco.general
Subject: Re: SCO Unix 3.2.2, C News and lack of inodes
Date: 16 Oct 92 07:36:37 GMT
Reply-To: ti@bazooka.UUCP (Ti Kan)
Organization: AMB Research Labs, Sunnyvale, CA.

In article <16367@mindlink.bc.ca> Frank@mindlink.bc.ca (Frank I. Reiter) writes:
>> Sean Eric Fagan writes:
>>
>> Correct.  The SCO filesystems are still V7-type (which, despite what Larry
>> Snyder wants to believe, can be a good thing in a lot of cases, but it also
>> does have its limitations), which 16-bit inodes.  (The kernel doesn't have
>> this limitation, just the filesystem.)
>
>Hmmm.  One has to wonder then, why when they recently introduced their spiffy
>new EAFS with long filenames and symlinks they did not also go to larger
>inodes?

My speculation is that they wanted to maintain compatibility between
AFS and EAFS.  The current implementation allows one to convert from
an AFS to an EAFS simply by running fsck with the proper option.
There is even a secret, undocumented option to convert an EAFS back
to an AFS (provided no long file names or symbolic names were created
in the filesystem).  I won't tell you what the option is, because it's
supposed to be undocumented, and you'd barf when you find out the option
letter anyway.

Speaking of AFS/EAFS, I have always held the opinion that SCO implemented
AFS wrong.  The design of the filesystem is fine (thanks to Counterpoint,
the company that originally developed AFS, later acquired and dismantled
by Acer), and the exemplary filesystem benchmark results bear this out.
However, I have problems with the way that grafted the AFS stuff into
S5.  You see, instead of separate S5 and AFS filesystem types, under SCO
"S5" and AFS are one and the same.  If you specify "mkfs -f S5 /dev/xxx"
You will still get an AFS.  This makes it impossible to create, say, a
real S5 filesystem on a floppy under SCO and mount that floppy on SVR4
or other System V machines.

Oh well...

-Ti
-- 
    ///  Ti Kan                vorsprung durch technik
   ///   AMB Research Laboratories, Sunnyvale, CA. USA
  ///    ti@amb.org
 //////  ...!{decwrl,synopsys,tandem,tsoft,ultra}!sgiblab!bazooka!ti
///      ...!{uunet,sun,apple,sco}!altos!bazooka!ti
From: sfrazier@eng.norstan.com
Newsgroups: biz.sco.general
Subject: Credit Card Software
Date: 11 Oct 92 00:40:00 GMT
Reply-To: Steven E Frazier <sfrazier@norstan.com>
Organization: [resent by] The SCOGEN gateway and Propagation Society
Resent-From: mmdf@xenitec.on.ca
Submit-To: scogen@xenitec.on.ca
Precedence: bulk

Does anyone know of any type of software that anyone has that will do 
credit cards for Visa or Mastercard, American Express etc.

I am looking for a package that will dialup the bank and do the same
thing as the "card swipe machines" do that you find in restarunts, 
department stores and every place that takes credit cards.

Thanks for anyone's help in this area.

Steve


-- 
Norstan Communications, Inc.        | Steven E. Frazier
8101 N. High Street Suite 100       |---------------------------------------
West Worthington, OH   43235        | Local : sfrazier
Voice 614-785-7335 Fax 614-785-7337 | Remote: sfrazier@norstan.com
From: paul@openage.COM (Paul A. Fischer, Sr UNIX Sys Consultant)
Newsgroups: biz.sco.general
Subject: MAC to SCO terminal emulator
Date: 13 Oct 92 12:02:57 GMT
Organization: [resent by] The SCOGEN gateway and Propagation Society
Resent-From: mmdf@xenitec.on.ca
Submit-To: scogen@xenitec.on.ca
Precedence: bulk

Hi All,

I have a customer with a MAC powerbook who wants to dial into his new SCO 
system.  Does anyone have any recommendations for a good terminal emulation 
package.  I'd love to see SCO ansi emulation, but I know that is rare.  Any 
help would be appreciated.

--------------------------------------------------------------------------------
Independent SCO support and service provider in the D.C. metro area.
No Incumbents in '92. Get the crooks out of office. Vote & Send a Message
Paul A. Fischer           | Open Age Inc.  | paul@openage.com
Sr. UNIX Sys. Consultant  | (301) 948-6422 | (301) 948-9644 Fax
From: sfrazier@eng.norstan.com
Newsgroups: biz.sco.general
Subject: Bar Coding within a SCO Print Spooler Interface
Date: 11 Oct 92 00:56:56 GMT
Reply-To: Steven E Frazier <sfrazier@norstan.com>
Organization: [resent by] The SCOGEN gateway and Propagation Society
Resent-From: mmdf@xenitec.on.ca
Submit-To: scogen@xenitec.on.ca
Precedence: bulk

Has anyone done or know how I could accomplish this in a SCO print spooler:

The spooler would send the following to the printer:

John Doe
123 S. Main street
Anytown, OH 43430
~83838~

When the spooler saw "~" it would run another "bar code program" that would
bar code what was between the special characters.  I am looking as to how
to do this in the interface as well as find the code to do the bar code under
unix.

I know it's out there for dos world.

Any help would be appreciated.

Steve


-- 
Norstan Communications, Inc.        | Steven E. Frazier
8101 N. High Street Suite 100       |---------------------------------------
West Worthington, OH   43235        | Local : sfrazier
Voice 614-785-7335 Fax 614-785-7337 | Remote: sfrazier@norstan.com
Newsgroups: biz.sco.general,comp.unix.sysv386
From: tomh@wes.on.ca (Tom Haapanen)
Subject: Re: SCO Unix 3.2.2, C News and lack of inodes
Organization: Waterloo Engineering Software
Date: Thu, 15 Oct 1992 21:41:20 GMT

> tomh@wes.on.ca (Tom Haapanen) writes:
>> BZZZZT!  The EAFS filesystem in 3.2.4 has 32-bit inodes (and soft links),
>> removing the 65,536-inode limitation.

sef@kithrup.COM (Sean Eric Fagan) writes:
> *sigh*
> I wrote (most of) the new code in the EAFS.

Well, I didn't.  And I didn't know that.  Sorry!  :)

> It has symbolic links, long filenames (limited to 255 characters, although
> it was designed to handle up to 266), and 16-bit inodes.  The structure of
> the directory entries is unchanged with the EAFS, except that an inode number
> of 0xffff is given the special meaning of a continuation mark.

What I was BZZZZTing was your comment that EAFS is still limited to 64K
inodes.  I'm sure I've seen claims by SCO that you can have more inodes in
an EAFS filesystem.  Is that not true?

> Please, before you go spouting off in public about what you think is
> correct, consider that the person posting might know more than you do.
> Especially when he wrote the code 8-).

Hey, didn't know that.  And unless you put it in your signature, no one else
will know that either.  :)  

[ \tom haapanen    "i don't even know what street canada is on" -- al capone ]
[ tomh@wes.on.ca                   "trust the programmer" -- ansi c standard ]
[ waterloo engineering software      "to thine own self be true" -- polonius ]
From: davidf@golem.uucp (David J. Fiander)
Subject: Re: ELM under SCO w/ MMDF?
Date: Wed, 07 Oct 1992 10:03:18 GMT

According to Jean-Pierre Radley:
>You customize ELM for mmdf with an answer to a question in the Configure
>routine. That's been the case for quite a while. All it involves is
>recognizing the ^A^A^A^A separators that mmdf wants in the spool files.

You have to be careful 'though.  When last I dealt with Elm, at
release 2.11 [PL14], there were two bugs in it that caused
problems with MMDF.  The first was the ELM assumes that System
V sites will use lock files to lock mailboxes, and that isn't
true for the first release of SCO MMDF, and may not be true for
the second.  In order to ensure that your mailbox is being
properly locked during delivery and reading, build Elm to use
lockfile style of locking and, in the mmdftailor file, set the
parameter MLCKTYPE to 'v7'.  This only works on ODT 2.0, UNIX
3.2.4, and the MMDF TLS.

The second problem has to do with the handing of blind carbon
copies:  Elm and MMDF disagree about who is supposed to handle
them.  As a result, Bcc recipients will never receive their
copy (but normal recipients still won't know about the Bcc
list).  There is no easy fix for this problem, but I think
there is a patch for Elm floating around to take care of it.

- David
Newsgroups: biz.sco.general
From: apl@world.std.com (Anthony P Lawrence)
Subject: ftp to sosco
Organization: The World Public Access UNIX, Brookline, MA
Distribution: biz
Date: Fri, 16 Oct 1992 22:10:24 GMT

This new ftp to sosco is nice to have, but logging in as
"anonymous" gives you no access to the IT scripts.

Obviously one shouldn't have access if not signed up for SOS.

But, I am signed up.

It would be a lot more covenient if I could grab the IT's I want
without tee'ing everything off to a file.



		Tony

Lawrence & Clark, Inc		(617) 762-0707	(206) 323-2864
Xenix/Unix support,etc 	 	 Boston		 Seattle
From: watson@carssdf.UUCP (- Self Empl. Sys.Integrator)
Newsgroups: biz.sco.general
Subject: Re: Credit Card Software
Date: 15 Oct 92 12:18:14 GMT
Reply-To: watson@carssdf.UUCP (John Watson -- Self Empl. Sys.Integrator)
Organization: John Watson (Self Employed System Integrator)

YES, I too would like any information, specs, etc... on the credit card
machines.  I do POS systems for customers and would like to integrate it,
but haven't gone to the clearing company for the spces.  One phone call
to a brick wall was as far as I got.

There is a lot of interest here, please post (an Email me of course).

John Watson
From: d166alab@utarlg.uta.edu (AJAY BARVE)
Newsgroups: biz.sco.general
Subject: Usenet News and ODT 2.0
Date: 7 Oct 92 17:16:00 GMT
Organization: The University of Texas at Arlington
News-Software: VAX/VMS VNEWS 1.41

I am looking for some help!  I have ODT 2.0 server system and the
development system.  I would like to be able to read news from my machine.
We have a central NNTP news server at our site so I guess my machine
would just connect to the server and act as a client so the news dont
get stored on my machine.  What I am looking for is some information
on how to go about doing this.  That is what news reader I need to get
and also what version of NNTP to get.  SCO was unable to help
me with this eventhough I am still within my 30 day free Instalation
help.  I was told that they only had usenet SLS for UUCP.

Any and all assistance will be greatly appreciated.

Ajay Barve
Dept. of Accounting
University of Texas at Arlington.
Arlington, TX 76019.

d166alab@utarlg.uta.edu
Newsgroups: biz.sco.general
From: bill@Celestial.COM (Bill Campbell)
Subject: Re: TeX/LaTeX binaries
Organization: Celestial Software, Mercer Island, WA
Distribution: usa
Date: Fri, 16 Oct 1992 15:45:28 GMT

In <1992Oct15.000139.7429@nmt.edu> borchers@nmt.edu (Brian Borchers) writes:

:Now that I've got PC running MST's SVR4 product, I'd like to get TeX
:and LaTeX up and running.  I suppose that I could compile the C versions, 
:but it would be much simpler if I could find binaries from some place.  

:The TeX FAQ lists a version of TeX for ESIX, supposedly available via
:FTP from a site vt4130.kent.edu, but my name server can't seem to 
:find that machine.  Any other suggestions?  

I too would like to see this (are you listening Stuart?).
dvi->hp would be helpful too.

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: biz.sco.general,comp.unix.sysv386
From: larry@gator.rn.com (Larry Snyder)
Subject: Re: Problems with cnews+nn6.4.16 on SCO3.2.2
Keywords: problem cnews nn 6.4.16 sco 3.2 v2 news
Organization: The Gator Conferencing System 219-289-3745 
Date: Wed, 14 Oct 1992 18:08:09 GMT

bill@Celestial.COM (Bill Campbell) writes:

>In <Bw2rzu.4x2@gator.rn.com> larry@gator.rn.com (Larry Snyder) writes:

>>I hardly consider ODT2.0 a modern day OS -- considering it's origin
>>is 3.2 regardless of any enhancements.   

>OK Larry.  Tell me exactly what it is that makes SVR4 so great.
>	-	Is it Xenix compatibility?  SCO has had that for years.

Yes, but as far as I am concerned, I don't care.  Yes, I have a few
Xenix binaries that I run, but quite honestly, the only reason I still
run them is that I haven't found reason to dig up the source and recompile
them..  There comes a point when we have to worry about the future and
not deal with the past.  Xenix was great -- it still has a lot to offer -
but what about the overhead involved with supporting an OS 5-6 years old?

>	-	Is it Berkley enhancements?  Most of them have been in
>		Xenix since 1982.  Long file names and symbolic links are
>		in SCO UNIX 3.2v4.

Long file names and symbolic links have been in SVR4 since day one 3 years
ago.  How about inodes > 64K, how about the ability to compile code for
both SunOS and Unix?  Everyone is aware of the problems with the SCO compiler

>	-	Is is compatibility with net.code (particularly gnu and
>		fsf)?  This works fine with gcc (which compiles easily
>		once some minor changes are made in header files to take
>		care of the multiplicity of interpretations of __STDC__.
>		It is interesting that much of this code is heavily
>		weighted toward the Beserkley religion and seems to be
>		purposely non-portable on AT&T based systems.

It is amazing the about of code which references SCO about being non-standard
All of the gnu stuff runs just fine under SVR4 (as does it under SCO -- I 
would think).

>I work primarily with commercial clients who want a stable
>platform to run software critical to their business, and I'm very
>leery of ANY new software because it tends to be buggy and
>unstable and I cannot subject my client's business to the

I hardly consider SVR4 release 4.0 non-stable.  SVR4 is
field proven (Kmart, Walgreens, etc are running with SVR4 -- as
are many other sites which require a stable, robust, solid OS).
I also believe SCO is stable, but I don't agree with comments about
SVR4 not being stable.  See, you are compairing a vendors OS
(SCO) release 3.2 against a whole group of vendors who distribute
SVR4.  Compare vendor against vendor (SCO 3.2) against
vendor (Dell SVR4 release 4).  

-- 
Larry Snyder                                    internet: larry@gator.rn.com
keeper of the Gator                                  uucp: uunet!gator!larry
Xref: sparky biz.sco.general:3644 comp.unix.sysv386:15384 news.software.nn:1352
From: larryp@sco.COM (Larry Philps)
Newsgroups: biz.sco.general,comp.unix.sysv386,news.software.nn
Subject: Re: Problems with cnews+nn6.4.16 on SCO3.2.2
Keywords: problem cnews nn 6.4.16 sco 3.2 v2 news
Date: 8 Oct 92 13:11:56 GMT
Distribution: usa
Organization: SCO Canada, Inc.

In <2AD1883E.74E5@tct.com> chip@tct.com (Chip Salzenberg) writes:

> According to mike@sojurn.lns.pa.us (Mike J. Sangrey):
> > Yep,  fixed by getting rid of SCO's buggy libdir.a.

Its not buggy.  It does exactly the right thing if you are trying to
produce binaries for old Xenix systems. :-)  Unfortunately, this is not the
right thing for EAFS or NFS filesystems.

> I'll bet that nn is including <dirent.h> and linking with -lx, or else
> including <sys/ndir.h> and _not_ linking with -lx.
> 
> So what's the fix?
> 
> "Well, don't do that, then."

If you are producing a Unix binary and you absolutely need something
from the xenix library, modify your link line to read

	.... -lc -lx

This will resolve everything possible from the C library (and in this
case get the "right" directory routines) first, and then (and only
then) get the undefined things from the Xenix library.  Thus if there
are Unix equivalents of the Xenix routines in libx.a, they will be
picked up.  Libdir should not be used at all for Unix binaries.

However, you should not need either for compiling nn6.4.16.  That is
what I am using to respond to this message, and the only libraries
needed to compile my version were -lcurses -lsocket.

---
#include <std/disclaimer>

Larry Philps,	 SCO Canada, Inc.
Postman:  130 Bloor St. West, 10th floor, Toronto, Ontario.  M5S 1N5
InterNet: larryp@sco.COM
UUCP:	  {uunet,utcsri,sco}!scocan!larryp
Phone:	  (416) 922-1937
Newsgroups: biz.sco.general
From: hung@octel.com (Hung Le)
Subject: Help with sendmail on SCO machine
Organization: Octel Communications Inc., Milpitas Ca.
Date: Fri, 9 Oct 1992 00:04:56 GMT

 	I have a problem with the sendmail on my SCO machine. I tried
	to send mail from my SUN workstation (named 'zulu') to my
	SCO box (called 'cruz'). 

	From the zulu:

	mail -s "Test mail" hung@cruz < <message>

	Then on the cruz machine when I type mail I see the header:

	>1    N    zulu!hung Thu Oct  8 16:56:12 1992	14/434 Test mail

	It looks like the SCO box converts the domain name style to the
	route-based style. Hence when I respond to the message I have to
	change the header again. It looks like the sendmail.cf on the SCO
	needs to be modified somehow. Does anyone had the similer problem
	and found a fix for it. Please send me the suggestion or a sample
	of the sendmail.cf file that may work in my case. 

	The sendmail works fine between SUN machines. What should I look
	for?